Index
Business customers usually have multiple contacts for purchasing, operations and finance. Account-oriented service helps gather context without giving everyone access to every conversation.
How to evaluate this decision
Model company, contacts and their links. Identify what information can be shared internally and what needs to be restricted. A request made by a user does not authorize the disclosure of contracts or data from other departments. The team must see relevant relationships and confirm identity or authorization when the action requires it.
Criteria for comparing proposals
- Links: maintain contacts associated with the account and record role changes or terminations.
- Context: Gather requests related to control over restricted messages and attachments.
- Responsibility: distinguishing account owner from person responsible for specific service.
A scenario to discuss with the supplier
Hypothetical example: two people from the same company report the same incident. The system can list tickets without exposing one of them to attachments sent by the other that are not necessary for resolution.
What to validate upon delivery
Test contact without confirmed link, person disconnected and related requests. Check that the search by company does not unduly expand access to sensitive data.
Prepare the conversation about the project
Quantum9 can integrate customer service, CRM and portal. Provide account structure, roles and types of information to design the shared vision with the necessary limits.
Conversational commerce · Map the company's priority