Trigger
booking_complete
Timing
Immediately
Fires
email_sent · demo_confirmation
Confirms a meeting that already exists rather than asking for one. The only job left is getting the API reference out of them while intent is at its peak.
The form is the easy half. This is the other half.
Booking happens on the page, in one click, because every email you make somebody open is a place to lose them. Email is the safety net underneath that, not the path through it. Seven of them, and every one ends.
- 7
- Emails, one generator
- 1 click
- Submit to booked
- 0
- Emails after a no
- 4
- Paths, all of them end
The flow, node by node. Four paths, including the one where the form decides not to show a calendar at all. Pick a path, read it top to bottom, and click any email card to open the real thing. Every path here is also subject to the rules that cancel a send, which are shared with the other flow.
Trigger
booking_complete fires on the booking page
Email 01Day 0
Confirmation
Confirmed: Thursday 10:30 with Payload
Open the real emailTime delay
Until 24 hours before the call
Email 03Call minus 1
Reminder
Tomorrow at 10:30: what we will cover
Open the real emailTime delay
One business day after the call
Email 04Call plus 1
Estimate
Your integration estimate
Open the real emailTime delay
Fourteen days with no reply
Email 05Call plus 15
Close the file
Closing this out, unless you say otherwise
Open the real emailExit
Closes as closed_lost. Nothing else is ever sent.
The path most people take. Four emails across sixteen days, and only one of them asks for anything.
- Who lands here
- Anyone who picks a slot on the booking page and joins the call.
- The only ask
- Email 01 asks for an API reference or flow diagram. Nothing else in the path requests anything.
- Why fourteen days
- Long enough that silence means something, short enough that the estimate is still fresh.
Trigger
booking_complete fires, then the call is marked call_no_show
Email 01Day 0
Confirmation
Confirmed: Thursday 10:30 with Payload
Open the real emailTime delay
Until 24 hours before the call
Email 03Call minus 1
Reminder
Tomorrow at 10:30: what we will cover
Open the real emailTime delay
Within the hour of the missed call
Email 06Call day
Missed you
Missed you at 10:30
Open the real emailExit
Three days with no rebook closes it as no_show_lapsed.
The one most funnels forget. The recovery email fires inside the hour, because a same day rebook is the only kind that converts.
- Who lands here
- They booked, the calendar held the slot, and the call was marked a no show.
- Why within the hour
- Waiting until the next morning turns a missed call into a lost one.
- What never sends
- The estimate. There is nothing to estimate, and sending one would prove nobody was paying attention.
Trigger
generate_lead fires and booking_complete never does
Time delay
Twenty four hours after the form
Email 02Day 1
One nudge
Still want the thirty minutes?
Open the real emailExit
Closes as no_booking and moves to a quarterly list a person reviews. Not a third email.
One email, on purpose. Someone who reached the calendar and closed it does not need a second ask.
- Who lands here
- They completed the form, reached the calendar, and left without picking.
- Why only one email
- Email 02 says out loud that it is the only reminder. Breaking that promise is worse than losing the lead.
- Where the record goes
- A quarterly list a person reviews by hand. A human decision, not a third automated send.
Trigger
lead_routed returns review, so no calendar is ever shown
Time delay
Within one business day, once an engineer has read it
Email 07Day 1
Not yet, and why
No call yet, and what I would decide first
Open the real emailExit
Closes as too_early. Any reply re enters at the booking page, not at the form.
The path that never sees a calendar. One email, and it has to carry everything a call would have, or the gate is just a rejection with extra steps.
- Who lands here
- Pre-launch and still deciding, together. Either one alone still gets the calendar.
- What the email has to do
- Name the two decisions that come before a demo is useful, hand over sandbox credentials anyway, and offer to book manually once they answer. A gate that gives nothing back is just a no.
- And it is not one email
- The first decision is a different question per industry. Title companies get asked which side of the close they start on, legal gets asked whether trust funds touch their balance, platforms get asked who holds the funds. Five versions, same shell, because a generic "what to decide" email is worse than no email.
- Why only one
- They did not ask for a sequence and they are not ready for one. The email says it is the only one until they reply, and that is kept.
What never happens
- No re entry. Once a record closes, this flow cannot pick it up again.
- No win back campaign, no reactivation series, no "just checking in" six weeks later.
- No email after someone says no. One word ends it, on every path.
- No third automated email to anyone, ever. Two is the ceiling on path C, one on path D.
The seven emails, full size. Every one is triggered by something the person did or did not do, never by a calendar alone. Previews render with a sample recipient and sender instead of merge tokens, so they read the way they would land in an inbox.
Trigger
generate_lead, no booking_complete
Timing
+24 hours
Fires
email_sent · booking_nudge
Catches the person who reached the calendar and closed it. Step one of the form captured the use case before any typing, so this email knows what they wanted even though they never booked.
Trigger
Booking exists, call tomorrow
Timing
T minus 24 hours
Fires
email_sent · call_reminder
Cut the no-show rate and make the call better at the same time. The agenda is the same three steps the demo page sells.
Trigger
Call marked complete
Timing
+1 business day
Fires
email_sent · estimate_delivered
This is the promise the whole page rests on. If this email does not ship on time, the demo page is writing cheques the company does not cash.
Trigger
No activity 14 days after estimate
Timing
+14 days
Fires
email_sent · final_check
Force a decision instead of letting the deal rot in the pipeline. Naming 'you went another way' as an option is what makes people answer.
Trigger
call_no_show
Timing
Within the hour
Fires
email_sent · no_show_recovery
Path B only. The tone does all the work: no guilt, no suggestion they wasted anyone's time, and an explicit one word way to say no. A clean no is worth more than a guilty rebook that also does not happen.
Trigger
lead_review_queue
Timing
Within 1 business day
Fires
email_sent · too_early_reply
Path D only, and the hardest one to write. The form just declined to show them a calendar, so this email has to be worth more than the meeting they did not get. It names the two decisions that come first, hands over sandbox credentials anyway, and offers to book manually once they answer.
Same template, routed. The form asks two questions and both are a single click. They come straight off payload.com/solutions, so the answers map onto pages and content that already exist.
Step one, one click
What does your company do
The five options are Payload's own solutions nav: real estate, legal payments, insurance, professional services, software platform. Decides the tailored paragraph and the reading. Fires form_step_complete before a character is typed, so an abandon later still reports the industry.
Step two, one click
What are you building
Inbound, outbound, multi party, or still deciding. Decides which engineer takes the call and what the agenda leads with. Asking beats inferring from the email domain, which guesses wrong on every gmail.com and every holding company.
| Answer in step one | What it covers | What changes in the email |
|---|---|---|
| Real estate | Brokerage, title, mortgage, property mgmt | Earnest money and commission splits. Reading is the eXp Realty story and Payload Protect. |
| Legal payments | IOLTA, invoicing, co-counsel | Trust accounting decides the rail first. Reading is the legal payments page and Payload Protect. |
| Insurance | Premiums, commissions, claims | Premiums in and claims out on one integration. Reading is the insurance page and the Fifth Third announcement. |
| Professional services | CPA, consulting, engineering | Collections speed over cost. Reading is the professional services page and the sandbox quickstarts. |
| Software platform | Embedding payments in your product | Who holds the funds and month end reconciliation. Reading is the quickstarts and the Fifth Third announcement. |
Same email, same code path. Emails 03 and 07 branch, so the generator writes four variants of each. Emails 01, 02, 04, 05 and 06 are byte identical across every industry, so it writes none. Eight variant files rather than thirty five.
Path A compresses when the call is soon. A sequence built for a meeting nine days out is wrong for a meeting tomorrow. Only the booked path has this problem, so only the booked path has this rule.
| When the meeting sits | What sends | Why |
|---|---|---|
| Three days out or more | All four. Confirmation now, reminder at T-24h, estimate, close. |
Long enough for the booking to fall out of memory, so the reminder earns its place. |
| Under three days | Confirmation now, carrying the agenda. Reminder only if T-24h is still more than six hours away. |
Two emails inside 48 hours about the same meeting reads as nagging, not service. |
| Under 24 hours | Confirmation only. It is the reminder. | Sending a "tomorrow" email about a meeting three hours from now is how automation announces itself. |
Booking is also capped at five business days out, soonest first. No show rate climbs with lead time, so the cheapest way to improve attendance is to stop offering dates three weeks away.
Why it is built this way. Six decisions, and the reasoning behind each one. This is the part worth arguing about, because the copy can change and the structure cannot.
01
Booking happens on the page, not in an email
Every email you make somebody open is a place to lose them, and intent is highest in the seconds right after they submit. Moving the calendar onto the thank you page acts on that peak instead of posting a letter to it. Email then becomes the safety net underneath, which is a job it is good at.
02
The qualifier costs one click and comes first
Typing is the expensive part of a form, so the first screen asks for none. One click is close to the lowest activation energy a page can ask for, and once someone has answered anything, finishing feels less like a decision and more like following through. It also means an abandon at screen four still tells us who they were.
03
The exit is named out loud
Email 05 offers three answers and says the third one, no, happens by default. People reply when refusing is easy and costs them nothing. A message that only has room for yes usually gets silence, and silence is the one answer you cannot act on.
04
Proof lands after the commitment, not before
The Fifth Third quote sits in the confirmation email rather than on the landing page. The wobbliest moment is just after someone commits, not just before, so that is where reassurance is worth the space.
05
The calendar refuses dates that are too far out
The longer the gap between booking and the call, the more chances there are to forget it, double book it, or stop caring. So the picker caps at five business days and shows the soonest first. Saying that on the page turns a constraint into a reason to trust the person on the other end.
06
Every promise the page makes is one the flow can keep
The page says there is no drip, so there is no reactivation program, no win back, and two automated emails is the ceiling. A promise that is quietly broken later is worse than never making it, and the only way to keep this one is to build nothing that could break it.