WhatsApp in a network: one number per unit, a single number, or both?

Who sees what: the decision that prevents conflict

The most sensitive question in a network is not technical, it’s political: can the franchisor read the franchisee’s conversations? The answer must be defined in writing before any implementation, and the design that usually works separates three levels:

• Franchisee: full access to conversations and the unit’s own database.
• Franchisor: access to indicators for all units — volume, response time, conversion, reasons for loss — and conversations only in contractually defined situations, such as quality audits and complaint investigations.
• Agent: access only to conversations assigned to them.

Leaving this vague produces one of two extremes: either the franchisor becomes a daily reader and the franchisee sabotages adoption, or no one can investigate when a customer complains. It’s also worth recording each party’s role in handling customer data, a point addressed in LGPD on WhatsApp — in a network, franchisor and franchisee usually have distinct responsibilities over the same database.

How the lead reaches the right unit

With a single number, distribution needs clear rules. Four criteria, from simplest to most precise:

1. Ask in the first message: "Which city are you from?" Simple, effective, adds a step.
2. Unique link or QR per unit, with a pre-filled message identifying the origin. Eliminates the question and also tracks promotion — the same logic as link and QR code.
3. Regionally targeted ads, each campaign pointing to the number or identifier of the unit serving that area.
4. Rule by postal code, when the network has defined territory and the customer provides the address early on.

Whatever the criterion, the essential part is what happens when no one responds: there must be a reassignment rule. A lead stuck in a unit that does not respond within X minutes should go to another person or to the central team — otherwise the customer is lost while the network thinks they are being served.

The cost of slow response in a network

Network with 14 units, average of 240 leads per unit per month, average ticket of R$ 620.

There is no media investment in this calculation: these are the same leads, answered better. The franchisor’s role here shifts from demanding targets to showing differences between units — and peer comparison usually motivates franchisees more than any announcement.

What to standardize and what to leave flexible

Over-centralizing kills local relationships; under-centralizing maintains chaos. The division that works:

• Standardize: maximum first response time, greeting and absence messages, price and commercial condition information, discount policy, complaint handling, and the text of approved templates.
• Leave flexible: tone of conversation, local relationship initiatives, contact schedules with regional customers, actions with neighboring businesses.

The practical rule: standardize what protects the customer and the brand; leave free what depends on knowing the neighborhood. A franchisee who loses autonomy to relate to their own base loses precisely the advantage of being local.

How to implement without backlash

1. Start with two or three pilot units, preferably with franchisees who already complain about disorganization. They become advocates.
2. Show the gain from the franchisee’s perspective first: fewer lost leads, history that doesn’t disappear when an employee leaves, divided service without confusion. Adoption based on enforcement doesn’t survive past the third month.
3. Migrate the number, not the entire database at once. Connecting the existing number preserves ongoing conversations and avoids the worst moment of any transition, when the customer talks to a dead number.
4. Train with real cases from the network itself, not with generic material — the same principle as training the team on the CRM.
5. Publish the comparative dashboard by unit starting from the second month. Transparency among peers accelerates adoption more than any contract rule.

What the network gains in brand consistency

There is a benefit that rarely enters the project justification and is often the most valuable in the long term: the customer experiences the same service in any unit.

This manifests in concrete ways:

• Same response time, regardless of which store they contacted.
• Same price and condition information, eliminating the awkward situation of two units charging differently for the same item without justification.
• Same complaint handling, with a defined process instead of depending on each manager’s style.
• Continuity when the customer moves city, since their history exists in the network and not just on that device.

For a network, consistency is the product. Customers choose a known brand precisely to avoid surprises — and a unit that responds in three hours when others respond in five minutes breaks that promise without anyone noticing, because this failure never reaches the franchisor’s dashboard while service is on individual phones.

How to add a new unit without rework

In a growing network, each opening is an opportunity to do it right from the start — or to repeat improvisation. An opening checklist solves this:

1. Number defined and verified before opening, preferably a local landline already appearing in promotional material.
2. Connection to the platform on day one, with users created for the manager and team.
3. Preloaded drip campaigns and ready responses, copied from the network standard instead of written from scratch by the unit.
4. Complete commercial profile, with name, address, and hours of the specific unit.
5. Training before opening, not after the first hectic month.

A unit that opens with the structure ready reaches the network standard in weeks. One that opens improvising takes months to correct — and in that interval forms habits that later cost a lot to undo.

Mistakes that stall the network

• Forcing without showing value. Franchisees adopt the minimum to comply and continue serving through personal phones on the side.
• Central team responds instead of the store. The customer senses the distance and the unit loses local connection.
• Allowing new units to join without structure. Every opening should start with the number connected and the drip campaign configured.
• Not defining what happens when a unit closes or changes ownership. Who owns the number and database? This must be in the contract, not just a conversation.

This last point causes the most conflict and is the least discussed during implementation. Defined early, it’s a two-line clause. Defined after the unit closes, it becomes a dispute over a customer base that no one knows who owns.