Call operations
Write a call script for a caller who asks for a named employee
A call script for named-employee requests, with relationship questions, availability wording, message capture, and a safe transfer rule.

Table of contents
A caller who asks for a named employee often believes the request is simple. The employee may be the only person who knows the history, or the caller may have been told to ask for that name. The receptionist has to respect the request without promising a connection that may not exist. A written script keeps that balance consistent across shifts.
Key takeaways
- Ask how the caller knows the employee before routing.
- State the employee's availability only if the schedule is current.
- Capture a message that the employee can act on without calling back.
- Offer a scheduled call instead of an open-ended promise.
- Protect private schedules and personal contact details.
Why the request sounds simple
The caller says a name and expects a transfer. From the caller's side, the name is the shortest path to the person who can help. From the office side, the name may be one of several people with similar roles. The script has to bridge those two views without making the caller repeat everything.
A named request is also a trust signal. The caller may have a direct relationship with the employee or may have been referred by someone else. Treating the request as ordinary can feel dismissive. Treating it as urgent can bypass the queue for the wrong reasons. The agent needs a few facts before choosing a route.
Do not confirm whether a person works at the office until the purpose is clear. A name alone is not proof of a relationship, and a caller may be testing whether the name is real. Ask an open question about the reason for the call. The answer usually shows whether the request is routine, sensitive, or urgent.
Ask about the relationship
Use a neutral question such as "How do you know this person?" The answer may be a project name, a referral, or a family connection. Each answer suggests a different routing path. Write the relationship in the note in the caller's own words where possible. The note should carry the same words the caller used.
Ask what the caller needs from the employee, not only who they want. A caller may ask for a name when any trained agent could solve the problem. The need is the useful part. The name is one route to meeting it.
If the caller declines to explain, do not press for personal details. Offer the standard queue or a message instead. A refusal to explain is not proof of a bad actor. It is simply a boundary that the office should respect.
Set a reachability script
Say what the office can check and what it cannot. "I can see whether she is scheduled today" is honest. "She is at her desk" is a claim that may be false by the time the transfer lands. Use the schedule, not a guess.
If the employee is available, confirm that a transfer is acceptable. A caller may prefer a message once they hear the person is busy. Ask before sending the call through. That small check prevents a dropped transfer and a frustrated caller.
If the employee is not available, say when a reply is likely without inventing a time. Use the office's stated response window. A window of "today or tomorrow morning" is more useful than "soon." Record the window in the note and repeat it to the caller. A clear window is better than a vague reassurance.
Protect the employee's schedule
Do not read out a personal calendar or a home phone number. The caller needs to know when a reply is possible, not where the employee is at every hour. Share only the availability the office has approved for external use. A schedule detail can become a privacy problem in the wrong hands.
For senior staff, use a gatekeeping rule rather than a hard refusal. The caller can leave a message with the reason and the deadline. A manager or assistant reviews the message and decides on the route. This keeps the decision with the person who owns the time.
If the caller claims an emergency, move to the urgent-call script instead of the named-employee script. An emergency route should have its own criteria and its own owner. The name of the employee does not create an emergency. The situation does.
Take a message that works
A useful message contains the caller's name, the reason, the deadline, and the best reply channel. It also contains the relationship to the employee. Without the reason, the employee cannot judge priority. Without the deadline, the message may sit too long.
Read the message back before ending the call. Confirm the spelling of the caller's name and the callback number. Ask whether the caller wants the reply by phone or email. A quick readback catches most errors while they are still easy to fix.
Tell the caller what happens next and who owns the message. "I will place this in her queue and she will see it today" is a clear handoff. Avoid saying the employee will call if the employee has not agreed. The callback promise policy applies here as well.
Handle the caller who insists
Some callers will not accept a message or a queue. They may raise their voice or threaten to escalate. Keep the tone even and repeat the options once. Do not match the pressure with a promise the office cannot keep.
Offer a scheduled call with the employee or a supervisor. A fixed window gives the caller something concrete. It also protects the employee from an unexpected interruption. Record the window and the owner of the call.
If the caller remains abusive, end the call under the office's conduct policy. Note the behavior factually and pass the record to a supervisor. A named-employee request does not require an agent to absorb abuse. The different-agent rule offers language for that handoff.
Review named requests monthly
Count how many callers asked for a named employee and how many reached that person. Group the requests by employee and by reason. A high volume for one person may signal a process that depends on them. That dependency is a risk, not only a compliment.
Read a sample of messages for completeness. Check that the reason, deadline, and owner are present. Ask employees whether the messages gave them enough context. Their feedback is more useful than a satisfaction score.
Change one part of the script and measure again. Try a scheduled window or a different opening question. Keep the version that reduces repeat calls and missed connections. The named-employee study shows how to compare results over time.