Integrations
Does Plaibook work with your stack?
Every phone system and field service platform people ask us about, with an honest status next to each one. If yours is missing, it is not on purpose. Tell us and we will add the row.
Live today: 18 phone systems, 3 FSM platforms, and 19 other tools. Everything else on this page is marked in progress, we build it free, or not possible.
Live integrations at a glance
Phone systems
Your calls, automatically captured
Plaibook connects to your phone platform and pulls every call recording for scoring. No hardware, no browser extensions, no changes to how your reps make calls. The phone system is the gate: if it records and has an API, we can score it. If it does not, we cannot, and the rows at the bottom say so.

Five9
SFTP push to S3
Live~5 min setup
Five9
SFTP push to S3
Data captured
Call recordings, metadata, agent assignments
Connection method
SFTP push to S3
Authentication
Auto-provisioned SFTP credentials
Five9 pushes call recordings and CDR data to a dedicated SFTP endpoint that lands in S3. Plaibook pulls additional metadata from Five9's SOAP API (agent, disposition, call segments) so attribution stays accurate, even across warm transfers.
See how calls are scored after capture
Dialpad
Real-time webhook
Live~5 min setup
Dialpad
Real-time webhook
Data captured
Call recordings, transcripts, agent info
Connection method
Real-time webhook
Authentication
API key
Dialpad fires a webhook when a call ends. Plaibook grabs the recording URL, downloads the audio, and starts scoring it within seconds. You can filter by inbound, outbound, or all calls.
See how calls are scored after capture
RingCentral
OAuth 2.0 polling
LiveOne-click setup
RingCentral
OAuth 2.0 polling
Data captured
Call recordings, call log, agent details
Connection method
OAuth 2.0 polling
Authentication
OAuth 2.0 (one-click authorize)
RingCentral connects through a standard OAuth flow. Plaibook polls the call log API for completed calls, downloads recordings, and scores them. Also works with RingCentral Team Messaging for coaching notifications.
See how calls are scored after capture
Genesys Cloud
Direct S3 write (BYOB)
Live~30 min with our team
Genesys Cloud
Direct S3 write (BYOB)
Data captured
Call recordings, conversation analytics, queue data
Connection method
Direct S3 write (BYOB)
Authentication
OAuth 2.0 client credentials
Genesys Cloud writes recordings directly to Plaibook's S3 bucket via cross-account IAM (Bring Your Own Bucket). No polling, no file transfers. Recordings land in S3 as soon as Genesys finishes processing them.
See how calls are scored after capture
Zoom Contact Center
Server-to-server OAuth
Live~5 min setup
Zoom Contact Center
Server-to-server OAuth
Data captured
Call recordings, contact center interactions
Connection method
Server-to-server OAuth
Authentication
Server-to-Server OAuth app credentials
Connects via Zoom's Server-to-Server OAuth. Plaibook syncs call recordings from your Zoom Contact Center and scores them. No per-user OAuth flow required.
See how calls are scored after capture
GoTo Connect
OAuth 2.0 with webhooks
LiveOne-click setup
GoTo Connect
OAuth 2.0 with webhooks
Data captured
Call recordings, call events, agent extensions
Connection method
OAuth 2.0 with webhooks
Authentication
OAuth 2.0 (one-click authorize)
GoTo Connect authenticates through OAuth and subscribes to call event notifications. When a call completes, Plaibook fetches the recording and scores it.
See how calls are scored after capture
CallRail
HMAC-signed webhook
Live~5 min setup
CallRail
HMAC-signed webhook
Data captured
Call recordings, tracking numbers, source attribution
Connection method
HMAC-signed webhook
Authentication
API token
CallRail pushes completed calls via HMAC-signed webhooks. Plaibook captures the recording, caller info, and CallRail's marketing attribution data (which campaign, which keyword) so you get call scores tied to ad spend.
See how calls are scored after capture
CallTrackingMetrics
Webhook push
Live~5 min setup
CallTrackingMetrics
Webhook push
Data captured
Call recordings, tracking data, agent info
Connection method
Webhook push
Authentication
Access key + secret key
CTM pushes call events via webhook when recordings are ready. Plaibook downloads the audio and scores it. You can auto-process all new calls or do manual batch imports.
See how calls are scored after capture
Nextiva
SFTP push to S3
Live~5 min setup
Nextiva
SFTP push to S3
Data captured
Call recordings, CDR data
Connection method
SFTP push to S3
Authentication
Auto-provisioned SFTP credentials
Nextiva pushes call recordings and CDR data daily via SFTP, similar to the Five9 flow. Plaibook provisions SFTP credentials automatically and scores recordings as they arrive.
See how calls are scored after capture
Quo
Webhook push
Live~5 min setup
Quo
Webhook push
Data captured
Call recordings, SMS messages, transcripts
Connection method
Webhook push
Authentication
API key
Quo (formerly OpenPhone) sends webhooks for completed calls, messages, and transcripts. Plaibook receives recordings in real time and can run both call scoring and text follow-up. This is the phone system we recommend for offices with fewer than five reps.
See how calls are scored after capture
GoHighLevel
API polling
Live~5 min setup
GoHighLevel
API polling
Data captured
Call recordings from GHL's built-in phone
Connection method
API polling
Authentication
API key or OAuth 2.0
For companies using GHL's built-in phone system, Plaibook polls for new call recordings and scores them. This is separate from GHL's CRM integration (listed below).
See how calls are scored after capture
Voice for Pest
API polling
Live~5 min setup
Voice for Pest
API polling
Data captured
Call recordings, call metadata
Connection method
API polling
Authentication
ATS API username, password and customer ID
Voice for Pest is a partner, and the phone system stays. Plaibook runs alongside it and pulls recordings through the Voice for Pest API, then scores them the same way as any other system. If you already have your ATS API password and customer ID, connecting takes a few minutes. If you do not, ask Voice for Pest for API access first, since that is the only part that waits on someone else.
See how calls are scored after capture
JustCall
Real-time webhook
Live~5 min setup
JustCall
Real-time webhook
Data captured
Call recordings, call metadata, agent info
Connection method
Real-time webhook
Authentication
API key + API secret
JustCall fires a signed webhook when a call ends and Plaibook scores the recording within seconds. You can process every call automatically or filter to inbound only, outbound only, or a specific time zone.
See how calls are scored after capture
Kixie
Real-time webhook
Live~5 min setup
Kixie
Real-time webhook
Data captured
Call recordings, call metadata, agent info
Connection method
Real-time webhook
Authentication
Business ID + webhook secret
Kixie pushes completed calls to Plaibook through a signed webhook. Nothing to poll and nothing to schedule: the scorecard is ready shortly after the rep hangs up.
See how calls are scored after capture
Talkdesk
API polling
Live~5 min setup
Talkdesk
API polling
Data captured
Call recordings, call metadata, agent info
Connection method
API polling
Authentication
Account name, Client ID, Client Secret and region
Talkdesk has no per-call webhook for outside tools, so Plaibook polls the recordings API on a schedule, the same shape as Genesys and Five9. You enter the credentials from your Talkdesk admin console once.
See how calls are scored after capture
NICE CXone
API polling
Live~30 min with our team
NICE CXone
API polling
Data captured
Call recordings, agent and skill data
Connection method
API polling
Authentication
Access key ID + secret from NICE
NICE CXone is a full contact-center platform, so Plaibook discovers your region automatically and then polls for finished recordings. There is no per-call webhook available to third parties, so polling is the ingestion path. Worth a 30-minute setup call because contact-center tenants vary more than a simple softphone.
See how calls are scored after capture
WhatConverts
API polling
Live~5 min setup
WhatConverts
API polling
Data captured
Call recordings, lead records, marketing source attribution
Connection method
API polling
Authentication
API token + API secret
WhatConverts is both a call source and an attribution source. Plaibook pulls the recordings and scores them, and it pulls the lead record alongside so a scored call carries the campaign and keyword that produced it. You can exclude spam and duplicate leads.
See how calls are scored after capture
Surge
Webhook push
Live~5 min setup
Surge
Webhook push
Data captured
Call recordings from a Surge forwarding number
Connection method
Webhook push
Authentication
Surge number + forwarding target (no per-office API keys)
For offices whose phone system will not give up recordings, Surge provides a recording number that forwards to your real line. Calls route through it, Surge posts the finished recording to Plaibook, and scoring works normally. This is the fallback when the phone system itself is a dead end.
See how calls are scored after captureAAircall
Webhook push
We build it free, about a day
Aircall
Webhook push
Data captured
Call recordings, call metadata, agent info
Connection method
Webhook push
Authentication
API key
Not built yet, but Aircall has a clean API and webhooks, so this is a one-day build. We have done around thirty softphone integrations and they all follow the same shape.
Tell us you run this and we will scope itGGrasshopper
No recording API
Not possible (no API or recordings)
Grasshopper
No recording API
Data captured
Nothing we can pull
Connection method
No recording API
Authentication
n/a
Grasshopper does not expose call recordings through an API, so there is nothing for Plaibook to score. If you are on Grasshopper and want call scoring, see the section below on which phone system to move to.
Which phone system we recommend insteadGGoogle Voice
No recording API
Not possible (no API or recordings)
Google Voice
No recording API
Data captured
Nothing we can pull
Connection method
No recording API
Authentication
n/a
Google Voice does not offer programmatic access to call recordings. We have lost more than one deal to this and we would rather tell you on the page than on the third call. See the section below on which phone system to move to.
Which phone system we recommend insteadUUnitel (forwarding to a cell)
No recordings
Not possible (no API or recordings)
Unitel (forwarding to a cell)
No recordings
Data captured
Nothing we can pull
Connection method
No recordings
Authentication
n/a
Any setup that forwards the office line to someone's cell phone produces no recording we can reach, Unitel included. The fix is not an integration, it is a phone system that records. See below.
Which phone system we recommend insteadNo phone system yet?
Here is what we tell people
More deals stall on the phone system than on anything else. If your office line forwards to a cell, or you are on Google Voice or Grasshopper, there is no recording for us to score. Here is the advice we give on the call.
Under five reps
Go with Quo
Quo (formerly OpenPhone) is cheap, sets up in an afternoon, records every call, and its webhooks feed Plaibook in real time. For a small office it is the least friction we have seen. Calls and texts both come through, so the AI text follow-up works on the same number.
Five to fifteen reps
Go with Dialpad
Once you have a real inside sales floor you want queues, routing and a manager view, and Dialpad does that without contact-center pricing. It fires a webhook the moment a call ends, so scoring starts within seconds.
What to avoid
Anything that forwards to a cell
Google Voice, Grasshopper, Unitel forwarding, or a number that rings someone's personal phone. None of these give us a recording through an API. It is not a Plaibook limitation, it is a no-recording limitation, and it will block any call scoring tool, not just ours.
Bigger than fifteen reps? You are probably already on Five9, RingCentral, Genesys or NICE, and the table above covers those. We wrote a longer version of this advice: which phone system to pick for a pest control office.
Field service management
Read and write to your FSM
Plaibook's AI reads and writes to your FSM. It books appointments, creates customers, generates contracts, and collects payments in your system. The customer stays in the text conversation the whole time. Call scoring alone does not need the FSM, so an unbuilt FSM row never blocks you from starting.
FieldRoutes
Deepest integrationLive~30 min with our teamFull bidirectional sync via REST API
The most complete integration Plaibook offers. Over SMS, the AI can look up real-time availability, book a confirmed appointment on the right route, create the subscription, send the contract, and collect payment. The whole sale happens in a text thread without anyone touching the FSM. FieldRoutes is also the source of truth for close rate and attribution: Plaibook keeps a daily cached mirror (roughly 20 to 30 API calls a day) and the transcript never overrides it.
Data flow between Plaibook and FieldRoutes
Plaibook
AI text follow-up
Call scoring
Lead source attribution
Commission tracking
FieldRoutes
Customers & history
Routes & availability
Subscriptions & pricing
Payments & contracts
What Plaibook reads from FieldRoutes
- Customer records and service history
- Available appointment slots by route and zip code
- Subscription and contract status
- Payment status and portal links
- Service types and pricing
What Plaibook writes to FieldRoutes
- Create new customers from phone conversations
- Book confirmed appointments on specific routes
- Create subscriptions with pricing and frequency
- Generate and send service contracts for e-signature
- Send payment portal links via SMS
- Add notes to customer records
Auth: API key + token (from FieldRoutes API settings)
ServiceTitan
In progress. The shape is settled: you enter ServiceTitan credentials directly in Plaibook with no redirect flow, and the AI will check availability, create or match customers, and submit booking requests. ServiceTitan bookings land in the dispatcher queue as pending requests rather than confirmed appointments, so a dispatcher accepts and converts them to jobs. If you run ServiceTitan, tell us on the demo and you help decide what gets finished first. Call scoring does not wait on any of this.
Briostack
Briostack connects via REST API with per-instance subdomains. Availability is service-based: the AI asks for a specific service at a specific branch. Briostack has a native slot reservation system, so Plaibook can hold a time while the customer decides and release it if they decline. Appointments are confirmed, not pending.
Reads
- Customer records
- Available appointment slots by service and branch
- Service area coverage
- +1 more
Writes
- Book confirmed appointments with native slot reservation
- Create or match customer records
- Log communications to customer history
PestPac
Plaibook signs in to PestPac the same way your office does, then checks coverage by zip, looks up open slots at the right branch, books the appointment, sends the contract and collects payment. The first connection test takes about thirty seconds because it signs in with a real browser session; after that it reuses the session and finishes quickly.
Reads
- Customer records and service history
- Available appointment slots by branch
- Service area coverage by zip code
- +1 more
Writes
- Book confirmed appointments
- Create or match customer records
- Generate and send service contracts
- +2 more
Jobber
Not built yet. Jobber has a solid API, so booking and customer sync are a standard FSM build: two to three weeks from kickoff to production, no charge.
Housecall Pro
Not built yet. Same shape as Jobber: two to three weeks for read and write, free. Call scoring does not need the FSM at all, so you can start on that side while we build.
Pocomos
Not built yet. Pest-specific, so the mapping to routes and subscriptions is close to what we already do for FieldRoutes. Two to three weeks, free.
GorillaDesk
Not built yet. We have offered to build GorillaDesk for the first customer who asks, at no charge. Two to three weeks.
Evolve
Not built yet. Two to three weeks for an FSM build, free, assuming Evolve grants API access for your account.
CRM, analytics and communication
Close the loop
Sync outcomes to your CRM, send conversion data to your ad platform, and notify your team when something needs attention.
GoHighLevel CRM
Beyond call recording import, GHL is also a full CRM integration. Plaibook imports contacts from GHL pipelines, syncs conversation outcomes back as opportunity stage changes (won/lost/abandoned), and can send SMS through GHL's Twilio-backed phone numbers. Pipeline sync runs automatically.
Auth: API key or OAuth 2.0
Slack
Plaibook posts to Slack channels with coaching DMs for reps, leaderboard updates, alerts when calls need attention, and daily or weekly performance summaries. RingCentral Team Messaging works as an alternative if you don't use Slack.
Auth: OAuth 2.0 (one-click install)
SignWell
After the AI books an appointment and the customer is ready to sign, Plaibook sends a SignWell document right in the SMS thread. The customer signs on their phone without leaving the conversation. A webhook confirms when the document is completed.
Auth: API key
Google Analytics 4
Plaibook sends conversion events to GA4 via the Measurement Protocol when calls result in booked appointments or closed deals. You can also upload offline conversions to Google Ads for campaign optimization using actual revenue data instead of lead counts.
Auth: GA4 Measurement ID + API secret
Connecteam
If your crews already live in Connecteam instead of Slack, Plaibook sends coaching notes, alerts and performance summaries there instead. Same messages, different app.
Auth: API key + publisher ID
Pronto
Another Slack alternative for teams already on Pronto. One thing to know before setup: Pronto turns API access off by default, so ask Pronto support to enable it for your account first, otherwise the key will be rejected and it looks like a Plaibook problem.
Auth: API key
Google Ads
Plaibook pulls campaign spend and performance so you can put ad dollars next to what those calls actually closed. Pushing conversions back the other way runs through the GA4 integration above.
Auth: OAuth 2.0 (one-click authorize)
Meta Ads
Pulls ad accounts, campaigns, spend and lead-form submissions from Meta so Facebook and Instagram spend lands in the same attribution picture as everything else.
Auth: OAuth 2.0 (one-click authorize)
Microsoft Ads
Campaign spend from Microsoft Ads (formerly Bing Ads), same treatment as Google and Meta. Smaller channel for most pest companies, but it is on the list so the spend total is honest.
Auth: OAuth 2.0 (one-click authorize)
StackAdapt
Programmatic display and video spend by campaign and by day, pulled in so agency-run StackAdapt budgets show up next to the calls they produced.
Auth: API key
Google Search Console
Impressions, clicks and queries for your site, so organic search sits in the same report as paid. Useful for seeing which pages bring in the calls that close, not just the calls that come in.
Auth: OAuth 2.0 (one-click authorize)
Ahrefs
Domain rating, backlink counts and AI-answer visibility pulled on a schedule, so SEO movement is tracked next to call volume instead of in a separate tool nobody opens.
Auth: API key
BrightLocal
Local search rankings and listing health, the part of SEO that actually drives phone calls for a service business with branches.
Auth: API key
Whitespark
Local rank tracking by location. An alternative to BrightLocal if that is what your agency already runs.
Auth: API key
eLocal
eLocal sells pay-per-call and web leads. Plaibook pulls both, scores the calls, and tracks what share of purchased leads turned into booked jobs, which is the number that decides whether the channel is worth keeping.
Auth: API key
Yelp
Leads from Yelp arrive by webhook and land in the same pipeline as everything else, so the AI can follow up by text and the channel gets measured on closed jobs.
Auth: Webhook (no keys to manage)
Clicki
Clicki posts new leads to Plaibook as they come in. Inbound only: Plaibook receives, it does not write anything back to Clicki.
Auth: Webhook (no keys to manage)
Baton
Baton sends overflow and after-hours leads to Plaibook by webhook so they get the same text follow-up as a lead from anywhere else.
Auth: Webhook (no keys to manage)
Website forms
Point any form on your site at a Plaibook webhook URL and the submission becomes a lead the AI can text within seconds. Works with whatever built your site, because it is just a URL to post to.
Auth: Webhook (no keys to manage)
SmarterLaunch
SmarterLaunch is a quoting tool. There is no integration and you do not need one: call scoring works off the recording from your phone system, and the booking side runs through your FSM. Keep using SmarterLaunch exactly as you do today.
Auth: n/a
Where your reps work
Reps change nothing. Managers get one screen.
The question we get on almost every demo, answered plainly.
Reps
Stay in the phone system and FieldRoutes
They take calls where they take them today and book where they book today. There is nothing for a rep to log into and nothing to type in after a call.
Managers
Live in Plaibook
Scorecards, leaderboard, close rate and save rate by rep and by lead source, and the handful of calls worth a listen. Every score links to the recording.
Coaching
Arrives in Slack
Reps get their notes in the channel they already use. Managers can ask the AI Coach questions there too. If you do not use Slack, RingCentral Team Messaging works.
So yes, it is one more login. It is the manager's login, not the rep's, and it replaces the spreadsheet.
Quick guide
Which integrations do I need?
It depends on what you want Plaibook to do. Here is a simple way to think about it.
"I just want call scoring and coaching."
Connect your phone system only. That gets you scorecards for every call, rep leaderboards, coaching in Slack, and close rate by rep. No FSM or CRM needed.
Typical setup: under 5 minutes
"I want the AI to text the leads we didn't close."
Connect your phone system plus your FSM. The phone integration captures calls. The FSM integration lets the AI text leads, check availability, book appointments, send contracts, and collect payments without a human.
Typical setup: 30-minute call with our team
"I want the full picture: calls, texts, and attribution."
Connect everything: phone system, FSM, CRM, Slack, and GA4. You get call scores, AI text follow-up, pipeline sync, team notifications, and conversion data flowing back to your ad campaigns so you can spend on the lead sources that actually close.
Typical setup: under an hour total, done in stages
Setup
How setup works
Connect your phone system
Most integrations need an API key or an OAuth "Authorize" click. SFTP-based systems (Five9, Nextiva) get credentials generated for you. Usually takes under 5 minutes.
Backfill historical calls
Plaibook imports a month of past call recordings at no charge so your dashboards and leaderboards have real data from day one. The backfill runs in the background and usually finishes in a few hours.
Connect your FSM (if applicable)
If you want text follow-up that books appointments and closes deals, connect your field service platform. You will need API credentials from your FSM admin portal. Plaibook runs an initial sync to cache your customers, routes, and service types. Setup call with our team takes about 30 minutes.
Go live
New calls flow in automatically and scoring starts right away. Text follow-up launches when you are ready. No training period, no minimum data requirements.
What your IT team will need to do
API-key integrations (Dialpad, CallRail, CTM, FieldRoutes, Briostack): an admin generates an API key in the platform's settings.
OAuth integrations (RingCentral, GoTo Connect, Slack): an admin clicks "Authorize" and approves the permission request.
SFTP integrations (Five9, Nextiva): Plaibook generates the credentials, your admin configures the SFTP destination in your phone system.
No custom development, no firewall changes, no VPN.
Don't see your tool?
We build integrations at no charge. A phone system with an API takes about a day; we have done around thirty of them. An FSM with booking and payments takes two to three weeks. The only hard no is a system with no API and no recordings.
Tell us what you use on the demo and we will give you a date, not a maybe.