Why the call disappears
The phone system logs the call. The CRM does not. Someone pastes a note into a spreadsheet, forwards a voicemail into a shared inbox, or types a summary in chat. That second place becomes the real record, because it is the one a person can find later. The CRM stays empty. The next person who talks to the customer starts from nothing.
A services team, as an example and not a client story, answers the main line in a unified communications app and tracks follow-ups in a sheet named for the week. Sales opens the CRM and sees no activity. The sheet is where work is decided. The CRM is where leadership looks for a report that does not match the week.
A connector writes what you told it to write. With no list of facts to capture, it stores a timestamp and a phone number, and the work stays in the sheet, the inbox, or the chat thread.
If you are still choosing the phone platform, start with the practical guide to choosing UCaaS. It inventories every number, queue, mailbox, and after-hours rule, and asks whether a missed call can become a task a named person sees. Connect a system once you know which one you are keeping.
Inventory the call paths that must write a record
List every way a conversation starts, and mark which ones must leave a record. Four paths cover most businesses. Write them down before you open an integration catalog.
Inbound, answered: who called, who answered, why, and what happens next. When the answer lives only in the agent's memory, the next call repeats the conversation.
Missed and voicemail: a named person who will call back, and a place they will see it the same day. A missed call with no owner is a dropped customer. A notification that expires leaves the callback to chance.
Outbound: the calls your team places, including from a mobile app or softphone. When those stay inside the phone app, the activity view undercounts the work and the next person does not know the conversation happened.
After hours: the rule, and where the result lands in the morning. Take a message, reach someone on call, or stop after a short list. A mailbox nobody opens drops the call.
A regional operations group, as an example and not a client story, often finds the inbound queue writes a ticket, outbound calls from the mobile app write nothing, and after-hours voicemail lands in one person's inbox. Those gaps are the scope. Connect the paths that lose work today.
Write one owner next to each path. A queue, a shared inbox, or a team name leaves the task unassigned. If you cannot name the person, the integration has nowhere to send the work.
Name the CRM fields before you connect
Decide the minimum a call record is, on paper, before anyone opens an admin console. Five facts are enough to start. Add more only after these five survive a real week.
Who called. The number, and the person or company when you already know them. Matching an existing contact is the point. A new contact for every call fills the CRM with duplicates.
Why they called. A short reason from a list your team already uses: new inquiry, existing account, billing, support, wrong number. Notes help the next person. A blank reason means the call was logged and not understood.
Disposition. Answered, missed, voicemail, transferred, or the caller hung up. Use words your team will actually choose. A long list collapses to the one status people click without reading.
Next action. Callback, send something, hand to another team, or no action, said on purpose. An empty next action looks the same as a forgotten one, and forgotten is how the sheet comes back.
Owner. The person who acts. When the next action is a callback, the owner is the person who will make it. A queue that waits for someone to claim the record rebuilds the shared inbox inside the CRM.
Use the same pass when the call has to move from the person who answered to sales or success. Mapping a CRM handoff does that on paper: name the record, write the states, then test them. The five facts above are the call. The handoff map is what the next team is allowed to assume.
If those facts live in a ticketing tool, write that down. The system of record is the place someone acts. Revenue operations enablement starts from one definition of a customer that sales, success, and the people on the phone can trust. A call log that does not join that record is another shadow inbox.
Choose the integration shape
Three shapes cover the decision. Pick one, write why, and name who administers it after the setup is done.
A native connector is the first place to look. The phone platform and the CRM already ship an integration that matches a contact, logs the call, and can open the record while the phone is ringing. Use it when it writes the fields you named and assigns the owner you named. Turn off the extra objects it offers to create. A connector that logs everything and assigns nothing moves the spreadsheet into the CRM.
Middleware sits between the two systems when the native connector cannot carry a field you named, the disposition, or the task. It earns a place when a specific fact has to move and no native path carries it. Every extra system is another admin console and another mapping that drifts when someone renames a field.
A shared inbox with one owner is a temporary record. Use it while the connector is being tested, or while volume is small enough that one person can turn each message into the CRM record the same day. Name that person, put a date on the temporary path, and write what replaces it. A shared inbox everyone can see and no one owns is the arrangement this project exists to retire.
Treat the phone path and the customer record as one project. That is the work in communications and workflow optimization: inventory, a written call flow, then the connection to the record. Buying the connector before the fields exist produces a log nobody opens.
Test three real call types before go-live
Pick three calls from last week. Use real ones. One answered inbound. One missed call or voicemail. One outbound call, or one after-hours call if that is where work disappears.
Walk each one through the fields you named. Did the contact match an existing record, or did the integration create a duplicate? Did the disposition match what happened? Did the owner see the next action without opening the phone app, the sheet, or chat? Does the note say enough that the next person can act without calling the customer back just to learn the reason?
Write down what was missing. That list is the configuration backlog. Fix it before you turn the integration on for the whole team, and run the test with the person who answers and the person who owns the CRM fields. When they disagree on a complete record, that disagreement is the project. Training on a path that failed three real calls teaches the team to keep the spreadsheet.
If an assistant will answer some of these calls, hold it to the same record. How to evaluate an AI receptionist asks whether every call ends as something a person acts on. A transcript in a folder nobody opens is another shadow inbox, whether a person or an assistant left it.
Measure it, and name who owns it
Pick the measures from the inventory, before go-live, and write them down. You choose them. Two are enough.
Missed-call follow-up. Of the missed calls and voicemails in a recent week, how many have a record, an owner, and a next action someone completed. A missed call with no follow-up is the path still dropping work. Count it from the phone system and from the CRM, and look at the gap between the two.
Records acted on. Of the calls that asked for something, how many have a next action that is done or explicitly closed. A call log that grows while the task list stays still means the spreadsheet moved into the CRM. The work did not move with it.
Review both on a date you set, with the owner of the main number and the owner of the CRM record. When the sheet or the chat thread is still where follow-up is decided, the integration is unfinished. Name the person who keeps that review after setup. The path needs an owner.
Bring the call-path inventory and the field list to a strategy assessment. Book a strategy assessment and we will use them as the agenda: whether a connector is the project, or whether the phones and the CRM need an owner and a written record first.