My staff answer the phone, but every decision still comes back to me. How do I fix that?

In this guide

• Find out why they still need you
• Use the recurring questions to choose your first three notes
• Note 1: “Can you deliver this Friday?”
• Note 2: “Can I move my appointment?”
• Note 3: “Does delivery include taking it upstairs?”
• A short template you can actually maintain
• Try the notes before relying on them
• Where Call Nerd helps

THE SHORT ANSWER

Start with three customer questions that repeatedly reach you. For each, establish what staff need to know, which decisions they can make and when they must escalate. Write a short decision note, practise an ordinary case and an exception, then review what still comes back. Call analysis can reveal the questions; the owner must supply the policy and authority.

Your staff pick up the phone. Then someone asks you whether Friday delivery is possible, whether an appointment can move, or whether a particular service is included. You answer between other jobs. Tomorrow, a similar question comes back.

The handoff happened at the phone, but the decision stayed with you.

Start by turning three recurring customer questions into three usable staff decision notes. Each note should give the person an answer or a place to check, permission to act within a boundary, and a route for exceptions. The examples below are fictional rules for a small service business, not policies to adopt unchanged.

Find out why they still need you

Before telling staff to be more independent, ask about one recent escalation: “What was missing that stopped you finishing this?”

On a small screen, swipe the table to see all columns.

What stopped the decision?	Example	What the owner needs to change
Information	Only you can see the delivery schedule	Give the relevant person access to the current record
Guidance	Staff do not know whether a date is confirmed or provisional	Define what counts as confirmation and what to say while waiting
Authority	Staff know an open appointment exists but need your permission to offer it	Explicitly delegate that decision within agreed limits
Practice	The rule exists, but staff struggle to apply it to a changed situation	Rehearse an ordinary case and an exception
A real exception	The request falls outside capacity or agreed service	Keep an escalation route with a named decision-maker

A script cannot fix a schedule nobody can access. Training cannot grant authority you have withheld. And a justified exception is not evidence that the employee has failed.

Ask yourself a second question: “If they followed the written rule and I would have chosen differently, would I still support their decision?” If the answer is no, the rule needs work before you delegate it. Quietly reversing decisions made within the agreed boundary teaches people to ask you again.

Use the recurring questions to choose your first three notes

Look through a manageable set of recent calls and the questions staff brought to you. You can do this from existing notes, a shared log or authorised recordings. Write down the customer's question, the staff member's decision, and what they needed from you.

Keep the two questions separate:

• Customer: “Can you deliver this Friday?”
• Staff: “Am I allowed to confirm Friday from the schedule, or must you approve it?”

The customer question alone does not tell you why the call was escalated. Ask the person who handled it. The missing ingredient could be access, permission or information that was not said aloud.

Group similar questions, but keep exceptions visible. A routine date enquiry and a request for an urgent delivery outside your normal area might share words while requiring different authority. If you need a method for grouping the evidence, start with the recurring-question guide.

Choose questions that recur and have a reasonably stable answer or decision boundary. You do not need to document the whole business before helping with the next call. GOV.UK's service guidance similarly emphasises involving frontline staff and keeping them informed when the service changes. It concerns public services; the three-note exercise here is our practical adaptation, not a validated management intervention.

Note 1: “Can you deliver this Friday?”

The problem: the owner keeps interpreting the delivery schedule for everyone else.

Check: the current order record and delivery schedule. A requested date is not a confirmed date. In this fictional business, the schedule must show both a confirmed slot and the order cleared for dispatch.

Staff may decide: when both conditions are met, confirm the recorded slot without asking the owner again. Do not create a new slot or override a dispatch hold.

Say: “Your order is confirmed for Friday in the current schedule.” If either condition is missing: “Friday is not confirmed yet. I will check with dispatch and update you by [time I have arranged].”

Escalate when: the customer needs an exception, records conflict, or dispatch cannot resolve the uncertainty within the agreed update window. Send the order reference, the requested date, what the record shows and the decision needed. The dispatch lead is the first contact; the owner is the named backup.

Record: what was confirmed, or who owns the check and when the customer will hear back. An update can honestly say that the date is still unknown; it must not silently become a delivery promise.

The operational change is access to an authoritative schedule plus permission to communicate it. If dispatch never confirms dates, another staff note will not repair that process.

Note 2: “Can I move my appointment?”

The problem: every ordinary booking change waits for the owner, even when a suitable slot is available.

For this fictional example, consider only changes allowed without a fee under the business's existing booking terms. Disputes about fees or cancellation terms need their own review.

