Where the work gets stuck
A support process should give customers an answer or send them to someone responsible for helping. Watermelon’s shared inbox and transfer to staff can help when routine questions and individual cases arrive together. Evaluate the whole conversation, including whether the customer received useful help.
What to prepare
- Routine categories and approved answers
- A named receiving team and support hours
- Rules for complaints, uncertainty, and unavailable staff
Follow these steps
- Choose a routine category with stable public information.
- Test the agent with routine questions, unclear requests, and messages from unhappy customers.
- Make sure a request to speak to a person reaches staff with the necessary details.
- Review resolution and repeat contacts alongside automation volume.
An example from everyday work
A return-policy answer may resolve a shopper’s question. If the shopper explains that an earlier return was rejected, the case should go to staff with the available context. Repeating the return policy does not resolve that dispute.
When your team should take over
Do not make the only contact route a loop of AI questions. Plan the experience when staff are offline and make response expectations realistic.
How to check the results
- Questions resolved without repeat contact
- Successful transfers to staff and the time taken to respond
- Customer feedback on the actual resolution
Your next step
Read conversations passed to staff as part of every pilot review. That is where the support process often needs the most attention.