The consultation she forgot
An estate planning firm is hiring someone to get booked consultations to show up and to chase the leads who never booked. Here is how a booked hour goes empty, what went wrong for others who automated the follow-up, and a build that holds up.
How to use this page
Read the story, then the map. If no one in your business holds the middle square, start there, not with the build. If someone does, read what went wrong for others, then copy the build kit into your AI agent.
On 29 September 2026 an estate planning and elder law firm with three offices posted for a sales development representative. The lines that carry the job: “Driving consultation attendance through proactive communication and follow-up”, “Re-engaging dormant leads who previously expressed interest but did not schedule or move forward”, and “using a consistent, multi-touch follow-up cadence.” Pay: $22 to $24 an hour, with a bonus “tied to consultation scheduling and attendance metrics.” The pipeline runs in HubSpot.
Here is how it goes today. On Tuesday evening a daughter fills in the website form: her father had a fall, and she wants to ask about long-term care and his house. The next morning the intake rep calls and gets voicemail, then sends the standard email. On Thursday the daughter calls back on her lunch break, and the rep qualifies her, runs the conflict check and books a consultation a week out.
The day before, the rep means to call the five consultations on tomorrow's calendar. The phone has not stopped. Three get a call. Hers does not.
At 10:00 on the day, her father's doctor has taken the same hour, and she has forgotten. The team member waits in the meeting room. At 10:15 the hour is written off, and her record goes to inactive. About $450 of expected fee, on one guide's numbers, went with it.
Nobody here is careless. The inquiry was answered the next morning, the booking was made on the first call, and the confirmation call was on the rep's list. Every one of those steps waits on a person who is also on the phone, so the reminder is the step that gets dropped, and the consultation booked furthest out is the one that goes quiet. Automate the chasing without a person reading the replies and you get the other failure: the message that keeps coming after someone said stop.
The daughter, the five consultations and the days are an example built from the posting, which gives no counts. The 30 bookings, the 7 no-shows a month and the $450 are estimates from published ranges.
The map: the same job as a system
The judgment it all runs on sits in the middle square, held by a person. Around it, the work in the order it moves, each square run by the machine or by a person. Along the bottom, what it runs on.
The middle is who is ready for a consultation: whether the inquiry fits, clears the conflict check and is ready to act, and when to stop chasing someone. The intake rep holds it.
The same job as a system. The middle is who is ready for a consultation, held by the intake rep. The inquiry comes in on the left and is answered within a minute; across the top the rep qualifies and books, the machine reminds before the consultation and chases the leads who went quiet; on the right every touch is logged and the morning list is built. Along the bottom is what it runs on: the switch and the alert, the counts, and the templates, the consent list and the cadence.
- Runs on its own
- A person does it
- The judgment it all depends on
- What it runs on
Who holds the middle square
The intake rep. Who is ready for a consultation: whether the inquiry fits the firm, clears the conflict check and is ready to act, and when to stop chasing someone who has gone quiet.
Before you build, these must already be true in your business:
- Every inquiry lands in one place, the CRM, with its number, email and source, and the record says whether the person agreed to texts.
- The firm has written the words for every touch once, and a person reads every reply.
- One person owns the qualifying call and the conflict check before any consultation is booked.
Still deciding whether to do this, or no one holds this judgment yet? See the verdict: what it costs today, what to hand over, the bill and the owner
What went wrong for others, and the rules it gives the build
Five things that went wrong for people who did this job, or that tripped them up, and the rule each one gives the build.
“I hardly ever confirm because I believe the appointment should not rest on my confirmation unless I've been told otherwise”, in reply to an attorney who cancels appointments nobody confirmed.
Attorneys on a lawyers' forum, August 2026. Read it
The rule: Never cancel or move an appointment; a missing confirmation goes on the rep's morning list, and a person calls.
A paralegal “wasting like 2 hours a day just dialing numbers that go straight to full mailboxes”; the fix that worked for others: “people answer at way higher rates when they're expecting the call vs getting a random number.”
A law firm owner and the replies, April 2026. Read it
The rule: The first reply names the time the rep will call and the number it will come from, or offers a link to pick a time; the machine never dials.
Ringless voicemails to mobile numbers are calls under federal law and need prior express consent, the FCC ruled in 2022; the same forum thread's owner had wired one in.
The FCC's ruling, as reported by a law firm, November 2022. Read it
The rule: No voicemail drops and no automated calls, ever; the machine texts and emails only, and only people who gave the firm their number.
A stop word in reply to a text revokes consent for every channel from that sender and must be honoured within ten business days.
The FCC's 2025 rule, as reported by a law firm. Read it
The rule: Any stop word, in any words, stops every channel within the hour, and the count of messages sent after a stop is zero.
A booked meeting takes a contact out of a sequence only when the person who booked it is the same user who enrolled the contact.
The CRM maker's own help page. Read it
The rule: Read the booking from the firm's calendar, not from the sequence's own switch, and stop every touch the moment anyone books, whoever booked it.
What it costs to run
About $0.50 with the reminder tool (from $30 a month over about 60 inquiries, with the HubSpot already paid for); about $1.50 more if the firm must move to Sales Hub Professional for sequences ($90 a seat over 60); about $0.45 built ($28 over 60), then the build and the upkeep. The rep's time: not known until the baseline week counts it.
Estimate. The 60 inquiries, 30 bookings and 300 texts a month are assumed. The baseline weeks replace all three.
The build kit
One prompt to paste into Claude, ChatGPT or any AI agent that can build. It checks the middle square before anything else, builds the map square by square, carries the 5 rules above, and has the whole build: what starts it, every step, the data, the review, the alerts, what to do when it breaks, and what to count before you switch it on.
Before you build
- It may never, on its own: cancel or move an appointment; call anyone or leave a voicemail; compose a reply to a question; message anyone whose number and consent are not on file, or anyone after a stop word; or say anything about fees, Medicaid, or the law.
- Keep with a person: the call that qualifies, and the conflict check before any consultation is booked; every reply that carries a question or a story; the decision to stop chasing someone; whether to cancel an appointment nobody confirmed (a person calls first; the machine never cancels); and anything about fees, Medicaid, or what the law says.
- Not yet: phone calls or voicemails of any kind on its own (a ringless voicemail needs consent under federal rules); composing a reply to a question; texting anyone who did not give the firm their number and agree to texts; and any message after a stop word, on any channel.
Help me build this in my business: Answering every inbound inquiry fast, qualifying it and booking the consultation, getting the people who booked to show up, and re-engaging the leads who asked and never booked. Before you build anything: this runs on one person's judgment, "Who is ready for a consultation", held by the intake rep. Ask me whether each of these is true in my business, one at a time: 1. Every inquiry lands in one place, the CRM, with its number, email and source, and the record says whether the person agreed to texts. 2. The firm has written the words for every touch once, and a person reads every reply. 3. One person owns the qualifying call and the conflict check before any consultation is booked. If any is not true, stop and tell me which, and what I need in place first. Do not build around it. Rules from others who built this and got it wrong. Keep every one: - Never cancel or move an appointment; a missing confirmation goes on the rep's morning list, and a person calls. - The first reply names the time the rep will call and the number it will come from, or offers a link to pick a time; the machine never dials. - No voicemail drops and no automated calls, ever; the machine texts and emails only, and only people who gave the firm their number. - Any stop word, in any words, stops every channel within the hour, and the count of messages sent after a stop is zero. - Read the booking from the firm's calendar, not from the sequence's own switch, and stop every touch the moment anyone books, whoever booked it. The map of this system, a 3x3: - The middle square, the judgment it all runs on: Who is ready for a consultation (Held by the intake rep). It stays with a person. - The work, in the order it moves: 1. Answer the inquiry (runs on its own: Within a minute, with a promised call time); 2. Qualify and book (a person does it: The rep: the call, the conflict check); 3. Remind before the consult (runs on its own: Four touches, moved with the appointment); 4. Chase the quiet ones (runs on its own: Eight touches over six weeks, stops at a reply); 5. Log and list (runs on its own: Every touch on the record, the morning list). - Along the bottom, what it runs on: Automation (The sequence switch and the stop-word alert); Measure (Minutes to first reply, show rate, stops, apologies); Build (The templates, the consent list, the cadence). Build the squares in that order, and keep the person's squares with a person. The working set to build from: - Trigger: a new inquiry lands in HubSpot (the website form, a logged call, a webinar sign-up, an information request); a consultation is booked, moved or cancelled on the firm's calendar; and a daily run at 8:00 for the dormant list. - Steps: on a new inquiry, read the name, number, email and source; check the consent flag; text and email the first reply from the firm's templates, with the rep's next call slot or a link to pick one; create the call task for the rep. On a booking, send the confirmation at once; schedule the prep email for two days before, the confirm-or-reschedule text for the day before at 10:00, and the address text for two hours before; on a move, cancel the pending touches and schedule them again from the new time; on a confirm reply, mark confirmed; on any other reply, stop the touches and put the reply on the rep's screen. Daily at 8:00: every lead with no booking and no reply, from day 2 to week 6, gets the next touch on the cadence (day 2 text, day 4 email, day 7 text, day 12 email, day 20 text, day 30 email, day 42 email, then closed as dormant and listed); webinar attendees enter the same cadence the morning after the event; any reply, booking or stop word ends the cadence. Every event is written to the HubSpot record as it happens, and the morning list is built at 8:15. - Data: one record per inquiry: source, received at, consent on file (yes or no), minutes to first reply, call slot promised, rep's call made (yes or no, when), qualified (yes, no, reason), conflict check cleared, consultation booked (when, for when, days out), each touch (channel, time, template), each reply (time, text, handled by), reschedules, confirmed, showed (yes or no), signed, stop requested (when, how), closed by (person or cadence, reason). - Review step: the intake rep reads the morning list every day and clears every reply the same morning. The chief operating officer reads the Friday counts. - Alerts: an inquiry with no first reply after one minute; a reply from a prospect with no person's answer after 30 minutes in business hours; any message sent after a stop word (zero is the only acceptable count); a consultation inside 24 hours with no day-before text sent; a touch scheduled for a time the appointment no longer holds; the connection to HubSpot, the calendar or the texting number down; a lead past eight touches; and the wrong-but-green count, the messages the rep had to apologise for. - If it breaks: what you see: a prospect texted twice in a minute, a reminder for a time that moved, or a message after someone said stop. Check first: the connection to HubSpot and the calendar; the consent flag on the record; the template that was sent. Safe fix: unenroll everyone from the sequences and pause the reminder tool; the rep works the list by hand, as today. - Baseline to count before switch-on: two weeks of: inquiries a week by source; minutes from the form's timestamp to the first reply (from the record, not memory); consultations booked and days out; show rate, counted on its own; the rep's minutes on reminders, chase messages and logging (time it, do not ask); leads closed as dormant. - Tools by name: HubSpot (the firm's own; sequences from Sales Hub Professional, $90 a seat a month billed annually, $100 monthly, $1,500 onboarding; a reply unenrolls a contact when that switch is on, and a booked meeting unenrolls only when booked by the same user who enrolled the contact; texting is a Marketing Hub add-on priced on request, opt-in only, STOP on every message); Apptoto (from $30 a month plus $10 a user, 23% off annual, $0.12 a message over the plan's credits, HIPAA plan from $208; reminders by text, email or voice, reply "1" or "C" to confirm, two-way messaging); Lawmatics (price on request, 3-user minimum, Premium caps two-way texting at 50 messages a month, SMS an add-on); Clio Grow (quote-gated, about $59 a user as third parties report); people: Smith.ai ($300 a month for 30 calls, $11.50 a call over, booking $1.50 a call, text and email follow-up $0.50 a call); built: Twilio ($0.0083 a segment each way plus carrier fees, $1.15 a number a month, A2P registration required), n8n (Starter 20 euros a month billed annually, 2,500 runs), Claude Haiku 5.5 ($0.10 per million tokens in, $0.50 out), HubSpot's API. The rules: the FCC's 2022 ruling that ringless voicemails need prior express consent, and its 2025 rule that a stop word in reply to a text revokes consent for every channel, to be honoured within ten business days (this build does it within the hour). It may never, on its own: cancel or move an appointment; call anyone or leave a voicemail; compose a reply to a question; message anyone whose number and consent are not on file, or anyone after a stop word; or say anything about fees, Medicaid, or the law. Keep with a person: the call that qualifies, and the conflict check before any consultation is booked; every reply that carries a question or a story; the decision to stop chasing someone; whether to cancel an appointment nobody confirmed (a person calls first; the machine never cancels); and anything about fees, Medicaid, or what the law says. Not yet: phone calls or voicemails of any kind on its own (a ringless voicemail needs consent under federal rules); composing a reply to a question; texting anyone who did not give the firm their number and agree to texts; and any message after a stop word, on any channel. Ask me for the tools and numbers you need from my business before you start. Then build it one step at a time, and show me each step working before the next.
No one in your business holds this judgment?
Then the first step is the expertise, not the build. Konstellation, Nick's advisory firm, judges one of your jobs with you, free: what it costs today, the verdict, the bill and who owns it.
Get the verdict on one jobKnow someone doing this job by hand? Send them this page.
Free, for one email
One email opens every job and every system.
Everything on instig8.ai is free. Your email, once, unlocks all of it on this device, and you hear when the next job is out.
Unsubscribe any time.