CallataGuides

How to Write a Call Handling SOP

Write a one-page call handling standard operating procedure for your business: what to include, a template you can copy, and how to keep it current and used.

A call handling SOP (standard operating procedure) is a one- or two-page document that tells anyone answering your business phone exactly how to greet callers, what information to collect, where to route each type of call, when to escalate, and how fast to follow up. To write one, list your common call types, write the steps for each, attach your scripts, and post it where every phone is answered.

Without an SOP, each person handles calls their own way, which is fine until someone new starts, someone is out sick, or a customer gets three different answers to the same question. This guide gives you the sections to include and a template to copy.

What a good SOP does

  • Makes every call sound like the same business
  • Lets a new hire or temp answer competently on day one
  • Removes guesswork about who handles what
  • Sets clear response-time promises
  • Protects you on recording consent, payment data and privacy

The sections to include

1. Purpose and scope

One sentence: "This procedure covers all inbound and outbound calls on [business numbers]." Add the date it was last reviewed and who owns it.

2. Greeting

The exact words, so everyone uses them:

"Thank you for calling [business], this is [name]. How can I help?"

Background in how to answer a business phone.

3. Information to capture on every call

  • Caller's name
  • Best callback number
  • Reason for calling
  • Existing customer or new
  • Any job, invoice or account reference
  • Agreed next step and when

4. Call types and routing

The core of the SOP. A table works best:

Call type Handled by If unavailable Target
New customer inquiry Front desk, using inbound script Take full details, callback within 1 hour Answer or callback within 1 hour
Scheduling / rescheduling Front desk Text-back or callback same day Same day
Billing question Bookkeeper Message, callback same day Same day
Complaint Owner or manager Acknowledge, callback within 2 hours Within 2 hours
Emergency (your definition) On-call person Escalation chain Immediately
Vendor / sales Nobody; polite decline n/a n/a
Media, legal, government Owner only Take message, no comment Same day

Adjust to your business. Our guides on inbound lead call scripts, complaint call scripts and screening vendor and sales calls cover the individual call types.

5. Hold and transfer rules

  • Ask permission before hold; check back every 30 to 45 seconds.
  • Warm-transfer whenever possible: introduce the caller and the reason.
  • Never transfer to a voicemail box without telling the caller.

See how to put callers on hold and warm vs cold call transfers.

6. Taking messages

What a complete message includes and where it goes. See how to take a phone message.

7. Escalation

Who gets interrupted, for what, and how. A written chain: first person, second person, owner. Define "emergency" in plain words for your business. See urgent call escalation rules.

8. After hours

What happens to calls outside business hours, who checks voicemail first thing, and whether anyone is on call. See after-hours call coverage.

9. Voicemail and callbacks

Who owns the voicemail inbox, the check schedule, and callback targets. See how to manage a business voicemail inbox and scheduling callbacks.

10. Compliance and privacy

Short and specific:

  • Recording: if calls are recorded, the notice plays at the start; recording laws vary by state, and some require all parties' consent.
  • Payment cards: do not write card numbers down; follow your payment process. PCI guidance for telephone payments recommends keeping card data out of call recordings.
  • Identity checks: what callers must confirm before you discuss an account.
  • Scams: no payments, passwords or codes approved by phone; call back on known numbers. The FCC advises hanging up and calling back on an official number when a caller claims to be a company or agency.
  • Relay calls: accept calls from relay services like any other call. The FCC explains how Telecommunications Relay Service works; see calls from deaf and hard-of-hearing customers.

11. Notes and records

Every customer call gets a note on the contact: date, who, what, next step. See call notes best practices.

12. Attachments

Scripts, FAQ answers (hours, pricing ranges, service area, policies), the escalation contact list, and the ring group setup.

A one-page template

[Business] Call Handling Procedure Owner: [name] ยท Last reviewed: [date]

Greeting: "Thank you for calling [business], this is [name]. How can I help?"

Capture: name, callback number, reason, new or existing, reference, next step.

Routing: [table of call types]

Hold: ask first, check back every 30 to 45 seconds, offer callback after 2 minutes.

Transfers: warm by default; never to voicemail without telling the caller.

Escalation: [person 1, phone] then [person 2, phone] then [owner, phone]. Emergency means: [definition].

After hours: [what happens]. Voicemail checked by [name] at [time].

Response targets: new inquiry 1 hour; existing customer same day; complaint 2 hours.

Compliance: recording notice on; no card numbers written down; verify identity with [method]; no payments or codes by phone.

Notes: every call logged on the contact before the next call.

Making the SOP stick

  • Post it where calls are answered, physically or pinned in your team tool.
  • Train on it in the first week; role-play the top five call types. Use the phone training checklist for new hires.
  • Audit it with a few test calls each quarter; see how to mystery shop your phone line.
  • Update it whenever something changes, and change the review date.
  • Ask the team monthly: "Which calls did the SOP not cover?"

SOP checklist

  • Owner and last-reviewed date at top
  • Greeting written word for word
  • Information to capture listed
  • Routing table for every common call type
  • Hold, transfer and message rules
  • Escalation chain with names and numbers
  • After-hours and voicemail ownership
  • Compliance section (recording, payments, identity, scams, relay calls)
  • Scripts and FAQ attached
  • Posted where calls are answered

Running your SOP on Callata

Many SOP steps map directly to settings in Callata: business hours and after-hours routing, ring groups and extensions for routing, hold and transfers, and a recording notice that plays automatically when recording is on. Voicemails are transcribed and triaged for urgency, contact records keep calls, texts and notes together, and the Analytics page shows answer rate and missed calls so you can check whether the procedure is working.

The plan is $99 a month with five users included and $20 a month per extra user. Set up Callata and build your SOP around it.

Frequently asked questions

What is a call handling SOP?

A short written procedure that tells everyone who answers your phone what to say, how to route and escalate calls, what to record, and how fast to respond. It makes calls consistent no matter who picks up.

How long should a call handling SOP be?

One or two pages for the core procedure, with scripts and FAQs as attachments. If it is longer, people will not read it under pressure.

Who should write the SOP?

The person who answers the most calls, with the owner reviewing it. Front-line staff know which questions actually come up and where calls go wrong.

How often should a call handling SOP be updated?

Review it quarterly and whenever hours, services, prices, staff or phone routing change. Put a 'last reviewed' date at the top.