Two roles available now.
Customer Service & Sales and Finance document collection are available for onboarding. A capability is described as active only after its channels, limits and workflow are confirmed and tested.
Customer conversations, handled.
Channels and replies
Kai handles configured WhatsApp and email customer conversations. It can reply in the customer's language where the connected workflow supports it. Other input types are confirmed and tested per setup before they are offered.
Connected scope
Kai uses only what the configured WhatsApp or email workflow makes available. Permanent customer memory and cross-channel identity matching are not universal current capabilities.
Role-specific sales work
Customer Service & Sales is available for onboarding. Lead qualification, research, follow-up, quotes and payment steps are included only when the specific workflow has been agreed and tested.
Owner boundaries
Asked directly, Kai says it is AI. The owner can pause Kai or take over through Telegram. Price, discount, link and escalation rules are setup-dependent and must be tested before they are described as active safeguards.
Document collection, with clear boundaries.
Select collection sources
Finance is available for onboarding. WhatsApp, email or any other collection source is described as active only after its access and collection path have been tested.
Define fields and categories
Required fields, categories and exception handling are agreed during onboarding. Extraction and classification are setup-dependent and not presented as universal behavior.
Set document rules
Accepted document types and duplicate handling are agreed and tested during onboarding. The site does not assume that every connected workflow rejects them automatically.
Choose the output
The output destination, format and timing are agreed and tested per setup. The Finance role does not provide bookkeeping, accounting or tax advice.
Define the sales workflow before activation.
Choose the record
The fields and source for any lead record are agreed during onboarding. No cross-channel identity match is assumed.
Choose the sales steps
Qualification, service guidance, prices, discounts, promises and owner decisions are included only after their workflow has been agreed and tested.
Choose any follow-up
Timing, stop conditions and any follow-up action are setup-dependent. Follow-up is not presented as active by default.
Know what is connected and what is not.
Knowledge
Any business knowledge, tone behavior, price guidance, files or approval path is setup-dependent and tested before activation.
Integrations
WhatsApp, email and Telegram control are confirmed per client. Any other integration is quoted and approved before it is presented as available.
Coming soon
Reviews, supplier chasing, win-back, reception, collections, ad campaigns and technical support are in development and cannot be booked today.
The owner controls what is activated.
Connected conversations
Handle configured WhatsApp and email conversations in the customer's language where supported.
Anything beyond the core
Activate only after its permissions and workflow have been agreed and tested.
No assumed approval flow
Keep the decision with the owner unless a tested workflow says exactly what Kai may do.