Speed to lead, half built
Capture and routing are live and fast. The actions that respond without a person are on the roadmap, and this page keeps the two apart.
- Capture works today
- Auto actions on the roadmap
- Source recorded on every lead
The short answer
- Working now: a form or a booking reaches your instance in seconds, creates or matches a contact, records the source and puts an owned task in front of a person.
- Planned: an automatic acknowledgement by SMS, an AI callback, round-robin assignment across a pool and an escalation timer when nobody has touched a lead.
- Not a feature at all: someone willing to answer. Speed to lead is an operating decision that software supports and cannot supply.
What it does and what it will do
Today the fast part is capture. A website form posts to your instance's inbound endpoint and a Calendly booking arrives by webhook, both in seconds, both landing as a contact and a lead with its source. task_create puts the callback on a named person's list with a due time. Spam submissions are throttled so an overnight bot does not fill the queue.
What is planned is the half that acts without waiting for a person. An acknowledgement text within seconds of a form submission, an AI callback for the leads worth calling immediately, round-robin assignment so a lead has an owner rather than an audience, and an escalation when a lead has sat untouched past your threshold.
Those planned actions will be defined as speed-to-lead action types you configure, and each will respect the same policy table as everything else. An automatic text is an external send, and external sends start in review until you deliberately move them.
What is planned, and why
An acknowledgement buys minutes
A text within seconds does not qualify anyone. It stops the buyer opening the next tab, which is the entire mechanism.
Read moreA lead needs one owner
Round-robin assignment means the lead belongs to a person rather than to a queue everybody assumes somebody else is watching.
Read moreAn untouched lead escalates
A timer that surfaces the leads nobody picked up, because those are the ones that quietly cost the most.
Read moreHow you get there
The first two steps are available today.
- 1
Connect
Point your website form at the inbound endpoint and connect the booking webhook. Test both with a real submission rather than a sample payload.
- 2
Configure
Lead source on every lead, the task owner and the due time, and the spam throttle. This is the part that makes everything later measurable.
- 3
Run in review
When the automatic actions ship, they start in review. An acknowledgement message a person approves is still faster than an acknowledgement nobody sends.
- 4
Move to auto
For the acknowledgement only, after you have read a week of them. Anything that spends money stays human-only in every mode.
In which tier
Speed-to-lead actions are part of the Local pack.
| Tier | Price | Speed to lead status |
|---|---|---|
| Core | $299/mo | Capture, contact matching, lead source and tasks. Live today |
| Local | $499/mo | Automatic replies, AI callback, round-robin and escalation. On the roadmap |
| Outbound | $699/mo | The pack when it ships, plus Campaign and LinkedIn agents |
| Agency | $1,200/mo | Everything above, plus marketplaces and the marketing module |
Published tiers as of September 2026, unlimited seats on every one.
Questions
- Can it text a new lead in sixty seconds?
- No. There is no SMS channel today. If an automatic text within a minute is the requirement, this is not the product for it this month.
- What is fast today?
- Capture and routing. The lead exists in your database with its source and an owned task within seconds, which is more than a shared inbox gives you.
- Does it assign leads round-robin?
- Not yet. Tasks get an owner you configure; a rota across a pool is on the roadmap.
- What about texting consent?
- When SMS ships, consent records and STOP handling are part of the planned feature. The consent itself is yours to collect, and this is not legal advice.
- What should I set up now?
- Lead source on every lead. It is dull, nothing breaks without it, and it is what makes cost per lead by channel a query later.
Get capture and source right first
Everything the roadmap adds depends on the lead existing with its source attached.