Split a mixed call into useful staff actions

The decision this workflow supports

A caller may ask about opening hours, mention a future event and raise an issue from yesterday in one conversation. A single vague summary can bury the task that needs action beneath information already supplied.

Put the review process in place

Answer approved factual questions first, then separate unresolved requests by their staff owner. Keep the same conversation reference so reviewers recognize the relationship. Read back each proposed action and avoid generating duplicate callbacks merely because the caller repeated a point.

Worked example for your team

A fictional caller asks about Saturday hours, then requests information for a staff lunch, then reports a problem from a previous visit. The hours answer is complete information; the catering inquiry and manager callback are separate unresolved tasks. Give them linked references and appropriate owners. In the readback, the assistant should ask whether those are the follow-ups the caller wants, rather than automatically creating a third task for the hours question. Review the records together to ensure the same contact preference and corrected date remain consistent across both handoffs.

Sample wording to approve

“I have answered the hours question. I can also record a catering inquiry and a separate manager callback request. Let me check that those are the two follow-ups you want.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need conversation reference, answered question, each unresolved request, owner for each action, and shared contact preference. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

The catering team receives the event details. The manager receives the visit issue. The caller’s repeated explanation does not create two copies of the same request. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides