Every branch answers differently
Hours, services, prices, territories and escalation paths drift when local knowledge lives only in people.
MULTI-LOCATION HOME SERVICES · AI OPERATING LAYER
TWINMIND builds one AI receptionist across your brands and branches. It identifies the service territory, applies the correct local rules, checks real capacity and creates the work in the right field-service system.
THE SCALE PROBLEM
As a home-service company adds branches, every phone line, territory, service list, business hour, price rule, capacity source, credential and exception path becomes another place where a qualified request can be delayed or routed incorrectly.
Hours, services, prices, territories and escalation paths drift when local knowledge lives only in people.
A shared number or campaign can produce a good lead that the receiving team cannot serve.
One branch is full while another has availability, but the customer and office team cannot see a safe overflow path.
Managers see volume, but not why bookings failed, which rules differed or who owns each exception.
ONE REQUEST, ONE OWNED OUTCOME
The operating layer combines central standards with an explicit rule pack for each location. It never silently writes into another branch or invents capacity.
Capture customer, address, service need, urgency and preferred time through the approved shared or local channel flow.
Use phone line, campaign, postcode, service area and existing customer ownership in a documented order with a confidence threshold.
Apply that branch's hours, services, business units, job types, skills, booking horizon, price disclosures and escalation paths.
Query the authorised location. If it is full, evaluate only approved overflow locations and explain the change before confirmation.
Create or update the verified customer and booking with location, source, conversation summary, action identifiers and idempotency evidence.
The local team receives the job or exception. Central operations receives the common outcome and reason without taking over local record ownership.
THE MULTI-LOCATION CONTROL PLANE
Each location keeps its authorised field-service records and employees. Shared routing, observability and exception contracts sit above them.
Shared and local phone numbers, chat, web forms and campaigns entering one approved intake contract with source attribution.
Brands, branches, phone lines, addresses, postcodes, territories, hours, services, priorities and named exception owners.
ServiceTitan, Housecall Pro, ServiceM8, Workiz or another authorised system remains the record owner for each location.
Location-specific business unit, job type, employee skill, duration, service area and real availability used before an offer.
Dispatchers and managers receive complete context for emergencies, overrides, ambiguous customers and unsupported work.
Common outcome taxonomy, routing evidence, exception age and location comparisons without erasing local authority.
RULES BEFORE ROUTING
The operating layer resolves a location only from approved brand, phone-line, address, postcode, territory and customer-history rules. Low-confidence matches, unavailable capacity, unsupported cross-location writes and conflicting records become owned exceptions instead of silent automation.
DATA OWNERSHIP AND EXCEPTIONS
Use the minimum read/write scope for the selected workflow and location. Do not give the orchestration layer unrestricted access by default.
Store the target location, source request, system identifiers and result so retries do not silently create duplicate customers or jobs.
No territory, two possible customers, zero capacity, API failure or unsupported work becomes a visible task for a central or local owner.
VERIFIABLE SYSTEM BEHAVIOUR
Official documentation supports location, business-unit, zone, capacity and permission concepts. It does not prove a customer result; that evidence must come from the measured rollout.
Published customer lookup, business-unit and job-type resolution, dispatch capacity and booking capabilities used in controlled field-service flows.
Open source ↗Official platform APIServiceTitan documents business units, employees, technicians and user roles; business units can be assigned to locations and tracked separately in reporting.
Open source ↗Official platform APIServiceTitan documents real-time capacity by time range, business unit, job type and skill-based availability for booking workflows.
Open source ↗Official platform guidanceHousecall Pro documents multiple zones defined by city or postcode, assigned technicians, optional trip charges and booking gates.
Open source ↗Official platform APIServiceM8 documents granular scopes for locations, staff, customers, jobs, email and SMS and recommends requesting only essential permissions.
Open source ↗Compare baseline and pilot by location: eligible request volume, booking completion, employee minutes per request, overflow accepted, duplicate writes and exception age. Convert only measured time and recovered work into a financial model.
EXPAND BY RULE PACK, NOT BY REBUILD
Numbers, brands, territories, services, hours, job types, capacity sources, credentials and exception owners.
Centralise the common intake contract; version every location-specific difference instead of hiding it in prompts.
Boundary postcode, existing cross-location customer, no capacity, closed branch, duplicate request, timeout and manual takeover.
Pilot one shared customer journey across two locations, compare valid routing, booking completion, manual minutes and exception age by branch, and add each next location through a reviewed versioned rule pack.
MULTI-LOCATION AI QUESTIONS
TWINMIND defines a deterministic resolution order using approved signals such as the called number, brand, campaign, customer address, postcode, service territory and existing record ownership. A low-confidence or conflicting match goes to a named person.
Yes. Shared intake fields and outcome definitions can remain central while hours, services, job types, skills, capacity, pricing disclosures, overflow and escalation stay in a versioned location rule pack.
Only when the business approves the participating locations, services, territory exceptions, capacity source and customer disclosure. The agent explains the target location before confirmation and does not silently write into another branch.
No. A canonical request and outcome contract can route into different authorised adapters. Each adapter still needs verified identifiers, permissions, error handling, idempotency and a responsible local owner.
They own their operational rules, credentials, staff handoff and exception queue. Central operations can see a common outcome and exception model without receiving unrestricted write access to every local record.
Baseline each location first. Measure eligible requests, correct routing, booking completion, employee minutes per request, overflow accepted, duplicate writes and exception age. Apply your own labour cost and recovered-work value only to observed changes; do not assume a universal percentage.
BRING ONE ROUTING PROBLEM