Skip to main content

Wittify.ai — Ultimate Comprehensive FAQs

This guide covers everything about Text, Voice, and Hybrid Assistants, including setup, customization, integrations, deployment, testing, and troubleshooting. Whether you’re a first-time user or an advanced operator, you’ll find detailed, actionable answers here.

1. General Platform Overview

Q1.1 — What is Wittify.ai?
Wittify.ai is a no-code platform for creating multilingual, multimodal AI assistants that interact with customers via text, voice, or both, across websites, mobile applications, messaging apps, and telephony systems.
Q1.2 — What makes Wittify.ai unique?
  • Arabic-first: Supports 25+ Arabic dialects (e.g., Saudi Najdi, Hejazi, Egyptian, Syrian, Jordanian, Moroccan, Tunisian) + 100+ languages.
  • Multimodal: Text 💬, Voice 🎙, or Hybrid 🎙💬 experiences.
  • No coding required: User-friendly, quick setup.
  • Deep integrations: CRMs, booking tools, telephony systems.
  • Real-time control: Monitoring, analytics, and human takeover.
Q1.3 — Who can use Wittify.ai?
Startups, enterprises, e-commerce stores, government agencies, customer support teams, agencies, and independent professionals.
Q1.4 — What can Wittify.ai agents do?
  • Answer FAQs and policy questions.
  • Qualify leads & capture customer data.
  • Schedule appointments.
  • Handle support tickets.
  • Process multimedia (voice notes, images, soon documents).
  • Integrate with CRMs, booking tools, and ticketing systems.
Q1.5 — What types of assistants can I create?
  1. Text Assistant 💬 — Website widget, mobile applications, WhatsApp, Messenger, Instagram.
  2. Voice Assistant 🎙 — Real-time speech on websites, mobile applications, telephony (Twilio, SIP).
  3. Hybrid Assistant 🎙💬 — Combines text & voice for websites, mobile applications, and web apps (not for social/messaging or telephony).

2. Account Creation & Profile Setup

Q2.1 — How do I create a new account?
Go to Wittify.ai → Sign Up, choose email, Google, Microsoft, or Apple login. Email sign-ups require OTP verification.
Q2.2 — What information is required?
  • Full name
  • Phone (OTP verification)
  • Password (email sign-ups)
  • Company name
  • Website URL (optional)
Q2.3 — Can I update my profile later?
Yes — from the top-right menu → Profile Settings.
Q2.4 — Do I need a business email?
Not required, but recommended for integrations like WhatsApp Business API.

3. Plans, Billing & Payments

Q3.1 — What subscription plans are available?
Free, Starter, Business, Premium, Enterprise — each with different limits, integrations, and support levels.
Q3.2 — Key differences between plans:
  • Monthly text conversation limits
  • Monthly voice minutes
  • Number of assistants
  • Voice recording availability
  • Level of integrations (Basic, Advanced, Custom)
  • Branding removal (Powered by Wittify)
  • Analytics depth (Basic, Advanced, Custom)
  • API access
  • Onboarding/training sessions
  • Support level (AI support, Email, Priority, Dedicated)
  • SLA availability (Enterprise)
Q3.3 — How do I upgrade or downgrade?
  • Upgrade: Dashboard → Plans & Subscriptions → Upgrade Plan → Confirm payment.
  • Downgrade: Dashboard → Plans & Subscriptions → Select lower tier. Changes apply next billing cycle.
Q3.4 — Can I buy extra usage without changing plans?
Yes — purchase add-ons for additional text conversations or voice minutes.
Q3.5 — Supported payment methods:
Credit/debit cards (other payment options coming soon).
Q3.6 — Viewing invoices & billing history:
Dashboard → Plans & Subscriptions → Billing History → Download invoices.
Q3.7 — How to cancel a plan?
Dashboard → Plans & Subscriptions → Cancel Plan → Reverts to Free plan at end of billing cycle.

