Write to every new lead before your competitors do
The first business to answer usually wins the deal. Post a lead from your website form, Zapier, Make or the API, and the agent sends a personal first email within a minute, from your own inbox. When they reply, it qualifies them, handles objections and books the call, exactly like an inbound conversation.
A closer look at Speed-to-lead
One webhook URL per agent, for every form and automation
Each agent gets its own webhook URL. Point a website form, a Zapier zap, a Make scenario or an n8n flow at it: the email is required, and every other field (service, budget, company) becomes a variable the first email can use. Developers can call the REST API or the start_conversation MCP tool, and your team can start one by hand.
- Form posts or JSON, from any tool
- Extra fields become {{vars.<field>}}
- REST API and MCP start_conversation
- Start one by hand from the Outreach page
Sending hours, a daily limit, and nobody written to twice
Before each first email the agent checks it's a good time (your inbox's business hours, or daytime in its timezone), that the inbox is under its daily limit, and that the person isn't already in a conversation or written to recently. A lead that has to wait goes out at the next good moment; it's never dropped.
- Waits for business hours instead of emailing at 3am
- Daily limit per inbox protects deliverability
- Skips people already in a conversation
- Every lead's status, with why it waited or was skipped
A template you trust, or an opener written for each lead
Write the first email yourself with {{contact.first_name}}, {{vars.service}} and your business details filled in, or let the agent write each one in its character from a short brief and the first step of its flow. AI-written openers wait for your approval until you put the agent on autopilot. After sending, the conversation goes on the agent's follow-up sequence.
- Template with fallbacks: {{contact.first_name | there}}
- AI openers in the agent's own voice
- Approve, edit or skip AI openers
- Follow-up nudges until they reply
The details
Inboxes
Sent from the agent's Outlook / Microsoft 365 or IMAP (Gmail, Zoho, any provider) inbox, in the same thread the reply lands in.
Webhook
POST /api/hooks/start/… with email, name or first_name / last_name, and any other fields. Answers 202 with the queued lead.
API and MCP
POST /api/agents/:id/start, MCP start_conversation, get_first_touch, update_first_touch, approve_first_touch.
Events
first_touch.sent goes to your webhook endpoints, so your CRM knows the lead was contacted.
Notes
The agent gets a note that it wrote first and what the form said, so its reply makes sense.
Who it's for
Home services
A quote form at 9pm gets a personal email at 8am sharp, and the estimate visit is booked by lunch.
Agencies
Every client's lead forms go through Zapier to that client's agent, written in the client's voice.
B2B demo requests
Demo requests get a reply that references their company and use case, and a meeting on the calendar.
Speed-to-lead: common questions
Which inboxes can write first?
Email inboxes: Outlook / Microsoft 365 and any IMAP mailbox, Gmail included. The first email comes from your own address, so replies land back in the same conversation.
What if the lead already talked to us?
They're skipped. Nobody already in a conversation, or written to within the window you set (30 days by default), gets a second first email.
Can I check the AI's first emails before they go out?
Yes. AI-written openers wait on the Outreach page for you to send, edit or skip, unless the agent runs on autopilot. Your own template goes straight out.
Does it work with Zapier and Make?
Yes. Use the agent's webhook URL as the target of a Zapier, Make or n8n webhook step, or post your website form to it directly.
What happens if they don't reply?
The conversation goes on the follow-up sequence you pick, with fresh nudges inside business hours that stop the moment they reply.
Works hand in hand with
Reactivation campaigns
Upload a list of old leads and the agent writes to each one a few an hour, then books whoever replies.
ExploreApprovals & autonomy
Suggest, draft or auto autonomy, an Approvals queue, business hours and follow-up sequences.
ExploreWebhooks
Signed events for new messages, qualified leads, hand-offs and bookings, to Zapier, Make, n8n or your server.
ExplorePut it to work on your own inbox
Connect an inbox, describe the job, test it in a sandbox and go live with exactly the autonomy you're comfortable with.