Response times nobody can level up
One location replies in ten minutes, another in two days, and the customer experienced the brand either way. Training changes it for a month; staffing changes it back.
A network reputation set by its weakest week.
SOLUTIONS · FRANCHISE NETWORKS
A network is judged on the slowest front desk in it. Connect gives every location the same digital front office — answering the enquiry, qualifying it, booking the appointment and following up — while the location keeps its own mailbox, number, prices, hours, territory and customer memory. The playbook is shared. The customer is not.
A customer enquiry, at one location
Every step above is a real action in the product, written to that location's records — not to a shared network inbox. The documentation names the screen each one lands on.
THE BUSINESS PROBLEM
Head office can mandate the playbook. It cannot answer the phone at location forty-one on a Saturday afternoon.
One location replies in ten minutes, another in two days, and the customer experienced the brand either way. Training changes it for a month; staffing changes it back.
A network reputation set by its weakest week.
A customer contacts head office, or the location nearest the motorway rather than nearest to them. The handover is an email, and the second location starts the conversation again.
Enquiries lost between locations that both wanted them.
Hours, prices, services and territory differ by location and change without notice. Any central answer is out of date somewhere, and a wrong answer in the brand's voice is worse than a slow one.
Head office answering for facts it does not own.
Who this customer is and what was agreed lives in one outlet's inbox and one manager's head. When that outlet changes hands or staff, the relationship restarts.
A network of first conversations.
None of this is a compliance failure. It is what happens when a shared standard has to be executed by separately owned businesses with separate staffing.
THE CONNECT WORKFLOW
One chain, run identically across the network — and at every step the acting party is the location, not the centre.
Hover, tap or tab any part.
Someone in the area wants what the network sells. They arrive through a form, a local listing, a referral or a number they already had — and they expect an answer today, from whoever is nearest.
Hover, tap or tab any part.
The enquiry is routed to the location that owns it and lands in that location's workspace, with its prices, hours, services and territory attached. The centre can see that it happened; it does not have to handle it.
Hover, tap or tab any part.
Answered on the channel it arrived on, from the knowledge that location approved. A question the local knowledge does not cover escalates to the franchisee rather than being improvised in the brand's voice.
Hover, tap or tab any part.
What they need, when, for how many, at which address, and whether it is inside this location's territory — captured as structured fields on the customer record instead of being buried in a thread.
Hover, tap or tab any part.
An appointment, visit or job slot is proposed against the hours and capacity that location actually keeps. Anything the location gates — discounted work, out-of-hours slots, jobs outside the territory — waits for the franchisee in Needs You.
Hover, tap or tab any part.
The customer who did not confirm, the quote that went quiet and the booking that needs a reminder each carry a scheduled next action, owned by the location. Chasing stops depending on how busy Saturday was.
Hover, tap or tab any part.
Questions after the visit, complaints, rebookings and repeat business continue on the same local record, with the original enquiry and the booking already attached to it.
Nothing in this chain crosses a location boundary on its own. A customer who moves between two locations is handed over deliberately, by a person, and the handover is a recorded action rather than a forwarded mailbox.
ONE INFRASTRUCTURE · MANY LOCATIONS
The network runs one system and one standard. What each location keeps is everything that makes it a separate business.
One Connect infrastructure
The same product, the same workflow and the same standard of answer, deployed once for the network.
Central visibility across locations is a matter of who is granted access to which workspace, agreed with you in setup. It is not something a location's own login can reach.
EMAIL · PHONE · WHATSAPP
Every channel a location already publishes stays the channel it publishes. Connect answers on it — as that location.
The location's own address — the one on its listing, its van and its invoices — connected with the provider's own authorisation. Replies go out from it, and the thread lands on that location's customer record.
Inbound and outbound calls on the location's line, with transcript and summary written back to the same customer the emails belong to.
The channel most local customers actually use. Inbound messages and replies run through the same local knowledge, rules and approval gate as email.
Which channels are live for a location depends on the accounts and provider numbers that location connects during setup. SMS sending and call recording are carrier-dependent and confirmed in your pilot, not assumed here.
RELATIONSHIP MEMORY
A returning customer should not have to re-explain themselves because the person who knew them left the outlet.
What a local customer record holds
RULES · PERMISSIONS · APPROVALS
Autonomy is a setting, and in a network it is a setting per location. A cautious franchisee and a confident one can run the same system differently.
Connect prepares everything and sends nothing. Where most locations start, and where a new franchisee starts regardless of how the rest of the network runs.
Routine answers go out; anything that commits the location — price, date, obligation — stops in Needs You with the full context attached.
It acts inside the boundary that location defined, and escalates the moment a request touches the edge of it.
Every action Connect takes is recorded — what it did, at which location, on whose authority, and the evidence it used. An approval is a decision with a name on it, not a silent automation.
BEFORE VS WITH CONNECT
Nothing here is a claim about results. It is a description of where the work moves.
Today
An auto-reply, then Monday. The customer has booked somewhere else by then.
With Connect
Answered from that location's approved knowledge within minutes, on the channel it arrived on.
Today
Answered from a central list that is wrong for this location, or not answered at all.
With Connect
Answered from the prices that location actually keeps, or escalated if the local knowledge does not cover it.
Today
Forwarded by email and usually dropped between two locations.
With Connect
Flagged as outside the territory and handed over deliberately, as a recorded action.
Today
A training problem that returns with every staffing change.
With Connect
A shared workflow each location runs, with local facts and local approval rules.
Today
The customer list is an inbox and a phone that leave with the owner.
With Connect
The workspace holds the customers, agreements and open obligations, and transfers with the location.
Today
A survey of franchisees, and numbers everyone compiles differently.
With Connect
The record each location writes as it works, visible to whoever you granted access to.
BUSINESS OUTCOMES
Connect does not come with a number attached. These are the effects to measure against your own baseline during a pilot at two locations.
Enquiries are answered when they arrive rather than when the counter is free, including evenings and Sundays.
How you would measure it: Median time from enquiry to first substantive reply, per location, before and during the pilot.
The gap between the fastest and slowest location narrows because the first answer no longer depends on staffing.
How you would measure it: The spread of first-response times across pilot locations, compared with the network's current spread.
An enquiry that belongs to another location is identified and handed over as a tracked action rather than forwarded and forgotten.
How you would measure it: Share of cross-location enquiries that received a reply from the receiving location.
The relationship survives a manager leaving, because it is on the location's record rather than in their inbox.
How you would measure it: Time to bring new counter staff to full handling on existing customers.
Every one of these is measurable from the record Connect writes. If a pilot does not move them at your locations, that is a finding, and we would rather you found it in four weeks than after a network-wide rollout.
DEPLOYMENT
A network rollout that begins everywhere is one nobody can judge and nobody can reverse. This begins with two locations that are not alike.
One busy, one quiet — or one enthusiastic franchisee and one sceptical one. Agreement from both, because a location cannot be enrolled over its own objection.
Each location's own mailbox and identity, and its phone line or WhatsApp number if it uses them. Nothing is scraped and no password is shared.
The network answers that are genuinely shared, and then the prices, hours, services and territory that belong to each location. Both are the knowledge Connect is allowed to speak from.
Autonomy mode and approval gates per location, agreed with that franchisee. Most locations start in Draft only.
Connect prepares every reply and sends none. The franchisee reads them, corrects what is wrong, and sees exactly how their week would have been handled.
Turn on sending for the categories each location is confident about, keeping prices and commitments behind approval — then review both locations against the numbers they started with.
Existing email continues to work throughout. Connect joins a location's mailbox; it does not replace it, and the franchisee can take over a conversation at any point.
TRUST & LIMITATIONS
A supplier that oversells to a franchisor now is a supplier that will oversell to its franchisees later.
QUESTIONS
Only where that access is granted. Each location is a separate workspace, and visibility across workspaces is something you agree and configure in setup rather than something that exists by default. It is worth deciding this before the pilot, because franchisees will ask on day one.
It answers from the prices that location loaded and approved, and stops outside them. A request for a discount past the local list waits in Needs You with the conversation and the number it would have sent. Pricing authority stays with the franchisee.
No. Autonomy level and approval gates are set per location. One franchisee can stay in draft-only for months while another sends routine replies automatically, on the same shared workflow.
It is identified as outside the territory and handed over as a recorded action to the location that owns it, rather than forwarded into a mailbox where it can quietly die. The handover is a decision a person can see and, where your rules require, approve.
Their workspace is theirs to disconnect, and the rest of the network is unaffected. What the departing location may take with it is a matter of your franchise agreement, not of what the software allows — the Trust Centre documents the export and deletion rights that exist.
The draft-only week tells you about quality — the franchisee reads what would have been sent. Response times and follow-up coverage move in the first weeks after sending is enabled. Anything about network-level revenue takes longer than a pilot, and we will say so rather than promise otherwise.
There is no public price list. Commercial terms follow JBRH-approved commercial configurations based on the locations, channels and volume actually in scope — the pricing page explains what drives the number and how in-policy pricing or owner review is produced.
START HERE
A pilot is two of your real locations, their real mailboxes and their own approval boundaries — not a scripted demonstration. Both franchisees will know inside a week whether the drafts are good enough to trust.