4. Building & Configuring Assistants

Q4.1 — What is the “Agent Name” used for?
Internal identification in your dashboard. Pick clear, descriptive names. This will not be shown to your customers.
Q4.2 — What are “Core Instructions” (System Prompt)?
The assistant’s brain — define:
  • Role & Goal (support, sales, booking).
  • Tone & Style (friendly, professional).
  • Language & Dialect (English US, Arabic Saudi Najdi).
  • Speech Style (short & natural for voice).
  • Boundaries (no legal/medical advice).
  • Compliance (industry rules, disclaimers).
Q4.3 — Best practices for Core Instructions:
  • Write in full sentences.
  • Be specific — vague prompts cause unpredictable behavior.
  • Include fallback instructions for unknown questions.
Q4.4 — Can I start from templates?
Yes — select pre-built templates (Customer Support, Sales, etc.) and edit them for your brand.
Q4.5 — What is “Creativity Level” (Temperature)?
Controls response variability:
  • 0.0–0.3: Factual and consistent.
  • 0.4–0.6: Balanced (recommended default).
  • 0.7–1.0: Creative and varied.
Q4.6 — What are “Starter Questions”?
Pre-defined prompts shown at conversation start (e.g., “Book a demo”). Helps guide user flow.
Q4.7 — Can I restrict certain topics?
Yes — clearly list restricted areas in Core Instructions.

5. Appearance & Multilingual Experience

Q5.1 — How many interface languages can I use for the web widget?
Up to 4 languages at once. Auto-detect and switch between RTL and LTR layouts.
Q5.2 — What can I customize per language?
  • Header title
  • Header subtitle/tagline
  • Welcome message (text or voice)
  • Input placeholder text
  • Disclaimer text
Q5.3 — Can I change branding and layout?
Yes — upload company logo & bot avatar, choose colors, fonts, and widget position. Premium plans can hide “Powered by Wittify.”
Q5.4 — Can the widget auto-open?
Yes — enable auto-open on first visit for higher engagement.

6. Knowledge Base (KB) Management

Q6.1 — What content sources can I add?
  • Files: PDF, DOC/DOCX, XLS/XLSX, TXT (up to 100 MB each).
  • Links (URLs): Documentation, help centers, product pages.
  • FAQs: Curated question-and-answer pairs for precise replies.
Q6.2 — How do I refresh content from a URL?
Remove the link from your KB, then re-add it — this re-indexes the page.
Q6.3 — Best practices for KB content:
  • Keep information accurate and up-to-date.
  • Use FAQs for fixed policies (pricing, shipping, legal disclaimers).
  • Avoid overloading the KB with outdated or irrelevant pages.
  • For voice agents, keep answers concise for comfortable listening.
  • Use structured, clear language to avoid ambiguity.
Q6.4 — How often should I update my KB?
At least monthly, or immediately after changes in business operations, pricing, or policies.

7. Voice-Specific Settings

Q7.1 — How do I choose and test a voice?
Open Select Voice, preview with Play, and apply with Use Voice.
You can test with your own custom text (up to 140 characters) to hear exactly how your script will sound.
Q7.2 — What is “Enable Auto Detect Language”?
When enabled, the assistant automatically detects the caller’s language and responds accordingly.
Q7.3 — What is “Allow Interruption”?
Allows callers to interrupt the assistant mid-speech. This creates more natural, human-like conversation flow.
Q7.4 — Advanced voice timing controls:
  • End Call on Silence (seconds): Time to wait when no one speaks before ending the call.
  • Max Call Length (minutes): Hard cap on conversation duration.
  • Time Before Widget Pop-Up (seconds): Delay before the voice widget appears after page load.
  • Min Speech Duration (seconds): Filters out short noises or accidental sounds.
  • Min Silence Duration (seconds): Pause threshold before the assistant begins speaking — prevents talking over the user.
