Decide what the phone line is for
An executive office phone line serves several purposes: reaching the assistant, reaching the executive, reaching a function, and giving a human answer to an important caller. Decide which purposes the line supports and publish the alternatives. A line that tries to do everything will fail the urgent caller and annoy the routine one.
Route routine requests to a form, a shared inbox, or a function-specific number. Keep the executive line for people who have a genuine relationship or an urgent matter. The assistant should not be a switchboard for the whole organization.
State the hours, the expected response time, and the escalation path in the voicemail greeting. A caller who knows what to expect is less likely to call three times or escalate through a board member.
Open with a consistent greeting
Use a short greeting that names the office, the assistant, and the offer to help. Avoid “He’s not available” as an opening, because it invites the caller to argue. “Executive office, this is Dana.
How can I help?” is enough.
Keep your name and role consistent across the phone, email, and calendar. A caller who cannot verify who they are speaking with will try another route. If the organization uses titles, use the approved one.
Smile and slow down. The first ten seconds set the tone, and a rushed greeting makes a legitimate caller feel like an interruption. The script should sound like a person, not a recording.
Verify identity without interrogating
Ask for the caller’s name, organization, and reason for calling. For a sensitive matter, ask for a callback number and verify it against the contact record rather than trusting the number displayed. Caller ID is a hint, not an identity.
Do not confirm the executive’s location, travel, health, or schedule to an unverified caller. “I can take a message” is a complete answer. If the caller claims urgency, ask what the matter concerns and who else is involved, then follow the escalation rule.
Use the same verification standard for someone who sounds familiar. Familiarity is easy to imitate. A short, polite verification protects the executive and does not insult a genuine contact.
Sort the request into four paths
Every call should end in one of four paths: transfer to the right person, take a message for the executive, schedule a follow-up, or close with information. Decide the path before the call ends, and tell the caller what will happen next.
For a transfer, confirm the receiving person is available and brief them on the caller and the reason. A blind transfer is a second interruption. If the person is unavailable, offer a callback time rather than returning the caller to the queue.
For a message, capture the request, the deadline, the desired outcome, and the caller’s relationship to the executive. A message that says “please call back” is not actionable. A message that says “asks for a decision on the vendor contract by Thursday” is.
Take a message that can be actioned
Use a fixed message template: caller, organization, relationship, reason, deadline, desired outcome, callback number, and any reference number. Add the date and time and the assistant’s initials. If the caller refuses to state the reason, record that fact rather than inventing one.
Read the message back to the caller. This catches misspelled names, wrong numbers, and misunderstood deadlines. It also signals that the message will be handled, which reduces repeat calls.
Deliver the message through the agreed channel with the right priority. Do not send a sensitive message through a group chat. If the matter is urgent, use the escalation path and record who was notified and when.
Handle pressure and vague urgency
Callers sometimes claim urgency to bypass the process. Ask a neutral question: “What happens if this waits until tomorrow?” The answer usually reveals whether the matter is genuinely time-sensitive or simply important to the caller.
Do not promise an outcome you cannot control. “I will make sure she sees this before noon” is a commitment; “I’ll try” is not. If you cannot meet the commitment, say what you can do and when.
If the caller becomes abusive, end the call politely and record the incident. Tell the appropriate owner. The assistant should not absorb harassment as part of the job, and a pattern of abusive calls is a security and wellbeing issue.
Log calls and review patterns
Keep a call log with the date, caller, organization, reason category, path taken, and outcome. Do not log sensitive details that are not needed. The log is a service record, not a transcript.
Review the log monthly for patterns: a function that repeatedly routes callers to the executive, a vendor who calls every week, a caller who refuses to use the proper channel. Fix the routing rather than adding more screening.
Share the patterns with the executive in a short note. If the line is receiving matters that belong elsewhere, the fix may be a published contact page or a delegation. The phone script is a control, but the routing decision is a management choice.
Background sources consulted for this workflow: Business Guidance; Cybersecurity Framework; Privacy Framework.