SYNTHROPHIC- Customer need
- A customer asks about an existing service request.
- Channel
- Web chat, voice or WhatsApp preview
- Available context
- SR-218 is assigned. Completion time is unknown.
- Automation
- Acknowledge the status; prepare a source-grounded update.
- Human boundary
- A coordinator must confirm timing. The draft remains unsent.
COMMUNICATION / PROPOSED USE CASES
Start with the customer’s need.
Three understandable patterns, each with its own context and human boundary. These are proposed examples, not a list of validated production capabilities.
- Customer need
- A customer asks when a service desk is open.
- Channel
- Web-chat sample
- Available context
- FAQ-01 supplies explicitly fictional service hours.
- Automation
- Select the answer that the sample source supports.
- Human boundary
- Questions outside the supplied FAQ get a limitation and an escalation option.
- Customer need
- A customer wants to change an existing request.
- Channel
- Voice transcript or WhatsApp-style preview
- Available context
- A conversation and the available service reference.
- Automation
- Identify the need for review and attach the conversation.
- Human boundary
- No booking or service change is made. A human owns the decision.
LET’S THINK IT THROUGH