Sample call categories before changing coverage

The decision this workflow supports

Before changing an answering script, learn what callers actually ask during the relevant service. A small reviewed sample can reveal repeated information questions or misrouted requests without turning every conversation into a sales claim.

Put the review process in place

Choose a sampling period and classify calls using the restaurant’s agreed categories. Record unanswered questions and whether staff follow-up was needed. Avoid inferring lost revenue from a missed call; discuss the underlying examples with the owner before changing coverage or staffing.

Worked example for your team

Use a fictional service sample containing questions about hours, table requests, a supplier message and an unanswered catering inquiry. Have two reviewers categorize the calls using the same definitions, then discuss disagreements. A long conversation is not automatically a valuable lead, and a brief question is not automatically wasted time. Look at the task and unresolved work. If the repeated issue is callers missing the website’s hours, the improvement may be clearer information rather than a longer answering script. Tie the proposed change to those observed questions.

Sample wording to approve

“Staff review prompt: what was the caller trying to do, was approved information enough, and what task remained for staff? Classify the request without guessing whether it would have become a sale.” This wording is a draft for the restaurant owner to approve before use.

Fields for the staff handoff

Staff need sample period, caller task category, answer source, staff action needed, and reviewer. Mark uncertain details explicitly and keep the requested action separate from anything restaurant staff have already confirmed.

Acceptance tests before use

Two reviewers can explain their categories. Unsupported revenue estimates are excluded. A proposed script change points to the actual questions that motivated it. Record the observed result, assign any mismatch, and repeat the affected scenario after correction.

Related guides