Initial customer conversation
Understand the customer need before handing it to a specialist.
- Managers repeat basic questions and receive enquiries without context.
Example paths: the agreed action or human review. This diagram does not run on your live data.
- 01Input: Enquiry · questions.
- 02The assistant asks agreed questions about needs, scope and timing, records answers and sends a brief to the appropriate specialist.
- 03Output to verify: Brief for manager.
- 04Unknown services, a request for a person or missing information trigger a handoff; prices and commitments are not invented.
- ✓The brief retains customer answers, unresolved questions and conversation sources; a manager decides what to offer.
- ✓We check repeated processing and connection failures using agreed examples.
An illustration of the logic, not a customer case. Connections and results are agreed before implementation.
What inputs do we need?
We need an example of “Enquiry · questions”, processing rules and an owner for “Brief for manager”. Access is requested after connections are agreed.
What happens if data is missing or an error occurs?
We check “Enough information?”. Unknown services, a request for a person or missing information trigger a handoff; prices and commitments are not invented.
How is the result accepted?
The brief retains customer answers, unresolved questions and conversation sources; a manager decides what to offer.
How long does implementation take?
Scope, price and timing are defined after checking systems, access and exceptions. This page describes a possible workflow, not a ready connection to your data.