Call operations
Write a call script for a caller who asks whether a manager is available
A manager-availability call script, with need questions, honest schedule wording, scheduled callbacks, and an urgent-exception path.

Table of contents
A request for a manager can mean many things. The caller may want a decision, a complaint heard, or a price exception approved. The receptionist cannot know which one from the question alone. A short script turns the request into a route instead of a guessing game.
Key takeaways
- Ask what decision or outcome the caller needs from the manager.
- Say only what the current schedule supports.
- Offer a scheduled call with a named owner and window.
- Use a separate urgent path for safety and service failures.
- Record the request and the promised window.
Ask what the caller needs
The first response should be a question, not a transfer. "What would you like the manager to help with?" gives the caller room to explain. The answer may reveal that another team can solve the problem faster. It may also show that the request is a genuine escalation.
Listen for the outcome behind the request. A caller who wants a refund is asking for a decision. A caller who wants an apology is asking for recognition. A caller who wants an exception is asking for authority. Each outcome suggests a different owner.
Repeat the need in one sentence before going further. "You need someone to approve a later delivery date" is a useful summary. The caller can correct it if it is wrong. The agent now has a route to work with.
Explain the manager's role honestly
Describe what the manager can decide and what the manager cannot. A manager may approve a schedule change but not a clinical question. A manager may hear a complaint but not process a payment. Clear boundaries prevent a wasted callback.
Do not promise that the manager will call if the manager has not agreed. A transfer to voicemail is not a scheduled call. A message in a queue is not a commitment. The caller should hear the actual next step.
If the manager is in a meeting, say so without sharing private details. "She is in a meeting until three" is enough. Avoid describing the meeting or the people in it. The schedule is the caller's business only at the level of availability.
Offer a scheduled call
A scheduled call is usually better than an open-ended promise. Offer a window that the manager's calendar can support. A two-hour window is specific enough to plan around. It is also wide enough to absorb a delayed meeting.
Ask whether the caller can take a call in that window. If not, offer a second window or a different channel. A caller who works nights may need a morning slot. A caller who is traveling may prefer email. The callback promise policy explains how to keep the promise credible.
Record the window, the time zone, and the channel. Add the manager's name and the reason for the call. The next agent should be able to see the commitment without reading the whole note. A clear record prevents a duplicate callback.
Set a response window
Use the office's standard response time unless the manager has set a different one. "Within one business day" is a real commitment. "As soon as possible" is not. A standard window helps the caller decide whether to wait.
Explain what happens if the window passes. A short apology and a new window are better than silence. The caller should not have to call back to find out why no one called. A missed window is a process failure, not a caller failure.
Track the window as part of the case. A simple field for the promised time makes the queue visible. The callback attempt limit offers a related rule for repeated attempts. A visible promise is easier to keep.
Handle urgent exceptions
Some requests should not wait for a manager's calendar. A safety issue, a service outage, or a vulnerable caller may need an immediate route. Write the criteria down and give them to every agent. An exception without criteria becomes a way to jump the queue.
Route the urgent case to the on-call owner, not to the manager by default. The on-call owner may be a supervisor or a duty technician. The important part is that someone with authority is reachable. The manager can be informed afterward.
Record why the urgent path was used. A short code and a sentence are enough. Review the exceptions weekly to see whether the criteria are too broad. A high volume of urgent cases may mean the normal route is too slow.
Record the manager request
Capture the caller's name, the need, the urgency, and the promised window. Add the manager or owner who accepted the request. If the manager has not accepted it, mark the request as pending. A pending request is not a promise.
Use a consistent subject line so the manager can scan the queue. "Approval needed: delivery date change" is easier than a long paragraph. Put the deadline near the top. Managers read the first line first.
Close the loop when the manager responds. Record the decision and the time. Tell the caller the outcome even if the answer is no. A clear no is better than an unanswered request, and the different-agent rule helps when the caller wants someone else to hear it. The record should show that the caller heard the answer.
Review manager requests monthly
Count how many callers asked for a manager and how many needed that level of authority. A high count may signal a script problem or a policy gap. A low count may mean agents are blocking legitimate escalations. Compare the count with the reasons.
Read a sample of requests for completeness. Check the need, the window, and the owner. Ask managers whether the requests arrived with enough context. Their feedback shows where the template needs work.
Change one part of the script and measure again. Try a better opening question or a shorter window. Keep the version that reduces repeat calls and missed commitments. The manager availability study shows how to compare the results.