The distinction that changes the decision
A new social enquiry asks for a resource or information. Messaging automation can organize that requested response and route an exception. An existing customer with an unresolved issue needs continuity, status and a responsible person.
Check your actual workflow
Read ten real enquiries and mark whether each one can finish with an answer or needs investigation. An acknowledgement is only the start of an issue. If both types are common, document the handoff between the social response and the support record.
Run this boundary test
Check whether the operator can see the original request, attempted answers and resolution status. A shared screen is useful only if it preserves that context.
When to pause
Promotional content in a complaint flow, repeated qualification questions and automatic closure without confirmation are signs that the boundary has been missed.
Compare the actual requirements
Scroll horizontally to read all columns.
| Decision | Messaging response | Helpdesk resolution |
|---|---|---|
| Starting item | A relevant request for information or a resource | A customer problem that remains open |
| Record | Request, delivered response and handoff state | Case history, priority, owner and resolution state |
| Completion | The requested answer is delivered or correctly handed over | The issue meets the agreed resolution condition |
| Failure to test | The response does not answer the question | A case is closed while the customer still needs help |
A worked boundary decision
A customer asks for a sizing chart, then explains that a previous order arrived damaged. The first action can be a requested-resource response. The second requires a case with its own owner and resolution condition. Repeating the sizing-chart automation would lose the change in task.
If the work crosses the boundary
Carry the source message, resource already delivered, customer context and unresolved question into the support record. Assign the receiving person and make the unresolved state visible. Do not count the routing event itself as a resolution.
Use this review sequence
- Trace one enquiry that stays a simple question and one that becomes an issue.
- Confirm that the same conversation does not receive a promotion while an operator is resolving a complaint.
- Check that the receiving operator can see the original question without asking the customer to repeat it.