Integrations
Connect your phone system in minutes
19 native integrations. All providers get automatic call ingestion and AI scoring. Preferred and Compatible providers also unlock the real-time agent and queue dashboard.
Feature Compatibility
What each provider gives you
All 19 integrations support automatic call ingestion and AI scoring. The real-time agent and queue dashboard requires a Preferred or Compatible provider.
| Provider | Tier | Call Ingestion | AI Scoring | Agent Identity | Live Agent Status | Live Queue Stats | Shift Time Allocation | Notes |
|---|---|---|---|---|---|---|---|---|
| Preferred | Named states | Call Coach IQ uses | ||||||
| Preferred | Named states | — | ||||||
| Preferred | Named states | — | ||||||
| Preferred | Named states | — | ||||||
| Preferred | Named states | — | ||||||
| Preferred | Named states | — | ||||||
| Compatible | Binary only | Full queue SLA requires Advanced Analytics scope; agent status is Available/Busy only — no named AUX codes | ||||||
| Compatible | Extension | Binary only | Agent matching uses extension/display name; status is profile name only — no named AUX codes | |||||
| Compatible | Binary only | No dedicated real-time API — status approximated from users list; Available/On-Call only | ||||||
| Compatible | Binary only | No dedicated real-time API at standard tier — status approximated; Available/On-Call only | ||||||
| Compatible | Binary only | Queue stats approximated from active calls; agent status is Available/Calling only | ||||||
| Compatible | Binary only | Native availability API; Available/On-Call only — no named AUX codes or duration | ||||||
| Compatible | Binary only | Native availability API with ACW state; Available/On-Call/ACW only — no named AUX codes | ||||||
| Others | Recording platform only — no real-time presence API | |||||||
| Others | Binary only | User roster shown; real-time call state needs Dashboard scope — Available/Inactive only | ||||||
| Others | Binary only | User roster shown; live call state requires WebSocket — Active/Inactive only | ||||||
| Others | Extension | On-premise PBX — no built-in real-time REST endpoint; extension matching only | ||||||
| Others | Phone # | Binary only | Agent presence approximated from active calls — On-Call/Idle only; no named AUX states | |||||
| Others | Phone # | Basic VoIP — no agent identity or real-time contact-centre APIs |
Preferred
Full real-time dashboard support
These platforms expose real-time agent presence and queue statistics via their API, unlocking the full live dashboard alongside automatic call ingestion and AI scoring.
Compatible
Good real-time support
Full call ingestion and AI scoring plus a good-quality live dashboard. Agent availability is accurate; queue SLA metrics are approximated because these platforms don't expose a dedicated real-time queue endpoint.
Others
Call records & AI scoring
Recordings pull in automatically and every call gets AI-powered scoring and coaching. The real-time agent and queue dashboard is not available for these platforms — switching to a Preferred provider unlocks it.
Billing & CRM
Billing and customer data
Stripe powers subscription billing today. CRM integrations are coming soon — sync agent data, accounts, and call outcomes directly into your workflow.
Subscription billing — live
API Security
How your provider connection stays secure
Every API call from Call Coach IQ to your phone platform travels through our hardened server-side proxy layer — never directly from your browser. Six independent controls protect your credentials and your data.
Server-side proxy
Provider API calls are made exclusively from Firebase Cloud Functions — one dedicated callable per provider. Your browser never contacts your phone platform directly, eliminating a class of token-leakage attacks.
Credentials in Secret Manager
API keys and OAuth tokens are stored in Google Secret Manager and loaded at call time by the function. They are never written to Firestore, never returned to the client, and never appear in logs.
App Check enforcement
Every proxy callable requires a valid Firebase App Check token, verified by reCAPTCHA Enterprise. Requests that lack a token — bots, scrapers, unapproved clients — are rejected before any provider call is made.
Independent rate limits
Each of the 19 provider callables carries its own Firestore-backed rate limit, sized by tier: Preferred (500 req / 5 min), Compatible (200 req / 5 min), Others (100 req / 5 min). A runaway client cannot exhaust your provider quota.
Path allowlisting
Every provider adapter maintains a strict allowlist of permitted API paths. Requests to paths outside that list are rejected at the function boundary — the proxy cannot be used to reach arbitrary provider endpoints.
Token revocation checks
Each proxy call verifies that the caller's Firebase session has not been revoked. Offboarded agents or compromised accounts cannot use a still-valid ID token to continue accessing provider data after their session is invalidated.
Don't see your platform?
We're adding new integrations every quarter. If your phone system isn't listed, let us know — we prioritize based on customer demand.
Request an integrationReady when you are
Try it free with a real call — no account, no setup. Or book a demo to walk through the platform on your own data.