Q7.5 — Tuning tips:
  • Shorter Min Silence → snappier responses, but higher risk of interruptions.
  • Longer End Call on Silence → more forgiving for slower speakers.
  • For mobile applications, consider slightly longer pause times to account for microphone latency.

8. Integrations & Built-in Tools

Q8.1 — What built-in tools can I enable?
  • Lead Data Collection: Ask for name, email, and phone during conversation.
  • WhatsApp Campaign Sending: Send bulk messages and handle replies in real time.
  • Ticketing System (coming soon).
  • Search Tool & MCP Server (coming soon) for advanced integrations.
Q8.2 — Which CRMs are supported?
  • Salesforce: Send leads directly to your CRM.
  • Zendesk: Create and manage support tickets.
Q8.3 — Which booking tools are supported?
  • Google Calendar
  • Calendly (real-time scheduling)
Q8.4 — Voice telephony integrations:
  • Twilio: Connect via Account SID, Auth Token, and phone number.
  • SIP: Available upon request for other telephony providers.
Q8.5 — Can I integrate Wittify.ai into my mobile application?
Yes — agents can be embedded in iOS and Android apps via:
  • Web views for the chat or voice widget.
  • Native SDK integrations.
  • Custom setups for advanced use cases (contact our team).
Q8.6 — Can I connect to my own systems?
Yes — through available integrations, APIs, or custom MCP/SIP configurations (Enterprise feature).

9. Deployment & Channels

Q9.1 — How do I embed the widget on my website?
Copy the embed snippet from Deployment and paste it before the closing </body> tag on your site.
Q9.2 — How do I deploy assistants in mobile apps?
Integrate using:
  • A web view pointing to the widget.
  • Our mobile SDK (when available).
  • Custom embedding for voice and hybrid assistants.
Q9.3 — What channels are supported for each type?
  • Text Assistant 💬: Website, mobile applications, WhatsApp, Messenger, Instagram.
  • Voice Assistant 🎙: Website, mobile applications, telephony (Twilio/SIP).
  • Hybrid Assistant 🎙💬: Website, mobile applications, web apps.
Q9.4 — Can I restrict where the widget loads?
Yes — set Allowed Domains in Deployment to whitelist specific websites.
Q9.5 — Can Voice or Hybrid assistants connect to social channels?
No — Voice is for web/mobile/telephony. Hybrid is for web/mobile only.
Q9.6 — How to deactivate an assistant without deleting it?
From Deployment, click Deactivate — you can re-enable later without losing settings.

10. Testing & Quality Assurance (QA)

Q10.1 — Pre-launch checklist:
  • Test key user flows in Preview.
  • Verify language switching and RTL/LTR behavior.
  • Ask edge case questions to confirm fallback responses.
  • Test lead collection flows — ensure data is saved in Inbox → Leads.
  • Confirm widget embedding and Allowed Domains settings.
  • For connected social channels, send real messages and check responses.
  • For voice/hybrid assistants, test interruptions, silence timeouts, and audio quality.
Q10.2 — How to improve testing results:
  • Involve multiple team members to simulate real conversations.
  • Test on both desktop and mobile devices.
  • Use different languages and dialects to check multilingual performance.

Q10.3 — Can I run pilot programs before going live?
Yes — you can deploy on limited domains, a staging site, or a closed WhatsApp group before full launch.

6. Knowledge Base (KB) Management

Q6.1 — What content sources can I add?
  • Files: PDF, DOC/DOCX, XLS/XLSX, TXT (up to 100 MB each).
  • Links (URLs): Documentation, help centers, product pages.
  • FAQs: Curated question-and-answer pairs for precise replies.
Q6.2 — How do I refresh content from a URL?
Remove the link from your KB, then re-add it — this re-indexes the page.
Q6.3 — Best practices for KB content:
  • Keep information accurate and up-to-date.
  • Use FAQs for fixed policies (pricing, shipping, legal disclaimers).
  • Avoid overloading the KB with outdated or irrelevant pages.
  • For voice agents, keep answers concise for comfortable listening.
  • Use structured, clear language to avoid ambiguity.
