How long does it take to connect an existing system, like a CRM?

The honest answer is: it depends on your system, not on Kav's code — so we don't publish one number that would be wrong for most organizations. What we can tell you is what's fixed, and what actually decides the time.

What's fixed: it's configuration, not development

Connecting a system to Kav doesn't mean a custom integration project or a new software release. A connection is configured in the Studio as a capability — once — and then reused everywhere the assistant, flows and channels need it. Kav's connectors speak REST, SOAP, SQL, SFTP, GraphQL, gRPC and webhooks. For teams working in Microsoft Dynamics 365, agents also get a Kav side pane inside Dynamics itself.

The three steps

1. Connect your systems. Each system you already use — CRM, billing, scheduling, a knowledge base — is set up as a capability.
2. Bring your content. Your existing articles and knowledge pages are ingested on a schedule you set, and nothing reaches a customer until someone on your team approves it.
3. Turn on your channels. Embed the website widget, or connect Telegram and WhatsApp.

What decides how long it takes

• Whether your system already exposes an interface Kav's connectors can speak to — and how quickly its owner can issue access credentials.
• Which fields your system can supply. If your vendor can't provide a field, that's declared openly in configuration rather than guessed. The Studio won't publish a connection that can't fill a field the capability requires.
• Testing before going live. Every new connection starts in draft and mock mode, unable to call your real system. Switching it live is a deliberate, recorded step, and it's refused if no credential has been stored for it.
• Your team's content review. Every knowledge article needs a submitter and a different approver before customers see it.
• Meta's approval, if you want WhatsApp — that step is on Meta's side, not Kav's.