How we use cookies
Telonic

Good service, by design.

Agents built around how your industry works answer every call and message, keep one record of each customer, and finish the work in your own systems, within limits you control.

Book a demo

A sample screen recording: a customer's cancelled flight arrives on WhatsApp, the agent checks the fare rules, rebooks her and updates her record.

Sample data
  • 5

    channels: voice, WhatsApp, SMS, email and web

  • 4

    forms of Arabic, plus English and many other languages

  • 24/7

    including public holidays

  • 1

    continuous record for each customer

  • 4

    ways to host: UAE, Saudi Arabia, on‑premise or your own cloud

Every conversation has a method.

A customer message mixing English and Arabic, tagged with its languages and the intent to rebook.

Step 01

Hear what they mean.

Customers mix Arabic and English and rarely open with the real request. The agent follows both and works out what they need.

A booking record checked against the fare rules, with rebooking selected from three options.

Step 02

Check your rules.

Before it answers, the agent looks up the booking, claim or unit in your systems and checks what your policy allows. It cannot offer anything else.

A customer record where the rebooking is confirmed and two new timeline entries are added.

Step 03

Finish the work.

The change is made, the record is updated and your team sees the outcome. Nothing waits for someone to remember.

Your systems at the base. The agent on top.

Four stacked layers: your channels and systems at the base, then one customer record, your industry model, and the agent on top.

  1. 01

    Your channels and systems

    Your phone lines, WhatsApp number and core systems. Nothing is replaced.

    • Voice, WhatsApp, SMS, email and web
    • Your CRM, booking and claims systems
  2. 02

    One customer record

    Every call, message and email joins one history per customer.

    • Agent and staff conversations together
    • Every department reads the same history
  3. 03

    Your industry model

    The units, claims and bookings you run on, with their rules.

    • Workflows from first enquiry to resolution
    • Policies built in, not written into a prompt
  4. 04

    The agent

    Holds the conversation within limits your team sets and changes.

    • Hands over with the full conversation
    • Every decision recorded with its reasoning

Ready at any hour, and ready for the rush.

Conversations by hour · Dubai time

Messaging now from

  • Riyadh01:14
  • Karachi03:14
  • Mumbai03:44
  • Manila06:14
Illustrative: a travel operator's conversations across one day.

Every hour, every day.

Nights, weekends, Eid and public holidays run to the same standard as a Tuesday morning.

Replies without a pause.

The agent starts forming its answer while the caller is still finishing, so nobody is left waiting in silence.

Capacity that follows demand.

Many conversations run at once. A disruption or a launch day does not create a queue.

A person when it matters.

When the agent reaches its limit, it hands over to your team with everything said so far.

Hosted where your organisation needs it

In the UAE, in Saudi Arabia, in your own cloud or on your own premises. All processing stays where you choose.

Your data, your terms.

Choose the region. Deploy in the UAE or Saudi Arabia, and all processing, including speech and language models, stays in that region.

Or keep it in-house. Run it in your own cloud account, or on your own premises, set up for your requirements.

Decide what is kept. Nothing is stored without your permission, and you set how long anything is kept. Personal information is redacted before any data leaves your deployment, and calls are recorded only once consent is given.

Read the detail for your technical team

UAE region

Hosted and processed in the UAE.

Saudi Arabia region

Hosted and processed in Saudi Arabia.

Your own cloud

Runs inside your own cloud account.

On your premises

Set up in your own data centre, to your requirements.

Your data. Your decision.

Nothing is stored without your permission. You decide what is kept, and for how long.

Personal data redacted

Personal information is removed before any data leaves your deployment.

How it works

How a deployment runs, in three steps

01 Design

We build it around your operation

We map your workflows, connect your systems and build your policies into the agent. We start from our model of your industry, so the work is fitting it to how you operate, not teaching it what a booking or a claim is. Your team reviews every rule before a single customer hears it.

02 Deploy

Your team sets the limits

Choose what the agent handles, what it never touches and when a conversation goes to a person. Set how the handover works and what your team receives with it. Start with one channel or one queue, and widen it when you're ready.

03 Measure

Every conversation, reviewed

Every conversation is scored against your standards, with the reason it ended the way it did. Patterns across thousands of conversations show where a policy confuses customers or a process breaks. You see what to fix, and we fix it with you.

Control

You set the boundaries. The agent keeps to them.

You're right to ask what an agent might say on your behalf. The answer is only what you allow, and every conversation shows it.

Decide what it handles

You choose the topics the agent covers and the ones it never discusses. Anything outside them goes to a person on your team, with the conversation so far.

Looked up, never invented

Prices, policies, entitlements and dates come from your own systems. If the answer isn't there, the agent says so and offers a person.

Handover with the whole story

When a conversation needs a person, they receive a written brief of what was said and done, so the customer never starts again.

Every decision on the record

Open any conversation and see what the agent looked up, what it decided and why, for as long as you keep it.

Some decisions stay with you

Claims outcomes, goodwill outside policy and anything involving safety are never available to the agent. Those actions do not exist for it.

Current when your rules change

When a policy, price or document changes in your systems, the agent works from the new version. Nobody retrains anything.

1 — 6

Questions

What teams ask us first

Do we have to replace our phone system or contact centre platform?

No. The agent connects to the phone lines, WhatsApp number and systems you already run, including the contact centre platform you use today. Calls arrive on your existing lines through a standard SIP connection, and control passes back to your team whenever it's needed. Your customers keep calling the same numbers.

What happens when the agent can't help?

It hands the conversation to a person on your team, with a written brief of what was said, what was looked up and what was promised. You decide when that happens: a customer who is upset, a legal question, anything outside the topics you've approved. The customer doesn't start again, and your team doesn't start cold.

Can it make a decision we haven't approved?

No. The agent can only take the actions you make available to it, within the limits you set, such as refund ceilings, fare rules and approval thresholds. Those limits are built into what it is able to do, not written into its instructions, so it has no way to go beyond them. Some decisions, such as claims outcomes, are never available to it at all.

Which languages does it handle?

Arabic in its Gulf, Egyptian, Levantine and Modern Standard forms, English, and many other languages your customers speak, including Urdu, Russian, Chinese and Spanish. It works out the language from the first few words, and follows customers who switch languages mid-sentence.

Where is our data held and processed?

In the region you choose: the UAE or Saudi Arabia, your own cloud, or your own premises. All processing, including speech and language models, stays there. Nothing is stored without your permission, you set how long anything is kept, and personal information is redacted before any data leaves your deployment. Calls are recorded only once the caller has given consent.

How long does it take to go live?

Most deployments start with one channel in one department: a single queue, a single line or a single inbox. The timing depends mostly on the systems it connects to and how your policies are documented today. You'll have a plan with dates before you commit, and we widen to further channels and departments once the first is working the way you want.

How is it priced?

A monthly usage package for each channel group, based on volume: calls for voice, conversations for messaging and sessions for web. Everything is included at every size, so you pay for volume, not features.

Get started

Start with one channel.Live within weeks.

One monthly figure per channel. Everything included.

  1. Design

    We map your workflows, systems and rules, and design the agents around how your business already runs.

  2. Deploy

    Live on your first channel within weeks, connected to the systems your teams already use.

  3. Measure

    Performance tracked against measures agreed with you before launch. Then extend, channel by channel.