VOKAR
The foundation we use to build conversational bots on WhatsApp and RCS, without rewriting the plumbing for every operation.
VOKAR (Versatile Omnichannel Knowledge And Relay) is the foundation we use to build conversational bots on WhatsApp and RCS, the rich messaging channels where a brand's customers already are. An operation plugs in its scenario, its copy and its rules; the core handles everything else, which is most of what costs money and never shows: message delivery, the state of each conversation, recovery after an incident, moderation, quotas, and the back office that lets people steer the programme while it runs.
A bot can be fully open: anyone writes to the brand's number, the bot answers, nobody needs a code or an account. It can also be restricted to an existing customer base, where a conversation only opens for someone the brand already identifies. That is a configuration choice, not two different products.
One core, N bots
The shared code is a versioned package, published to our private registry, that contains no client-specific reference. A new operation starts from the latest stable version instead of a blank page, and a live bot is never forced to follow the core: it consumes an exact version and decides when to move.
Open or customer-based
Open to all, the bot answers whoever writes to it, with no code and no sign-up. Backed by a customer base, it only opens for someone the brand already knows, with an identifier linking the conversation to the existing account. The entry model is a configuration point: you switch model without switching platform.
The scenario is data
Menus, replies, exit rules, error messages and, where relevant, the dated steps of a journey over time: all of it is declared as configuration. Changing a message or a rule does not touch the engine, and the behaviour of the bot stays readable by a non-technical team.