Loading…
Email is the only channel with no platform to approve you and no single way in. That is why the connect screen asks a question first instead of a password: the right answer depends on whether you can change your mailbox's settings, and on whether you mind what address your replies come from.
Three ways are available today. Forwarding keeps the address your customers already write to — support@yourcompany.com — and asks your mail provider to send a copy to us. A Zynqly address gives you yourbrand@mail.zynqly.com with nothing to set up. IMAP signs in to your mailbox directly with its password, so mail is read where it already lands and no forwarding rule exists.
Sign in with Google and Sign in with Microsoft appear on the same screen marked Coming soon. They are not hidden, because the honest answer to "can I just use my Gmail" is "not by signing in yet — but forwarding or IMAP both work with it today".
Pick forwarding if you cannot or would rather not hand over a mailbox password, and you can add a forwarding rule. Pick a Zynqly address if you want to be answering mail in the next two minutes. Pick IMAP if you want replies to go out from your own server, with your own domain's reputation behind them.
Every provider makes you prove you own the destination before it will forward anywhere. Gmail, Outlook and Zoho all send a confirmation code to the new address the moment you add it — so the step that traps people is not the rule, it is that the code arrives in Zynqly rather than in their inbox, and they never look for it there.
The connect screen shows the address to forward to and, underneath, the exact clicks for your provider. Once the code has been confirmed the rule starts working immediately and nothing else changes: customers keep writing to the address they always used.
Keep "also keep a copy in the inbox" turned on while you are settling in. Nothing is lost that way, and you can turn it off once the shared inbox is where your team actually reads.
Choose your provider from the list — Zoho, Zoho India, GoDaddy, Hostinger, Titan, Gmail or Google Workspace, Yahoo, iCloud, Outlook or Microsoft 365, or Other for cPanel — and the servers, ports and security fill themselves in. You then give the mailbox address and its password.
The word that trips people is password. If the mailbox has two-factor authentication turned on, your ordinary password will be refused by the mail server, not by us: Gmail, Yahoo and iCloud all require an app password, generated in the provider's own security settings and used only here. The field says "mailbox or app password" for that reason.
The connection is checked before anything is saved, and the rules are deliberately narrow: the server name is resolved once and connected to on the address that was checked, every address must be a public one, only mail ports are allowed, and the session must upgrade to TLS or it is refused. A saved password is never re-sent to a host or username you have since changed — if you edit either, you type it again.
This is the part worth reading before you choose, because it is the part people notice afterwards.
Sending over your own SMTP server is offered only when we can actually reach one from where Zynqly runs. Many hosting providers block outbound mail ports by default — ours does — so the form probes for a working route and shows the SMTP option only if there is one. Where there is not, replies go out through Zynqly instead.
Going out through Zynqly on a domain you have not verified means the From line is a Zynqly address with your name on it, and Reply-To is your mailbox — so the conversation still comes back to you, and your customer's reply lands in the right thread. Verify your sending domain on the address's Sending domain tab and the From line becomes your own.
The last step sends a message and waits for it. For a forwarded address it is an ordinary mail to the address you gave; for IMAP it is a message sent through your SMTP and read back through your IMAP, which proves both halves in one go.
Mail from your own address to your own address is dropped rather than threaded — it would otherwise look like a customer writing in. If the test seems to vanish, that is usually why: you sent it from the mailbox you just connected.
After it passes, the address appears in the shared inbox beside every other channel, and the same automations, broadcasts and sequences work on it.
Only if you choose the IMAP method. Forwarding needs no password at all — you add a rule in your own mail settings — and a Zynqly address needs nothing. Where you do supply credentials they are encrypted at rest, used only to read and send for you, and deleted when you disconnect the channel.
Almost always because the mailbox has two-factor authentication on. Gmail, Yahoo and iCloud all require an app password for mail clients — generate one in your provider's security settings and use that instead. The refusal comes from your mail server, not from Zynqly.
Because sending through your own SMTP server was not available, so the reply went out through Zynqly on a domain you have not verified yet. Reply-To is still your mailbox, so the customer's answer reaches you normally. Verify your sending domain to send as your own address.
Yes. Forwarding can keep a copy in your original mailbox, and IMAP reads mail where it already is rather than moving it. Nothing is deleted from your mailbox by connecting it.