Cold outreach that can't burn your domain.
Warmup and campaigns share one enforced daily send budget. WhatsApp, LinkedIn and call steps run in the same sequences, and an AI agent gets the same ceilings, not a bypass.
- Warmup free on every plan, forever
- No card, at any point
- Campaigns pause themselves past 5% bounce
It clears every gate, or it doesn't leave.
Limits you set in a settings screen are only as good as the moment you set them. Terlido applies them at send time, in the worker, after the campaign is already running, from the app or from an agent. There's no privileged send path, and no unguarded channel: the suppression that stops an email also stops a WhatsApp message and a dial.
One mailbox budget, shared
Warmup and campaigns draw on the same daily allowance. Two separate tools structurally cannot do that.
Sender auth that doesn't round up
Real DNS lookups for SPF, DKIM, DMARC and MX, with DKIM probed across every mainstream selector. “Unknown” stays unknown instead of rounding up to green.
Circuit breakers that name the cause
Bounce and spam rates re-checked hourly, per campaign. Cross a threshold and the campaign pauses itself, and writes down which one.
An unsubscribe you can't switch off
List-Unsubscribe headers go on every email unconditionally; the per-step toggle only controls the visible footer link. One click commits the suppression everywhere, or commits none of it.
Mailbox limits live in mailbox settings, campaign limits in the campaign's Options tab. Warmup volume is API or MCP only for now. The last two are fixed on purpose. They're the ones we won't let a bad afternoon switch off.
A send slot is claimed before the provider is called and refunded if the send doesn't happen, so a retry, or a second worker, can't spend the same budget twice.
The gates don't stop at email.
WhatsApp, LinkedIn and call steps run in the same sequences as email, and one do-not-contact list stands behind them: an address suppression blocks the email, a phone suppression blocks the WhatsApp message and the dial. Two channels send themselves. Two keep a human in the loop, on purpose, and the gates hold either way.
Automated through your own mailboxes: Gmail, Microsoft 365 or any SMTP. Warmup and campaigns share one enforced daily budget, and every send clears the gates above.
Automated through the official WhatsApp Business API, from your own verified business number. Opening messages are templates approved in advance, replies land in the unified inbox, and a STOP writes a suppression the send gate enforces.
Visit, invite, message and InMail steps queue as tasks with the note and link rendered for each lead. Work them from your own browser; completing one advances the sequence. Nothing automated touches your account.
Calls
Press dial on a call task and your own phone rings first; Terlido bridges you to the contact from your workspace's number. The do-not-contact check runs when you press dial and again as you pick up, so a STOP landing mid-ring still stops the call. Log the outcome and the sequence advances.
WhatsApp, LinkedIn and call steps sit on the Multichannel plan and up. Pricing has the details.
Warmup can't be withdrawn at renewal.
Warmup is free on every plan, from day one: every mailbox you connect on a paid plan or the trial, and one mailbox on Free, for as long as the account exists. There's no warmup add-on, no warmup seat and no per-mailbox warmup fee, so there's nothing to withdraw at renewal.
The pool is small. Warmup mail goes to other Terlido mailboxes with warmup switched on, and Terlido is new. Peer reply volume and spam-folder rescue are bounded by that. The ramp, the shared budget and the DNS checks aren't. They work on day one at n=1. Connect a spare mailbox and watch those three before you move anything real.
An AI agent can run it, behind caps and a kill switch.
Connect Claude, Cursor or any MCP client and it can build campaigns, read the inbox, send replies and pause what's failing. It signs in the way an app does, with no API key to paste and leak, and one workspace switch pauses every agent, enforced on the server rather than in the interface.
terlido.com/api/mcpPaste it into Claude under Settings, then Connectors. Sign in, approve the scopes. There's no API key to create. Agent access is included on every paid plan except Email Pro.
A send cap per grant
50 emails a day by default. Not a request rate limit. A ceiling on mail that reaches a human.
A kill switch that means it
One workspace switch pauses every agent, enforced at token verification rather than in the interface, so it stops a client mid-run rather than greying out a button.
Execution-scope fingerprinting
The campaign's revision and a hash of its live send scope are re-checked inside the same transaction that enrols the leads. If the copy, schedule, senders or audience changed after your agent showed it to you, the launch fails instead of sending.
No agent fast path
launch_campaign only flips a status; the worker still applies every send gate afterwards. An agent can't launch its way around your deliverability rules, and suppression and unsubscribes apply to agent replies exactly as they do to yours.
Retries that don't double-send
send_reply requires an operation id your client owns, so a dropped connection resolves the original send instead of emailing someone twice.
An audit row for every mutation
Anything an agent changes is written to an audit log you can read back, per grant and per workspace.
Where it stands, plainly: read and campaign-management paths over MCP run in production. Anything that puts mail on the wire through an agent grant is behind the same worker gates as everything else and is in production testing now. The caps, the kill switch and the fingerprint are what the code enforces today.
The gates get the headline. This is the rest of the platform.
All of it runs today, from the app, with no agent and no API involved.
Sequences that branch for real
Email, WhatsApp, LinkedIn and call steps in one tree, with wait days and yes/no branches on opened, clicked or replied. A/B variants at any step.
What you preview is what sends
Merge fields, fallbacks and seeded spintax resolved per lead. The preview leaves character for character.
A spam linter in the editor
Subject and body checked as you write: shouting caps, fake Re:, spam wording, link ratios. Inline, before you send.
AI that reads every reply
Each reply labelled interested, not, out of office or wrong person, with a confidence score. No opinion beats a guess.
One inbox, and a queue before it sends
Every mailbox, threaded and labelled. A reply stops the sequence; turn on Review and every email waits for a human.
Contacts, tracking and teams
CSV import with column mapping, tracking on a dedicated host, workspaces with roles, webhooks and HubSpot sync.
Connect a mailbox, and the checks run before anything sends.
Bring a list. Enrichment and verification run through your own provider integrations when you want them, but nothing here waits on them.
Connect a mailbox
Gmail or Microsoft 365 over OAuth, or any IMAP/SMTP. Credentials encrypted at rest, shared across your workspace.
Get the verdict
Terlido reads SPF, DKIM, DMARC and MX live and recommends a sending volume. Seconds, and it works at n=1.
Warm, or send, or both
Warmup begins the day you connect, at two sends a day, and it's free on every plan — one mailbox on Free, every mailbox on a paid plan. Import a list, build the sequence across email, WhatsApp, LinkedIn and call steps, launch. Every send goes through the gates.
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.comWhat Terlido doesn't do, so you don't find out on day three.
Terlido runs outreach and protects the accounts it runs from. Some channels send themselves and some keep a human in the loop, and the list below is where the edges are. Rule it out in thirty seconds instead of on day three.
Four plans. One button, and it's free.
Every new workspace gets 14 days at Multichannel limits, no card. Warmup isn't gated by any of it.
No expiry and no card. This isn't a trial with a timer.
No API or MCP access on this tier.
WhatsApp sends automatically. LinkedIn steps become prepared tasks, and calls bridge through your own number with you on the line.
Team invitations are a copy-a-link flow today.
Nothing to cancel. Card details aren't collected anywhere in Terlido today. When the 14 days end the workspace moves to Free automatically: campaigns stop, and warmup keeps running on one mailbox.
The awkward questions first.
You have no customers. Why would I connect a production mailbox?
That's the right question, and we don't have a social-proof answer for it. What we have is a page where every claim is a mechanism you can check inside the product. Start on a spare mailbox: read the DNS verdict, open the per-contact preview, call the MCP server. If any of it doesn't match what's written here, better you find out on a mailbox you don't care about.
How is this different from Lemlist, Smartlead or Instantly?
Two things. First, warmup and campaigns share one daily send budget per mailbox. Two separate tools structurally cannot do that, which is why a warmed mailbox on their stack quietly sends double what you planned. Second, they all speak MCP now too. The difference is what an agent is allowed to do once it's connected. Here your approval is bound to one version of a campaign: if the content, senders, schedule or audience changed after your agent showed it to you, the launch fails instead of going out. We're missing a lead database of our own, and we won't run robots on your LinkedIn account: those steps become prepared tasks here. If either of those is what you're shopping for, they're the better buy.
Do I have to stop using the tool I'm on now?
No, and you shouldn't for the first week. Connect one mailbox, get the DNS verdict, let warmup ramp, watch what the gates do. The one thing that only works when everything lives in one place is the shared per-mailbox budget (Terlido can't see what another tool sent this morning), so that part pays off only once you move a mailbox across.
Is letting an AI agent send cold email a bad idea?
It is, unless the thing it's driving refuses to be driven off a cliff. The part that matters most isn't the send cap. It's that your approval is tied to one specific version of a campaign. If the content, schedule, senders or audience changed after your agent showed it to you, the launch fails inside the same transaction that would have enrolled the leads. And launch_campaign only flips a status, so the worker still applies every send gate afterwards. There's no privileged agent path.
Can I use my existing mailboxes and domains?
Yes. Google Workspace, Microsoft 365, or any SMTP/IMAP provider. Terlido checks SPF, DKIM, DMARC and MX before the first send and tells you which are actually wrong rather than rounding an unknown up to a pass. Mailboxes belong to the workspace, so teammates can send from them without reconnecting.
What happens when the 14 days end?
The workspace moves to Free: one mailbox, 50 leads, and active campaigns stop. Warmup doesn't — it's free on every plan, and on Free it keeps running on one mailbox for as long as the account exists, so the reputation you spent a fortnight building isn't thrown away. The deliverability checks keep running too. Nothing is charged, because there's currently nothing to charge with: checkout isn't open. Your data stays where it is.
Connect a mailbox.
Your domain's score lands today.
It costs nothing and doesn't depend on anyone else being on the platform. Warmup runs free on every plan, forever.
Start free