Q6.4 — How often should I update my KB?
At least monthly, or immediately after changes in business operations, pricing, or policies.

7. Voice-Specific Settings

Q7.1 — How do I choose and test a voice?
Open Select Voice, preview with Play, and apply with Use Voice.
You can test with your own custom text (up to 140 characters) to hear exactly how your script will sound.
Q7.2 — What is “Enable Auto Detect Language”?
When enabled, the assistant automatically detects the caller’s language and responds accordingly.
Q7.3 — What is “Allow Interruption”?
Allows callers to interrupt the assistant mid-speech. This creates more natural, human-like conversation flow.
Q7.4 — Advanced voice timing controls:
  • End Call on Silence (seconds): Time to wait when no one speaks before ending the call.
  • Max Call Length (minutes): Hard cap on conversation duration.
  • Time Before Widget Pop-Up (seconds): Delay before the voice widget appears after page load.
  • Min Speech Duration (seconds): Filters out short noises or accidental sounds.
  • Min Silence Duration (seconds): Pause threshold before the assistant begins speaking — prevents talking over the user.
Q7.5 — Tuning tips:
  • Shorter Min Silence → snappier responses, but higher risk of interruptions.
  • Longer End Call on Silence → more forgiving for slower speakers.
  • For mobile applications, consider slightly longer pause times to account for microphone latency.

8. Integrations & Built-in Tools

Q8.1 — What built-in tools can I enable?
  • Lead Data Collection: Ask for name, email, and phone during conversation.
  • WhatsApp Campaign Sending: Send bulk messages and handle replies in real time.
  • Ticketing System (coming soon).
  • Search Tool & MCP Server (coming soon) for advanced integrations.
Q8.2 — Which CRMs are supported?
  • Salesforce: Send leads directly to your CRM.
  • Zendesk: Create and manage support tickets.
Q8.3 — Which booking tools are supported?
  • Google Calendar
  • Calendly (real-time scheduling)
Q8.4 — Voice telephony integrations:
  • Twilio: Connect via Account SID, Auth Token, and phone number.
  • SIP: Available upon request for other telephony providers.
Q8.5 — Can I integrate Wittify.ai into my mobile application?
Yes — agents can be embedded in iOS and Android apps via:
  • Web views for the chat or voice widget.
  • Native SDK integrations.
  • Custom setups for advanced use cases (contact our team).
Q8.6 — Can I connect to my own systems?
Yes — through available integrations, APIs, or custom MCP/SIP configurations (Enterprise feature).

9. Deployment & Channels

Q9.1 — How do I embed the widget on my website?
Copy the embed snippet from Deployment and paste it before the closing </body> tag on your site.
Q9.2 — How do I deploy assistants in mobile apps?
Integrate using:
  • A web view pointing to the widget.
  • Our mobile SDK (when available).
  • Custom embedding for voice and hybrid assistants.
Q9.3 — What channels are supported for each type?
  • Text Assistant 💬: Website, mobile applications, WhatsApp, Messenger, Instagram.
  • Voice Assistant 🎙: Website, mobile applications, telephony (Twilio/SIP).
  • Hybrid Assistant 🎙💬: Website, mobile applications, web apps.
Q9.4 — Can I restrict where the widget loads?
Yes — set Allowed Domains in Deployment to whitelist specific websites.
Q9.5 — Can Voice or Hybrid assistants connect to social channels?
No — Voice is for web/mobile/telephony. Hybrid is for web/mobile only.
Q9.6 — How to deactivate an assistant without deleting it?
From Deployment, click Deactivate — you can re-enable later without losing settings.

10. Testing & Quality Assurance (QA)

