01
Capture the missed call
Resolve the tracked number, persist the event, and open the lead thread cleanly.
Residential HVAC missed-call recovery
Keep working. We’ll handle the callback.
Docs / Workflows
The missed-call-to-booking flow is small on purpose and durable under real operating pressure
This page describes the workflow model rather than every UI click. CallSnare captures the missed call, replies quickly, moves the lead toward booking, keeps reminder behavior aligned, and preserves proof of the outcome.
The workflow is intentionally narrow: one lead thread, one booking path, and one evidence trail. Complexity stays behind guardrails rather than leaking into the operating surface.
Signal path
Missed ring, fast reply, booked job, stored proof
02
Move the conversation
Send the first text when the rules allow it, then keep office and automated work in one thread.
03
Keep booking behavior aligned
Confirmation and reminder work stays attached to the booking instead of drifting from it.
The customer sees speed. The operator gets structure.
Customer path
The customer feels speed first: missed call, quick text reply, clear next step.
Operator path
The team sees one thread with status, notes, booking context, and who needs to act next.
Rules engine
Billing checks, business-hour rules, opt-outs, and terminal states keep the automation from running loose.
Missed-call to booking
Six durable stages from missed ring to proof of outcome
The public explanation is simple because the workflow itself is supposed to stay simple. Each stage reuses the same lead and booking facts instead of creating side records that later need cleanup.
A missed call is captured
CallSnare watches your HVAC business number, records the missed-call event, and keeps the call evidence tied to the right organization.
The homeowner gets a fast text reply
When the rules allow it, CallSnare sends the first follow-up text quickly so a no-cooling or no-heat lead does not fall through the cracks.
The conversation moves toward booking
The inbox, templates, and response rules help gather enough detail to either book the diagnostic or hand it to the office.
Booked work lands on one calendar
Appointments can be created in the built-in calendar or by approved external systems using the protected booking API.
Confirmations and reminders stay aligned
Confirmation and reminder jobs are scheduled from the booking record, and changes to the booking resync those unsent jobs.
Results stay auditable
Leads, messages, bookings, lifecycle timestamps, and proof records stay persisted so results and guarantee outcomes can be explained later.
Why it holds together
One record carries the story forward
The missed call creates the lead context instead of starting a detached callback list.
Replies, notes, booking state, and reminders continue from that same thread.
Proof and guarantee views can explain the result later because the transitions stay persisted.
Lead lifecycle
Lead state is explicit so the team and automation stop guessing
The lead lifecycle tracks whether the conversation is new, active, booked, won, or closed. Those states also drive what automation should stop or continue.
Primary states
- `NEW`: newly captured with limited context.
- `WORKING`: active conversation or triage in progress.
- `BOOKED`: appointment scheduled on the calendar.
- `WON`: job completed and revenue realized.
- `LOST`: closed, opted out, or not converted.
Guardrails
- Inbound replies move the lead into active work.
- STOP ends outbound recovery until START reverses it.
- Terminal outcomes stop follow-up automation.
- Status changes write timeline evidence for audit and reporting.
Booking lifecycle
Booking communication stays coupled to the appointment record
Confirmations and reminders are not free-floating sends. They exist because a booking exists, and reschedules or cancellations update that communication path.
Booking states
- `PENDING` until the appointment is confirmed or completed.
- `CONFIRMED` when the visit is locked in.
- `COMPLETED` after the work is finished.
- `CANCELED` or `NO_SHOW` when the visit no longer stands.
Communication behavior
- Confirmation and reminder jobs are tied to the booking record.
- Reschedules replace unsent booking jobs so messages stay accurate.
- Cancellations keep history intact instead of deleting proof.
- Outbound sends still obey billing and automation guardrails.
Workflow FAQ
The common trust questions should be easy to answer
These are the questions owners usually ask before they trust the product to move quickly on their behalf.
What happens when I miss a call?
CallSnare records the missed HVAC call, texts the homeowner back when the rules allow it, and opens a lead so the office can keep the conversation moving.
Does CallSnare text customers back automatically?
Yes. The product is built around fast missed-call follow-up by text, with business-hour and billing guardrails applied before outbound sends.
Can CallSnare book jobs onto the calendar?
Yes. Diagnostic visits and other jobs can be booked from the web app and from the protected private booking API used by approved integrations.
Can owners still step in manually?
Yes. Owners, admins, and agents can work leads directly in the inbox, update statuses, book appointments, and review the full history.
Continue reading
Once the workflow shape is clear, the next question is capability and control
Use the next docs to see which actions exist today, where explicit permissions apply, and how the protected machine-facing surface is kept narrow.
Actions
Review what is live via protected access, what remains internal, and what is only planned.
Permissions
See how roles, scopes, tenant boundaries, and audit expectations shape real access.
Webhooks
Understand the provider callback model that feeds the workflow and why no public event bus exists yet.
Agent access
Check what models and approved integrators can discover publicly versus what remains protected.