Questions people ask before they sign up

Takallam is an AI customer-support platform built in the UAE.

You create AI agents, connect them to your knowledge, and put them in front of customers on four channels — a QR code they scan and speak to, chat on your website or inside your app, your support inbox, and a phone number. Behind those sits a support console: one inbox across all four channels, human takeover in the same conversation, tickets and SLAs, a knowledge base, analytics, and a workflow builder for what happens after the conversation ends.

One agent. Every channel. One platform instead of a ticketing suite, plus an AI add-on, plus a separate voice vendor.

Most businesses can have a first agent answering the same day.

You answer four questions at sign-up and give Takallam your website. It provisions the workspace, crawls your site, builds a knowledge base from what it found, and drafts your first agents. The time you actually spend is on reviewing what it learned and deciding what each agent is allowed to do.

No — onboarding, the knowledge base, the agent builder and all four channels are point-and-click. A developer is only needed if you want the mobile SDK inside your own app, or if you want to drive Takallam from your own backend through the API.

It is a printed code that a customer scans with their phone camera and then speaks to.

The page opens voice-first — no app to download, no number to dial, no queue — and the customer can switch to text mid-conversation without losing the thread. You print a different code for each location, so a code on a hotel room door and a code on a shelf edge are separate and separately measurable.

Yes, and it keeps one record of the customer across them. Someone who called this morning and emails this afternoon does not start again. You can also run a different agent per channel if the jobs are genuinely different — reservations on the phone, billing in chat.

No. Turn on the ones you want and leave the rest off. Plenty of teams start with chat on the website or a QR code in one location, then add the support inbox and the phone line once they have watched the agent handle real questions.

You forward your support address to Takallam, or connect the mailbox directly.

The agent reads the whole thread, replies in-thread from your own address in the language the customer wrote in, and reads attachments — an invoice, a booking confirmation, a photo of a damaged item. What it should not answer is tagged by intent, routed by your rules, and escalated to your team with the full thread attached. You can run it in draft mode first, where the agent writes and a person approves, until the team trusts it.

Yes. Point an existing number at Takallam or take a new one. Either way, calls the agent cannot handle route to your team with the full transcript attached, and you define what happens after hours.

Yes — Emirati and wider Gulf dialect, in voice and in text.

This is the reason Takallam exists rather than being a translation layer bolted onto an English-first product. Dialect is the default case here, not an edge case someone remembered to test.

The agent follows them. Code-switching is normal in the UAE, so Takallam tracks the language the customer is actually using and answers in the same register rather than forcing them back to one language.

English and Arabic, and you choose per agent. Arabic covers Modern Standard as well as Emirati and Gulf dialect, and you set the register the agent replies in — a hotel front desk and a bank should not sound the same.

From your knowledge base, not from the open internet.

Takallam builds that base by crawling your website, and you add documents, price lists and policies on top. In testing, every answer shows the source it came from, so you can tell a knowledge gap from a tone problem.

Then you add them. Upload PDFs and documents, write entries directly, or connect the system where the answer actually lives — a PMS, a booking system, an order database. The website crawl is a starting point, not the ceiling.

It answers from your knowledge base and is instructed to escalate rather than guess.

You set the line: which topics it must never answer alone, what it says when it does not know, and what confidence level sends a conversation to a person. The test screen exists so you can push it with your awkward questions — refunds, complaints, the things it should refuse — before anyone outside sees it.

A person on your team takes over in the same conversation. Takallam flags it, puts it in the console with the full transcript, and your agent continues in the same thread — so the customer does not repeat themselves and never sees a ticket number.

Yes, per agent and per channel. Common triggers are low confidence, a tone the agent reads as unhappy, a topic it is not allowed to touch, or an explicit request for a human. You can also set different rules for a phone call than for a chat message.

Yes. Anything that outlives the conversation becomes a ticket with an owner, a state and an SLA clock. The difference is that the ticket is a record for your team, not something the customer has to quote back to you.

In the UAE region by default — me-central-1. Conversations, transcripts and knowledge bases are data resident in-region, and you decide what is retained and for how long.

Your team, according to the roles you set in the console. Access is role-based, data is encrypted in transit and at rest, and retention windows are yours to configure rather than something you inherit.

Not today, and we will not claim otherwise.

Takallam is pre-launch. What exists now is architectural: data resident in the UAE region by default, encryption in transit and at rest, role-based access in the console, and retention you control. The platform is built to support formal compliance work, and we will say so plainly when a certification is actually held rather than in advance of it.

You pay per interaction, and each channel is priced separately.

A phone call, a chat message and an email do not cost the same to deliver, so they are not priced as if they did. An email thread that keeps going is not counted again each time it continues. There are no per-seat licences and no minimum commitment. Takallam is pre-launch, so rates are being set with the first cohort — we quote against your real volume rather than publish a number that would not fit you.

No. There are no seats, so putting your whole support team in the console changes nothing on the bill. You are charged for what your customers do, not for how many colleagues can log in.

It puts you in front of the first cohort. You tell us which channels you need and roughly what volume you handle; we come back with a rate and a setup slot. There is no payment and no commitment at that point.

Yes. Every action in the console is an endpoint — create agents, push knowledge, start conversations, read tickets, trigger workflows — over a REST API at https://api.takallam.ai/v1, with signed webhooks for conversation, escalation and workflow-run events.

Yes. There is a drop-in embed for the web and SDKs for iOS and Android, so the agent runs inside your product rather than in a window next to it, and hands over to your team without leaving the app.