Implementation guide · Follow-Up & Automation 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 reputation management should behave at that moment rather than treating the entire operation as one automation project. Request honest feedback at an appropriate completed-service moment, route private concerns responsibly, and preserve platform and customer-choice boundaries. 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 reputation management should behave at that moment rather than treating the entire operation as one automation project.
Request honest feedback at an appropriate completed-service moment, route private concerns responsibly, and preserve platform and customer-choice boundaries. 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 eligible customers receive one neutral request, customer choice remains intact, concerns reach a person, and exclusions and opt-outs are respected. 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 service completion, permission, platform policy, customer eligibility, concern ownership, or neutral request language cannot be verified. 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 Review Growth System, also review eligible completions, requests, exclusions, delivery, feedback routes, opt-outs, staff responses, and documented closure without promising ratings. 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
Request honest feedback at an appropriate completed-service moment, route private concerns responsibly, and preserve platform and customer-choice boundaries. 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 eligible customers receive one neutral request, customer choice remains intact, concerns reach a person, and exclusions and opt-outs are respected. 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 service completion, permission, platform policy, customer eligibility, concern ownership, or neutral request language cannot be verified. 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 Eligible completion event, approved request, channel permission, timing, frequency, and exclusion rules Concern-routing owner, suppression, platform-policy review, response approval, and closure state
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 eligible customers receive one neutral request, customer choice remains intact, concerns reach a person, and exclusions and opt-outs are respected. 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.