Features
Notifications & Automations
Confirmations and reminders go out on their own once you publish an event. Pro adds webhooks, so the rest of your stack finds out the moment a lead qualifies, rejects, routes, or books, without anyone checking a dashboard.
On every plan
Runs the moment you publish
Emails
Templates
- Booking Confirmation
- Meeting Reminder (1 day)
- Meeting Reminder (1 hour)
- Qualification Summary
- Meeting Follow-up
- Booking Cancellation
Meeting confirmed for {{meeting_date}} at {{meeting_time}}
Booking confirmation
Sent to the prospect automatically the moment they book.
24-hour reminder
Sent before the meeting so it doesn't rely on anyone remembering.
1-hour reminder
Sent about an hour before the meeting, when it was booked at least two hours ahead.
Qualification summary
Sent to you after each submission: the answers and the decision, without opening the dashboard.
Pro
Connect your own stack
Custom email templates
Edit the subject and body of your emails to match your own voice, on every event.
Webhooks
Send a POST request to your own endpoint the moment something happens, no dashboard required.
Webhook test
Send a sample payload to your endpoint before anything real depends on it.
Delivery logs
A history of every attempt. A failed delivery's request and response are kept 30 days to help you debug; a successful one is never stored.
Delivery Logs
| Event | Status |
|---|---|
| lead.qualified | 200 |
| lead.routed | 200 |
| booking.created | 200 |
Every event, one endpoint
Point a webhook at your own URL and choose which of these fire it.
| Event | Fires when |
|---|---|
| submission.completed | A prospect finished the funnel, whatever the decision. The payload carries their name, email, phone, every answer, and their score: the richest of all the events, send it only to an endpoint you trust. |
| lead.qualified | A prospect was qualified: no rule turned them away, routed them or flagged them for review, or you marked the lead as qualified yourself. Carries their name, email, and score. |
| lead.rejected | A rejection rule matched. Carries their name, email, and score. |
| lead.routed | A routing rule matched. Carries their name, email, and score; see the note below on what routing needs to do anything. |
| lead.review_required | A rule flagged the prospect for your review. They can still book, and the lead waits for you in Leads. Carries their name, email, and score. |
| booking.created | A qualified prospect booked a time slot. Carries their name, email, and the meeting details. |
| booking.cancelled | A booking was cancelled. Carries their name, email, and the cancellation reason if one was given. |
| booking.completed | You marked the meeting as held, once the few seconds to undo it have passed. Carries their name, email, the meeting details, and the outcome. |
| booking.no_show | You marked the prospect as a no-show, once the few seconds to undo it have passed. Carries the same fields as booking.completed. |
Every payload has prospect_name and prospect_email fields, which are empty when the
prospect did not give them. submission.completed also carries the answers, the score and the
phone number. booking.created, booking.completed and booking.no_show carry the meeting time and link. Treat your endpoint
accordingly. lead.routed fires when a routing
rule matches. A routing rule sends a lead to a named teammate, so it needs a second
member in the workspace, which the Team plan provides.
Works great with