What the service would prepare
Prepare a proposed update with the job reference, reason for calling and next step. Route ambiguous matches for review.
Turn an enquiry into a structured proposal for a CRM or job record. A colleague checks the match and approves the next step.
Illustrative workflow
A homeowner calls about a repair already in progress. Creating a fresh sales enquiry would hide the connection to the existing job.
Prepare a proposed update with the job reference, reason for calling and next step. Route ambiguous matches for review.
The destination record, fields needed for a useful update and who can approve it.
An authorised colleague checks the match and decides whether to update the record.
Agentic Fabric · Planned
Consider a caller who asks to move a service visit. In the proposed design, a scheduling specialist could check the requested time and a customer-record specialist could identify the existing job. Connect would bring their findings together for the dispatcher.
The dispatcher would review the proposed change before authorising a calendar or CRM update. If the job reference were ambiguous or a required permission were missing, the request would go to a person for clarification.
We are exploring how the Model Context Protocol (MCP) could support this exchange. Specialist routing, external connections and execution remain on the roadmap.
Agentic Fabric integration is a planned HelloVoix capability. It is not yet available as a public service.