Connecting a chat assistant to your CRM and ERP: one contract, many systems
How Kav is being built to answer deal, case and invoice questions from your CRM or ERP through common contracts. The contracts exist; vendor connectors are planned.
This is a roadmap. Kav does not connect to a CRM or an ERP today. The common contracts described here are built. The connectors to specific products are being built and none is available yet.
Every CRM answers "what is the status of this deal?" in its own way, and every accounting system answers "is this invoice paid?" in its own way. An assistant that had to learn each dialect would be rebuilt for every customer.
One contract per question
Kav defines each question once, as a contract: what goes in and what comes out. A connector translates between the contract and one specific system. The assistant, the flows and the rules only ever see the contract, which is why adding a system means writing a translation layer and nothing above it.
The contracts that exist
- Lead capture, with a confirmation step before anything is written.
- Deal or case status.
- Invoice status.
- Open balance.
How a question will be answered
- A customer asks, in their own words, on the website widget, WhatsApp or Telegram.
- The assistant picks the matching contract.
- The connector asks your system the question and returns typed fields.
- The amount, date or status reaches the customer through a template. The model writes the words around it, never the figure (why).
Planned connectors
CRM: HubSpot, Pipedrive, Zoho, monday, Dynamics and Salesforce. ERP and accounting: Odoo, Green Invoice, iCount and Priority. "Planned" is the accurate word for each. We are not giving dates and we are not claiming any of them works today.
What works today
Booking against Google Calendar works, and a free live demo, on request, shows how a connected system and the assistant fit together. Tell us which system matters to you; it helps decide the order.