eslamfatallaheslamfatallah
eslamfatallah
Jul 14, 2026

Q: Arabic AI, Live Product Data & CRM Integration

Hi DM Champ team,

I’m considering DM Champ for a furniture company and may later offer it under our brand.

Could you clarify:

1. How well does the AI support Egyptian Arabic and Arabic voice notes?

2. Can it access live product data via Google Sheets/API for updated prices, stock, images, and specifications while avoiding hallucinations?

3. Can it save qualification data in custom fields, score leads, and assign them to branches or agents?

4. Can AI follow-ups use conversation context and stop automatically when customers reply?

5. Do you support two-way CRM integration through API/webhooks or n8n?

6. Can managers track response times, unattended leads, follow-ups, and performance by agent or branch?

7. Does White Label provide isolated client workspaces and permit resale under our brand?

Thank you!

Founder Team
sohaib.dmchamp

sohaib.dmchamp

Jul 14, 2026

A: Hi Eslam,

Thanks for the detailed questions. Answers in order:

1. Arabic and voice notes. Yes on both. The AI detects the language a contact writes in and replies in that same language, so Arabic (including Egyptian dialect) works out of the box with no extra setup. There is no separate "dialect" switch, the underlying model just handles it naturally. Incoming voice notes are automatically transcribed so the AI reads and replies to them, and the transcription model is tuned for multilingual and noisy audio. One caveat to be straight with you: the AI replies in text, it does not generate its own voice-note replies (you can have it send a pre-recorded audio file, but not AI-synthesised speech).

2. Live product data without hallucinating. Yes. This is what Custom Functions are for. You wire the bot up to an external source (your own API, a webhook, or a Google Sheet via its API) and during a live chat the bot calls out, waits for the answer, and quotes the real current price, stock, image, or spec back to the customer. So pricing/stock stays accurate because it is fetched live, not memorised. On top of that the bot is grounded in your FAQ/knowledge base and is explicitly instructed not to invent answers, if it does not have a verified fact it says so or routes to a human rather than guessing. There is no one-click "Google Sheets connector," it is set up as a custom function pointing at the sheet.

3. Qualification data, scoring, and assignment. Custom fields: yes, you define the fields you want captured and the AI saves what it collects during the conversation into them. Assignment: yes, chats/contacts can be assigned to specific team members, manually or with automatic round-robin. Two honest limitations: there is no built-in numeric "lead score" field, most people handle qualification with auto-tags (the bot tags a contact when it meets a rule you describe) plus a visual deals pipeline where leads move through your own stages. And there is no dedicated "branch"/multi-location object, teams model separate locations either with team-member assignment or, at the Agency level, with separate sub-accounts per branch.

4. AI follow-ups. Yes, and this is a strong area. There are automatic follow-ups that re-engage contacts who go quiet, and they are written from the actual conversation history, not a generic template (cold, never-replied leads are the one templated exception). They stop automatically the moment the customer replies, and also skip if the chat was handed to a human, the sale closed, or the contact opted out.

5. Two-way CRM integration. Yes. We have a full REST API (push contacts and messages in, pull data out) and outbound webhooks that fire on around 20 events (new contact, new message, human alerted, appointment booked, deal/stage changes, daily summary, and more). That covers n8n, Make, and Zapier, you connect them to our API and webhooks the same way you would any REST service, and there is a documented step-by-step for n8n specifically. There is also a native GoHighLevel two-way integration if you use GHL. To be clear, n8n/Zapier are supported through the API and webhooks, not a one-click prebuilt app.

6. Manager tracking. Partial, so I will be honest about the edges. You get account and per-campaign analytics (sent, delivered, read, replied, booked, contacts, credits) plus a reply-rate heatmap, and a daily AI summary that surfaces which chats needed human attention and where leads stalled. The inbox also shows how many chats are sitting unassigned. What we do not currently have is response-time metrics or performance broken down per individual agent or per branch, analytics is at the account and campaign level, not sliced by agent. If per-agent reporting is a hard requirement for you, I would rather tell you now than have you find out later.

7. White Label. Yes to both parts. On the Agency plan you get full white-labeling: your own branded domain (app.yourbrand.com), your logo, colours, and name throughout, so your clients never see us. Each client is a fully isolated sub-account with its own campaigns, contacts, and chats, and clients cannot see each other. You can resell under your brand and set your own credit pricing through your own Stripe, or invoice clients off-platform, whichever suits you.

You can dig into any of these at https://help.dmchamp.com, and our community is at https://skool.com/dm-champions.

Happy to answer anything else.

Share
Helpful?
0
Log in to join the conversation