What happens if a customer calls in with a gas leak or carbon monoxide emergency?

For HVAC Companies

This is exactly the kind of call that should be configured as a top-priority, immediate-escalation scenario during setup, and it's worth building a specific script for rather than treating it like a standard no-heat or no-cool call. A properly configured flow instructs Voksha to first tell the caller that if they smell gas or suspect a carbon monoxide leak, they should leave the property immediately and call 911 or their gas utility's emergency line, since that's a life-safety situation an HVAC company should never try to handle purely through scheduling a technician visit, no matter how fast you can dispatch. After that immediate safety guidance, Voksha can still capture the caller's information and flag the call for the fastest possible human follow-up or emergency technician dispatch, since many gas-related HVAC calls do also require a technician visit once the immediate danger is addressed by emergency services. This is a case where the value of Voksha isn't replacing judgment, it's making sure the caller gets consistent, correct safety guidance immediately rather than waiting on hold or reaching voicemail during a situation where minutes matter. During onboarding, HVAC companies should explicitly walk through how they want gas leak, carbon monoxide, and similar safety-critical calls handled, including whether to auto-escalate to a specific on-call manager's phone in addition to the standard booking flow, since this is one area where the configuration deserves more attention than routine scheduling questions, given the stakes involved.