An AI receptionist for home-service calls that need a clear next step.
Configure Truvoca to collect the issue in the caller's words, service address, contact details, property context, access constraints, and approved urgency signals, then create a request, notify the team, or use the verified human route.
This umbrella page covers HVAC, plumbing, electrical, roofing, garage-door, appliance, cleaning, and similar services without pretending every trade has a finished product. Diagnosis, quotes, emergency classification, dispatch, technician assignment or ETA, same-day guarantees, booking, payments, financing, and 24/7 availability are not approved claims.
30 minutes over Google Meet. Times are shown in Eastern European Time (GMT+03:00). Scheduling runs on Google Calendar, so choosing a time takes you into Google’s service.
- Structured job-request intake
- Trade- and category-specific questions
- Approved request, notification, or handoff
- Connected result only after system verification
The phone rings while the team is on the road or on site
Separate repeatable intake from calls that need dispatch or trade judgment.
Technicians may be driving, working in a home, or coordinating a job while dispatchers manage schedules and changes. New customers describe a problem, existing customers ask about an appointment or job, vendors need a route, and some callers use urgent language.
Truvoca can organize facts and apply defined rules. It should not diagnose the issue, decide that a situation is safe, quote from an unverified price book, or promise when a technician will arrive.
- New customer and job request
- Existing customer or open-job question
- Appointment request or confirmation
- After-hours intake after workflow validation
- Vendor, landlord, tenant, or property-manager route
- Urgent, unsafe, or out-of-scope call for staff
One platform, different intake details
Adapt the questions to the trade without copying the same script.
The common structure is contact, location, issue, context, timing, and next owner. The details change by service, and each trade requires subject-matter review before launch.
- HVACequipment type, heating or cooling, visible display, and caller observations
- Plumbingfixture or area, leak description, water status, and visible damage
- Electricalaffected area, power status, smell, sound, or visible condition
- Roofingproperty area, leak or damage context, weather timing, and access constraints.
- Garage door or applianceequipment context, current position or behavior, and service-request details.
- Cleaning and other servicesproperty type, scope, access, timing, and special instructions after review.
Start with outcomes the operations team owns
Choose the call type that can end in a defined request or route.
Workflow labels separate proven behavior from future automation.
-
New job request Configurable
collect approved intake and create the verified destination.
-
Existing-customer request Configurable
look up a record only after identity and field tests; otherwise collect context.
-
Appointment request Validation required
booking needs service area, duration, skills, availability, and write-back proof.
-
Appointment confirmation Production-adjacent
use the verified confirmation model on approved service data.
-
After-hours intake Gated
requires schedule, urgent-call, transfer, fallback, and monitoring tests.
-
Dispatch, pricing, diagnosis, safety, complaint, warranty, or payment decision. Staff route
Capture what the team needs without diagnosing
Create a job request with clear facts, location, and ownership.
A validated intake can include caller details, service address and area, property type and ownership context, issue in the caller's words, relevant equipment or fixture, visible, smelled, or heard observations, access constraints, preferred timing, and urgency phrases.
The business must define which fields are required, which data can be spoken back, and where the request goes. Truvoca should not turn observations into a diagnosis, quote, emergency category, technician assignment, or arrival time.
- Caller name, number, and approved contact preference
- Service address, unit, property type, and service-area check
- Issue and relevant asset in the caller's words
- Visible, smelled, or heard observation
- Access, ownership, tenant, pet, or site constraints after review
- Preferred timing and approved urgency signal
- Existing customer or job only through verified lookup
Configured demonstration — not a customer case
Show a request from caller description to staff-ready context.
A multi-trade demo can show a caller describing an issue, Truvoca collecting the approved facts, stating that it cannot diagnose or promise price or arrival, and applying the tested request or handoff rule.
The reviewer should see the resulting task, notification, or system record and the exact fields delivered to the team. Include an urgent signal, missing-data case, or unavailable system to prove the boundary and fallback.
- Trade-specific sample without customer identity
- Approved questions and prohibited advice
- Verified request, task, notification, or no-write state
- Named staff destination and context
- Urgent or failure case with tested caller wording
Field-service software needs workflow-specific proof
Verify the exact action in ServiceTitan, Jobber, Housecall Pro, or FieldEdge.
These systems are research priorities, not claims of native connectors or partnerships. An assessment must verify access, customer and job objects, service locations, appointments, fields, permissions, actions, validation, error behavior, and reconciliation.
The registry should show Available, Custom, or Planned plus last review and exact scope. Do not infer lookup, booking, dispatch, technician assignment, price-book access, or write-back from a logo or a generic API connection.
- Connector status and reviewed scope
- Customer, location, job, appointment, and task objects
- Permitted reads and writes
- Authentication and minimum permissions
- Duplicate, failure, and reconciliation behavior
- Operational and technical owner
The agent should not decide whether a home is safe
Use approved warning phrases and a tested human or emergency boundary.
For smell, smoke, sparks, flooding, loss of essential service, possible gas, vulnerable occupants, or other high-risk language, Truvoca should stop the routine intake according to rules reviewed by the contractor, trade specialist, and counsel. It does not diagnose the hazard or declare an emergency.
The workflow may try a verified person or queue, give approved emergency-services wording, create an urgent callback task, or use another tested fallback. The caller message, no-answer path, alert, and audit must all be explicit.
- Customer-approved warning words and questions
- No technical troubleshooting or safety determination
- Named person, queue, or emergency instruction after review
- No-answer and unavailable-destination behavior
- Urgent task, notification, and responsible owner
- Recorded disposition and audit detail
Test each trade path before accepting live traffic
Use a controlled workflow review to prove the boundary.
Review the intake schema, approved knowledge, forbidden claims, service-area rules, trade-specific test cases, dispositions, verified system behavior, handoff, and fallback. Test new and existing customers, properties outside the area, missing details, urgent language, and system failure.
The best fit has repeatable intake, manageable service areas, an owned routing policy, and staff capacity for exceptions. Exclude diagnosis, autonomous quotes, emergency dispatch, technician ETA, and undocumented field-service actions.
- Approved intake and service-area rules
- Trade-specific script and safety review
- Successful, ambiguous, urgent, and failed test calls
- Verified result or explicit no-write state
- Staff-context and handoff review
- Named launch and monitoring owner
See how Truvoca would structure your next job request.
Tell us the trade, service area, priority call, intake fields, hours, systems, routing destination, urgent rules, and actions the agent must not take. We will prepare a scoped test flow that shows both the caller experience and staff context.
Do not send customer addresses, job records, payment information, credentials, or confidential materials through the public form.
FAQ
FAQ
Which home-service trades can use Truvoca?
The launch page covers HVAC, plumbing, electrical, roofing, garage-door, appliance, cleaning, and similar services. Each trade receives a separately reviewed intake, knowledge boundary, urgent rule, and destination.
Can Truvoca diagnose the problem or quote a price?
No diagnosis or autonomous quote is claimed. The agent can collect the caller's description and use explicitly approved static information, then route technical or pricing decisions to the responsible team.
How are urgent or unsafe calls handled?
The workflow uses reviewed warning phrases, stops routine intake, and follows a tested staff or emergency-instruction route. Truvoca does not determine safety, diagnose the hazard, or guarantee a response.
Can it schedule or dispatch a technician?
Only after service area, skills, duration, resources, availability, permissions, write-back, confirmation, and failure handling are proven. Otherwise it captures a request; dispatch, technician assignment, and ETA stay with staff.
Can it recognize an existing customer or job?
Only through a verified lookup with identity rules, exact objects and fields, permissions, and safe wrong-record behavior. Otherwise Truvoca collects context without claiming that it found the record.
Does it integrate with ServiceTitan, Jobber, or Housecall Pro?
Those are research priorities. The integration registry must show the current Available, Custom, or Planned status and exact verified scope; no native availability or partnership is implied.
Can it answer after hours?
The after-hours workflow remains gated until inbound routing, schedules, disclosure, urgent rules, transfer or callback, no-answer fallback, telephony failure, and monitoring are tested.
How does the team receive the request?
The implementation names the verified system record, task, notification, or transfer and the included fields. It should show caller details, issue, address, context, disposition, urgency flag, and next owner as approved.