What is here, what is next, and what we are still arguing about
No dates. Takallam is pre-launch, and a dated roadmap this early is a promise someone else has to break. What follows is honest about which of these you can use today and which you cannot.
Three lanes, no deadlines
Anything in the first lane is in the product and shown on this site. Anything in the other two is not — and we would rather say so than blur the line.
In the product
12Working today. Every screenshot on this site comes from these.
- QR voiceScan a printed code and speak. No app, no number.
- In-app & web chatOne embed, or an SDK inside your app.
- EmailForward or connect your support inbox.
- Inbound phoneA new number, or point your existing one.
- English + Emirati ArabicIncluding mid-sentence code-switching.
- Agent builderIdentity, voice, knowledge, actions, exposure.
- Knowledge baseBuilt from your website, then editable.
- Human takeoverIn the same thread, with the transcript.
- Tickets & SLAsFor the things that need tracking.
- Workflow builderWhen → Then → If, on a canvas.
- Conversation analyticsWhat customers actually ask.
- REST API & webhooksEverything clickable is also an endpoint.
Building now
5Committed and in active development. Not available yet.
- Multilingual supportBeyond Arabic and English — starting with the languages the UAE actually speaks.
- MCP server & CLIDrive Takallam from your terminal and from AI tools that speak MCP.
- WhatsApp as a channelA fifth channel, on the same agent and the same customer record.
- Roles & permissionsFiner control over who can see and change what.
- Redaction controlsChoose what is masked in transcripts before anyone reads them.
Exploring
6Genuinely undecided. Requests here carry the most weight.
- More Arabic dialectsEgyptian, Levantine and Saudi beyond Gulf.
- Brand voiceA voice that is recognisably yours, not a stock one.
- Automatic QA scoringGrading conversations without a human sampling them.
- Deeper system connectorsPrebuilt links to common PMS, POS and ERP systems.
- Multi-brand workspacesOne account, several brands, separate agents.
- Proactive follow-upsClosing the loop after a conversation ends.
Nothing on this page has a committed date, and items move between lanes. If something here is the reason you would or would not use Takallam, tell us below — that is genuinely how this gets ordered.
Multilingual, starting with the languages this country actually speaks
Around nine in ten people in the UAE were born somewhere else. A support line that handles Arabic and English handles the official languages — not the ones a lot of customers are most comfortable asking a question in. That is the gap we are closing next.
- First wave targets the UAE's largest language communities — Hindi, Urdu, Malayalam, Tagalog and Bengali.
- Then the languages that matter for tourism and trade: Russian, Mandarin, Farsi and French.
- Same agent, same knowledge base, same customer record — a language is not a separate bot.
- The agent replies in the language the customer used, and escalates in the language your team reads.
An MCP server and a CLI
Everything in the console is already an API call. The next step is making Takallam something you can drive from a terminal, and something an AI tool can operate directly through the Model Context Protocol — so an assistant can create an agent, push knowledge or read a conversation without a person clicking through screens.
- A CLI for the things you do repeatedly: publish an agent, sync knowledge, tail workflow runs.
- An MCP server so AI tools can operate Takallam as a set of typed tools rather than by scraping a UI.
- Scriptable and CI-friendly, so an agent's configuration can live in your repository.
- Same permissions as the console — the CLI cannot do anything your key is not allowed to do.
# Publish an agent from a config file in your repo
takallam agents publish ./agents/layla.json
# Re-crawl the knowledge base and show what changed
takallam knowledge sync --diff
# Follow workflow runs as they happen
takallam workflows tail --id wf_booking_confirm
# Expose Takallam to an AI tool over MCP
takallam mcp serve --scope "agents,knowledge,conversations"Ask for something
The exploring lane is genuinely undecided, and the first cohort has an outsized say in what moves out of it. Tell us the situation you are stuck in — that is more useful to us than the name of a feature.
About the roadmap
Why are there no dates?
Because we would miss them. Takallam is pre-launch and the first cohort is still shaping the order of work. A lane tells you the one thing a date is meant to: whether you can rely on it today.
Which languages are coming first?
The UAE's largest language communities — Hindi, Urdu, Malayalam, Tagalog and Bengali — followed by Russian, Mandarin, Farsi and French. If your customers speak something not on that list, say so in the form above; that is exactly how the order gets decided.
What is the MCP server for?
The Model Context Protocol lets AI tools call external systems as typed tools rather than by clicking around a browser. An MCP server means an assistant can create an agent, push knowledge or read a conversation in Takallam directly. The CLI is the same capability for a terminal and for CI.
Can we get early access to something in the "building now" lane?
Sometimes. If a specific item is the difference between using Takallam and not, mention it in the form or on the waitlist and we will tell you honestly where it is rather than guessing at a date.
Do you publish a changelog?
Not yet — there is no public release to log changes against. Once the first cohort is live, this page gains a shipped log and the lanes start moving in public.
Will requesting a feature get me a reply?
Yes, from a person. Not necessarily a yes, but you will hear back rather than watch your request disappear into a form.
Shape what gets built
The first cohort of businesses in the UAE has the loudest voice in what moves out of the exploring lane. Joining early is the way into that conversation.
Made with love in the UAE