Outbound calling platform
Import the list, and OneBloc Calling hands each lead to exactly one agent, holds callbacks until the day they are due, and suppresses a do-not-call everywhere at once.
Runs in the browser · English and 中文 · your data stays in your organisation
What goes wrong without it
The classic shared-spreadsheet failure. It makes the company look disorganised to the one prospect who was actually willing to talk.
A callback that only exists in someone's handwriting is a callback that will not happen — and it was your warmest lead.
Activity is invisible until someone compiles a report at month end, by which point the month is already lost.
Suppressed on one list, still sitting on three others. The complaint that follows costs more than the list was worth.
012-345 6789, +60 12 345 6789, and the 6.01E+10 that Excel makes of a phone column the moment you open the file.
Send a thousand identical messages too quickly and the number is banned — usually the number the whole team was using.
How it works
The whole design goal is that an agent never decides who to call next — the queue does, so the decision is consistent and nobody double-dials.
Drop in a .csv or .xlsx. Columns match by name and every number is normalised on the way in.
One lead is held for one agent. While the hold lasts, nobody else can be handed that person.
The dialer opens on the handset. WhatsApp opens with the approved script already written.
Required, not optional — that is the only reason the numbers on the dashboard can be trusted.
Save & next hands over the following lead immediately, keeping whatever filter the agent set.
For the person running the floor
What you get
Reservation is a single atomic write, so two agents pressing Start at the same instant cannot be given the same lead. The hold expires on its own if someone walks away.
Set a date and the lead leaves the queue until that morning, then returns to the agent who promised it. Nothing to remember.
One agent marking a number suppresses it across every campaign, every queue and every blast in your organisation — not just the list in front of them.
Sending days, hours, per-batch rate and a daily cap, with two or three wordings rotated so a thousand people do not receive a byte-identical message.
Calls per day, outcome mix and a team leaderboard that updates as the calls are logged — not a spreadsheet someone assembles on the 1st.
Leads, calls, scripts and the WhatsApp key belong to one tenant. The separation is enforced in the data layer, not by remembering to add a filter.
When someone asks not to be contacted again, any agent can record it in one press. That number is then suppressed across every campaign, every queue and every blast in the organisation — including lists imported later. Respecting it is the cheapest complaint you will ever avoid.
Create a campaign, import the leads, add your agents. The first call can go out the same afternoon.