Accounts and sub accounts explained + use cases
Web1on1 is designed and built as a collaborative Messaging system. Allowing for different collaborative messaging use cases.
- A OEM or national Sales organisation can set up multiple brands as sub accounts;
- A Dealership can break up its account (eg when it has multiple brandnames or business units).
This article intends to clarify the implications and use cases of different account / Sub accounts scenarios.
Use Case: Brand - Dealers account Structure
- 1 invoice at NSO level
- All users are billed at NSO level
- Each dealer can have it's own channels and add-ons
- Reporting at NSO level, filtered to Dealers
Use case: Dealer - Business Units
- 1 invoice at Dealer level
- All user-licenses are billed at Dealer level
- Each Business-Unit can have it's own channels and add-ons
- Reporting at Dealer-level, filtered to Business Units
Use case: Client Contact Center - Country Teams
- 1 invoice at CCC level
- All Sub-account, user-licenses are billed at CCC level
- Each Team can have it's own channels and add-ons
- Reporting at CCC-level, filtered to Country teams
Upstream rights management
This tree-structure allows for granular user rights.
Level 3 (Division) users can handle level 3 conversations
Level 2 (NCS / Dealership) user can handle Their level 2 and all associated level 3 organisations
Level 1 (Web1on1) users can assist Level 2 and Level 3 organisations.
Downstream resource sharing
Reversely up-level organisation resources can be shared with Child organisations / sub accounts
What can be shared?
- Users Agents
- Know how
Create a Child-organisation as a Level 2 Account Admin
You now have 3 sub organisations which can have their own resources (agents, integrations, routing, knowledge).