Does Kav connect to our CRM and other systems?

Yes. Kav reaches into your CRM — and any other system you already run — through a connector: configured once in the Studio, then reused by the assistant, by flows, and by anyone on your team using the agent desk.

What a connector actually does

A connector isn't a one-off integration project. It's a capability: your CRM's "get customer record" or "update ticket status" becomes something the assistant can call, a flow can trigger, or an agent can pull up from inside their own desk — all through the same configured connection, defined once.

Today that connection speaks REST over JSON — the protocol most modern CRMs, including Dynamics, already expose. Support for SOAP, direct SQL, SFTP batch files, GraphQL, gRPC and inbound webhooks is designed into the platform and comes online as customers need it; we'll tell you plainly, before you commit to anything, whether your specific system is a fit today.

What it looks like once it's connected: Microsoft Dynamics 365

For teams already living in Dynamics, Kav ships a dedicated side panel inside Dynamics 365 itself — Kav Desk for Dynamics. An agent takes a Kav conversation without ever leaving the customer record they're already working on. Setting it up is a guided, one-time walk (see Onboarding Kav Desk for Dynamics); the screen a team comes back to afterward, to see or change what's connected, is covered in Maintaining a live Dynamics surface. Both are written for the team running Kav day to day, not as a sales pitch — read them for a concrete sense of how deep the Dynamics integration actually goes.

Nothing calls your system by accident

Every new connector starts Draft and Mock — wired into the platform everywhere it'll eventually be used, but unable to touch your real CRM. Going properly live is a separate, deliberate, audited step, and it's refused outright if no credential has been stored for it. A demo, a bulk import, or someone clicking around the Studio can never cause an unintended call to your real system.