Example: Booking follow-through
Every form chased to paid, signed and booked.
Every new lead gets the payment link, the forms, a booking link and a reminder, and anyone who replies goes to you. If 40 people filled out your form last month and 10 paid, this goes after the other 30.
Chasing people to pay, sign and book. About 10 minutes each time, every time it comes up.
Handled for you, and nothing reaches a customer in words you have not approved.
What a diagnostic would check first
The diagnostic decides what gets built, or whether anything should. What follows is one way it could look.
- How many people filled out the form last month, and how many paid
- Where leads wait today, and who chases them
- Which steps need a person
One way it could look
Open the working exampleQuick look. The full example has every screen. Made-up guiding business and people. Nothing is sent or charged from this page.
How it would work
- Step 1
The form comes in
They get an email with your payment link and price. A text too, only if they ticked the box for texts.
- Step 2
Paid means paid
The intake form and waiver go out once Stripe reports the payment, never before. Reminders follow until both are signed.
- Step 3
Signed, then booked
Next comes your booking link. The calendar invite carries the address or the video link, and a reminder goes out the day before.
- Step 4
You step in where a person is needed
A reply, a failed payment, a refund or three reminders with no answer comes to you, and the reminders stop. If it turns a few more forms into paid clients each month, it has paid for itself.
Waits for your OK
- The price and the payment link. You set both in Stripe, and the build only sends the link you gave it.
- Refunds, price changes and exceptions. A person handles every one. The build never issues a refund or changes a price.
- The wording of every message. You approve it before it goes live. Until then, people are tracked and nothing is sent.
Konsul builds it. Kustos keeps it running and right.
Once it is live, Kustos checks it on a schedule and drafts a fix when something breaks. A person approves every change.
What could go wrong
Reminders that feel pushy.
The first reminder comes after a day, then one every three days, three at most per step. Nothing goes out between 9pm and 8am in your time zone. After the third, it stops and tells you.
Texting someone who never agreed to texts.
Texts go only to people who ticked the text box on your form. Everyone else gets email. Texting from a US business number also needs carrier registration, which can take two to three weeks, so it starts with email.
A payment that failed or was refunded.
A payment counts only when Stripe reports it. A failed payment or a refund stops the reminders and goes to you. Nothing retries a charge or issues a refund.
Someone replied with a question and still gets a nudge.
Any reply stops the reminders for that person and lands in your inbox. From there, you write to them.
Someone asks to stop.
An opt-out is final. They get nothing else from the build, by email or text.
Next step
Start with the process that costs you the most.
Rough numbers are fine. Describing it takes about three minutes.
Tell us what's breaking