Most phone systems claim CRM integration. What they usually mean is they can send a webhook to Zapier. That is not an integration. A real integration screen-pops the customer record when the phone rings, lets you click a number in the CRM to dial, and writes the call back to the contact record automatically. Here is what we actually connect to, what each integration does on a live call, and the workflows our customers run every day on them.
The reason the distinction matters: when an agent picks up a call and has to wait 45 seconds for a Zapier webhook to push the contact ID into a notification, the call is half over before context lands. A real integration shows the record before the third ring. The difference is whether your agent answers the call already knowing the customer or apologetically asks them to repeat their account number while the page loads.
The CRMs we have built integrations for
Real estate
Follow Up Boss. Incoming calls pop the lead record. Outbound dials by clicking the number in the lead profile. Call notes and recordings get attached to the contact timeline. See the real estate phone system page for the full picture.
Property management
AppFolio, Buildium, and Rent Manager. Tenant calls pop the unit and lease. Maintenance requests get logged against the property. Owner calls route to the right portfolio manager. Details on the property management page.
Field service
ServiceTitan, Housecall Pro, and Jobber. Customer calls pop the job history and active work orders. Dispatchers see who is on the line before they pick up. Field service page has the install pattern.
Legal
Clio. Calls pop the matter, log against the client, and timer-track for billing if you want them to. See the legal firm phone system page.
Sales and marketing operations
GoHighLevel. Inbound calls trigger the right pipeline stage, outbound dials respect the agency workflow. Common with marketing agencies and high-volume sales teams.
Microsoft Teams
Not a CRM, but worth listing: Teams calling lets you keep the Teams interface and use our PSTN service underneath.
Full list, including the ones not called out above, on the integrations page.
What the integration actually does on a live call
Take a Follow Up Boss example. Lead calls the office line. The phone rings, and at the same time the Follow Up Boss lead profile opens in the agent's browser. Agent sees: name, last touch, source, current stage, last note. Agent answers the call already knowing who they are talking to. Call ends. The audio recording, the duration, and any notes the agent typed get pushed back to the FUB contact timeline. Zero copy-paste. Zero "hold on, let me pull up your file."
Same pattern for the others: pop the record, log the call, attach the recording.
What the agent sees before they pick up
The pop is fast (sub-second on a healthy network) and shows the contact name, the recent activity (last call, last email, last text), the lifecycle stage or matter status, and the most recent internal note. For property managers it adds the unit number, lease status, and open work orders. For field service it adds the most recent job, the assigned tech, and current ETA. For legal it adds the matter and any active timer. The amount of context that fits on a 1080p monitor is striking when you have not seen it before.
Real workflows our customers run
Property management: "the tenant is calling about unit 4B"
A 200-unit AppFolio shop in Orlando runs the following: tenant calls, screen pops the lease record with current rent balance, last work order, and open ticket list. The leasing agent answers with the tenant's name and the unit number, asks if it is about the open dishwasher repair, and 80% of the time the answer is yes. Average call length dropped from 4 minutes to under 2. The savings show up in not needing to hire a second agent.
Field service: dispatcher with three job windows open
A ServiceTitan plumbing shop in Clermont keeps the dispatch board on the left monitor and the call queue on the right. When a customer calls, the screen pop pulls the most recent job, the technician assigned, and the GPS ETA. The dispatcher answers with "Hi Maria, Brandon is about 12 minutes out, is that still working for you?" That single line replaces a 90-second back-and-forth where the dispatcher used to look up the address, the technician, and the ETA manually.
Legal: timer starts when the call connects
A small Clio firm running family law sets the integration to start a billing timer the moment a client call connects. The attorney never has to remember to track it. Call ends, the timer stops, the time entry attaches to the matter with the call recording linked. End of week, billable hours reconcile against the call log automatically. They estimate it captures three to five additional billable hours per attorney per week that used to go uninvoiced.
Real estate: hot-lead routing through Follow Up Boss
A Follow Up Boss team in Winter Garden routes inbound calls from new leads to the agent on the up-rotation, pops the lead profile with source attribution (Zillow, sphere referral, postcard), and logs the call to the lead's timeline. The team lead reviews recorded calls weekly to coach the rotation, which would not be possible if the calls weren't auto-attached to the records.
HVAC service company: end-of-day reconciliation
A Housecall Pro HVAC shop runs the same integration. Inbound and outbound calls log against the customer record automatically. At the end of the day the office manager pulls a report of calls vs jobs and reconciles which calls turned into work and which did not. The conversation that used to happen with a dispatcher and a sticky-note pad now happens in the CRM dashboard.
Marketing agency: pipeline staging via GoHighLevel
A marketing agency in Sanford running GoHighLevel uses inbound calls to advance leads through pipeline stages automatically. A first call from a prospect moves the lead from "new" to "contacted." A scheduled outbound call from the closer moves the lead from "qualified" to "proposal sent." The phone system feeds the events, GoHighLevel runs the workflows.
Click-to-call from the CRM
Inside any of the supported CRMs, phone numbers become clickable. Click the number on a contact, the call originates from the agent's extension, and the system logs the outbound the same way it logs inbound. No copy-paste, no misdial, no "wait, that was the wrong number." The numbers in the CRM are the source of truth; the phone system just executes them.
What about the mobile app?
The Pro Mobile app supports click-to-call from the device contacts and from supported CRM apps with deep-linking enabled. A real estate agent in their car can tap a number in the Follow Up Boss app and the call dials from their business number. Outbound caller ID is still the office, not their personal cell.
Click-to-text in addition to click-to-call
For CRMs that support SMS (most of them now), the integration also surfaces a text option. The agent can choose between voice and text from the same record. Texts log back the same way calls do, with timestamps and full transcript attached to the contact.
What we will not pretend to do
- Custom CRMs we have not built for yet. We can usually do click-to-call via TAPI or a browser extension, and webhook the call event in. But screen pops require a real adapter. If you have a homegrown CRM, tell us what it is and we will say yes or no honestly.
- Two-way contact sync. Your CRM is the source of truth for contacts. We do not push our own contact list into your CRM.
- Replacing your CRM with a contact manager. We are a phone system. Your CRM does the CRM work.
- Magic transcription analytics across thousands of calls. We can record everything and tag calls. Sentiment analysis and conversation intelligence is what dedicated tools like Gong or Chorus are for.
- Auto-creating leads from missed calls without your input. We can log the missed call against an existing contact. Creating a new lead from an unknown caller is something your CRM workflow has to be set up to do.
- Sync with systems that have no public API. If your CRM is closed or undocumented, we cannot integrate. Most are not, but it does happen.
What to ask before you switch providers
- Is the integration a real screen pop, or just a Zapier webhook? If they say "we use Zapier," the latency will be 30-90 seconds. Not useful on a live call.
- Does the integration write the call recording back to the contact, or just the metadata? Metadata only is half a feature.
- Does click-to-call work from inside the CRM, or only from a separate dialer window? The latter is a deal-breaker for high-volume sales.
- Will the integration survive a CRM update? Real integrations use stable APIs the CRM vendor maintains. Browser extensions break every six months.
- Is there a cap on the number of contacts or matched records? Some vendors throttle integration usage on lower tiers.
- How does the integration handle multiple records that share the same phone number? Family members, businesses with shared lines, and tenants of the same property all hit this. The integration should let the agent pick from a short list, not guess.
Common mistakes we see
Letting the integration replace agent judgment
The screen pop gives the agent context, not a script. Reading the customer's last note verbatim back to them is creepy. Use the data to be ready, then have the conversation.
Not setting the integration up for both directions
Inbound pops are easy and obvious. Outbound logging takes a couple of extra steps and is the half customers most often skip. If you only log inbound, the contact timeline misses every callback an agent makes.
Trying to integrate too many systems
If your sales team uses Follow Up Boss, your billing team uses QuickBooks, and your service team uses ServiceTitan, integrate the phone with the system each team actually lives in. Trying to pop three different windows on every call confuses everyone.
Skipping the training on click-to-call
Agents who learned to dial manually do not switch to click-to-call until somebody shows them. A 10-minute team huddle pays back in misdial reduction within a week.
Forgetting about call recording retention
The integration logs the recording link to the contact. If your phone service deletes recordings after 30 days but your CRM keeps the link forever, the link in the CRM eventually 404s. Plan retention together.
What it costs
Integrations are included on the All-Inclusive seat at $32/user/month. On the Per-Minute seat at $15/user plus 2.5 cents per outbound minute, integrations are available as an add-on. See pricing for the full breakdown. Hardware is separate (a Yealink T46U at $269 is typical for an agent doing 50+ calls a day; lighter users do fine on a T33G at $125).
What about the AI Receptionist with CRM integration?
The AI Receptionist at $99, $199, or $299 a month can also log calls to the CRM. Caller intent gets categorized, transcripts get attached, and high-priority calls dispatch to the right agent. The HIPAA add-on at $49/mo covers BAA and PHI handling for medical practices.
Where to start
Tell us which CRM your team uses and we will show you the integration on a 20-minute screen share. Get a quote or reach out. If your CRM is on the list above, we can usually have screen pops working the day your phones go live. If it is not, we will tell you straight up whether we can do click-to-call and webhook logging or whether a real screen pop would require custom work. We do not pretend integrations exist when they do not, and we do not bill for development work without quoting it first. For multi-team offices where each department uses a different CRM, we configure per-extension integration so the sales team gets the Follow Up Boss pop, the service team gets the ServiceTitan pop, and nobody has three browser tabs fighting for focus on every inbound call.