Integrations

To send emails directly from Anansio, you need to connect an email sending service in the Integrations tab.

Connect any standard email provider (Google Workspace, Microsoft 365, Zoho, etc.) using SMTP.

• Where to add it: Go to Account → SMTP configs, click Add config, and enter your provider's details.
• Host & Port: Check with your email provider for SMTP settings (usually port 587 or 465).
• Username & Password: Use App Passwords if your provider enforces Two-Factor Authentication.
• Test before you send: Click Test on the connection to verify it. A connection must pass verification before it can be used for outreach.
• Activate it: Once verified, open Outreach → Sending Methods, find the Custom SMTP card, and click Set as default to route campaigns through it.

If your account has AWS SES enabled, you can connect your domain natively. This allows for high-volume, reliable sending with automatic DKIM tracking.

Once you connect a sending domain, the Deliverability card on the Outreach home shows live authentication status for it: SPF, DKIM, DMARC, and whether the domain is on any public blocklist. Each failing check shows the exact DNS record(s) to add (host, type, and value) with one-click copy, so you can paste them straight into your registrar. Click Recheck after you update DNS. Getting SPF, DKIM, and DMARC all passing, and staying off blocklists, is the single biggest thing you can do to land in the inbox.

When you set up your own domain, Anansio looks up where your DNS is hosted and tailors the instructions to that panel. Most panels (including Cloudflare, GoDaddy and Namecheap) add your domain to whatever you type in the Name field, so we show the short name to paste rather than the full hostname. Pasting the full hostname into those panels quietly creates something like host.yourdomain.com.yourdomain.com, which never resolves and leaves the setup screen stuck on red. On Cloudflare there is one more step: set these records to DNS only (the grey cloud). A proxied record answers with Cloudflare's own address, so DKIM can never verify.

New accounts are enrolled in the Anansio Global Pool automatically at signup, so outreach works out of the box: your first campaign can send without any DNS, SMTP, or Gmail setup. You can switch to your own domain or mailbox at any time from the options below, and everything here still applies when you do.

When onboarding starts, Anansio now first shows a popup asking whether you want the fast-start Global Pool path or the full list of other setup options. If you are not sure, Global Pool is the simplest way to start.

If you open onboarding while creating a campaign and your workspace already has an active sender, that popup asks whether you want to keep using the active sender for this campaign or open the other setup options first.

If you opened onboarding while creating a campaign, finishing setup now brings you back to that campaign flow automatically.

If your workspace is already active and you open onboarding directly later, Anansio now sends you straight back to Outreach instead of leaving you on a separate active-status page.

1. Connect the sending provider.
2. Confirm authentication and any app-password requirements.
3. Start with conservative daily sending limits.
4. Increase volume only after deliverability stays healthy.

To protect your sender reputation, we recommend configuring daily limits in your integration settings. If you have connected a new domain, start with a low daily limit (e.g., 20-50 emails) and slowly increase it over a few weeks.

When Anansio manages your sending, this ramp is automatic. New accounts start at 200 emails per day and step up over the first few weeks as your reputation builds, rising toward 1,000 per day by about week four. The limit that actually applies is the lower of this ramp and your account's own daily cap. If a campaign reaches the cap for the day, it pauses and resumes on its own at midnight UTC, so you never need to restart it.

If your bounce or complaint rate climbs too high while a campaign is sending, Anansio pauses that campaign for a short cooldown to protect your sender reputation, then resumes it on its own. The campaign page shows a banner with how long is left. Once the rate recovers, you can also choose Resume sending now on the banner instead of waiting out the cooldown. If your bounce rate is still high, we tell you the current number and ask you to confirm, because resuming into a bad rate can keep bouncing and damage your domain. A pause caused by shared sending infrastructure rather than your own list clears automatically and has no resume button.