Q10.1 — Pre-launch checklist:
  • Test key user flows in Preview.
  • Verify language switching and RTL/LTR behavior.
  • Ask edge case questions to confirm fallback responses.
  • Test lead collection flows — ensure data is saved in Inbox → Leads.
  • Confirm widget embedding and Allowed Domains settings.
  • For connected social channels, send real messages and check responses.
  • For voice/hybrid assistants, test interruptions, silence timeouts, and audio quality.
Q10.2 — How to improve testing results:
  • Involve multiple team members to simulate real conversations.
  • Test on both desktop and mobile devices.
  • Use different languages and dialects to check multilingual performance.
Q10.3 — Can I run pilot programs before going live? Yes — you can deploy on limited domains, a staging site, or a closed WhatsApp group before full launch.

11. Inbox, Conversations & Transcriptions

Q11.1 — What does the Inbox show for each assistant type?
  • Text Assistants 💬: All chat conversations.
  • Voice Assistants 🎙: Voice call recordings + transcriptions.
  • Hybrid Assistants 🎙💬: Separate tabs for text conversations and voice recordings.
Q11.2 — What can I do inside the Inbox?
  • Search by keyword, customer name, or email.
  • Sort conversations by newest/oldest.
  • Filter by channel (Web, WhatsApp, Messenger, Instagram).
  • Open full conversation threads with timestamps.
  • Play audio recordings and show/hide transcriptions.
  • Delete unwanted conversations.
  • Export lead data to CSV.
Q11.3 — Can users send voice notes or images to a Text Assistant?
Yes — users can send voice notes and image attachments. The assistant can listen/view and respond accordingly. These appear in the chat history. Support for additional file types (e.g., documents) is coming soon.
Q11.4 — Can a human take over a live conversation?
Yes — from the Inbox, pause AI responses and respond manually. You can later resume AI handling. This works across all connected channels.

12. Leads & Campaigns

Q12.1 — Where do captured leads appear?
In Inbox → Leads when the Lead Collection tool is enabled. Each lead entry contains:
  • Name
  • Email
  • Phone number
  • Source channel (e.g., WhatsApp, Website)
Q12.2 — Can I export leads?
Yes — export leads as CSV directly from the Leads tab.
Q12.3 — Can I send WhatsApp campaigns?
Yes — if your Text Assistant is connected to WhatsApp. Requirements:
  • Verified Meta WhatsApp Business account.
  • Active payment method in Meta for messaging credits.
    Workflow: Send a campaign → customers reply → the assistant handles responses in real time.

13. Managing Multiple Assistants

Q13.1 — What can I do from the main dashboard list of assistants?
For each assistant:
  • Rename — for easy identification.
  • Clone — duplicate configuration for quick setup of similar agents.
  • Deactivate — pause without deleting.
  • Delete — permanently remove.
    Click an assistant’s name to open its detailed dashboard with usage reports, quick links to Inbox, Voice Recordings, Leads, Tickets (coming soon), and Settings.
Q13.2 — Can assistants share the same Knowledge Base?
Not directly — you must upload or link the same sources to each assistant that needs them.

14. Languages, RTL & Localization

Q14.1 — Does Wittify.ai support Arabic and other RTL languages?
Yes — full RTL/LTR support. The widget can auto-switch based on site language or user input.
Q14.2 — How many languages can be active at once?
Up to 4. Each language can have:
  • Unique welcome messages.
  • Custom disclaimers.
  • Localized interface labels.
Q14.3 — Can I set different dialects of the same language?
Yes — specify dialects in Core Instructions (e.g., Arabic Saudi Najdi, Arabic Egyptian).

15. Compliance, Troubleshooting & Best Practices

Q15.1 — What policies must assistants comply with?
  • Your organization’s policies.
  • Wittify’s Terms of Service, Prohibited Use Policy, and Privacy Policy.
  • Any industry-specific compliance requirements (e.g., HIPAA, GDPR).
