Explore Mossy

Transfer a call without making the customer start again

Give the person taking over a short, usable summary.

All blog posts

A good transfer starts with a reason. Collect the caller’s name, a suitable reference and what they want to happen. Record any checks already completed and keep the summary short enough to read before answering.

Route the call by responsibility. Booking exceptions may go to a duty manager while billing enquiries go to finance. Decide who covers each queue outside normal opening hours and when to offer a callback.

Test the path when the destination is busy. Capture how the caller can be reached, set expectations and assign the callback. The handover is complete when somebody owns that next action.

Help the receiving colleague start in the right place

Imagine a customer has already explained that they want to change the number of guests on a reservation. A useful handover states the reservation reference, current party size, requested party size and any action already taken. The receiving colleague should get the detail that affects the decision without having to skim an entire transcript while the customer waits.

Agree how to distinguish facts from assumptions. If the booking was found, include the reference. If the reference could not be confirmed, say so and pass the clues you can use to find it. Keep the customer’s requested outcome in their own words when a paraphrase could change the meaning. Avoid copying unrelated details into the receiving queue.

Choose the route by what needs to happen

Routing to the team named first in a customer’s sentence can send the call to the wrong place. A caller may say they want sales when they actually need an invoice corrected. Use the requested outcome to select the team, and agree which requests can be handed elsewhere if that team is unavailable. Maintain a rota or destination list someone can update.

Test the transfer with a busy destination, an unanswered extension and a caller who hangs up mid-transfer. The fallback could create a callback task with a contact number and a clear owner. Give the customer an honest estimate of when someone can respond. Record the state so the same enquiry does not create several unowned requests.

Audit the handover with the people using it

Ask a colleague to take a test transfer and explain what they would say first. If their opening question repeats information already captured, check where the note is displayed and what it says. Move the important fields to the top or shorten the wording. The colleague may need a prompt on the case itself, where they are already working.

Review a handful of real handovers each week during the pilot. Count repeat explanations, incorrect routes and callbacks that never reached the customer. Check the exceptions alongside the smooth calls. Use what you find to adjust the briefing fields, team routing or fallback until staff can take over without unpicking the earlier conversation.

Check how the transition sounds to callers

Explain why the call is being passed on and whether the person taking it already has the main details. Avoid making the caller listen to an internal summary when a short update will do. Test how much silence or hold time the customer experiences, and agree when to offer a callback. This makes the handover understandable from the caller’s side as well as the receiving team’s side.

Explore related Mossy features

Cookie preferences

Essential storage remembers your choices. Optional analytics measure site use.