Deep dive · Qalqul Engine · shipped
Qalqul: Botpress integration
Integrating Botpress v12 into Qalqul's contact-centre suite, so bots, human agents and tickets share one conversation and hand-off path.
Problem
Qalqul’s clients, banks, insurers, healthcare and retail, wanted bots on their channels that could answer the routine questions and hand the rest to an agent with the context intact. Botpress v12 gave a strong bot runtime, but on its own it was a separate product next to the contact centre.
Constraints
- Hand-off without loss: an agent picking up a bot conversation sees the whole exchange and what the bot understood.
- Client-specific understanding: Arabic, French and Darija, with each client’s own intents.
- Embedded everywhere: the same bots run in web widgets, mobile SDKs and messaging channels.
Architecture

Key decisions
- Bots are participants, not a separate product. A bot is one more participant in a Qalqul conversation, so hand-off is a routing decision, not a migration.
- Own the understanding. Botpress calls Qalqul’s NLU engines for intents and entities.
- Work in Botpress core where needed. Some integration needed changes in Botpress v12 itself, not just a plugin.
Results
Numbers to come.