A call center without CRM integration is two screens, two systems, and an agent retyping caller phone numbers all day. The integrations that earn their keep do three specific things: pop the customer record when the phone rings, log the call automatically when it ends, and let agents click-to-dial from the CRM.
What we actually integrate with
These are the CRM integrations we ship and support directly, with the kind of business each one shows up in most:
- Follow Up Boss - real estate teams. Lead routing into our queues, click-to-dial from a contact, calls and texts logged to the lead automatically.
- GoHighLevel - marketing agencies and lead-gen shops. Pipeline events trigger call workflows; missed calls trigger SMS responses.
- Clio - law firms. Calls log to matters with billable time tracking. Caller match by phone number opens the matter file.
- ServiceTitan - HVAC, plumbing, electrical. Inbound calls pop the customer's service history, equipment list, and open jobs. Dispatch routing by zip code.
- Housecall Pro and Jobber - small field service. Click-to-dial from a job, calls log to the customer.
- AppFolio, Buildium, Rent Manager - property management. Tenant lookup by phone number, maintenance request routing, owner calls flagged separately from tenant calls.
- Microsoft Teams - calling inside the Teams client. Different shape but solves a similar problem.
The full list lives at our integrations page.
What integration actually buys you
Screen-pop on inbound
Phone rings, the CRM record opens on the agent's screen with the caller's name, last interaction, open tickets or matters or jobs, and notes. Agent answers "Hi Mike, calling about the AC install we scheduled for Thursday?" instead of "Can I get your account number?" That difference compounds across 10,000 calls a month.
The screen-pop is keyed on caller ID. If the number is in the CRM, the match is instant. If the number is not in the CRM, we fall back to a search-by-number prompt so the agent can find the contact in one click rather than retyping the number.
Automatic call logging
Call ends, a logged record appears in the CRM with timestamp, duration, recording link, and the agent who handled it. No tab-switching, no copy-paste, no missed entries that the QA team has to reconstruct from memory three weeks later.
Call logging supports custom fields where the CRM allows it: disposition tags ("qualified," "voicemail," "do not call"), outcome codes, follow-up dates, and any field the agent fills in during after-call work. Those fields drive reporting downstream.
Click-to-dial
Click a phone number in the CRM, the call places through our system. Saves about 8 seconds per outbound call. Across an outbound dialer, that is real hours per week per agent.
Call disposition sync
Agent tags the call ("voicemail," "no answer," "qualified lead," "booked") and the tag flows into the CRM. Drives reporting and workflows downstream. Build a controlled vocabulary for dispositions; ten options is plenty, twenty options is too many for agents to use consistently.
What each integration actually does, by example
ServiceTitan for a 40-tech HVAC shop
Customer calls in. Screen-pop shows their equipment, service history, the open quote from last week, and any open jobs. Dispatcher sees a Y-shaped icon if the customer is in a service area covered by an available tech today. Click-to-dial works in reverse too: a tech in the field calls a customer from the job card on their phone, and the call logs as outbound activity on the job. After-hours emergency routing pulls from the on-call rotation defined in ServiceTitan.
Clio for a 15-attorney firm
Caller match by number opens the matter file with billing rate, recent activity, and any open invoices. The call timer starts billable. When the call ends, time entry is pre-populated and waiting for the attorney to confirm and submit. The recording link attaches to the matter so the paralegal can transcribe later. Conflict checks pop a warning if the caller's number matches an opposing party in another matter; the attorney can decline the call before it connects.
Follow Up Boss for a 30-agent brokerage
Buyer lead calls the main number. Round-robin routes the call to the next available agent based on presence (DND on during a showing = skip). The lead's source, last activity, and any saved searches pop in Follow Up Boss. Text messages logged to the same lead. Missed-call SMS auto-reply fires within seconds if no one answers. See real estate phone system for the full configuration.
AppFolio for a 1,200-unit property manager
Tenant call pops the unit, the lease, the open work orders, and the resident's communication history. Owner call routes to a different queue with their portfolio waiting. Maintenance request goes from voicemail transcription (paid add-on) straight into the work order queue without anyone typing it in. See property management for the broader pattern.
Buildium for a mid-size manager
Same shape as AppFolio but with Buildium's specific field map. Tenants, owners, vendors all surface differently on inbound calls. Work order creation from voicemail transcription is the same workflow.
Rent Manager for a regional operator
Rent Manager's API is more granular than AppFolio's; we surface lease-specific fields (current balance, scheduled rent increase, work order count) on the inbound screen-pop. Agents in the call center have enough information to resolve most calls without transferring to property-specific staff.
GoHighLevel for a marketing agency
Pipeline stage moves trigger calling workflows: when a deal moves to "discovery scheduled," the lead gets a confirmation SMS. Missed calls trigger an SMS auto-reply with a booking link. Voice calls log as activities on the contact record.
Housecall Pro and Jobber for small field service
Lighter touch than ServiceTitan, same core behavior. Click-to-dial from a job, call logs to the customer record, voicemail transcription routes to the dispatch board. Right fit for shops under 15 techs that do not need the heavier ServiceTitan workflow.
Microsoft Teams for everyone
Calling inside Teams. Presence sync, call history sync, voicemail in Teams. The integration page is at Microsoft Teams. The right fit when Teams is already the day-to-day client and adding another app would create friction.
What integration does not do
It does not fix bad data. If your CRM contacts have wrong phone numbers, no integration will guess right. It does not solve coverage holes either: if your sales team works leads in a CRM nobody on the call team uses, the calls will not log there.
It also does not replace a real implementation conversation. Each CRM has quirks about what it lets us log, how it handles custom fields, and what its API rate limits look like. The integration setup is usually under an hour. The conversation about which fields to map and how to handle edge cases is longer than that.
API limits and what they mean in practice
Most CRMs cap API calls per minute. For a 30-agent center making 4,000 calls a day, that is usually fine. For a 200-seat center making 40,000 calls a day, we have to throttle and batch some operations. We tell you whether your CRM can handle your volume before we sell you anything.
Data residency and security
CRM integration moves customer data between systems. We use OAuth tokens scoped to the operations the integration actually performs. We do not store CRM data on our side beyond what the integration requires; everything routes through and stays in the CRM as the system of record. For HIPAA, GLBA, or other regulated data, we configure the integration with extra controls.
What we do not integrate with (yet)
- Salesforce: covered via generic CTI and Microsoft Teams routing, not native today.
- HubSpot: similar story, accessible through generic webhook flows.
- Homegrown internal systems: we scope these per project. If you have a documented API, we can usually build it in 1-3 weeks.
- Zendesk: webhook-based for now; native integration on the roadmap.
If you do not see your CRM in the list, the answer is not always "no." It is "let us talk about how your system exposes data."
Common mistakes when planning a CRM integration
- Skipping data cleanup. Bad phone numbers, duplicate contacts, missing area codes. Clean the data before you flip the integration on.
- Assuming the integration logs everything. Some CRMs cap call log fields. Know the limits.
- Routing only on caller ID. If the caller is using a number not in the CRM, the screen-pop fails. Build a fallback to a search-by-number prompt.
- Not training agents on the dispositions. If "qualified lead" and "hot lead" are both options, agents will pick randomly. Define the taxonomy.
- Forgetting recording disclosure. Recording laws vary by state. Get the disclosure built into your IVR before recording goes live.
- Letting every agent customize their disposition list. Centralize the list; otherwise reporting is meaningless.
- Not auditing the integration quarterly. Field mappings break when the CRM changes. Schedule a check.
What to ask before signing
- Does the integration support inbound and outbound, or just one?
- What custom fields can we map?
- What is the latency on screen-pops? (Should be under 2 seconds.)
- Are recording links accessible from the CRM or only from the VoIP portal?
- What happens when the CRM is down? (Calls still happen, logging queues.)
- How are duplicate contacts handled when both have the same caller ID?
- Can the integration trigger workflows on call events (missed call, long call, after-hours call)?
What it costs
Integration is included with our Phone Service at no per-seat upcharge for the CRMs above. Custom integrations to a homegrown system go through our integrations team and get scoped per project. SIP-level routing for high-volume centers runs on SIP Trunking at $15/channel/mo.
What "included" actually means
Included means the standard integration: screen-pop, call logging, click-to-dial, disposition sync. It does not include heavy custom field mapping for non-standard CRM configurations, or building bespoke workflows on top of the integration. Those are scoped per project, billed at a rate we quote up front, and we tell you the total before we start.
Industry-specific patterns
The integrations break down by industry in a way that makes sense once you have seen a few deployments. Property management companies on AppFolio, Buildium, or Rent Manager all need the same screen-pop pattern: unit, lease, work orders, communications. Field service shops on ServiceTitan, Housecall Pro, or Jobber all need the dispatch + job-card pattern. Sales teams need click-to-dial, call logging, and disposition reporting against a pipeline. Multi-location operators need the CRM split across sites with site-aware routing.
What good integration data looks like in reporting
Six months after a good integration is live, the reports tell a different story than they did before. Inbound call volume mapped to customer segment shows which kinds of customers actually call. Outbound call activity by agent shows which agents are making the dials. Call recording archives surface dispute patterns. Disposition trends show which call types are growing or shrinking. The CRM becomes a system of record for voice activity, not just for deals and tickets. For sales leadership especially, that change is the difference between coaching from anecdotes and coaching from data. Pulling those reports weekly is a habit we recommend customers build during ramp-up; once it is in the routine, it stays useful.
The integration setup process, step by step
For a typical CRM integration on a call center already running our Phone Service:
- Step 1: OAuth handshake. The CRM admin authorizes our integration through the CRM's standard OAuth flow. Takes about five minutes.
- Step 2: Field mapping. We walk through the fields the integration will read and write. Most customers stick with the defaults; some have custom field requirements that need an extra conversation.
- Step 3: Call routing rules. Decide which inbound numbers trigger which screen-pop behavior. Most centers have one primary number; some split inbound by purpose (sales line, support line, billing line).
- Step 4: Disposition vocabulary. Define the tags agents will pick from after each call. Keep it under ten options.
- Step 5: Pilot. Roll the integration out to two or three agents first. Watch them use it. Adjust based on what they actually do.
- Step 6: Full rollout. Move all agents onto the integration. Schedule a 30-day review to tune field mappings and dispositions based on real usage.
Where to start
If your CRM is on the list above, the integration takes a working day to scope and stand up. Tell us which CRM and how many seats and we will give you a real timeline and a real number. For the full pricing menu, see pricing. To browse integrations by name, the master list is at integrations.