OmniServe by Runox
Architecture

The AI and your team share one seat

Most tools bolt an AI onto the side of a phone system, which is why the handover is always the worst part of the call. Here they are the same kind of thing — same queue, same connection, same recording, same report.

Routing

Decided per link, not per company

A link that says "my team" overrides the company default, because somebody set it deliberately on that link. Your plan has the last word, and only ever downwards — nothing silently upgrades itself.

Queue

One queue for every channel

A caller on the line asking for a person lands in the same place as a chat escalation, an email and a social mention. Nobody watches an empty screen while a phone rings somewhere else.

Knowledge

Answers from your files and your database

PDFs, Word, Excel and CSV — or a live connection to your own system, so the AI quotes a real balance, a real stock level, a real free slot. Different links can answer from different parts of it.

Memory

It remembers the last time you called

A returning customer isn't asked their story again. Across calls and chats, on the phone and on the website — the same thread, so the second conversation starts where the first one ended.

Mid-call

The conversation has parts

Check who you're speaking to, and only then discuss the account. Confirm, then offer times, then take a deposit. The AI's instructions change as the call moves, so it can't offer to take money from someone it hasn't identified.

Honesty

It says when it doesn't know

And it says it's an AI. Callers work it out anyway, and the ones who feel misled don't come back. Disclosure is on by default and isn't a setting we let you hide.

Outbound

Four ways to make a call

AI campaigns, preview dialling, power dialling with your own people, or AI-qualifies-then-transfers — where the AI makes three hundred dials and your person only ever picks up a live one.

Lists

Call from anything you already have

Your contacts, a live query against your own database, or a spreadsheet somebody emailed over. Every column comes with it, so the AI says "invoice 4471 for £340, due on the 12th" instead of "regarding your account".

The call arrives already introduced

When a call is put through to your existing phone system, it does not arrive as an anonymous ring. The context travels with it in the SIP invitation, so the person answering knows who is calling and what brought them before they pick up.

Any PBX, CRM or softphone that reads custom SIP headers can pop that on screen — which is most of them, and it is how a handover stops feeling like being passed between two companies.

What travels with the callSIP headers on the invitation
X-Omniserve-Call-IdThe one identifier joining this ring to the recording, the transcript, the report and the CDR row. hc__acme__9f2c…
X-Caller-NameWho they said they were before the call started. Jane Smith
X-Caller-PhoneTheir number, where they gave one or the network supplied it. +44 7700 900 001
X-Attribution-SourceWhat sent them. Your receptionist can answer differently to an emergency ad than to a price-comparison click. google / cpc
X-Attribution-CampaignWhich campaign paid for this ring, on the screen while it is still ringing. emergency-dentist-leeds
X-Agent-NameOn calls your team makes, so the far end and your own logs know which agent placed it. Tunde A.

On SIP legs to your own phone system or care centre. Agents working in the browser see the same context in the dashboard, without needing a PBX to interpret it.