Logistics
A hundred confirmations before the vans leave.
In courier work the most expensive call is the one that was never made: the van arrives, nobody is home, the parcel goes back and gets paid for twice. The confirmation beforehand is a short, repetitive call and a perfect fit for automation, provided it respects the calling rules.
The assistant dials recipients before the round, confirms somebody will be at the address in the announced window, rebooks the delivery when they will not, checks unclear addresses, and writes the outcome against every contact plus the fixed reason for every number not dialled.
Where the calls go out
Every call below goes out in bulk, in a short window, and its value lies in what changes on the round before the van leaves.
Pre-round confirmation
One question, one answer, one structured result: yes, no, or another day.
Rebooking
When nobody is home, it offers the available windows and records the choice.
Address checking
For incomplete addresses it asks for the block, stairwell and floor before the driver hunts for them on the ground.
A delay notice
When a round has slipped, a short call stating the new window and asking for nothing.
Business deliveries
Goods-in hours and the contact person, which are the most common reasons for a B2B return.
How a wave of confirmations is dialled
The hard part is not the call, it is the rules. A wave of a thousand calls dialled outside the legal window is a bigger problem than a hundred returned parcels.
- 01 Upload tomorrow rounds A file with name, number, address and window. Unrecognised columns become per-contact variables, usable in the prompt.
- 02 Set the window and the rules Days, hours, suppression list and retry count. Anything outside the rules is not dialled, and the reason is written on the row.
- 03 The assistant confirms One question, with the window stated plainly. If the answer is no, it offers the alternatives immediately, in the same call.
- 04 Write the outcome Confirmed, rebooked or failed, as structured output with the same values every time, plus the new window if there is one.
- 05 Send it onward The results go into the sheet or system the round is built from, through your own HTTP tool or through Google Sheets.
What reaches the dispatch desk
A wave of calls with no report you can act on before the vans leave has achieved nothing.
| The outcome per contact | Confirmed, rebooked or failed, with the new window wherever it changed. |
|---|---|
| The reason for the ones not dialled | One of the fixed values: outside the window, suppressed, invalid number, too many attempts, and the rest. |
| In your system | Through your own HTTP tool or as rows in Google Sheets, depending on where the round is built. |
| On the call record | The transcript, the ended reason and voicemail detection, which in courier work is the most common outcome of all. |
What it does not do for a courier firm
Courier work is where it is easiest to go from a useful call to a complaint, if the rules are not respected.
- No link to the courier systems There is no connector for the Romanian courier firms. Rounds and results move through your own HTTP tool or a spreadsheet.
- It does not track the parcel live It has access to no tracking beyond what you hand it through a tool.
- It collects no cash on delivery It takes no payment on the phone, not even partially and not as a commitment.
- It does not optimise the round It gathers answers. Routing and stop order stay with your system.
- It has not been run at large volume The dispatcher overlap safety is proven with concurrency tests, not with a real campaign of thousands of calls.
What courier firms ask us
How many simultaneous calls can it place?
The practical limit does not come from us but from your telephony account and the pacing you set on the campaign. What has to be said is that we have not yet run a wave of thousands of calls in production, and the status page states exactly what has been run.
What happens when an answering machine picks up?
The call closes with the voicemail-detected reason and the contact goes to retry if your policy allows. In courier work this is the most common outcome, so it is worth deciding up front what you do with it.
Can it call on behalf of our clients, under their name?
Yes, with the caller ID you configure and the wording you write. What does not change is the responsibility: the basis for the call and the displayed number remain yours, and the national calling rules apply whoever the name in the greeting is.
Does it work for B2B deliveries?
Yes, and there the useful question is a different one: not whether somebody is home, but what the goods-in hours are and who signs. You change the prompt, not the mechanism.
Where to go next
Outbound campaign
Contacts, pacing, window, compliance, start, report.
Developers
A REST surface with OpenAPI, webhooks, MCP, and a tenant boundary enforced in several places.
Integrations
25 business connectors, 18 selectable providers, eight storage destinations.
Pricing
Components at their published price, the platform on top, and what we cannot price yet.
Notes
-
1
The tools named on this page are the ones in
App\Services\Integrations\ConnectorRegistrycarryingimplemented. Anything that is only in the catalogue, without that flag, is not named here as though it worked. -
2
The reasons a contact is not dialled are the fixed values in
App\Enums\CampaignSkipReason, written on every skipped row of the campaign report.