Thrum

What is callservicesd, and why is it running on my Mac?

Last reviewed: 19 November 2026. Path, account, launchd job and man page checked on macOS 26.3.1.

callservicesd is the macOS daemon that maintains call state: it keeps track of FaceTime calls and iPhone phone calls that ring on or are made from your Mac. It is usually idle and becomes active when a call starts, rings or ends. Turning off Calls on Other Devices on your iPhone stops phone calls reaching the Mac.

callservicesd at a glance

callservicesd
Made byApple (part of macOS, TelephonyUtilities)
TypeLaunch agent
Location/System/Library/PrivateFrameworks/TelephonyUtilities.framework/callservicesd
Runs asyour user
Started bylaunchd job com.apple.telephonyutilities.callservicesd
Can you quit it?Yes, but calls in progress may be dropped. launchd starts it again when needed.

What is callservicesd?

Its man page describes callservicesd as the system daemon responsible for maintaining call state, with no configuration options. When an iPhone call rings on your Mac, when you answer or place one, and when you start a FaceTime call, callservicesd knows the call exists, which device has it, and when it ends. The audio and video of FaceTime calls are carried by avconferenced.

It lives inside the private TelephonyUtilities framework and runs as your user from the com.apple.telephonyutilities.callservicesd launchd job.

Is callservicesd safe?

Yes. callservicesd is part of macOS, signed by Apple, and lives in /System/Library/PrivateFrameworks on the read-only system volume. It runs as your user.

Why does callservicesd use so much CPU and memory?

How much CPU is normal for callservicesd?

Near 0% CPU between calls, with short activity when a call rings, connects or ends.

Memory use is typically in the tens of megabytes.

What can you do if callservicesd keeps using CPU?

  1. Stop iPhone calls on the Mac. On your iPhone, open Settings > Apps > Phone > Calls on Other Devices, and turn off your Mac in the list or turn off Allow Calls on Other Devices.
  2. End stuck calls. If a call seems to stay open, end it in FaceTime on the Mac and on the iPhone.
  3. Restart the Mac. If it stays busy with no calls, a restart resets the call state.

When should you worry about callservicesd?

Look closer if callservicesd stays above a few percent CPU for many minutes with no calls ringing or connected. A restart normally clears it.

It should run only from the TelephonyUtilities framework path above.

How do you check callservicesd in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type callservicesd in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every callservicesd process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'callservicesd' | grep -v grep

How can Thrum help with callservicesd?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when callservicesd is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click callservicesd in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions about callservicesd

Does callservicesd make phone calls by itself?

No. It tracks calls; phone calls come through your iPhone and FaceTime calls through FaceTime.

Why does it run if I never make calls on my Mac?

It is part of the system that lets calls ring on the Mac, and starts with your session. Without calls it stays idle.

Sources