Omniscore Integrations: Phone Systems, Email, API and Webhooks
How Omniscore connects to your phone system and email: call recordings via API, SFTP or upload, IMAP mailboxes, a REST API, webhooks and an MCP connector.
Calls sit in your phone system, emails in separate mailboxes, and the rest of the story in your reps’ heads. A manager sees only fragments of any one customer. Omniscore pulls these sources into one workspace: one timeline per customer, every conversation reviewed by AI and attached to the right deal.
Phone systems: calls with AI review
Omniscore doesn’t need a particular phone system — it needs the recordings. There are three ways to get them in:
| How | What it takes | Good for |
|---|---|---|
| Your provider’s API | We set up the connector during onboarding — usually within a week | RingCentral, Aircall, Dialpad, Zoom Phone, Nextiva, 8x8, Twilio and other cloud phone systems |
| SFTP or a folder sync | Your PBX drops recordings into a folder, we pick them up | An on-premise PBX or a call recorder |
| Upload | Drag and drop up to 20 files at a time: MP3, WAV, M4A, AAC, OGG, Opus, WebM, MP4 | Older calls, Zoom exports, a quick start before the connector is live |
Once a recording is in, the review shows up about two minutes later: a transcript with speakers and timestamps, a score against your checklist with a quote from the call, a summary, the outcome and the next step. The call attaches itself to the customer’s deal, and missed calls without a callback are tracked for every rep. Your reps keep calling as usual, from the same numbers. What exactly the AI checks is on the AI call analysis page.
Email: any mailbox in one customer timeline
Connect a shared sales inbox or your reps’ mailboxes over IMAP. Customer emails land in the same timeline as their calls, get an AI summary and a score against the same scorecard, and reps reply from Omniscore. AI drafts replies from your knowledge base, and the manager sees who has been waiting for an answer, and for how long.
Telegram
If your customers message you on Telegram, connect a company bot — or your reps’ own accounts through Telegram Business, so chats from their phones land in Omniscore in both directions.
REST API and webhooks
- REST API with tokens or OAuth 2.1: deals (including create-or-update by your own ID and stage moves), customers, companies, products and prices, pipelines, custom fields, tasks, notes and the deal timeline, plus linking conversations to deals.
- Webhooks, signed with the Standard Webhooks scheme: deal, task, payment and customer events in real time — to keep another CRM, an ERP or a spreadsheet in sync.
Ask about your data from Claude or ChatGPT
The Omniscore MCP connector lets you ask Omni’s questions — “Who haven’t we called back?”, “Which deals are stuck?” — from your own Claude, ChatGPT or Cursor. The connector reads your data with your permissions; it doesn’t change anything.
Notifications and digests
Every Monday the team gets an email digest of the week. Alerts and daily digests can also go to a manager’s Telegram.
Custom connectors
A connector to your CRM, ERP or an unusual phone system is a custom module: from $149 a month, with development quoted separately. See the pricing page for how modules are priced.
On the roadmap
- SMS and WhatsApp in the same inbox as calls and email;
- Instagram and Facebook Messenger;
- one-click Gmail and Microsoft 365 connection;
- conversations, analyses and scores in the REST API.
Want to check whether your stack is covered? Tell us what you use, and we’ll show you how it connects during a free 14-day pilot.