How Mei's telecom AI services work
The subscriber experience, the platform behind it, and what we configure with your team. Explore existing product examples and the path to a service under your own brand.
Mei, Voxie and the AI platform
Mei is the company behind Voxie. Our shared AI platform combines agent-building tools with the backend that runs our generative AI products: conversations, model connections and authorized actions. Voxie is one way subscribers experience that platform. Your operator service can use it under your own brand.
Explore the agent builder and APIsTwo subscriber services
An assistant subscribers call or text
A familiar number or short code for questions, learning, writing and everyday advice. The AI responds over SMS or voice, with no separate app required for those channels.
- Choose the assistant’s personality and knowledge
- Use conversation context for relevant replies
- Offer access through a number, short code or digital channel
Voxie is a public product example; eYano is an operator-branded SMS deployment.
Explore the Voxie subscriber experienceAn assistant that handles incoming calls
A subscriber chooses when the AI should answer on their behalf. The assistant captures who is calling and why, takes a message, or follows an agreed transfer or action rule.
- Answer selected, missed or busy calls
- Capture the caller’s purpose and requested next step
- Deliver a summary through the selected channel
An operator pilot combines existing voice capabilities with subscriber settings and network routing.
Follow an example callA personal-assistant call, step by step
Subscriber enables the service
They choose when the assistant answers and how they receive summaries.
The network routes the call
Agreed forwarding or routing rules identify which subscriber the call is for.
The AI handles the conversation
It asks the caller’s name and purpose, then takes a message or follows the subscriber’s permitted rules.
The subscriber receives the result
A concise recap, with recording or transcript access and follow-up configured for the service.
Illustrative delivery call
“I'm delivering a package. May I leave it at reception?”
What the subscriber receives
A short recap of who called, what they needed and any agreed next step. The assistant follows the subscriber's instructions rather than making up permission to leave the package.
Recording, transcript access and follow-up depend on the service settings.
Capabilities and configuration
We combine the platform's existing components with the routing, subscriber experience and integrations required for your service.
| Capability | Platform components | Configured together |
|---|---|---|
| Answering calls | AI handling for inbound calls and transfer tools. | Forwarding rules, subscriber identity and when to hand off. |
| Real-time voice | Speech input and spoken responses in a conversation. | Target language, accents, voice, latency and fallbacks. |
| Screening & caller identity | Ask who is calling, why, and what needs attention. | Verified identity or spam reputation requires an agreed data source. |
| Call summaries | Conversation records and summary processing. | Summary format and delivery through SMS, email or an app. |
| Recordings & transcripts | Recording and transcription components. | Subscriber choices, access, retention and the service’s recording rules. |
| Calendar & other actions | Booking links and connections to permitted workflows. | The calendar or business system, account access and user authorization. |
| Network & digital channels | Voice, SMS, web chat and service APIs. | The operator’s interfaces, provisioning, billing and subscriber settings. |
Answering calls
AI handling for inbound calls and transfer tools.
Configured together: Forwarding rules, subscriber identity and when to hand off.
Real-time voice
Speech input and spoken responses in a conversation.
Configured together: Target language, accents, voice, latency and fallbacks.
Screening & caller identity
Ask who is calling, why, and what needs attention.
Configured together: Verified identity or spam reputation requires an agreed data source.
Call summaries
Conversation records and summary processing.
Configured together: Summary format and delivery through SMS, email or an app.
Recordings & transcripts
Recording and transcription components.
Configured together: Subscriber choices, access, retention and the service’s recording rules.
Calendar & other actions
Booking links and connections to permitted workflows.
Configured together: The calendar or business system, account access and user authorization.
Network & digital channels
Voice, SMS, web chat and service APIs.
Configured together: The operator’s interfaces, provisioning, billing and subscriber settings.
Explore the offering through existing examples
Voxie
Subscriber experience
See how people reach an AI by phone number. The public directory includes Voxie and Rhodey, with different personalities and supported channels.
Public numbers have regional access and usage limits. We can arrange a walkthrough for teams outside the supported regions.
Explore Voxie and available numberseYano on MTN Congo
Operator deployment
An operator-branded AI assistant delivered over SMS in the Republic of the Congo, including access from basic phones without an app or data plan.
An SMS integration reference; it does not imply personal call answering is deployed on MTN.
Read the deployment storyElla
Voice conversations and actions
A business intake agent that handles calls, collects job details and connects to a ServiceTitan booking workflow. The case study explains the integration and includes a public demo.
A related business example, not a personal subscriber assistant. The public demo collects intake but does not dispatch a job.
Explore the workflow and demoHow it fits your network
- Mei’s AI platform
- Agent configuration, conversation handling, model connections and tools for authorized actions. The same backend supports our generative AI products.
- Your subscriber service
- Your brand, activation experience, subscriber settings, retail prices and customer channels.
- The joint integration
- Call and message routing, subscriber identity, provisioning, notifications, billing and target-language testing.
Subscriber revenue options
Introduce the service with an included allowance, then offer paid top-ups, a monthly AI add-on or a premium plan bundle. Optional sponsored recommendations may fit some markets. You set subscriber retail prices and usage allowances; operator fees and partnership terms are discussed privately.
As an illustration, paying subscribers multiplied by the retail subscription price gives gross subscription revenue, before costs and any revenue-share arrangement.
Define an operator pilot
Choose a call/text assistant, a personal call assistant, or a limited group testing both. Agree the target language, network routing, subscriber settings and first permitted action. Then evaluate call quality, useful responses, completed tasks and subscriber feedback before expanding.
Discuss your service with Es at Mei