Two businesses can share an office team while needing different greetings and customer expectations. A caller who contacted one brand should not hear the other brand's prices or receive a follow-up with the wrong company name. Start with a simple model: one company account, its approved business identities and verified phone routes.
A shared CRM should preserve the source of each enquiry. That source is useful for staff context and reporting, but it must come from reliable routing evidence rather than a guess based on the caller's number.
Give every route a clear meaning
Document which number or verified route represents each business. If two brands use the same destination with no source information, the receiving system may be unable to distinguish them. Where the source is unknown, show that uncertainty and let the team ask the caller instead of silently assigning a brand.
Separate identity from shared operations
A shared team does not require identical policies. Review each brand's public name, service list, hours, pricing rules and escalation contacts. Reuse a policy only when the administrator has approved that relationship. The same voice can represent different businesses while drawing on the correct company-approved knowledge for each route.
Carry the source into the next step
The business identity should remain visible in the call record, follow-up and reviewed CRM delivery. This helps a representative greet a returning caller appropriately and keeps reporting meaningful. A lead record should not lose its original source merely because the team later works from a central customer view.
- Verified receiving route.
- Business name used in the greeting.
- Knowledge set used for answers.
- Source retained in the follow-up and CRM mapping.
Test both correct and unknown sources
Place fictional test calls through each approved route and inspect the resulting records. Include a call whose source cannot be verified. Confirm that the workflow leaves it unknown instead of borrowing the primary business by default. Repeat this check when numbers, forwarding rules or CRM mappings change.