Integrations
The phone finally talks to the tools you already use.
The context arrives on screen before you pick up, and the write-up goes back into your CRM after you hang up. With no double entry, and without your CRM’s logic getting into the telephony engine.
What flows
Three exchanges, not fifty settings.
A useful telephony integration does three things. The rest is configuration noise.
Before the call
The incoming number is looked up in your CRM. The name, the company, the open case and the last exchange appear on the call screen. A stranger stays a stranger — we do not invent a record.
During the call
One click opens the full record in your tool. Your notes are entered in the same place, whichever of the two you prefer to work in.
After the call
Duration, outcome, recording, transcript and summary are written into the contact’s activity. A callback task is created if a deadline was spoken.
Catalogue
The connectors available.
CRM and sales
Support and customer service
Office and directory
Team chat
Line of business
Automation
A missing tool is not a refusal. The public API and signed webhooks cover the cases we did not anticipate, and we build the connectors that several customers ask for. See the developer documentation
Architectural rule
Your CRM cannot take your telephony down.
A connector that wakes badly, a third-party API that is down or an expired token must never delay a ringtone. That is why integrations run alongside the call engine, never inside it.
- The record lookup has a short hard timeout. Past it, the call rings with no context rather than ringing late.
- Writes to your CRM are queued and replayed: a two-hour outage at your vendor loses no write-up.
- Every webhook is signed, time-stamped, retried, and carries an idempotency key so a replay duplicates nothing.
- A connector failing repeatedly is disabled and reported, not left looping in silence.
Inbound call
The telephony engine rings the handset. It waits for nobody.
Lookup in parallel
The connector queries the CRM. If it answers in time, the context appears; if not, the call rings anyway.
After hang-up
The event goes into a durable queue. Writes are replayed until confirmed.
Sustained failure
The connector is paused, an alert goes out, and nothing is lost — the queue resumes once it is fixed.
When the connector does not exist
There is still a public API, and it is the same one we use.
Our own screens consume that API and nothing else. It is the only serious guarantee that it will stay complete: the day it is missing something, our application stops too.
- Versioned REST — a version stays served for twelve months after its successor is announced.
- Signed webhooks — every event carries a signature and a replay identifier.
- Scoped tokens — a token can do only what you granted it, site by site.
- Sandbox — a test environment with real calls and fake numbers.
Authentication and directory
Your users sign in the way they do everywhere else.
Konvoice has no wish to manage one more password inside your company.
| Requirement | How | Available |
|---|---|---|
| Single sign-on | OpenID Connect with Microsoft Entra ID, Google Workspace, Okta, Keycloak | Yes |
| SAML single sign-on | SAML 2.0 for enterprise identity providers | Yes |
| Two-factor authentication | Authenticator app, security key, or your identity provider’s own | Yes |
| Automatic account creation and removal | SCIM, or LDAP and Active Directory synchronisation | Yes |
| Roles inherited from groups | Your directory groups feed Konvoice roles | Yes |
| Company directory on the handsets | Internal contacts appear on the phone, updated automatically | Yes |
A connector that writes into the wrong field does more damage than a connector that is missing.
Which is why the field mapping is reviewed before go-live
Questions about integrations
Are integrations charged separately?
What data leaves for our CRM?
Can we test without touching production?
What happens if we change CRM?
See Konvoice on your own numbers.
Thirty minutes, your call plan, your network constraints. We cut the link live and show you what keeps running.
No commitment. No card number asked for.