For Logistics
Turn delivery events into calls and customer responses.
Trigger delivery scheduling, confirmation and rescheduling calls from the software that already knows when an order is ready, dispatched or approaching the customer.
Live in Nigeria.
Call path
Order or delivery event
Logistics platform
Signals
Customer
Confirmation or response returned to workflow
The operating gap
The delivery system knows what changed. The customer still needs to be reached.
Order management, dispatch and route software record every meaningful change: an order is packed, a vehicle is assigned, a delivery is out, an attempt has failed. Each of those states is a precise signal that a customer should be contacted.
The contact itself usually happens outside that software. An operations team works down a manual call list, or a driver calls from a personal line as they approach. The answer the customer gives, whether they are available, whether the address has changed, whether they want a different day, is not written back into the system that needed it.
Signals turns those events into controlled calls and returns the supported response to the workflow. It does not replace dispatch, routing or order-management software, and it does not track vehicles or manage deliveries.
Where the loop breaks
Delivery state changes in the platform
Operations exports a manual call list
Driver or agent calls from a personal line
Customer response stays outside the system
Priority workflows
Four calls that decide whether a delivery lands.
Delivery scheduling
Ask or inform a customer about the intended delivery window before a vehicle is committed to the route.
Delivery confirmation
Capture a supported keypad response confirming the customer is available, before dispatch or on approach.
Rescheduling
Return the customer's response to the workflow so the operation can follow up and place the delivery again.
Order-status follow-up
Trigger a call when a defined order or delivery state changes, rather than waiting for a manual check.
How it works
Your platform triggers the call. Signals returns the outcome.
- 01The logistics system emits a webhook or a scheduled event.
- 02Signals places the call from the number you selected for that workload.
- 03The call plays a message or executes OneML call control.
- 04The customer responds through supported keypad input or call control.
- 05The result returns to your software through a webhook or status callback, and is recorded in the call log.
Automation run
Event received
webhook
Call placed
outbound
Input gathered
keypad
Outcome recorded
call log
Automations or Programmable Voice
Automations is a configured workflow: you define the trigger, the message, the response you want to capture and where the outcome goes. No application code is required to run it.
Programmable Voice is application-controlled: your own service creates the call through the Calls API, returns OneML to control what happens on the line, and handles webhooks and status callbacks itself.
Choose the building block
Configure a workflow, or build the call yourself.
Path 01
Automations
For repeatable delivery workflows where the pattern is stable across thousands of orders.
- Event triggers the configured workflow.
- Call placed from a selected owned number.
- Supported keypad response captured.
- Outcome returned to your systems.
Path 02
Programmable Voice (Twilio Compatible)
For direct, application-controlled calls where the logic belongs in your own codebase.
- Create calls through the Calls API.
- Control the call with OneML.
- Handle webhooks and status callbacks.
- Retrieve recordings and records where enabled.
Already running a contact centre
Where an operation already runs a dialler or contact-centre platform for customer care, SIP Access connects that system to Nigerian phone networks without replacing it.
Explore SIP Access →Numbers
Stop depending on driver or operations staff personal lines.
Calls run on Nigerian mobile numbers the company owns. Numbers backed by different Nigerian providers can be held in the same account, and you choose which owned number a workflow calls from.
Numbers can be organised by workflow, merchant or customer segment where you configure them that way. This is a manual decision you make in the account: Signals does not assign numbers to drivers or select a provider automatically.
Because the number belongs to the operation, so do the call records and any recordings enabled on the account.
Phone numbers
Interface preview
Numbers purchased from Nigerian providers · originating number selected per workload
Visibility
See what the operation actually attempted.
Call logs record the direction and documented state of each call, so the operation can see whether a call was attempted, answered or completed, and inspect the supported responses that were captured.
Workflow runs and usage sit alongside the numbers in the same account, so the cost and the volume of a delivery workflow are visible in one place.
These are telephony records, not delivery analytics. What they show is what happened on the call.
Call log
Interface preview
| Run | Direction | State | Response |
|---|---|---|---|
| Run 001 | outbound-api | completed | Keypad 1 |
| Run 002 | outbound-api | completed | Keypad 2 |
| Run 003 | outbound-api | no-answer | — |
| Run 004 | inbound | completed | — |
Illustrative interface. Records shown are placeholders.
Usage and billing
Interface preview
Implementation
Start with one delivery state, then widen.
- 01Identify the order or delivery event that should trigger a call.
- 02Complete KYC and enable Developer Mode.
- 03Purchase the Nigerian numbers the workload requires.
- 04Configure the workflow in Automations, or build the call directly with Programmable Voice.
- 05Test in the documented environment.
- 06Run one delivery workflow in production, then extend to further states.
Self-service onboarding is available and costs nothing extra. Developer Mode is enabled after full KYC, after which numbers and workflows can be configured directly.
A technical discovery call is optional. It is most useful for platform-scale integration, where a logistics product serves many merchants or connects an existing voice stack.
Read the documentation →Connect your delivery workflow to the telephone network.
Path 01
Review your delivery events, numbering and integration approach with our engineers.
Path 02
Subscribe, complete KYC, enable Developer Mode and configure your first delivery workflow.