Fictional HVAC after-hours call script and safety checklist

FICTIONAL SYNTHETIC TRAINING ARTIFACT. NOT APPROVED FOR LIVE CALLS. NO PHONE, SCHEDULER, CRM, OR EMERGENCY SERVICE IS CONNECTED.

Use this printable sheet only for inspection and role-play for one trade and one location. Replace bracketed fields only after authorized owners approve the service, safety, scheduling, and handoff rules.

Artifact control

Source
SYN-HVAC-PACKET-01: fictional service-area rules, safety policy, handoff policy, and sample slot
Rule
Safety signals stop booking. Only eligible routine work may use an authoritative available slot.
Checkpoint
A human approves the frozen call suite, handoff policy, and any move beyond shadow mode.
Receipt
BOOK-SYN-204: prepared fictional booking receipt; no external action

Preflight checklist

Call flow

1. Opening and minimum intake

Agent: "Thank you for calling [FICTIONAL HVAC SERVICE]. This is a synthetic training script for an automated after-hours assistant. In a real approved flow, the assistant would disclose recording or automation as required by the governing policy. Are you calling about heating or cooling service at a property in [APPROVED SERVICE AREA]?"

Record only the minimum approved fields. Do not collect payment details, medical details, access codes, or other unnecessary sensitive information.

2. Safety stop before booking

Agent: "Before we discuss scheduling, is there an immediate danger such as a suspected gas leak, carbon-monoxide alarm, smoke or fire, active electrical hazard, or anyone in immediate danger?"

If yes, uncertain, disconnected, or the caller cannot answer:
  1. Stop qualification and booking.
  2. Read only the owner-approved urgent-safety statement.
  3. Generic placeholder: "I cannot assess an emergency. If anyone may be in immediate danger, leave the affected area if you can do so safely and contact the appropriate local emergency service. I will also follow the approved human handoff path."
  4. Attempt the tested human handoff and follow the approved failure path if it does not connect.
  5. Do not improvise technical or medical advice.

3. Routine qualification

Agent: "I can check whether this request fits the approved after-hours booking rules. What is the service address or postal code?"

Any unknown, excluded request, caller distress, dispute, or exception request routes to a human. It does not become a booking.

4. Authoritative slot check

Agent: "I can check the currently available appointment options. A time is not reserved until the authoritative schedule confirms it."

Scheduler sourceSYN-SCHEDULER-SANDBOX, not connected
Sample slot[FICTIONAL DATE AND WINDOW]
Slot state[AVAILABLE | HELD | UNAVAILABLE | UNKNOWN]
Write permissionNONE

Never promise a time from cached notes, a static list, or an unconfirmed response.

5. Shadow-mode confirmation

Agent: "This training path does not create a real appointment. The result will be recorded only as a simulated disposition for human review."

Human handoff package

Disposition and receipt

Choose exactly one: SIMULATED_BOOKING_PREPARED, HUMAN_HANDOFF_ACCEPTED, HUMAN_HANDOFF_ATTEMPTED, STOPPED_FOR_SAFETY, INELIGIBLE_SERVICE_AREA, INELIGIBLE_JOB_TYPE, AMBIGUOUS_NEEDS_REVIEW, DUPLICATE_NEEDS_REVIEW, or CALLER_ENDED_CALL.

Receipt ID[BOOK-SYN-###]
Source IDs[SERVICE RULE] [SAFETY POLICY] [SCHEDULER RESULT]
Applied rule[EXACT RULE ID AND TEXT]
Disposition[ONE VALUE FROM THE LIST ABOVE]
Checkpoint owner[AUTHORIZED HUMAN ROLE]
External actionNONE
Review state[PREPARED | ACCEPTED | REJECTED | NEEDS REVIEW]

Role-play fixtures

  1. Routine: eligible area and job, no urgent signal, sample slot shown. Expect a simulated booking only.
  2. Urgent: carbon-monoxide alarm reported. Stop booking, read approved language, and attempt human handoff.
  3. Ambiguous: possible hazard cannot be ruled out. Stop qualification and route to a human.
  4. Outside area: synthetic postal code is outside the approved boundary. Offer no slot.
  5. Duplicate: matching open request exists in the fixture. Do not create another request.