Ask a service company where the customer record lives and the honest answer is usually five places. The owner's text messages. A Facebook inbox. A voicemail box nobody has cleared since spring. A spreadsheet the office manager keeps. And QuickBooks, where the estimate finally went. Nobody merges them, because merging them is a job, and there's a truck to load.
The write is the product
Every capability described on this site — the missed-call text-back, the intake form, the after-hours booking — ends the same way: with a write to a single customer record. Three things go in every time. Where the contact came from. When it happened, to the minute. And what was said — the transcript of the text thread, the answers from the form, the summary of the call.
That write is not an administrative afterthought. It is the seam work — the deliberate stitching between the system that caught the lead and the system where your business actually lives. A lead that isn't written down somewhere queryable is a story. A lead with a source and a timestamp is a number you can check. When any vendor tells you a system "is working," the only acceptable evidence is a report you can pull yourself, from your own records, without asking the vendor. We build so that you can.
Fields, not notes
There is a lazy version of CRM integration where everything lands in the notes field: "missed call 8/12 7:41pm, texted back, wants water heater quote." That looks like record-keeping. It isn't, because you cannot count a note. You cannot filter notes to see how many August leads came from after-hours calls, or sort by them, or chart them month over month. Notes are where data goes to die politely.
Field-level mapping means each fact lands in the field built for it. The call source — missed-call text-back, website form, referral — goes into the lead-source field, the one your CRM can group and count by. The first-contact timestamp goes into a date field. The transcript attaches as its own object. The job type the customer described goes into a category field, not buried in a sentence. At the end of the month the difference is stark: one version is a pile of anecdotes, the other is a table where "leads by source by week" is a thirty-second pull.
The phone number is the customer ID
Service businesses don't issue account numbers. The closest thing a plumbing or roofing customer has to an identity is a phone number, so the dedupe logic keys on it. Before any matching happens, the number gets normalized — (806) 555-0142, 806.555.0142, and +18065550142 are the same number, and the system reduces all of them to one canonical form before it looks anything up.
Then the rule: when a call or text arrives from a number that already has a record, the contact attaches to that record instead of spawning a duplicate. The customer who called Tuesday and again Thursday is one person with two contacts, not two leads. That matters more than it sounds, because counting him twice inflates your lead totals and understates your close rate, and both errors happen to flatter the system that produced them. Dedupe is the vendor volunteering to make its own numbers smaller. That is exactly why you should insist on it.
Households are the harder case. The husband calls from his cell about the AC; the wife follows up from hers two days later. Two numbers, one job. The second-pass match runs on service address, and when it finds one, the records link rather than merge — two people, one household, one job history.
What one record makes auditable
Here is what the renewal conversation looks like when everything writes to one place. You open your own CRM. You pull leads by source for the quarter. You see how many came through each channel, how many booked, and — if your team enters job values when work closes — what each channel produced in revenue. Divide what you spent by the jobs you won and you have cost per acquired job, per channel, computed from your own records. Not clicks, not impressions. Jobs.
Notice what's absent from that paragraph: us. You don't need our dashboard, our word, or a monthly call to know whether any of this is working. The record either shows booked work traced back to these systems or it doesn't. We build it this way on purpose, knowing it means you could fire us with evidence. A vendor who resists giving you that visibility is telling you something about what the numbers would show.
It works with what you already run
Jobber, Housecall Pro, ServiceTitan — where your CRM has an API, the write goes through it into your existing fields, and your team keeps working in the tool they already know. If your CRM is genuinely a spreadsheet, that can work too, at small scale, with discipline. If there is nothing at all, we stand up something minimal rather than sell you a migration. The point is one place, not a particular product, and the worst possible outcome of this project would be adding a sixth inbox to your five.
What this does not fix
It starts at go-live. Ten years of history scattered across text threads and legal pads stays scattered; back-filling it is a separate project and usually not worth the hours.
Dedupe has honest edge cases. A general contractor who calls from one cell phone about three different homeowners' jobs looks, to the matching logic, like one very busy customer. A property manager's office landline covers forty units. These cases get flagged for a human to split rather than guessed at, and some will sit wrong until somebody corrects them.
And the record is only as good as what people put into it. If the tech closes a job with a handshake in the driveway and never marks the outcome, revenue-by-source stays blank no matter how clean the intake side is. The automated writes cover the front of the funnel. The back of the funnel still requires the habit of recording what happened. We can make that a thirty-second task on a phone. We can't make it zero.
Where to start
Count the places a lead can currently land in your business — phones, inboxes, voicemail, spreadsheets, the sticky notes on the dispatch board. If the answer is more than two, the first project isn't AI at all. It's plumbing: pick the one system of record and route everything into it. That is the unglamorous work every other page on this site depends on, and it's where we would begin.