The missed-call callback flow (1-minute callback, 5-minute text)

This is the core leak-plug. When a call to your school goes unanswered, the system doesn't just log it — it acts, on a clock. Here's the timeline we configure for you.

1. 1

   Minute 0 — the call rings out

   A prospect calls while everyone's flying. Your phone rings, nobody picks up — exactly the moment schools lose students to the next school on the list.

2. 2

   Within ~1 minute — the Receptionist calls back

   The system calls the prospect back directly. To the caller it feels like the school returning their missed call almost immediately — because that's what it is. If they pick up, it's a normal Receptionist conversation: questions answered, discovery flight offered, booking made.

3. 3

   Minute 5 — the follow-up text

   If the callback wasn't answered (or to reinforce one that was), a text goes out: sorry we missed you, can we help, want to book a discovery flight? Texts get read. A surprising share of 'lost' callers reply to this message and convert in the thread.

4. 4

   You get notified either way

   Booked, messaged, or just called — you get a summary, and the full thread (recording, transcript, texts) is in Conversations. If the caller asked something the Receptionist didn't know, the summary flags it as needing your callback.

5. 5

   Everything lands in the pipeline

   The caller is in Contacts, with an open opportunity if they showed buying intent. Next time they call, the Receptionist already knows who they are and picks up the conversation where it left off.

6. 6

   Watch or adjust the timing

   The 1-minute / 5-minute timings live in Automation → Workflows (the missed-call flow we built for you). You can look, but call us before editing — and if you want different timings (say, 2 minutes and 10), that's a two-minute change on our side.

The math behind it: a prospect comparing three schools books with the first one that responds like a human. This flow makes that you, even at 9 PM on a Sunday.