Q15.2 — How to improve response speed?
  • Keep Core Instructions concise and focused.
  • Use FAQs for common questions.
  • Limit Knowledge Base to trusted, stable sources.
  • For voice, shorten responses and fine-tune timing settings.
Q15.3 — How to improve accuracy?
  • Tighten Boundaries and Compliance rules in Core Instructions.
  • Add FAQs for sensitive or frequently asked topics.
  • Remove outdated sources and re-index updated ones.
  • Lower creativity (≤ 0.5) for factual accuracy.
Q15.4 — The voice talks over users or cuts them off.
  • Increase Min Silence Duration to give users more time to speak.
  • Increase Min Speech Duration so only deliberate speech triggers a response.
Q15.5 — Voice session ends too quickly.
  • Increase End Call on Silence duration.
  • Check microphone permissions and network stability.
Q15.6 — Testing tips for ongoing improvement:
  • Regularly review conversation logs.
  • Update Knowledge Base monthly.
  • Train your team on human takeover workflows.
  • Run multilingual checks for accuracy and tone.

16. Arabic Language & Dialect Excellence

Wittify.ai is Arabic-first, designed to deliver exceptional AI-driven customer interactions for businesses in Saudi Arabia, United Arab Emirates, Qatar, Kuwait, Bahrain, Oman, Lebanon, Egypt, Morocco, Tunisia, Algeria, Sudan, Yemen, Syria, Jordan, Palestine, and Libya. Our AI assistants — Text, Voice, and Hybrid — are trained to understand, process, and respond in Modern Standard Arabic (MSA) and over 25 regional dialects. They also handle mixed-language conversations (e.g., Arabic + English or Arabic + French) while preserving cultural relevance.

16.1 — Does Wittify.ai support Arabic language AI assistants?

Yes. Wittify.ai supports:
  • Modern Standard Arabic (MSA) for formal and widely understood communication.
  • Over 25 Arabic dialects, covering all GCC countries, the Levant, North Africa, and more.
  • Natural language understanding for both text and voice interactions.

16.2 — Which Saudi Arabian dialects are supported?

  • Najdi Arabic — Spoken in Riyadh and central regions; formal yet direct style.
  • Hejazi Arabic — Used in Jeddah, Mecca, Medina; softer intonation and borrowed words from other languages.
  • Eastern Saudi Arabic — Common in Dammam, Al-Khobar, Qatif; influenced by Gulf coast culture.
  • White Arabic — Modern neutral Arabic widely understood across the Kingdom.

16.3 — Which United Arab Emirates dialects are supported?

  • Emirati Arabic — Includes variations from Abu Dhabi, Dubai, Sharjah, and northern emirates; recognized by its distinctive vocabulary and pronunciation.

16.4 — Which Qatari dialects are supported?

  • Qatari Arabic — Similar to other Gulf varieties but with unique local terms and expressions.

16.5 — Which Kuwaiti dialects are supported?

  • Kuwaiti Arabic — Recognized for its informal style, influenced by historical trade and cultural exchange.

16.6 — Which Bahraini dialects are supported?

  • Bahraini Arabic — Combines Gulf Arabic structure with local vocabulary; influenced by both Arab and Persian linguistic patterns.

16.7 — Which Omani dialects are supported?

  • Omani Arabic — Diverse set of variations, from coastal Muscat Arabic to distinct interior region dialects.

16.8 — Which other major Arabic dialects are supported outside the GCC?

Egypt
  • Egyptian Arabic (Masri) — The most widely understood dialect in the Arab world; ideal for broad audience engagement.
Levant
  • Lebanese Arabic — Warm, expressive, widely used in media.
  • Syrian Arabic — Clear pronunciation, easy to understand across the Levant.
  • Jordanian Arabic — Similar to northern Levantine but with Bedouin influences.
  • Palestinian Arabic — Recognizable vocabulary and rhythm, understood across the Levant.
