01segment, write, send
Campaigns to the contacts you own
Send to the people already on your list, cut by stage, source, or any field on the record. One campaign, every segment getting the version written for it.
§ EMAIL · SEQUENCES THAT KNOW WHEN TO STOP
It stops when
they reply.
Campaigns and multi-step sequences to the contacts you already own, written per segment and sent on a schedule. The moment somebody replies, the sequence stops and the agent takes the conversation.
Free to join · no card · beta invites go to this list first
- sequences per segment
- multi-stepsequences per segment
- auto stop
- on replyauto stop
- inbox for the answers
- 1inbox for the answers
Email · sequence 5 stepslive
01Opening noteSENT
02The case studySENT
03Short nudgeCANCELLED
04Last callCANCELLED
Reply detectedevery queued step cancelled
Sequence stoppedCAMPAIGN QUEUED · 3,600 CONTACTSSTEP 2 OF 5 · SENT 9:02AMREPLY DETECTED · SEQUENCE STOPPEDAGENT DRAFTED THE ANSWER · SENTMEETING BOOKED FROM THREADUNSUBSCRIBE HONORED · SUPPRESSEDCAMPAIGN QUEUED · 3,600 CONTACTSSTEP 2 OF 5 · SENT 9:02AMREPLY DETECTED · SEQUENCE STOPPEDAGENT DRAFTED THE ANSWER · SENTMEETING BOOKED FROM THREADUNSUBSCRIBE HONORED · SUPPRESSED
§ 02 / what it does
The job, done properly.
Email campaigns and sequences that stop on a reply and hand you the conversation.
02multi-step, timed, conditional
Sequences with a spine
Five steps or fifteen, spaced how you want, each step branching on what the last one did. Opens, clicks, and silence all route to different next moves.
03no 'just bumping this'
Reply detection that actually stops the drip
The second a human replies, every queued step for that contact is cancelled across every channel. Nobody ever gets a follow-up nudge after they already answered.
04drafted, sent, or handed over
The agent answers the reply
It reads the reply, answers the question, and books the meeting if that is what the reply was asking for. Anything it should not handle alone goes to your inbox with the context attached.
05auth · warm-up · pacing
Deliverability treated as the product
Domain authentication, sending warm-up, and volume pacing are set up as part of onboarding, because the best sequence in the world is worth nothing from the spam folder.
06voice · sms · email · crm
Email is one wire of the same engine
The email fires because the call and the text did not land. The stage moves because the email got a reply. One agent, one memory, one pipeline.
§ 03 / the mvp, no hand-waving
What you get on day one.
No roadmap theatre. This is what is in the first beta build, and what lands right after it.
In the beta
- Bulk campaigns to the contacts you upload
- Multi-step sequences with conditional steps
- Reply detection that stops every queued step
- Agent-drafted replies with human handoff
- Domain authentication and sending warm-up
- Open, click, reply, and bounce tracking
- One-click unsubscribe honored across channels
Right after
- Inbox rotation across multiple domains
- Template library with per-segment variants
- Deliverability scoring per domain
Beta testers pick what jumps the queue. That is most of the point of being on the list.
§ 04 / save your spot
Get in before the doors.
We are opening DialEcho in waves. The list decides who is in each one, and everybody on it gets beta access before the site sells a single seat.
- Free to join, no card, one email when your wave opens
- Beta testers get set up with a human, not a help doc
- You tell us what to build next while it is still cheap to change
SPF, DKIM, and DMARC set up with you at onboardingOne-click unsubscribe on every sendSuppression is permanent and applies across all channelsFull export of every contact and message you own
§ 05 / the obvious questions
Before you ask.
The contacts you already own and have permission to email. You bring the list, DialEcho works it.
A reply, a booking, an unsubscribe, or a stage change. Any of them cancels every queued step for that contact, on every channel.
It drafts them per segment and you approve the ones you want. You can also write every word yourself and just use the sending, timing, and reply logic.
Domain authentication and a warm-up ramp at onboarding, then volume pacing while you send. It is set up with you, not left as a checkbox.
Yes, and you should. Sending as you is the whole point.
Five lists, one engine
Pick your wire.
Each one is a different job the same agent does. Join as many lists as you want - it is one signup per list and it moves you up all of them.