Agent Grouping Why & How?

WHY?

A. NGU wants to sell some products in a set of shops
Examples:

• bPower20 pilot will take place at Homa Bay shop in Kenya, so only Homa Bay shop will be allowed to sell this product

• Bboxx Rwanda received a grant for customers in Eastern region to get discounted prices. Agents from only three shops will need to sell ESF bPower50 with a discounted price.

B. NGU wants to have specialized agents

Examples:

• Bboxx DRC wants to have a specialized team for bPower300.

• Some agents should only be able to sell Cook products.

HOW?

A. Configuration

• Products can have 0 or one ‘product public category’

• Sales agent can be linked to 0 or multiple ‘product public category’

B. Impact

• Products without ‘public category’ are visible by all agent. At release, all products will have ‘product category’ blank to avoid any impact before NGU requests specific configuration

• On the sales app, Products with a specific ‘public category’ are visible by each agent linked to that category

• The filter doesn’t apply in ERP: In ERP/’New lead creation form’ any customer can be linked to any agent with any products.

C. Who

• Product configuration will be handled by Supply Chain via support ticket (which means that NGUs will have to create a ticket requesting for the configuration)

• Sales agent configuration will be handled by the NGU sales agent admin