For sales teams running on Microsoft 365, Outlook is the inbox that matters. Connect it to toflow.ai and outreach sequences go out from your actual Outlook address, with your domain, your sending history, and the inbox your prospects may already recognise.
No separate sending domain to set up. No warmup from scratch. Your existing Microsoft 365 account, now with sequence automation, tracking, and AI-driven follow-ups running through it.
How to connect Outlook to toflow.ai
Go to Account in your toflow.ai settings. Click Add Account, select Outlook, and authorise toflow.ai via Microsoft OAuth. toflow.ai requests only the permissions needed to send and read email on your behalf.
Once connected, Outlook appears as an available sending account when building sequences or sending individual emails from toflow.ai.
Multiple Outlook accounts can be connected. Teams with several senders or dedicated outreach inboxes can manage all of them from a single toflow.ai workspace.
What you can do with the Outlook integration
Many outreach tools send from a generic domain prospects have never seen. With toflow.ai sending through your Outlook address, outreach comes from the inbox your contacts already recognise. That matters for both deliverability and reply rates.
The AI follow-up agent monitors opens and replies from Outlook sequences and sends follow-up steps at the right time. If a prospect opened an email twice without replying, the agent picks that up and acts on it, without anyone having to notice manually.
The inbox manager agent reads replies coming in through Outlook and categorises them: interested, not interested, wrong person, out of office. For straightforward responses it can send an initial reply, flagging only the conversations that actually need attention.
Outlook handles the email steps. LinkedIn and WhatsApp handle the other touchpoints. All of it runs in the same outreach sequence, with engagement tracked across channels in one view.
Outlook vs Gmail for outreach
toflow.ai supports both Outlook and Gmail with identical functionality. Which one to use depends on what your team already runs on.
If your organisation is on Microsoft 365, Outlook is the natural starting point. Your sending domain, email history, and contacts are already there. If your team uses Google Workspace, Gmail works the same way. Both can be connected to the same workspace simultaneously, which is useful for agencies or teams split across email clients.
From a deliverability standpoint, both send through your established domain reputation. Neither has an inherent advantage, as long as your domain authentication (SPF, DKIM, DMARC) is set up correctly on whichever domain you send from.