10
Networks live today
Subscriber support in one queue, priced per account
Run subscriber communication across WhatsApp, SMS, and web channels with no per-ticket fee. Message records stay inside your regional data boundary.
Unlimited
Conversations on every plan
Unlimited
Teammates on every plan
4 regions
EU, UK, US, or Gulf residency
The hidden cost of ticketing models
A support desk that bills by the conversation charges you most in the month an incident lands. The bill rises in the same week the margin thins.
Variable conversation charges
Inbox providers charge per hundred conversations over your quota, which turns a wave of network status questions into an invoice.
Multilingual operational teams
Native support in several countries means hiring regional speakers, or pasting subscriber text into an external translation tool.
Isolated customer records
Chat transcripts stay locked inside the support tool instead of reaching your network engineering logs and billing databases.
Duplicate subscriber threads
One subscriber writes on SMS, WhatsApp, and Messenger at once, and three agents work the same roaming problem.
Features this trade runs on
Live translation for agents
An agent reads and answers in their own language while the subscriber reads the reply in theirs. Nobody leaves the thread to translate it.
Account-based subscriptions
There is no per-seat fee and no per-conversation fee, so teammates and conversations are unlimited on every plan. An outage or a travel peak adds no charge for the extra chats.
Cross-channel subscriber ID
Enquiries from SMS, WhatsApp, and email collapse into one timeline against the subscriber's mobile number.
Where subscriber traffic lands
Connect your telecom service lines across WhatsApp Business, SMS shortcodes, Messenger, and Microsoft Teams. The records stay reachable from your billing and engineering systems through the API.
Channel list and statusWhatsApp
Carries top-up questions, roaming complaints, and SIM activation requests from retail subscribers.
SMS
Shortcode traffic, one-time codes, and the channel a prepaid subscriber falls back to.
Messenger
Public-facing complaints and pre-sales questions arriving from your market pages.
Microsoft Teams
Internal escalation between market support desks, network operations, and billing.
Email
Formal disputes, regulator correspondence, and monthly billing threads.
Regulatory telecom compliance
European telecommunications operators require strict data isolation and audit tracking. Subscriber conversations are stored in EU data centres with AES-256 encryption. Append-only access logs record each record export for a regulatory review.
Security detailA support desk across several markets
Lebara Mobile Group moved off per-ticket billing. Here is how the shared inbox carries their subscriber traffic.
Read the customer workflowsLebara Mobile Group
Support conversations from several European markets arrive in one shared inbox. The assignee and the internal notes stay with a thread as it moves between departments.
What this desk asks first
Ask us directlyHow does account-based pricing handle high subscriber volumes during outages?
We charge for connected accounts rather than conversation counts. If an outage brings tens of thousands of chats in one afternoon, none of them carries a per-conversation fee. Indexed storage is metered against the plan allowance.
Can we connect our existing billing systems through the API?
The TypeScript and Go SDKs let your developers pull customer metadata from your billing database into the agent interface beside the open chat.
Where are our European customer conversations stored?
Message text, search indexes, and attachment files sit in European data centres under European data protection standards. Enterprise deployments pin residency to the EU, UK, US, or Gulf.
Price your subscriber channels
Tell us how many accounts you run across your markets and we will size the deployment on a call.