Capabilities
AI service operations for home service companies
HumCrew connects AI answering, booking, dispatch-ready job records, estimate follow up, and human handoffs for home service companies. Run the core operation in the HumCrew command center, or separately scope a customer-specific connection to software your team already uses. External connectors must be built and verified before they are enabled.
These are deployment capabilities, not a claim that every module is fully enabled by default. Jobs, signed proposals, and the phone app are in the working core, and Stripe test checkout is the only payment path; live charges are not switched on. External field service connectors are not part of the current HumCrew core. Each one must be separately scoped, built, and verified before use. Text messaging also requires any applicable sender registration or verification, exact provider configuration and routing, and the consent required for each message type. The current demo text line has completed its required setup, but that does not enable text messaging for other tenant lines.
01
Answer and book
Coverage for every way a customer reaches you, with jobs landing on the schedule, not in a message queue.
- Voice agents that answer the configured line and book real appointments into HumCrew's internal calendar. Callers are informed up front that they are speaking with an AI assistant. An external calendar or field service write requires a separately built and verified connector.
- For a carrier-registered deployment, text agents can reply to inbound SMS, answer common questions, and move the conversation to a booked slot.
- Web booking flows linked from your own site that qualify the visitor and, when eligible, place a confirmed appointment on HumCrew's internal calendar.
- Warm handoff rules: pricing disputes, angry customers, and anything the agent should not decide get routed to your people with full context.
02
Follow up
The most expensive lead you have is the one you already paid for and then forgot.
- For a carrier-registered, configured deployment, HumCrew can prepare service-related transactional follow up about delivery, status, scheduling, or next steps for a customer-requested quote or estimate when the customer has given the appropriate service-message consent. Sales or promotional content requires separate marketing consent, and sending or automatic sequencing requires an approved, verified workflow.
- Promotional dormant-customer outreach is a separate deployment path. It may use your own past-job and seasonal-service records only after the customer gave valid marketing consent for that channel and the workflow is approved, implemented, and verified. Service-message permission is not treated as marketing permission.
- Missed call recovery: on a registered, configured text line, one recent-call rescue text can restart the conversation unless the caller already opted out. Further proactive texting requires the appropriate consent.
03
Route and schedule
Getting the job booked is half the work. Getting it to the right crew is the other half.
- Zip routed booking that assigns jobs to the right territory automatically, so crews stop crossing town for work the other crew should have taken.
- Technician routing dashboards that show the office who is where and what is next.
- With request-and-appointment messaging consent and a configured delivery channel, confirmation and reminder messages can cut no shows without the office chasing anyone.
04
Connect
Front office AI products often stop at the phone. We scope the authorized connection from first touch to the operational system.
- Website form capture with instant response, so a form fill gets a reply while the customer is still on your site.
- Meta lead form routing that pulls leads out of Facebook and Instagram the moment they arrive and starts the conversation.
- Quote tool webhooks can be separately scoped so an approved follow up workflow begins when your estimating tool produces a number. No external connection or automatic path is available until it is built and verified.
- Customer-specific CRM and field service connections can be scoped as separate engineering projects. No external sync is part of the current core, and no read or write is enabled until it is built and verified.
Illustrative example
From an after hours request to a usable job record
This fictional example shows the information flow. It is not a customer screenshot or a transcript from a live call.
Example caller
“My water heater is leaking. Can someone come tomorrow morning?”
Example AI response
The disclosed AI assistant collects the service details, location, preferred timing, and any information required by the company's approved call rules.
Example output
Apply approved rules- Request
- Water heater service
- Preferred timing
- Tomorrow morning
- Rules checked
- Territory, urgency, crew skill, availability
- Next action
- Offer an approved opening or hand off
- Destination
- Existing field service system
Controlled demonstration boundary
We demonstrate the working HumCrew core with a dedicated demo tenant and demo records. Phone, AI voice, and text are exercised only after their exact demo mappings pass the session check. The current demo text line is carrier registered, configured, and verified for real SMS. Text availability for other tenant lines depends on their own carrier registration and provider configuration. No outside customer production environment is used as proof or touched during the walkthrough.
Not sure which of these you need first?
That is what the discovery call is for. Bring how your shop runs today and we will map the leaks together.
Start by mapping your services, service area, booking rules, and handoffs with the home service AI receptionist setup workbook.