An AI SDR, from first domain to first meeting.
Raechly sets up and warms your senders, writes each email for each contact, sends inside your limits and drafts the answers when people reply. Every step is also open to your AI assistant. Here is the whole thing, in order.
Setup, step by step
- 01
Tell Raechly what you sell
Add each product with who buys it, the problem it solves, its price and your proof. Every email is written from this, so it reads like your company and quotes your pricing rather than inventing it.
upsert_offering → - 02
Pick your sending domain
Raechly suggests domains that look like yours and checks which are free. Pick one and name three senders. Raechly buys it, publishes the DNS records, turns on reply capture and starts warming. You never touch DNS, and your main domain never sends cold email.
order_senders → - 03
Warmup that proves itself
Senders ramp on real inboxes, and a warmup message only counts when its reply comes back. A sender whose replies don’t reach Raechly does not send at all. Each one shows the day it reaches full volume.
warmup_stats → - 04
Contacts and the sequence
Pick a list, a tag or a CSV, or describe who you want to reach: Raechly shows a count and five anonymous examples, then finds them once you confirm. It writes the steps from your product, and on autopilot each email for each contact. Nothing sends until you have read the real emails and approved them. Suppressed addresses are never brought back by a re-import.
create_campaign → - 05
Launch, even before the senders are ready
A campaign launched early waits and starts by itself once a sender can send. From then an hourly pass sends inside each contact’s window, under four layers of caps, and logs every failure with the verbatim error.
set_campaign_status → - 06
Answer the replies
A reply stops that person’s sequence and lands in one inbox, threaded with what you sent. Interested replies and questions come with an answer the AI wrote for you to edit and send, and an interested reply opens a deal. A summary of the day arrives each morning.
suggest_reply_answer →
The four decisions underneath it
Agent-native
Run outbound from your AI assistant
All 147 tools are exposed over the Model Context Protocol. Connect Claude, Claude Code or Cursor once and drive the entire product in plain language: order your sending domain, import contacts, draft sequences, answer replies, move deals, read the send log.
Senders that are yours alone
A domain bought for you, never shared
Every plan includes a sending domain that looks like yours, with three senders on it. Raechly buys it, publishes the DNS records, turns on reply capture and warms the senders. The domain belongs to one customer. It is never shared, and never handed to someone else when a customer leaves, so another company’s list can’t burn it.
Verified warmup
Warmup that proves replies actually landed
Most warmup can’t be checked: you are told threads happened. Raechly provisions an inbound routing rule per mailbox and refuses to send until replies are demonstrably being captured. A mailbox with no verified inbound path does not send.
Reads like one person
Cold email that reads like a person wrote it
By default a cold email from Raechly carries no tracking pixel and no List-Unsubscribe header, the two marks of bulk mail. It still ends with your company name and postal address, plus a plain line: “Reply ‘stop’ and I won’t email again.” A reply asking to stop is caught, and that address is never emailed again from your account.
What it refuses to do
Read these as product features, because that is what they are. Full reasoning in the four caps that keep a sending domain alive.
Timezone-aware send windows
Per campaign: IANA timezone, allowed weekdays, start and end hour. A lead in Berlin is not emailed at 3am because your server is in Virginia.
Four layers of daily caps
Per mailbox, per domain, per campaign, plus a provider ceiling (Gmail 500 a day, Outlook 300) and a per-plan ceiling for the whole organization. Volume is the fastest way to burn a domain, so the floors are low by default and warmup raises them slowly.
Suppression that holds
Unsubscribed and bounced leads are never resurrected by a re-import. Bulk imports upsert by email and skip anyone already suppressed.
Single-flight pipeline
The send pipeline takes a lock. A manual trigger during the hourly run returns busy instead of double-sending your sequence.
Product questions
What do I need before I start?
A plan and a few minutes to describe what you sell. Raechly buys and sets up the sending domain, so you need no AWS account and no DNS access. On Business you can also bring your own domains and connect your own inboxes.
How long until I can send real campaign mail?
Warmup is the honest constraint. New senders start at a few emails a day and climb for several weeks, and each one shows the day it reaches full volume. You can launch before then: the campaign starts as soon as a sender can send, slowly at first. Anyone promising full volume on day one from a fresh domain is selling you a reputation problem.
Does the dashboard do everything the MCP server does?
Both surfaces hit the same API. The dashboard covers campaigns, contacts, senders, the inbox, deals and settings. The MCP server exposes all 147 tools, which is the fuller surface, and it is the faster path for setup and debugging.
What happens when a lead replies?
The reply stops that person’s sequence and lands in your Raechly inbox, threaded with what you sent. Raechly reads it, sorts it (interested, not now, objection) and, for the ones worth answering, writes an answer you can edit and send in the same thread. Nothing goes out without you.
Can I use AI to write the campaigns?
Yes. Campaign generation is built in, and because the whole product is exposed over MCP, your assistant can read your leads and draft the sequence against them rather than producing generic copy.
Point your assistant at it and see.
Connect the MCP server, tell it what you sell and pick your sending domain. You will know inside an hour whether this is the setup you want.