Lead capture and invoice status in chat: confirmed writes and identity-protected lookups
How Kav is designed to capture leads with a confirmation step and look up invoice or deal status only for the verified customer. Contracts built; connectors planned.
Roadmap, not availability. The contracts for lead capture, deal and case status, invoice status and open balance are built. Connectors to specific CRM and ERP products are planned and none is available yet.
Two things go wrong when a chat assistant meets a business system: it writes something nobody approved, or it reads something about someone it should not. The design addresses both.
Writes need a confirmation
Capturing a lead writes into the CRM. So the assistant shows the customer what it is about to send and waits for an explicit yes before anything is written.
Lookups are identity-protected
Deal status, case status, invoice status and open balance all concern a specific person or company. The assistant never takes "which customer?" from the chat. The customer is identified on the server from a verified sign-in or a protected form, and the lookup is made with that identity. There is no field in the contract for who is asking, so typing someone else's name changes nothing.
Numbers from the system
An invoice amount, a due date or a deal stage is read from your system and shown through a template. The model writes the sentence around it (the rule).
Unsure means no
If the identity cannot be established, or the system cannot be reached, the assistant does not guess an answer. It says it cannot answer that.
Status of the work
Contracts: built. Connectors for HubSpot, Pipedrive, Zoho, monday, Dynamics, Salesforce, Odoo, Green Invoice, iCount and Priority: planned. If one matters to you, tell us.