Contact centre & dialer · engineered in the UK

Every conversation, on one connected floor.

Outbound campaigns, inbound queues and every other channel handled by the same agents on the same screen. Four dialing modes, skills-based routing, recording, and a supervisor console that shows the floor as it is now — not as it was yesterday.

4 dialing modes
Blended inbound & outbound
Self-hosted or cloud

Built for floors where idle agent minutes are the cost and connect rate is the product

TelesalesCollectionsRenewalsCustomer supportAppointment settingOutsourced BPO
What you get

A contact centre, not a phone system with reports bolted on.

Idle agent minutes are the cost. Connect rate is the product. The supervisor needs to see both while there is still time to do something about them — which is the whole design brief.

☎️

Four dialing modes

Manual, preview, progressive and predictive on the same list. Start a new campaign in preview while agents learn the script, then move it to predictive once the connect rate is known — without rebuilding anything.

📡

Pacing that respects the limit

The predictive engine adjusts its ratio against live connect rate, talk time and free agents, throttling itself to stay under the maximum abandonment rate you set. Occupancy is the goal, not the excuse.

🔄

Inbound ACD and IVR

Menus, business hours, skills-based routing, queue priority and callback-in-queue. Callers reach an agent who can actually help them, and the ones who cannot wait get called back instead of hanging up.

💻

One blended agent desktop

The same browser screen takes an outbound campaign call, an inbound queue call, an SMS or an email — with the customer record, the script and the disposition list already on it. No alt-tabbing between three systems mid-sentence.

🕵️

Monitor, whisper, barge

Supervisors listen silently, coach the agent without the customer hearing, or join the call outright. All three are one click from the live floor view, on site or on a home agent.

🎤

Recording built for review

Every call recorded and attached to the lead, the campaign and the agent, searchable by disposition and outcome. Pause-and-resume during card capture keeps payment details out of the audio entirely.

0Dialing modes
0Channels on one desktop
0Calls recorded
0Console refresh
Three jobs, one platform

The floor has three problems. So does the software.

Working a list without burning it. Answering a queue without losing callers. Seeing both clearly enough to change them today rather than next month.

📤
Outbound

Campaigns & dialing

The list works the agents, not the other way round — hoppers, pacing, recycling rules and suppression applied before the number is dialed.

  • Lead lists with custom fields & priority
  • Answering-machine detection
  • DNC, attempt caps & calling windows
Learn more
📥
Inbound

Queues & routing

Calls routed on skill, language and priority rather than on whoever picked up last, with callbacks that hold the caller's place in the queue.

  • IVR, business hours & holiday routing
  • Callback-in-queue & voicemail
  • Outbound agents pulled in on spikes
Learn more
📊
Supervision

Console & reporting

Every agent's state and time-in-state, every campaign's pacing and every queue's depth on one screen — then the history to back a coaching conversation.

  • Live floor view & wallboards
  • Talk, wrap, pause & idle per agent
  • Scheduled reports, CSV & REST API
Learn more
How it works

One team live, then the whole floor.

Dialers are judged on the first week with real numbers and real agents. We put a single team on it deliberately, before anybody commits a hundred seats.

Connect the trunks

SIP trunks registered, numbers and caller ID mapped, codecs and routing rules agreed with your carrier. Test calls both directions before anything else is configured.

Build campaigns and scripts

Lead lists imported with your custom fields, dispositions and scripts set up, suppression lists loaded, and inbound queues mapped to skills.

Pilot one team

A live week with one team, starting in preview mode and moving to predictive once the connect rate is measured rather than guessed. Pacing and retry rules tuned against real results.

Scale the floor

Remaining teams onboarded from the proven template, capacity sized to peak channels, and supervisors trained on the console they will actually use every day.

Specification

The details engineers ask about.

No asterisks. If something depends on your carrier, your hardware or your regulator, it says so.

Telephony
Standard SIP trunking with multiple carriers in parallel; per-campaign carrier and least-cost routing. Keep your existing numbers.
Audio
G.711 and G.729 supported; WebRTC or softphone at the agent. Bandwidth and concurrent-channel capacity depend on the codec chosen.
Dialing modes
Manual, preview, progressive and predictive, switchable per campaign without rebuilding the list.
Pacing
Ratio adjusted continuously against connect rate, talk time and available agents, capped by a maximum abandonment rate you configure.
Answering-machine detection
Per-campaign detection with configurable handling — drop, leave a recorded message, or route to an agent.
Inbound
IVR menus, business-hours and holiday routing, skills-based distribution, queue priority, callback-in-queue, voicemail.
Agent desktop
Browser-based; voice, SMS, email and chat in one interface with screen-pop, scripting, dispositions and scheduled callbacks.
Supervision
Live floor view with agent time-in-state, silent monitor, whisper coaching, barge-in, and wallboard display.
Recording
Full-call recording attached to lead, campaign and agent; pause-and-resume for card capture; retention period and automatic deletion configurable per campaign; role-based, logged access.
Calling controls
DNC and suppression lists applied pre-dial, per-number attempt caps, time-zone-aware calling windows and configurable abandonment limits. These are controls you set to match your regulator — they are not a compliance guarantee.
Scale
Single node for smaller floors; clusters with dialing, media and database roles separated for larger ones. Concurrent-channel capacity is sized against your peak during scoping.
Reporting
Real-time and historical reports on agent time, campaign outcome, queue service level and call detail records; scheduled delivery, CSV export and REST API.
Deployment
Self-hosted on your own hardware or hosted in the region you nominate. Your recordings and your call data stay where you put them.
Questions

Answers to what usually comes next.

Commercial questions are answered on the pricing page.

Do we keep our existing numbers and carrier?
Yes. Sentra Connect registers against standard SIP trunks, so you keep your numbers and your carrier contract. Most teams run two carriers side by side and route by cost or by destination, which is configured per campaign rather than hard-wired.
How does predictive dialing avoid abandoning calls?
The pacing engine watches connect rate, average talk time and how many agents are actually free, then adjusts the ratio continuously. You set a maximum abandonment rate and the dialer throttles itself to stay under it rather than chasing occupancy. The measured rate is on the supervisor console, not buried in a monthly report.
Can agents work from home?
The agent desktop is a browser page, and audio arrives over WebRTC or a softphone, so a home agent needs a headset and a stable connection rather than a desk phone on your LAN. Supervisors monitor, whisper and barge into remote agents exactly as they would on site.
How many concurrent calls can one server handle?
It depends on codec, recording settings and whether the media passes through the server. A single well-specified node comfortably runs a few hundred concurrent channels; beyond that the platform clusters, with dialing, media and database roles split across nodes. We size the cluster against your peak channel count during scoping rather than quoting a number that ignores your codec.
Where are recordings stored, and for how long?
Wherever you decide — on your own storage if you self-host, or in the region you nominate in the cloud. Retention is a policy you set per campaign, with automatic deletion when the period expires, and access to recordings is role-based and logged. Pause-and-resume during card capture is available so payment details never reach the recording.
Does it integrate with our CRM?
Leads, dispositions, recordings and call detail records are available over REST API and CSV export, and screen-pop can pass the caller's record straight into your CRM. Where SentraOne is already in use, contacts, tickets and campaign outcomes report alongside the rest of the operation instead of living in a separate silo.
Let's talk

Put one team on it for a week.

Bring a real list and a real queue. We will connect your trunks, configure one campaign, and show you the connect rate, the abandonment rate and the agent time that week produced.