illustrative public workflow // HVAC

From missed call to qualified booking handoff.

See what the caller receives, what your office sees and where a person takes over. The public replay uses synthetic records so you can inspect the sequence before discussing your phone setup.

Book a 20-Minute Fit Call See the six stages

// simulated stages

How does the missed-call sequence work?

Catch and answer
The missed call is detected and the contractor-approved acknowledgement goes out — nothing improvised, nothing unapproved.
Ask what a person needs to act
Service area, issue type, urgency, and preferred timing are collected with approved questions; equipment diagnosis and safety judgment stay human.
Hand off and stop cleanly
The record lands with a person or an approved booking path, and any reply, opt-out, confirmation, attempt limit, or failure ends automation visibly.

The full six-step configuration — every detection rule, approved message, qualifying field, and stop condition — lives on the service page. Read the complete missed-call workflow →

// public synthetic demonstration

What happens to a missed call, step by step?

This six-step clickable replay shows the buyer and dispatcher view without a private login. All names, times, messages, and records below are synthetic or illustrative data — not a live customer record.

Efficient Automate / synthetic dispatcher view

Standard path / Missed call selected

// 01 / Missed call

The missed call is captured as an event.

The workflow records the unanswered inquiry before any follow-up is considered.

Event type: Inbound HVAC call
Source: Google Business Profile
Received at: 2:14 PM
Outcome: No answer

// 02 / Acknowledgement

An approved SMS acknowledgement is sent.

This synthetic sent message asks only for the details an approved owner needs to continue the conversation.

Approved-message example

Thanks for calling Northline Heating & Air. We missed your call. Reply with what you need help with, your city, how urgent it feels, and a preferred time.

Synthetic delivery status

Channel: SMS
Status: Sent — synthetic demonstration
Sent at: 2:14:08 PM

// 03 / Qualification

The supplied qualification fields are collected.

This illustrative reply is organized for human review; it is not a diagnosis or scheduling decision.

Approved qualification fields

Issue: No cooling
Service area: Taylors, SC
Urgency: Needs attention today; no immediate safety concern reported
Preferred time: Today after 4 PM

// 04 / Stop-condition check

The normal example passes a safety stop-condition check.

No unsafe or emergency language appears in this synthetic reply, so the record can continue to the configured handoff.

Safety decision

State: Clear — no supplied stop condition triggered
Automation: Continues to the configured handoff in this synthetic path
Human boundary: Casey — office team owns review and any customer-facing decision

// 05 / Handoff

A responsible person or approved booking path receives the record.

The workflow surfaces the context and ownership; it does not dispatch a technician or confirm availability.

Handoff

Owner: Casey — office team
Route: Staff review or approved booking path
Status: Handoff created — booking not confirmed

// 06 / Tracking view

The event appears in the tracking view.

The sample record makes the status, owner, and workflow boundary visible to the buyer and dispatcher.

Sample tracked record

DEMO-041

Status: Handoff created — booking not confirmed
Owner: Casey — office team
Source: Missed-call text-back
Next action: Review or send to the approved booking path

// Safety stop

Unsafe or emergency language reaches a defined stop condition.

The reply is checked against the supplied stop conditions before qualification or booking continues.

Illustrative customer reply

Illustrative reply: “I smell gas and feel dizzy.”

Safety decision

State: Triggered — safety or emergency language
Automation: Stops before qualification or booking continues
Human boundary: Designated human owner follows the supplied escalation rules

// Owner review required

The automated path stops for owner review.

The record is surfaced to the designated human owner under the contractor’s supplied escalation rules.

Stop-condition status

Safety or emergency language

Automated qualification and booking are stopped. No emergency advice is provided by this demo.

// Tracking view / stopped

The stop condition is visible in the tracking view.

The record is retained for the designated owner; the demo does not provide emergency advice or create a booking.

Sample tracked record

DEMO-042

Status: Automation stopped — owner review required
Owner: Designated human owner
Source: Missed-call text-back
Next action: Follow the supplied escalation rules

Handoff does not guarantee a completed booking. This demonstration makes no diagnosis, dispatch decision, emergency advice, or price commitment. This synthetic demo does not guarantee revenue or recovered jobs.

// public simulation

What do the customer and the office each see?

Customer view - simulation

The caller receives the approved acknowledgement and can share the details the office needs. See the sample message and reply.

Office view - simulation

The office sees the inquiry history, assigned person and next action. The worked example shows a callback task with the booking still unconfirmed.

Human decisions remain human. Diagnosis, emergency advice, price, technician dispatch, and final availability remain human decisions.

// evidence boundary

How do we verify the workflow worked?

The measurement page names the observable states, timestamps, handoffs, stop conditions, and limits that make a workflow reviewable.

Map the handoff before switching it on.

Bring the current call, consent, escalation, service-area, and booking rules to a focused fit call.

Book a 20-Minute Fit Call