Monday, 8am, in the franchisee group
Someone asks whether the side in the combo can be swapped. Three franchisees answer, two of them correctly, and one repeats a rule that was revoked last year. The unit that reads last runs the wrong one.
Network operations · for whoever answers for every unit running the same way
Head office answered once. Every unit understood something different.
With Synapse's AI, every unit operates with the same knowledge as head office: the operations manual, the commercial policy and the approved procedures start answering in the unit's WhatsApp and in chat, with the document page in view and permission holding inside the answer. When the question is an exception nobody approved, it goes back to head office with the whole conversation.
A 15 to 20 minute diagnostic conversation · A 20 to 30 minute proof session, with your own material · A sprint of up to 7 days, with the decision date agreed before it starts
Before the demonstration
How do you make sure every unit receives the same guidance from head office?
What this page asks for
Send us a question that comes in from a unit and we build the session around it
We reply with which head office material we need, how long it takes and what you will see on screen on the day. If your network is not a fit for this product, we say that too.
First a 15 to 20 minute conversation about how guidance travels today, not about the platform. Then the proof session of 20 to 30 minutes, with the material head office sends us.
We have your unit's question. We will reply with the path of the session and what we need from head office.
We will use this information to answer your request, in line with our Privacy Policy. The question you wrote reaches our sales team by email and is used to build the proof session with your network's own material. It is not published and it is not used to train a model.
Does this scene sound familiar?
Wednesday, 11am, in a newly opened unit
The manager needs the exchange rule and calls the field consultant, who is on the road between two visits. The answer lands after the customer has left, and the unit has already decided on its own.
Friday, 4pm, in the operations meeting
Head office finds out the month's campaign ran differently across much of the network. Nobody acted in bad faith: each unit followed the last version it received, and putting it right becomes an audit, unit by unit.
Inside Synapse
The same question, in two units, with the same approved answer
It is the same sequence as the proof session: the policy head office approved, the question that comes in from a unit, the answer with the source pointed at, and the material that unit is not allowed to open.
bluey Synapse
Illustrative view of the product, with example data
01Commercial policy published by head office
02Approved by the operations team
03Available in every unit
Trindade unit · on WhatsApp · 8:12am
Can I swap the side in the combo when it runs out?
The same question, minutes later · Barreiros unit · in the network chatThe policy allows a swap within the same group of sides, with no change to the combo price, and requires the substitution to be logged at the end of the day. Both units received this answer, from the same source.
Source · Network commercial policy.pdf, page 9The passage opens in the document, on the page cited, for the unit to check
What the unit cannot open, it does not get in the answer either
Moments later, Barreiros asks what margin head office has with the supplier of that side. The spreadsheet sits in the contracts folder, restricted to the head office team: the answer does not carry the number, says that material is out of the unit's reach and points to who at head office answers for it.
01 Knows — only the approved material
02 Shows the source — the passage and the page
03 Acts — the next permitted step
04 Escalates — when it does not know, it calls a person
The limits, said up front
Three things it does not do
This is what we would say in the first meeting with your operations team. Saying it after the contract is signed, with the whole network watching, would be late.
It does not answer from anything head office has not approved.
The procedure one unit sent over, the file somebody uploaded yesterday and the screenshot from the group all show up in the list and stay out of the answers until the operations team approves them. For the network, they do not exist yet.
It does not decide which revision is current.
With two versions of the same manual approved, it cites both, the expired one included, and shows the page of each. Withdrawing the old one is still head office's work.
It does not name your files in an open channel.
Where whoever is asking is anonymous, such as a public customer channel for the unit, it names no folder and no document of the network, and answers only with the material released for that channel.
What Bluey proposes
A value sprint, with the scope closed before it starts
It is not an implementation and it is not open-ended consulting. It is a controlled experiment on one process of your network, with the decision date agreed before day one.
01problem
01process
01business owner
01set of documents
01metric
07days
In seven days, you decide. And three of the four outcomes are not a sale.
Goes to production
The narrow flow that ran in the sprint units is the same one that goes to production. Nothing is rebuilt from scratch.
Iterates once
The metric agreed at the start did not move enough. We adjust the cut, another process or another unit, and repeat, once.
No fit
The problem does not belong to this product: sometimes it is training, sometimes it is a system. We say so in the review meeting, and the sprint ends there.
Becomes a project with its own scope
The value is real, but it depends on work that does not fit in seven days, such as integrating the network's system. It becomes a separate proposal.
One process, one set of documents, one metric
Decision date agreed before day one
The proof does not require integration in production
Out of scope: open-ended consulting and system migration
Third-party proof · TECH SC · Globo NSC
There is no approved franchise case to show here, and we are not going to invent one
We do not measure and we do not publish client gains; what is on this page is the product. The proof that does exist is about the company, not about a network result: Bluey described by people who do not work here.
Watch the reportThis network operation rests on
The head office’s guidance, the same in every unit
The head-office-approved policy answers the unit with the source, respects what each one may see and sends the exception back to whoever decides. The same answer, across every unit.
The same answer, with the source
The network policy answers the unit’s question with the excerpt and the page — and the units receive the same answer, with the same source.
On each unit’s channel
Over WhatsApp or the network chat: the unit asks where it already talks and gets the answer on the spot.
Each unit sees what it may
What a unit can’t open, it doesn’t receive in an answer either: material restricted to the head office stays out of the unit’s reach.
The exception rises to the head office
A question beyond the unit’s authority rises to the head office with the whole conversation, instead of a guess.
Head-office approval
Policy published by the head office, operations team’s approval, available in every unit: nothing becomes a source before approval.
One platform for the network
Policies, manuals and procedures organized by folder, with per-unit permissions — the same platform that supports and operates.
Have you done this in a franchise network before?
No. This page is a validation door, and saying otherwise would be the easy move. The retail experience Bluey has is a centralised operation, with a single owner of the process, and that is not proof across many units. What we show here is the product running on your head office's own material, not a gain measured at another client.
Does the unit have to log into the platform to ask?
Not to ask. The question comes in through the channel the unit already uses, WhatsApp or the web chat, and the answer comes back there with its source. Whoever does have access to the platform also gets the material open on the page cited and the history of what was asked. What a person receives depends on what their folders allow, in the channel and on screen.
Who keeps this current when head office changes a rule?
Head office does. The new version arrives as awaiting approval and is only cited once someone on the operations team approves it, which is a permission separate from using the chat. While the old one stays approved, both are cited: taking the expired one down is your action, and there is no undo and no version history to catch a slip.
Can we start with a few units instead of the whole network?
That is how we recommend starting. The sprint is one process, one set of documents and one metric, with a business owner at head office and a small group of units using it for real. If the decision is to go to production, the setup that ran in the sprint is the one that opens to the rest of the network, with nothing rebuilt.
Bring the question head office answers today in the WhatsApp group
A commercial policy, an operations manual or a procedure the network already uses. In 20 to 30 minutes you see the same answer reaching two units and the page it came from.
Test a real question from your operation