Customer Inquiry Routing for Home Services
Route home-service inquiries by service area and role with Kiguri while keeping diagnosis, dispatch, safety, and quote decisions with staff.
Use homeowner language
Create categories such as new service request, plumbing, HVAC, electrical, cleaning, landscaping, property-management support, warranty question, billing, supplier contact, careers, and general information. Add service-area or branch labels when operations differ.
For each category, document area, primary role, backup, hours, channels, and fallback. Scheduling can own new requests; customer service can own warranty; field operations can own technician coordination. Categories describe routing, not a dispatch or repair decision.
Define a safe scope
Approved answers may include office hours, service areas, public categories, appointment steps, preparation instructions, accessibility, and contact routes. Give every answer an owner and review date. Do not let routing diagnose a system, assess a hazard, interpret a warranty, quote a job, or promise availability.
Use a boundary: “I can route your service question. I cannot diagnose, price, dispatch, or assess an emergency here.” Direct fire, gas smell, flooding, exposed wiring, or immediate danger to emergency services and the company’s urgent contact.
Keep intake concise
Ask for service area, broad service need, visitor role, preferred channel, and a short description. A homeowner may select HVAC and name a city; a property manager may select account support without posting access codes. Avoid alarm codes, passwords, payment details, identity documents, medical information, and detailed safety incidents in open reception.
Let visitors correct the summary before submission. A note such as “Austin area, warranty question, prefers phone” is enough for customer service. Do not imply that a technician reviewed the issue, a dispatch exists, or an arrival time is guaranteed.
Route to people
Use presence for scheduling, customer service, warranty, property-management, billing, and field-operations roles. Explain handoff wording: “I’m connecting you with customer service and sharing your HVAC topic.” If unavailable, offer a backup or queue with honest hours. Browser phone clarifies an address; video and screen sharing can show a public preparation page; a private room can focus an administrative call.
Hosts should close customer records, payment pages, alarm details, private photos, and unrelated tabs before sharing. A private room is a conversation setting, not a safety, privacy, security, licensing, or compliance certification.
Handle urgent and professional requests
For diagnosis, safety, code, warranty, cost, or emergency questions, route to qualified staff through approved processes. Do not promise a repair, quote, arrival, warranty decision, or safety outcome. Direct immediate hazards to emergency services and the company’s established urgent contact.
Review routes
Maintain a register with area, audience, category, owner, backup, hours, channels, fallback, review date, and retirement date. Update service coverage, team contacts, office moves, seasonal hours, and campaign pages. Retire old links. Review misroutes, repeated questions, unclaimed items, and corrections. Traffic is not evidence of workmanship, safety, revenue, or compliance.
Launch checklist
1. List audiences and service categories. 2. State diagnosis, safety, emergency, and sensitive-data boundaries. 3. Create area- and role-based destinations. 4. Keep intake short and non-sensitive. 5. Assign owners, backups, hours, channels, and fallbacks. 6. Test channels, handoffs, and queue states. 7. Review service-area and campaign links.
Related guides: AI receptionist for home services, human handoff workflow for home services, and shared response queue for home services.
Build a routing register
Keep one register that scheduling, customer service, field operations, dispatch, warranty, and safety leads can review without opening customer systems. Record service area, audience, category, intended role, backup, hours, channels, fallback, review owner, and retirement date. Add a “not for” note to categories that could be misunderstood. A warranty destination can route an administrative question but cannot approve coverage. A field-operations destination can coordinate a visit but cannot promise an arrival or repair.
Review the register when a branch opens, a service area changes, a dispatch platform changes, or seasonal hours begin. Ask someone outside the build team to follow every route on a phone. Confirm the area is obvious, the next role is understandable, and the fallback is truthful. Keep detailed safety, customer-record, payment, and access procedures in approved internal systems.
Communicate changes
When a route changes, tell scheduling, customer service, dispatch, warranty, and operations which label moved and why. Archive retired campaign links instead of silently sending visitors to a new audience. During a severe-weather event or seasonal peak, test the path again after the update. Keep public wording concise and avoid inviting alarm codes or private photos in open reception.
Review service quality
Inspect repeated questions, unclaimed queue items, transfer loops, and notes containing unnecessary information. If warranty requests reach scheduling, adjust labels. If homeowners cannot find the urgent contact, add the approved route. If no role reviews after hours, publish the queue window. These observations improve routing; they do not prove better workmanship, safety, or compliance.
Keep the routing review note in the operations runbook for future owners. Before a seasonal promotion or severe-weather period, confirm service-area labels, emergency contact, hours, queue ownership, and after-hours wording from a mobile device. Remove any public answer the team cannot verify rather than filling the gap with a diagnosis or safety assumption. Share the next review date with every backup role and branch lead.
During a monthly review, compare service-area questions with the approved menu and note which role owned each follow-up. If homeowners repeatedly ask for a preparation guide, publish a verified page. If a safety question reaches general reception, strengthen the boundary and show the urgent contact. Keep review notes operational and never treat them as a diagnosis, dispatch record, or safety certification.
Share the next review date with scheduling, dispatch, warranty, field operations, safety leads, and every backup role across areas.
Operational review note: Keep this Kiguri workflow focused on clear visitor orientation and human ownership. Review the branded entry link, approved answers, intake fields, response queue, presence language, and handoff channels on a dated schedule. Remove claims about performance, outcomes, security, compliance, or guaranteed response time. Ask staff to confirm that public wording matches current responsibilities and that sensitive records move through the organization’s established process. This review improves clarity without turning reception into professional advice or an automated decision system.
Frequently asked questions
Can routing diagnose a home system?
No. It routes questions to service staff.
Should visitors share alarm codes or access details?
No. Use the company’s approved secure channel.
Can one tree support several service areas?
Yes, with area labels, owners, hours, and fallbacks.
Does a queue guarantee a technician?
No. Publish actual scheduling expectations.
Is a private room automatically secure?
No. The company defines privacy, security, licensing, safety, and compliance practices.
Can routing handle an active hazard?
No. Direct immediate danger to emergency services and the company’s urgent contact.
Sources and further reading
• [Kiguri AI receptionist for home services](https://kiguri.com/blog/ai-receptionist-for-home-services) • [Kiguri human handoff workflow for home services](https://kiguri.com/blog/human-handoff-workflow-for-home-services) • [Occupational Safety and Health Administration](https://www.osha.gov/) • [NIST Privacy Framework](https://www.nist.gov/privacy-framework)
**Image candidate:** Unsplash home-services team photo: https://images.unsplash.com/photo-1581578731548-c64695cc6952
**Suggested image alt text:** Home-services team routing homeowner and property-manager inquiries.
Sources and further reading
Kiguri product overview, Kiguri pricing, security information, and Kiguri guides.