Explore Mossy

Write an inbound call brief your team can test

Set out what Calls can answer, capture and assign.

All blog posts

List the five reasons customers call most often. For each one, write down what information can be shared, what needs to be captured and what outcome should be offered. Use examples your team recognises.

Include the moments that need a person. A caller might ask to speak to the team, the answer may be unavailable or the request may fall outside a policy. Agree destination queues and a fallback when nobody is available.

Read the brief against real situations before rollout. Check unclear answers, competing requests and silence at the other end. Ask the people receiving handovers whether the brief captures the details they actually need.

Start with one call reason

Write down the calls your team handled yesterday and group them by what the caller wanted to achieve. A booking request, cancellation and availability question may mention the same service but need different outcomes. Pick the most common narrow reason with a clear ending. Describe that ending as something the next person can verify in the diary, queue or customer record.

For each question in the script, ask which decision depends on it. A postcode may determine coverage, while a long description may be unnecessary if the caller only wants opening times. Put essential details first and leave optional questions until you know they apply. Decide what the caller can skip and how a colleague can finish the job later.

Document answers and exceptions together

Give each response an approved source. Opening hours can come from the business guide, while live appointment availability needs the diary. Say what to do if two sources conflict or the diary is unavailable. A callback with a clear owner is a better outcome than a time offered on an assumption. Make the expected handover easy for the caller to understand.

Write a route for someone who asks to speak to a person or needs help outside the brief. Name the receiving team and its normal hours. If the team is busy, decide whether to ask for a callback number or offer another approved channel. Use the same routing rules the business can support during its busiest period.

Walk the brief through real situations

Read the brief out loud while another colleague plays the caller. Have them change their mind halfway through, give an unclear reference and ask a second question. Record where the flow keeps asking for information it already has. Check whether the final result reflects the latest request and gives the customer an accurate summary.

Ask the team receiving the work to review a test handover with no extra explanation. If they can identify the request and the next step, the brief is ready for a narrow pilot. Keep a simple version record so fixes to phrases, routing or information sources can be linked to the examples that prompted them.

Give someone ownership after launch

Make one person responsible for receiving corrections and updating the approved brief. If a branch changes its hours, that person should know which answer needs an update and how to check that the revised information appears on calls. Review requests that fell outside the brief and decide whether each one deserves a new path or should continue to go to a person.

Explore related Mossy features

Cookie preferences

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