North Africa
  • Moroccan Arabic (Darija) — Unique sentence structure and heavy Amazigh/French influence.
  • Tunisian Arabic — Smooth rhythm and blend of Arabic, French, Italian influences.
  • Algerian Arabic — Regionally varied but widely used across Algeria and diaspora communities.
  • Libyan Arabic — Distinct vocabulary, influenced by North African and Bedouin speech.
Other Regions
  • Sudanese Arabic — Soft consonant pronunciation, distinct vocabulary.
  • Yemeni Arabic — Includes San’ani, Ta’izzi, and Hadhrami dialects with deep cultural roots.

16.9 — Can a Wittify.ai agent handle multiple dialects in one conversation?

Yes. A single Wittify agent can:
  • Detect the user’s dialect and respond in the same style.
  • Switch between dialects when serving users from different regions.
  • Use Modern Standard Arabic for formal or mixed audiences.
  • Handle Arabic mixed with English, French, Urdu, or other languages.

16.10 — Can I create an agent specialized in a single dialect?

Yes. You can design an AI assistant to:
  • Exclusively use one dialect (e.g., Najdi for Riyadh-based services).
  • Maintain consistent tone and vocabulary for a specific regional audience.
  • Serve niche markets like local tourism or regional e-commerce.

16.11 — What are some Arabic use cases for each agent type?

Text Agents
  • Najdi Arabic chatbot for Saudi government services.
  • Lebanese Arabic bot for Beirut tourism offices.
  • Moroccan Darija bot for Casablanca online stores.
Voice Agents
  • Hejazi Arabic assistant for hotel bookings in Jeddah.
  • Egyptian Arabic helpline for courier services in Cairo.
  • Tunisian Arabic sales agent for telecom providers.
Hybrid Agents
  • Saudi White Arabic + English assistant for multinational banks.
  • Egyptian + Emirati Arabic hybrid bot for airline bookings.
  • Moroccan Arabic + French hybrid bot for travel agencies.

16.12 — How does Wittify ensure dialect accuracy?

  • Trained on region-specific datasets with authentic speech and text samples.
  • Continuous refinement based on real-world interactions.
  • Cultural adaptation for idioms, slang, and etiquette.
  • Ability to mix formal and informal speech styles as needed.

16.13 — Why is Wittify.ai better for Arabic AI assistants than generic platforms?

Generic AI systems often:
  • Misinterpret dialect-specific words.
  • Translate literally without cultural context.
  • Fail to capture local tone and politeness norms.
Wittify.ai:
  • Built for Arabic markets with local datasets.
  • Understands cultural nuances that impact customer trust.
  • Delivers natural, human-like Arabic conversations across text, voice, and hybrid channels.

16.14 — Can I clone a voice for my Arabic AI agent?

Yes. Wittify supports voice cloning to create a unique, brand-specific voice in your chosen dialect.
Requirements:
  • 2–3 hours of high-quality, professionally recorded speech in the target dialect.
  • Clean audio without background noise.
  • Written consent from the voice owner (if not yourself).

16.15 — Why might the voice not sound fully native in a certain dialect?

While Wittify offers multiple voice options per dialect, some dialects have subtle regional pronunciation differences that are harder to replicate perfectly.
Factors include:
  • Choosing a non-native voice model for the target dialect.
  • Regional variations within the same dialect (e.g., urban vs. rural speech).
  • Mixed-language speech patterns in certain markets.
Solution: From your Wittify dashboard, select a native dialect voice for the most authentic sound, or request a custom voice clone for perfect brand alignment.

Document Notes

This FAQ is continuously updated to reflect new features, integrations, and best practices. For the latest version, visit Wittify.ai Docs.
💡 Need help getting started?
Book a free onboarding session with one of our Customer Success Engineers and get personalized guidance on setting up your Wittify AI assistant.
📅 Book here: Schedule a Free Onboarding Session