Check: confirm you are authorised to change this customer's booking, then check appointment type, duration, required staff and available capacity.

Staff may decide: offer an available slot of the same service type and duration during normal hours, provided it satisfies the existing booking rules. Do not displace another customer's booking, shorten the appointment or add overtime.

Say: “I can offer Tuesday at ten or Thursday at two. Which works for you?” Make the change only after the customer chooses; do not release their current booking merely because they asked about alternatives.

Escalate when: there is no suitable slot, the customer needs a different service, the rules do not cover the request or an exception is required. The scheduling lead owns that decision, with a named backup when absent.

Record: the agreed new appointment in the shared booking system, release the previous slot as part of the confirmed change, and send the normal confirmation. Follow the system's booking procedure so two people cannot promise the same slot.

Here, writing a nicer answer is not enough. The person needs permission and system access to complete the change. Otherwise “I will ask the owner” remains the only honest answer.

Note 3: “Does delivery include taking it upstairs?”

The problem: staff pass every question about included service to the owner, or improvise an answer to keep the conversation moving.

Check: the service description supplied with this order. In this fictional business, standard delivery is to the agreed ground-floor access point; upstairs placement is a separately assessed service. A customer's specific order may include an approved exception, so check the actual record.

Staff may decide: explain the recorded service and collect details for an assessment. They may not promise upstairs placement, quote an unapproved charge or infer that the driver will “probably do it.”

Say: “The delivery on this order is to the agreed ground-floor access point. I can ask the delivery team to assess upstairs placement. It is not confirmed yet.”

Escalate when: the order wording is unclear, the customer says something different was promised, or the request needs an assessment. Send the relevant order wording and practical access details to the delivery lead. Do not dismiss a disputed promise just because it is missing from one screen.

Record: the request, who is assessing it and the agreed update time. Follow the team's safety process for access concerns; a customer-service note is not authority to improvise a physical delivery method.

This note deliberately keeps the exception with someone qualified to decide. Staff independence includes recognising the boundary and making a useful handoff.

A short template you can actually maintain

Use one note per recurring decision. Keep it in the place staff already consult while working. A second, conflicting copy in a chat thread creates another reason to ask the owner.

Copy this structure, or download the staff decision-note worksheet:

• Customer asks: the question in ordinary language.
• Check first: the current record or approved policy, and where to find it.
• You may decide: the permitted action and its limits.
• You may say: wording that preserves what is confirmed and what is unknown.
• Escalate when: the exceptions, decision-maker and backup.
• Send with the escalation: the facts and specific decision needed.
• Record and follow up: where the result goes, who acts next and the update time.
• Approved by / effective date / review trigger: who owns the rule and what change makes it need review.

The owner or authorised manager must approve the note before it becomes policy. Fill in the names, permissions, systems and limits; do not leave staff to invent them from placeholders.

If the difficulty is that nobody knows what a role owns at all, our sister project Resume Ranker has a guide to turning scattered work into a clear hiring brief. That is a broader job-design problem than one recurring call question.

Try the notes before relying on them

Ask a staff member to work through one ordinary example using only the note and the records it points to. Then change a fact:

• Friday appears on the order, but dispatch has not cleared it.
• A new appointment is available, but it is shorter than the booked service needs.
• The customer says upstairs placement was promised in an earlier message.

Ask: “What would you check, what could you decide, what would you say, and what would you record?” If two people interpret the boundary differently, revise it together. The staff-training guide explains how to turn a reviewed call into a short practice exercise.

During an initial review period, record when the note helped and when someone still needed a decision. Look at those cases with the team. Was the rule missing, inaccessible, unclear or genuinely outside its scope? Did the owner remain the only person allowed to act?

Do not make zero escalations the target. Fewer questions could mean clearer authority, but could also mean people are guessing or avoiding help. Check the decisions and customer follow-through alongside interruptions. A busy week and a quiet week are not a fair before-and-after comparison by themselves.

Where Call Nerd helps

Call Nerd can surface recurring customer questions and the transcripts behind them, giving an owner concrete examples to review with staff. Its weekly briefs can help identify topics worth discussing. You can then use the same questions to choose and revise the decision notes.

That does not automatically reveal why an employee asked for help, create an approved policy, grant permission or prove a customer issue was resolved. The owner supplies the business rules; the team needs access and authority to use them. Individual commitments still belong in the working customer record—see the CRM and call-analysis distinction.

You can begin with a manual question log. The useful outcome is that the next person has enough information and permission to handle the ordinary case, and knows exactly what to do when it is not ordinary.