OneReach.ai Product Capabilities
Sequence any open AI technologies and operate over any channel to support conversational experiences with best practices built-in.

Capabilities By Domain
Differentiated capability not commonly available in the market
Native Voice Stack Capabilities
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
GENERAL VOICE CAPABILITIES | SKILL LEVEL | CODING REQUIREMENTS | ||
Automated Speech Recognition (ASR) | Speech recognition enabled with Natural Language Understanding (NLU) to support natural conversations with users. |
|
![]() |
![]() |
Interspeech Timeouts | Inter-speech timeouts are the pauses between words or phrases in speech. The length of these pauses allow your chosen speech to text (STT) engines or your voice engine to determine when a customer is done speaking (or when they complete a thought) and to process results. |
|
![]() |
![]() |
Contextual Hinting for Speech Recognition | - Tokenization: allows for fine tuning of STT by setting pre-built tokens or creating custom tokens - Boosters: speed up STT with common terminology for your organization. - Live streaming (instead of batch streaming): most STT stream inputs in batches, but we support live streaming so that we can identify intents and entities, and change direction on the fly. |
|
![]() |
![]() |
Text-to-speech (TTS) | Create natural, high-quality custom voice prompts to use throughout interactions. Choose from 150+ languages, and dozens of voice options. |
|
![]() |
![]() |
TTS Cache Management | Complex caching and lazy loading for TTS models that have high latency. |
|
![]() |
![]() |
No code access to Speech Synthesis Markup Language (SSML) | Control the speed, pitch, inflection, pronunciation, and add pauses to voice prompts. Test prompts as you write them in the builder. |
|
![]() |
![]() |
⭐ Accents and Dialects | Advanced acoustic models and language models to account for voice variation across nationalities, regions, and dialects. |
|
![]() |
![]() |
Handle Background Noise | Our acoustic models are also trained to perform in a variety of scenarios—including in severely noisy environments. |
|
![]() |
![]() |
Barge In | Control for voice or DTMF is an user has to listen to a prompt before there is interaction. |
|
![]() |
![]() |
Ditto - Real time and post call analysis | Support for monitoring events live and taking action in real time during calls |
|
![]() |
![]() |
SECURITY | ||||
Voice Biometrics | Use a person’s voice as a uniquely identifying biological characteristic for authentication. |
|
![]() |
![]() |
Call Authentication | Detect fraudulent calls and identify phone numbers (mobile, landline, etc.) |
|
![]() |
![]() |
Inbound Calling | Create self-serve IVR portals. |
|
![]() |
![]() |
⭐ Visual IVR | Visuals to supplement IVR experiences. This can be done over web chat, mobile apps, or SMS. |
|
![]() |
![]() |
AI Powered IVR | Use customer data, contextual history, and advanced technologies together to create exceptional experiences. |
|
![]() |
![]() |
Telephony: Routing and Networking | ||||
Outbound Calling | Single calls, bulk outreach, and scheduled campaigns with IVR calls. |
|
![]() |
![]() |
⭐ Public/ Private Routing | We can transfer internally or externally using the PSTN or SIP (including SIP Refer) since we have a full telephony stack. We also have our own SBCS. |
|
![]() |
![]() |
Integrations with Providers | Natively integrate with our customer's existing telephony stack using private networking, high quality codecs, and cheaper rates. Traffic can be passed via SIP refer, SIP transfer, or PSTN transfer. |
|
![]() |
![]() |
⭐ Provider Relationships | We have direct carrier relationships so we can provide PSTN connectivity out of the box. |
|
![]() |
![]() |
Phone number Management | Buy, manage, and oversee phone numbers easily. Choose from International/domestic numbers, Long code/DID, Short code, Toll free number, and have the option for number pooling. |
|
![]() |
![]() |
RECORDING AND MESSAGES | ||||
Call Recording | Record calls or parts of calls. |
|
![]() |
![]() |
Call Transcriptions | Turn voice into text. |
|
![]() |
![]() |
Voicemail | Capture voicemails |
|
![]() |
![]() |
ANALYTICS AND REPORTING | ||||
Call Analytics | Monitor deliverability, errors, performance, call flow, percent of calls per flow, mobile vs landline recognition, CallerID lookup, call traffic, and outcomes. |
|
![]() |
![]() |
HUMAN-IN-THE-LOOP (HiTL) | ||||
Connect with HiTL systems | See full feature breakdown under Human-in-the-loop. |
|
![]() |
![]() |
Multimodality
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
STATE MACHINE | SKILL LEVEL | CODING REQUIREMENTS | ||
State Machine | Allows users to share any session variables and conversational context across channels and time (makes omnichannel, multimodal and contextual awareness feasible). |
|
![]() |
![]() |
Global Variables | Variables like conversation history, customer history, session |
|
![]() |
![]() |
⭐ Deep Native Integrations | Native functionality across all channels, with best practices for each channel built into our low / no code GUI designer. This is a major differentiator when compared to other platforms that don't have native integrations (e.g. rely on a third party 'voice gateway') or have basic integrations that don't allow for channel-specific functionality (utilizing buttons, noting character limits, allowing file/document sending, etc.). |
|
![]() |
![]() |
⭐ Experiences over any channel interacting simultaneously | Create omnichannel experiences by allowing any channels to interact with a customer simultaneously, automatically updating and knowing what is happening (actions taken, data collected, place in conversation) in the other channels. |
|
![]() |
![]() |
Rich Web Chat
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
ARCHITECTURE AND SECURITY | SKILL LEVEL | CODING REQUIREMENTS | ||
Disposable App with TLS Encryption | Lasts for a small amount of time and then disappears. Secure webpage conversation without the same limitations from the providers/carriers (like SMS). |
|
![]() |
![]() |
REPORTING | ||||
RWC Specific Analytics |
Create custom analytics cards with automatically collected information like: Browser info, Fingerprint knowledge, Location, IP address, Bread Crumbs - path they followed, What was achieved within the site, Session times, Response times, etc |
|
![]() |
![]() |
CUSTOMIZE CHAT INTERACTIONS | ||||
⭐ Brandable look and feel of chat | Use prebuilt options to customize how the chat looks on the webpage, font and headings, upload an avatar, and adjust message or typing bubbles. For even further customization needs, use custom javascript/CSS. |
|
![]() |
![]() |
⭐ Interactive Response |
RWC can respond with interactive items: Carousel, Drop downs, Multiple choice, Open text box input, Sliders, Date picker, Images, Wait for messages (hold on while I look up data), Menus (that can be driven by changing variables rather than hardcoded), and Media types. |
|
![]() |
![]() |
INTEGRATIONS | ||||
⭐ Seamless integration with other OneReach.ai Domains | Use human-in-the-loop, NLU, and create experiences that use RWC with any other channel and work simultaneously. See “Multimodality” for more features. |
|
![]() |
![]() |
Payment platforms | Use RWC custom components and templates to create integrations with payment platforms like PayPal, etc. |
|
![]() |
![]() |
Stateful chat experiences | Use Constacts service with RWC browser fingerprints to create chat experiences that behave differently based on who is interacting with them |
|
![]() |
![]() |
Enterprise Tools and Collaboration
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
SLACK | SKILL LEVEL | CODING REQUIREMENTS | ||
Inbound and outbound messaging | Automate and manage conversations in direct messages and channels (public and private), including use of threads. Update and delete messages. |
|
![]() |
![]() |
⭐ Rich Message Formatting | Take advantage of Slack's full interaction capabilities by designing with: Interactive & form components in messages and app surfaces, slash commands, reactions (emojis), snippets, posts, and ephemeral messages. |
|
![]() |
![]() |
Manage channels and members | Add, remove, view channel members. |
|
![]() |
![]() |
Search | Search conversation history, users, and files. |
|
![]() |
![]() |
Manage files | Upload and download files, snippets, and posts. |
|
![]() |
![]() |
HITL UI | Use Slack for Human In the Loop capability so that automation can extend to a Slack user. |
|
![]() |
![]() |
MICROSOFT TEAMS | ||||
Inbound and outbound messaging | Automate and manage conversations in direct messages and channels (public and private), including use of dialogs. Update and delete messages. |
|
![]() |
![]() |
⭐ Rich Message Formatting | Take advantage of Team’s full interaction capabilities by designing with: Interactive & form components in messages and app surfaces, slash commands, reactions (emojis), and files. |
|
![]() |
![]() |
Manage channels and members | Add, remove, view channel members. |
|
![]() |
![]() |
Search | Search conversation history, users, and files. |
|
![]() |
![]() |
Manage files | Upload and download files, snippets, and posts. |
|
![]() |
![]() |
HITL UI | Use Teams for Human In the Loop capability so that automation can extend to a Teams user. |
|
![]() |
![]() |
TEAMS AND SLACK COLLABORATION | ||||
⭐ Synchronize Channels | Create a single chat channel that can exist in Teams and Slack at the same time shared between systems. |
|
![]() |
![]() |
ENTERPRISE TOOLS | ||||
Native integration with SalesForce Marketing Cloud | Allows users to manage two-way messaging conversations from outbound Salesforce campaigns |
|
![]() |
![]() |
Native integration toolkits for dozens of enterprise tools |
Set up integrations with tools like: Trello, ClickTime, Monday, Jira, ServiceNow, Confluence, Formstack, GitLab, Slack, EWPS, Authorize.net, Zoom, MS Azure, Okta, MS Outlook, Basecamp, Salesforce, Bonusly, Teamwork, Stripe, Toggl, Todoist, Wrike, Survey Monkey, Eventbrite, Meetup, Expensify, Harvest, SmartSheet, JotFOrm, Typeform, Yammer, Scoro, ActiveCampaign, BigCommerce, Envoy, Pivotal Tracker, Time Doctor, Airtable, Dropbox, Asana, Zendesk, WordPress, iCalendar, Hubstaff, Instagram, Google Spreadsheet, Alexa, IMAP, WhatsApp, Facebook, Google Actions, Telegram, Twitter, Viber, Calendly, MS Teams, and many more* |
|
![]() |
![]() |
SMS and Messengers
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
SMS CONVERSATION MANAGEMENT | SKILL LEVEL | CODING REQUIREMENTS | ||
Inbound and Outbound Messaging | Send and receive messages, including bulk sending. |
|
![]() |
![]() |
Text & Files types support, Unicode support | Send messages with different file types |
|
![]() |
![]() |
Global commands | Set rules that adjust conversational flow. |
|
![]() |
![]() |
Random messaging | Set message variations that send during certain percentages of interactions. |
|
![]() |
![]() |
Timeout and error handling | Prompts in conversational design for accounting for errors and timeouts. For more see “Conversational Designer and Dialog Management.” |
|
![]() |
![]() |
Interactive Messaging Bus Integration | Deliver messages via Messaging Bus. Rather than inbound or outbound messaging, message bus keeps a backlog of messages queued for the next interaction with someone. Formatted for messaging channels. |
|
![]() |
![]() |
SMS DELIVERABILITY TOOLS | ||||
⭐ Status tracking – delivery receipts | See success rates and traffic history for flows. |
|
![]() |
![]() |
Identifiers management – includes number groups, shortcodes | Use different number types to increase success of delivery and decrease the risk of messages being blocked. |
|
![]() |
![]() |
Opt-in / Opt-out handling | Automatically handle opt in and opt out ongoing as well as date and time for each occurrence. |
|
![]() |
![]() |
OTHER MESSENGERS | ||||
Deep native integrations for messengers such as:
|
Robust support for any messaging platform utilizing the standard services and specific capabilities of each. OneReach acts as the orchestration layer to each platform using that system’s unique capabilities. |
|
![]() |
![]() |
Mobile App
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
SKILL LEVEL | CODING REQUIREMENTS | |||
Device Identification | Identify the kind of device a user is accessing the app with. |
|
![]() |
![]() |
Push Notifications | Send users notifications even when the app is not open. |
|
![]() |
![]() |
Interactive mobile notifications | Buttons within mobile notifications to get direct responses from end users in the notification itself |
|
![]() |
![]() |
Extension of RWC and HiTL | Device identification, push notifications and voice capabilities available to create a consistent experience |
|
![]() |
![]() |
Voice Functionality | With outbound voice, any app is able to place a call to our platform bypassing any vendors. |
|
![]() |
![]() |
Location Detection | Use location services to find where your users are. |
|
![]() |
![]() |
Mobile App Reporting | See global reporting through the mobile app. Pull mobile app and web app date together. |
|
![]() |
![]() |
Devices Supported | Fully compatible with both iPhone and Android. |
|
![]() |
![]() |
Apps Support in UI | Ability to manage mobile and browser extension apps in Communication Studio. |
|
![]() |
![]() |
Add Reporting View to Mobile App via QR Code | Ability to add views to our mobile and browser extension apps: Scan a QR code to add a view to your OneReach.ai app |
|
![]() |
![]() |
Natural Language Understanding (NLU)
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
Encoder Models | SKILL LEVEL | CODING REQUIREMENTS | ||
First Party NLU Product: Low cost Encoder solution based on Tensorflow | Encoder solution based on Tensorflow to enable the use of NLU for analytics at low costs |
|
![]() |
![]() |
Intentless NLU | We are using encoder models to establish a domain of knowledge so that knowledge doesn't need to be centralized (intentless NLU). |
|
![]() |
![]() |
Autoregressive Language Models - ALMs | ||||
⭐ ALMs (like GPT-3) and decoder native integrations | LLM and native decoder integrations have helped us improve support for entity extraction, disambiguating, extraction from documents, synonym phrases, and managing when the user changes the subject. We also use LLMs to do things like compare text and summarize differences and classify text into domains with no training phrases based on a supplied ontology. |
|
||
TRAINING | ||||
⭐Antagonistic Training | Use multiple NLU engines to train each other based on the highest percentage answer. |
|
![]() |
![]() |
Knowledge Model Training | Educating your bot with relevant information. |
|
![]() |
![]() |
Suggested / Unrecognized | Set up your flow to train and update your model easily based on confidence levels gathered from interactions with the user |
|
![]() |
![]() |
Confidence Scores | Your bot reports how certain it’s understanding is. |
|
![]() |
![]() |
Entity Extraction | Gather periphery information based on a user’s input. |
|
![]() |
![]() |
Custom Model Creation | Connect to an existing model that has already been created |
|
![]() |
![]() |
Mapping Entities to Parameters | Ability to capture entities from a end user utterance which then can be used to automate a task |
|
![]() |
![]() |
Importing Knowledge Model | Upload mass amounts of information to educate your bot. |
|
![]() |
![]() |
Knowledge Model Features | A list of relevant keywords that you can assign to entities or responses. |
|
![]() |
![]() |
ENTITIES | ||||
Multi-Language Support | Support for capturing data (entities) within an end user utterance across various languages |
|
![]() |
![]() |
Create Synonym Questions | Mimic natural language by asking the same question in different ways. |
|
![]() |
![]() |
Flow Entities | A post processing response mechanism in which each flow entity is associated with a certain flow that implements logic of processing each response the entity is assigned to |
|
![]() |
![]() |
LINGUISTICS | ||||
Spelling/Grammar Correction | Catch the errors you missed. |
|
![]() |
![]() |
Autogenerate Disambiguating Questions | If your bot is confused, it can generate questions to gain clarity and move forward. |
|
![]() |
![]() |
Generate Text | Generate training examples that extend NLU model | Greatly improve training datasets by generating many examples based on a few manually entered utterances. |
![]() |
![]() |
Human-in-the-Loop (HiTL)
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
CATEGORY | SKILL LEVEL | CODING REQUIREMENTS | ||
HiTL Supervised Learning | A human can monitor a bots learning. |
|
![]() |
![]() |
Prompt Human for Supervised Learning | A human or group can be notified when a confidence score is low on a customer utterance. |
|
![]() |
![]() |
Disambiguation with HiTL | Use a human to clarify something for the bot. |
|
![]() |
![]() |
HiTL Reporting | Receive analytics on when and how humans are brought in to support the bot. |
|
![]() |
![]() |
Creating Human as a Channel | Include a Human in an automated process as a failover resource to perform tasks and answer questions. |
|
![]() |
![]() |
Conversation Pass Between Automation to Human and Back | Move the conversation seamlessly between a human, when necessary, and back to a bot. |
|
![]() |
![]() |
Human Take-Over | Completely pass off from bot to human. |
|
![]() |
![]() |
Conversational Design and Dialog Management
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
CONVERSATIONAL DESIGN | SKILL LEVEL | CODING REQUIREMENTS | ||
Drag and Drop Conditional Routing | OneReach has out of the box conditional routing in dialogue building based on any number of factors including variables, conditions, sentiment, regex, voice actions (hangups, voicemail recognition, barge in, etc), NLU confidence, user characteristics, A/B performance, timeouts, GUI interactions, etc. |
|
![]() |
![]() |
⭐ Content Builder - Wysiwyg designer | Wysiwyg designer for creating content that can go into cards that are attached to views. |
|
![]() |
![]() |
⭐ Synchronizer | Synchronizer is the heart of multibot orchestration and our communication fabric. It is a service for syncing data between data storage and messaging systems in real time (like a channel created in Teams and with a channel created in Slack) so that channels or any other information stream is up to date as others. |
|
![]() |
![]() |
Customer Journey Mapping | Create customer journey maps and organize skills into a future roadmap |
|
||
Decoupled business logic from integration layers | We have decoupled the business logic and integration layers from the NLP engines to ensure you can leverage the same 'brain' regardless of channel. |
|
||
⭐ Event Based Model | Every flow is a microservice and is triggered by the centralized event-based system |
|
![]() |
![]() |
⭐ Complex task relationships | OneReach also supports complex flow relationships by enabling unlimited subflows. We automatically trace the relationship between complex flows with a visual GUI to represent dependencies and discover potential logical improvements. |
|
![]() |
![]() |
Design and build | ||||
Multithreading in a single flow | View Traffic |
|
||
⭐ Native Ticketing Product | Creates and assigns tickets to bots and to people. |
|
||
⭐ Message and Event Bus | Rather than inbound or outbound messaging, message bus keeps a backlog of messages queued for the next interaction with someone. Formatted for omnichannel delivery. |
|
||
Global Calendar for scheduled flows | Calendar that shows all scheduled flow executions in a single place. |
|
||
View Traffic | View conversational traffic with breakdowns of most common paths. |
|
![]() |
![]() |
Cross-account conversational support | Skill sharing across bots, accounts, and environments has made session management even easier for customers. |
|
Architecture and Integration
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
OPEN ARCHETECHURE | SKILL LEVEL | CODING REQUIREMENTS | ||
⭐ Composable architecture | All components of our platform can be composed |
|
![]() |
![]() |
⭐ Build custom integrations | Build your own channel toolkits to fit any channel or system independent of OneReach. We support the following types of integrations: Webooks, HTTP requests, APIs, Sockets, MSRP, SIP, and SSO. |
|
![]() |
![]() |
⭐ Private Dedicated Environments: Our architecture allows OneReach to provide our customer with one or more "Private Dedicated Environments", PDEs, which are unique instances of our platform in specific geographic regions just for the customer, each of which is multi-tenant. | ||||
⭐ Complete control over connection to other systems | Control how your OneReach services connect to other (cloud or on-premise) systems |
|
![]() |
![]() |
Multiple PDEs - Failover, Load balancing, and different staging/dev/test environments | Typically we provide customers with multiple PDEs to serve different purposes. |
|
![]() |
![]() |
⭐ Custom compliance, data, and security requirements | Design data storage and security needs to fit your company. |
|
![]() |
![]() |
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
EMAIL DOMAIN | SKILL LEVEL | CODING REQUIREMENTS | ||
Automate from existing email address | Connect user’s own domain |
|
![]() |
![]() |
Automate from OneReach.ai generated and hosted email address | Domain lives in OneReach account |
|
![]() |
![]() |
DELIVERY AND EVENTS | ||||
Send scheduled emails (single or bulk) | Schedule emails to be sent as specific time or when an event happens |
|
![]() |
![]() |
Track delivery status | Track and manage sent, opened, bounced, or failed delivery email statuses. Create events around them |
|
![]() |
![]() |
Track clicks within email content | Track and manage link clicks |
|
![]() |
![]() |
DELIVERY AND EVENTS | ||||
Autofill subject, recipient, and email content | Use merge fields (variables) to autofill recipients, subject, and email body content automatically. |
|
![]() |
![]() |
HTML, WYSIWYG, Plain Text | Edit email body using code and our built-in email builder. |
|
![]() |
![]() |
Prebuilt email templates | Get started quickly and iterate from prebuilt email templates |
|
![]() |
![]() |
Reporting and Analytics
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
CUSTOMIZABLE DASHBOARDS | SKILL LEVEL | CODING REQUIREMENTS | ||
Custom cards & card templates | Cards contain graphs and data from flows, separated out by what measurements matter to your use case. Customizable card settings, i.e. chart type, layout, axes, etc. Generate cards from scratch. |
|
![]() |
![]() |
Use pre collected metrics for card data | Since OneReach is based on an event model, we log vast amounts of data from every conversation. This includes: Time, Location, Context, Transcript history, Feedback, User information, Total Users, New Users, User Engagement, Session Length (including response times per each piece of the engagement), Completed Conversations, Uncompleted Conversations, Fallback Responses, Missed Intent Matches, Repeat Engagement, Top Messages, Top paths taken by users, Fulfilled Conversations, Escalated Conversations and Unfulfilled Conversations. |
|
![]() |
![]() |
Custom views and dashboards | Select which cards to contain in a “View” (dashboard) and create and duplicate views. |
|
![]() |
![]() |
⭐Data and Identity Manager (CIAM and CRM) | Our Data and Identity Management capabilities work in concert with CRM overlay capabilities to supplement enterprise data systems including the ability to store structured and unstructured metadata that supplements internal CRM and identity management data. |
|
![]() |
![]() |
⭐Omnidata | Abstraction layer for all data, resulting in better data security management by abstracting data sources from the conversational experience. |
|
![]() |
![]() |
⭐Graph DB Timeline Capture | Go back and see what relationships were in the past in graph DBs in our platform. |
|
![]() |
![]() |
⭐Graph DB ML prediction | Prediction of future relationship-generation based on previous graph DB content. |
|
![]() |
![]() |
⭐Synchronizer | Synchronizer is the heart of multibot orchestration and our communication fabric. It is a service for syncing data between data storage and messaging systems in real time (like a channel created in Teams and with a channel created in Slack) so that channels or any other information stream is up to date as others. |
|
![]() |
![]() |
Share views | Share via public links, shared UI and Live Agent view. |
|
![]() |
![]() |
Tag cards | Create tags for cards to filter for different views. |
|
![]() |
![]() |
Accounts and Admin
CAPABILITY | CAPABILITY DESCRIPTION | WHAT YOU CAN DO | FEASIBILITY | |
ACCOUNTS AND USERS | SKILL LEVEL | CODING REQUIREMENTS | ||
Roles and Permissions | Platform roles control which part of the platform various users have access to. This includes the ability to create custom roles/user types, and to break up environments into different accounts. Accounts are segregated groups of CS users and services that represent a billable set of solutions. |
|
![]() |
![]() |
⭐ Skill Based Permissions | Permissions can be assigned based on roles and individual users, and permissions can be assigned on a per-skill level. |
|
![]() |
![]() |
Cross-account conversational support | Skill sharing across bots, accounts, and environments has made session management even easier for customers. |
|
![]() |
![]() |
SINGLE SIGN-ON | ||||
Single Sign-On | Since OneReach provides a development platform many authentication methods are supported. |
|
![]() |
![]() |
Languages Supported
Common Languages (in production) | ||||
English: US, Great Britain, Canada, India, Australia | Chinese: Cantonese, Simplified, Traditional | Arabic: Peninsular Group, Mesopotamian Group, Levantine Group, Egypto-Sudanic Group, Maghrebi Group | Spanish: Latin America, Castillian Spain, Catalan Spain | Turkish |
Czech | Slovakian | Russian | Ukrainian | Latvian |
Romanian | Italian | French: France, Canada | German | |
Other Languages Supported | ||||
Afrikaans | Croatian | Ido | Malay | Romanian |
Albanian | Czech | Indonesian | Malayalam | Romansh |
Amharic | Danish | Irish | Maltese | Russian |
Aragonese | Dhivehi (Divehi/Maldivian) | Italian | Manipuri | Sanskrit |
Armenian | Dutch | Japanese | Manx | Sardinian |
Assamese | Esperanto | Javanese | Marathi | Scottish Gaelic |
Azerbaijani | Estonian | Kannada | Minangkabau | Serbian |
Bashkir | Filipino (Tagalog) | Kazakh | Mangolian | Serbo-Croatian |
Basque | Finnish | Khmer (Central Khmer) | Nepali | Sindhi |
Bengali (Bangla) | Galician | Kirghiz (Kyrgyz) | Norwegian: Bokmal, Nynorsk | Sinhala (Sinhalese) |
Bihari Languages | Georgian | Korean | Occitan | Slovak |
Bosnian | German | Kurdish (Kurmanji) | Odia (Oriya) | Slovenian |
Breton | Greek | Latin | Ossetian (Ossetic) | Somail |
Bulgarian | Gujarati | Latvian | Pashto | Sotho |
Burmese | Haitian Creole | Limburgan (Limburger/Limburgish) | Persian | Sundanese |
Cebuano | Hebrew | Lithuanian | Polish | Swahili |
Chechen | Hindi | Luxembourgish (Letzeburgesch) | Portugese: Brazil, Portugal | Swedish |
Chuvash | Hungarian | Macedonian | Punjabi | Tajik |
Corsican | Icelandic | Malagasy | Quechua | Tamil |
Tatar | Telugu | Thai | Tibetan | Turkish |
Turkmen | Urdu | Uyghur | Uzbek | Vietnamese |
Walloon | Welsh | West Frisian |