Teammates.ai wants to be the one AI platform a Gulf or wider MENA business needs: "Sara" for hiring, "Raya" for customer support, and "Adam" for sales, all sharing one dashboard and, notably, one pool of credits. The Dubai-based company rebranded from its original name, Uktob.ai, in early 2025, and by its own account the earlier product had already organically reached over 400,000 users and around 100,000 monthly active users before the relaunch — enough traction to earn it a spot on the UAE Ministry of Economy's Future100 list. It has since closed an undisclosed funding round backed by Hustle Fund, Access Bridge Ventures, Oraseya Capital, Beyond Capital, and a group of unnamed angels.
That puts Teammates.ai in an unusual spot for this series: it isn't a Silicon Valley platform retrofitting Arabic support as an afterthought, it's a homegrown Gulf competitor built around the same pitch — omnichannel coverage plus genuine Arabic dialect depth. If you're comparing it against Qalyb or anyone else, it deserves a closer look than "does it support Arabic," because on paper, it clearly does. The more useful questions are what its own marketing says about performance, and how its pricing behaves once you're a paying customer rather than a demo prospect.
What Raya Actually Offers
Across its various product pages, Raya's channel list adds up to phone and voice calls, WhatsApp, Instagram, email, and live chat, with integrations into Slack, Microsoft Teams, Zendesk, Salesforce, and HubSpot. The company advertises 50+ languages overall and, more specifically, 20+ Arabic dialects — with Egyptian, Gulf, Levantine, and Maghrebi Arabic named directly on its Arabic-chatbot page, alongside a claim of serving 22 Arab countries. That's genuinely broad dialect coverage, arguably broader in raw geographic spread across the Arab-speaking world than most vendors in this comparison series attempt.
On the operational side, Teammates.ai claims a five-minute setup, onboarding "in under 10 minutes," the ability to "handle 10,000+ chats at once," and sub-two-second response times. In October 2025 it also launched an "Enterprise Sandbox" — a demo environment meant to let a prospective customer experience the AI's autonomy before connecting any of their own systems, which is a reasonable way to kick the tires with zero integration risk.
The Resolution-Rate Problem: 78% Here, 85% There
Here's where it gets less tidy. As of September 2026, Teammates.ai's own Arabic-chatbot page states that Raya "resolves 78% of tickets with no human needed." Its general AI-chatbot solutions page, on the same site, states that Raya "resolves 85% of tickets without human help" and separately claims it "resolves 85% of tier-1 and tier-2 tickets." Neither page discloses a methodology — what counts as "resolved," across which channel mix, measured over what time period, or against what ticket complexity.
This isn't a one-off typo we happened to catch. An independent review published in July 2026 by eesel AI flagged the same inconsistency and went looking for outside validation of either number, reporting that it found "nothing citable on Reddit, G2, Capterra, or Trustpilot" to back up Teammates.ai's resolution claims. The same review noted a separate first-party stat — that Raya cuts average resolution time "from 26 hours to 38 minutes" — which is the kind of number that would be genuinely impressive if it came with a source, a sample size, or a customer name attached to it, none of which the page provides.
None of this means Raya doesn't work — it likely does, for a meaningful share of tickets, as plenty of AI support tools do. It means that if a vendor can't keep its own resolution number consistent across two of its own pages, that figure isn't something to build a purchasing decision on. Ask any AI support vendor, Teammates.ai included, to define what "resolved" means in the number they quote you, and whether it's been measured or audited by anyone outside the company.
How the Credit-Based Pricing Actually Works
Teammates.ai's pricing is refreshingly public — a real advantage over vendors that gate pricing behind a sales call. The published tiers are Free at $0/month with 10 credits, Pro at $25/month with 50 credits, Business at $50/month with 100 credits (marked "Popular"), Scale at $100/month with 200 credits, and a custom Enterprise tier above that.
The catch is what a "credit" is actually worth, because it isn't the same across the three AI teammates that share one wallet. Sara, the hiring assistant, costs 10 credits per interview. Adam, the sales assistant, costs 10 credits per 30-minute call. Raya, the support assistant, costs 1 credit per 10 responses — meaning 100 monthly credits theoretically buys 1,000 support responses. But a single support ticket usually takes more than one reply to close. eesel AI's review does this math directly: assuming roughly five agent replies to resolve a typical ticket, 100 credits doesn't stretch to 1,000 tickets, it's closer to 200 — and that's before Sara or Adam draw against the same shared pool for hiring or sales activity happening in the same billing month.
For a small team using only Raya for support, that arithmetic might land fine. For a team planning to run all three "teammates" at once — which is the platform's core pitch — a hiring push or a sales-calling sprint in the same month can quietly eat into the credits you were counting on for support, with no separate budget line to protect it. It's worth modeling your own reply-per-ticket average against these numbers before picking a tier, rather than taking the credit count at face value.
What to Actually Check Before You Switch, or Stay
A few concrete questions are worth asking of Teammates.ai, or of any vendor you're weighing against it. Ask for the exact methodology behind whichever resolution number they quote, since the published figure has already moved between pages. Ask to run a proof-of-concept against your own real conversation history rather than a scripted demo — the independent review found no obvious way to simulate Raya against a company's actual ticket backlog before going live, so push for that if it matters to you. Work through the credit math against your real monthly ticket volume and reply pattern, and get it in writing what happens if you exceed your wallet mid-month. If voice or Instagram carries meaningful volume, test those channels in your own dialect rather than trusting a general "Arabic supported" claim. And ask what a human agent actually sees when a case escalates — Raya's site describes "human-in-the-loop approvals," which is a rollout control, not a description of what context a human gets at hand-off.
If none of that is disqualifying and what you mainly need is broad pan-Arab dialect reach bundled with lightweight sales and hiring tools at a low self-serve entry price, Teammates.ai is a legitimate option worth shortlisting. If your ticket volume runs high enough that credit-wallet math becomes a monthly headache, or your customers are concentrated specifically in the Gulf rather than spread across Egypt, the Levant, and the Maghreb, it's worth comparing against options built more narrowly around that.
Where Qalyb Differs
Qalyb was built around a similar starting premise — that Arabic-speaking markets deserve more than a translation layer bolted onto a Western chat product — but takes a different shape from Teammates.ai in three specific ways. First, channel coverage runs through one agent and one knowledge base across voice, WhatsApp, Instagram, Messenger, kiosk, and web chat, rather than separate "teammates" for separate functions sharing one credit pool. Second, hand-off to a human comes with a built-in co-pilot — knowledge search, suggested replies, form auto-fill, and a call or chat summary — so an escalation arrives with context instead of a blind transfer. Third, the dialect focus is concentrated specifically on Gulf and Omani Arabic, rather than spread across the wider Arab-speaking world; that's a genuine trade-off, not a strict upgrade — if your customers are as likely to be in Cairo or Casablanca as Riyadh or Muscat, Teammates.ai's broader pan-Arab dialect claims are worth weighing on their own merits. And pricing runs usage-based per agent rather than a shared wallet split unevenly across unrelated products.
If your complaint about Teammates.ai specifically is the credit-math unpredictability or the unverified resolution numbers, and your customer base is concentrated in the GCC rather than the broader Arab world, that's the gap Qalyb was built to close. If you need pan-Arab dialect breadth more than Gulf-specific depth, or you want hiring and sales tooling bundled into the same product as support, Teammates.ai's pitch is the more direct fit — worth an honest side-by-side rather than a reflexive switch either way.
Side-by-Side
| Teammates.ai (Raya) | Qalyb | |
|---|---|---|
| Pricing model | Shared credit wallet across 3 products (Free–$100/mo tiers, custom Enterprise) | Usage-based per agent, single product |
| Native voice | Yes | Yes, native from day one |
| WhatsApp / Instagram | Yes | Yes, native |
| Arabic dialect focus | Broad pan-Arab (20+ dialects, 22 countries claimed) | Concentrated Gulf and Omani dialect |
| Resolution-rate transparency | Two different first-party figures (78% and 85%) published on different pages, no third-party validation found | N/A — ask any vendor, Qalyb included, how a quoted rate is measured |
| Pre-launch testing | Enterprise Sandbox demo environment | Configured against your own knowledge base and channels pre-launch |
| Bundled hiring/sales tools | Yes (Sara, Adam) | No — purpose-built for support and outbound support-adjacent campaigns |
The Bottom Line
Teammates.ai is a real, homegrown Gulf competitor with genuinely broad dialect coverage and unusually transparent pricing tiers — credit where it's due, literally. But the fact that its own site can't settle on 78% or 85% for the same core metric, with no outside source backing either number, is exactly the kind of thing that should slow down a purchasing decision, not because it proves the product doesn't work, but because it means that specific number tells you nothing you can rely on. Pair that with a shared credit wallet spread across three products with very different burn rates, and the real work before signing isn't reading the pricing page — it's modeling your own ticket volume against it and asking for a number you can actually verify. Whether you land on Teammates.ai, Qalyb, or something else entirely, that's the homework worth doing first.
See how Qalyb compares on your specific channels — book a demo and bring your toughest support conversation.