Implementation guide · Custom Customer Systems
A homeowner or property operator calls during a loss of heating, cooling, or system operation while technicians and dispatchers are already occupied. Intake must separate possible safety escalation, true service urgency, coverage, access, and the next promise the team can honor. This guide isolates how ai concierge should behave at that moment rather than treating the entire operation as one automation project. Hold a calm, bounded written conversation that answers approved questions, gathers useful context, and hands the customer to the right person or next step. For this HVAC emergency-service business, the job must use the practice or firm's approved language, records, ownership, and professional boundaries.
Return to the governed library parentA homeowner or property operator calls during a loss of heating, cooling, or system operation while technicians and dispatchers are already occupied. Intake must separate possible safety escalation, true service urgency, coverage, access, and the next promise the team can honor. This guide isolates how ai concierge should behave at that moment rather than treating the entire operation as one automation project.
Hold a calm, bounded written conversation that answers approved questions, gathers useful context, and hands the customer to the right person or next step. For this HVAC emergency-service business, the job must use the practice or firm's approved language, records, ownership, and professional boundaries. Qualified HVAC staff retain safety judgment, diagnosis, dispatch priority, pricing, scope, repair recommendations, and job acceptance. The configured system may capture and route approved facts but cannot diagnose equipment or improvise emergency instructions.
Run one de-identified or synthetic urgent HVAC service request through the configured path and verify that the test conversation answers within approved knowledge, asks only necessary questions, preserves context, and escalates sensitive or uncertain requests cleanly. Record the expected state, actual state, exception owner, and corrective action before release. Do not release or continue the automated path when the caller reports a possible safety hazard, the service promise is unavailable, or diagnosis, price, scope, or dispatch priority requires a qualified person, or when the answer is outside approved knowledge, sensitive context is unnecessary, or the next human and response expectation are unclear. Preserve the record and route the case to the named human owner.
Trace one recent urgent request from the first ring through safety handling, dispatch decision, arrival or handoff, and documented closure. For AI Concierge, also review transcripts, unanswered questions, handoff timing, captured context, consent state, staff response, and customer-visible wording. This is an implementation control, not a performance claim. Validate it with the business's own recent records, approved policies, synthetic or de-identified test cases, and named human reviewers before release.
Implementation control sheet
Hold a calm, bounded written conversation that answers approved questions, gathers useful context, and hands the customer to the right person or next step. For this HVAC emergency-service business, the job must use the practice or firm's approved language, records, ownership, and professional boundaries.
| Control | Release requirement |
|---|---|
| Required operating inputs |
|
| Release acceptance test | Run one de-identified or synthetic urgent HVAC service request through the configured path and verify that the test conversation answers within approved knowledge, asks only necessary questions, preserves context, and escalates sensitive or uncertain requests cleanly. Record the expected state, actual state, exception owner, and corrective action before release. |
| Stop condition | Do not release or continue the automated path when the caller reports a possible safety hazard, the service promise is unavailable, or diagnosis, price, scope, or dispatch priority requires a qualified person, or when the answer is outside approved knowledge, sensitive context is unnecessary, or the next human and response expectation are unclear. Preserve the record and route the case to the named human owner. |
| Human boundary | Qualified HVAC staff retain safety judgment, diagnosis, dispatch priority, pricing, scope, repair recommendations, and job acceptance. The configured system may capture and route approved facts but cannot diagnose equipment or improvise emergency instructions. |
Approved safety language, service-area, availability, equipment-context, and escalation rules The dispatch or job record and person accountable for urgent exceptions and schedule changes Approved knowledge, tone, identity disclosure, channel, privacy, and prohibited-topic rules Conversation states, handoff triggers, availability, follow-up permissions, and transcript retention boundary
Qualified HVAC staff retain safety judgment, diagnosis, dispatch priority, pricing, scope, repair recommendations, and job acceptance. The configured system may capture and route approved facts but cannot diagnose equipment or improvise emergency instructions.
Run one de-identified or synthetic urgent HVAC service request through the configured path and verify that the test conversation answers within approved knowledge, asks only necessary questions, preserves context, and escalates sensitive or uncertain requests cleanly. Record the expected state, actual state, exception owner, and corrective action before release. This is an implementation control, not a performance claim. Validate it with the business's own recent records, approved policies, synthetic or de-identified test cases, and named human reviewers before release.