For SaaS and Embedded Voice
Make calling part of the software your customers already use.
Add Nigerian phone numbers, call control and voice workflows to your SaaS product through one programmable telephony platform.
For products serving Nigerian businesses and customers.
Distribution path
Signals
Your SaaS product
Your business customers
Their users and phone workflows
Embed, do not bolt on
Keep the voice experience inside your product.
Most products that need calling end up sending users somewhere else: a separate dialler, a browser tab, or a handset. The context the software holds, who the customer is, what the record says, why the call is happening, is lost the moment the user leaves.
With Signals, your product initiates and controls the call from its own workflows and interface. The call is a feature of your software rather than a separate tool sitting beside it.
Signals provides the numbers and the connectivity underneath. Your product owns the interface, the permissions, the customer relationship and any commercial arrangement with your customers. Signals does not provide white-label portals, built-in tenant billing or native subaccounts.
Responsibility boundary
Your product: interface, workflow logic, permissions
Signals: numbers, call control, connectivity
Nigerian phone networks
Your customers and their users
What you can build
Documented capabilities you can put behind your own interface.
Click or trigger to call
Let a user start a call from inside your interface, or have a background job start it, using the Calls API.
Event-triggered calls
Place a call when a defined event occurs in your product, through your own service or a configured Automation.
Inbound call handling
Receive calls on Nigerian numbers held in the account and control what happens with OneML returned by your webhook.
Keypad input and supported responses
Collect keypad input during a call and act on the result, or return it to your product for processing.
Recordings and call history
Retain recordings where enabled and retrieve call records so your product can display its own history.
Connect an existing voice stack
Where your product already ships with a voice system, connect it to Nigerian networks over managed SIP.
Three product paths
Pick the layer that matches how your product works.
Path 01
Programmable Voice (Twilio Compatible)
The default for SaaS products. Your service drives every call directly.
- Calls API for creating calls.
- OneML for call control.
- Webhooks and status callbacks.
- Recordings and call records where enabled.
Path 02
Automations
For repeatable workflows that do not warrant bespoke application code.
- Configured event triggers the call.
- Message or call control runs.
- Supported keypad response captured.
- Outcome returned to your systems.
Path 03
SIP Access
For products that already ship a voice system and need Nigerian connectivity beneath it.
- Managed SIP connectivity to Nigerian networks.
- Keep your existing voice stack.
- Nigerian numbers held in one account.
- Usage and call records visible in Signals.
Distribution
Reuse the same telephony layer across products and customer workflows.
The telephony integration you build once can serve every workflow in your product, and every business customer using it. You are not rebuilding a voice layer for each module, each vertical or each deployment.
Numbers and workloads are managed deliberately: purchased in the account, then chosen for a given product feature or customer workflow. That decision stays yours, and Signals does not select numbers or providers automatically.
Where you build software that other companies operate, the Software Providers page sets out the same model for repeatable client implementations.
Read the Software Providers page →One integration, many workflows
One Signals integration
Multiple product features and modules
Multiple business customers
Their end users on Nigerian networks
Developer experience
A familiar API surface and documented call control.
Calls API request
POST /2010-04-01/Accounts/ACCOUNT_SID/Calls.json
To=+2341800000001
From=+2341700000000
Url=https://your-app.example/voice/answer
StatusCallback=https://your-app.example/voice/statusOneML response
<Response>
<Say>Connecting you to your account manager.</Say>
<Gather numDigits="1" action="/voice/menu" />
</Response>OneML is Signals’ call-control markup language, derived from TwiML and compatible with supported TwiML applications. Teams that have built against a Twilio-compatible API will recognise the request shape and the response format.
Numbers, usage and visibility
One account for the numbers your product calls from.
Familiar Nigerian mobile numbers are purchased and held in a single Signals account, including additional numbers backed by different Nigerian providers. Your product chooses which owned number a workflow calls from.
Call records stay central, with recordings available where enabled, and usage is visible alongside the numbers. Network performance is visible in real time.
Signals does not perform automatic provider selection, failover or routing decisions on your behalf.
Phone numbers
Interface preview
Numbers purchased from Nigerian providers · originating number selected per workload
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.
Network performance
Interface preview
Monitoring active
numbers · calls · usage
Call logs
per call, per leg
Usage and billing
Interface preview
Implementation
From subscription to a shipped calling feature.
- 01Decide which part of your product initiates a call.
- 02Complete KYC and enable Developer Mode.
- 03Purchase the Nigerian numbers your first workflow needs.
- 04Build the call with the Calls API and OneML, or configure it in Automations.
- 05Handle webhooks and status callbacks in your own service.
- 06Test in the documented environment, then ship the feature to customers.
Self-service onboarding is the default and costs nothing extra. Developer Mode is enabled after full KYC, after which you can purchase numbers and build against the API directly.
A technical discovery call is optional. It is most useful at higher call volumes, or where several products and customer deployments share one telephony architecture.
Put Nigerian voice inside your SaaS product.
Path 01
Review your product architecture, numbering and expected call volume with our engineers.
Path 02
Subscribe, complete KYC, enable Developer Mode and build your first calling feature.