What Is a CRM?

How a CRM Works

A CRM is a filing cabinet with one folder per customer, and the folder fills itself.

1. A record is created the first time a person contacts you. Name, phone number, address, and how they found you.
2. Every touch attaches to it. Calls, texts, quotes, booked jobs, invoices, and notes all land in the same folder.
3. The phone number is the key. When that number calls again, the CRM matches it and pulls up the record, so whoever answers already knows the history.
4. Follow-ups live there too. A quote sent Tuesday with no answer by Friday shows up as something to do.

There are two kinds. A standalone CRM is its own product. It is powerful, but it only knows what someone types into it or what another tool sends it. A built-in CRM lives inside your phone system, booking app, or AI receptionist. Because that tool already handles the call, it can write the record on its own.

The connection between tools usually runs on webhooks or an API. A webhook is a short message one app sends to another the moment something happens, like "call ended, here is the summary." An API is the door the other app opens to receive it.

Example of a CRM

A plumbing company has a crew of three and takes about 250 calls a month. In March, a homeowner calls about a slow drain. The CRM creates her record: name, address, the call recording, and the $400 drain job she books.

In August, the same number calls. The record pops up before anyone says hello: "Jane, 14 Oak Street, drain cleaning in March, $400, paid." Nobody asks for her address again. She needs the water heater looked at this time. That is a second job, and it gets booked in two minutes.

Now do the math the CRM makes visible. Two calls a year at $400 each is $800 a year. Over five years, that one folder is worth $4,000. That is her customer lifetime value, and the CRM is the only place it shows up. Without the record, she is a stranger every time she calls, and the August call is just as likely to go to whoever answers first.

What People Get Wrong About CRMs

Owners buy a big-name CRM and think the software is the system. It is not. A CRM is only as good as what gets into it, and for a service business, the thing that matters most is the phone call. A standalone CRM does not hear the phone ring. It learns about the call only if someone types it in afterward, or if the phone system is wired to send it.

Here is what actually happens. The office logs web leads, because the form feeds the CRM on its own. The crew does not log phone calls, because nobody types notes from a crawlspace at 4:45 pm. Six months later the CRM is full of form fills and empty of phone leads, and for a service business, the phone is usually where the work comes from. The reports look tidy and describe the wrong business.

The fix is to stop relying on a human to do data entry after the call. Either use the CRM that is built into the tool that answers the phone, so every call writes its own record, or wire the phone to the CRM with webhooks so the summary lands there the moment the call ends. Entry that depends on a person after 5 pm does not happen.

CRM vs. Help Desk vs. Field Service Software

• A CRM is the customer record. It tracks the relationship over years: who they are, what they bought, what is pending.
• A help desk tracks problems. Each issue becomes a ticket that gets opened, worked, and closed. It is built for support teams, not for winning new jobs.
• Field service software runs the job itself: scheduling, dispatch, invoicing. Many of these tools include a simple CRM inside.

A phone's contact list is none of these. It stores names and numbers, with no history.

Why It Matters

Repeat customers are the cheapest customers a service business will ever get. The CRM is what turns a one-time caller into a five-year customer, because it remembers what the owner cannot. It also pays off on the very next call, when customer intake takes one minute instead of five. An AI receptionist with a built-in CRM does this without staff: Cira auto-links every call to a customer record and sends a summary with the recording and transcript of every call. Its API and webhooks let you send that call data to another system. Our guide to business phone system CRM integration walks through the setup.

The Bottom Line

A CRM keeps one record per customer with every call, text, quote, and job attached. For a service business, the record is only useful if the phone calls are in it, and that only happens when the phone writes the record itself. Pick a CRM built into the tool that answers your calls, or connect the two with webhooks, and stop counting on anyone to type it in later.