For Software Providers
Add phone calls to your software.
Use documented APIs, Twilio-compatible call control and familiar Nigerian mobile numbers to make calling part of your product. Signals handles the telecom work behind the interface.
Your team owns the product and customer experience. Signals connects the calls.
Abstraction layer
Your product and business logic
Signals Programmable Voice
Nigerian phone networks
People
The problem
Adding a phone call should feel like an ordinary product task.
Software teams already know their users, their workflows, their data model, their application architecture and the product experience they are trying to deliver. Adding a phone call to that product should be an ordinary engineering task.
In Nigeria it usually is not. The underlying telephony domain has not been abstracted cleanly for developers, so a small product decision turns into an infrastructure programme run in an unfamiliar field.
Signals presents that telecom work through the requests, events and records your team already understands.
Complexity you should not have to master
- Carrier and number-provider relationships.
- Local number provisioning.
- Call states and call control.
- SIP and media behaviour.
- Webhooks and delivery events.
- Recordings and storage.
- Usage reconciliation and billing.
- Network behaviour, quality controls and compliance.
The abstraction
Work with calls as software.
Each surface below stands in place of the telecom work underneath it. You work with requests, markup, events and records; the carrier, numbering, SIP and network operations sit behind them.
Calls API
Create, control and end calls from your application using documented HTTP requests, not carrier procedures.
OneML call control
Describe what a call should do in markup, so call behaviour lives in your codebase rather than in telecom configuration.
Webhooks and call events
Receive documented callbacks as a call progresses, so your application reacts to call state the way it reacts to any other event.
Programmable Nigerian mobile numbers
Provision and address familiar Nigerian mobile numbers through the platform instead of negotiating numbering separately.
Call logs, recordings and history
Read call records, recordings where enabled and call history through one platform rather than assembling them per provider.
Usage and billing visibility
See the usage and billing for the traffic in your account instead of reconciling separate provider reports.
Why Signals exists
We were software people who had to figure out telephony.
PressOne was building a software product that needed Nigerian telephony. The infrastructure available at the time was fragmented and poorly abstracted for developers.
So the team assembled and operated the missing layer itself: provider relationships, numbering, call control, SIP, events, monitoring and day-to-day operations.
That layer has since served more than 5,000 customers through PressOne. Signals standardises it and opens it to other software teams, so the same journey does not have to be repeated.
Connectivity across six telco networks describes reach and number availability. It does not mean automatic carrier failover or dynamic routing.
How the layer was built
A software team needing Nigerian voice
Telecom assembled and operated in-house
Proven in production with PressOne customers
Standardised and opened as Signals
Responsibility boundary
Build the experience your way. Leave the telephony layer to Signals.
Your software owns
- Product experience.
- Business logic.
- Customer workflows.
- Application data.
- The customer relationship.
- How voice appears inside the product.
Signals handles
- Nigerian number access and management.
- Network-provider relationships.
- Programmable call creation and control.
- Events and webhooks.
- Call records and recordings where enabled.
- Usage, billing and network visibility.
Your product, its interface and your commercial relationship with your customers remain yours. Signals is the infrastructure beneath the calls your software makes.
Where to start
One primary path, with two supporting options.
Primary path
Programmable Voice (Twilio Compatible)
For developers building call creation and control into software with APIs, OneML, webhooks and Nigerian mobile numbers.
Supporting
Automations
For teams that want standard event-triggered voice workflows without constructing every interaction from low-level primitives.
Explore Automations →Supporting
SIP Access
Managed SIP trunking for software teams that already own or integrate an existing voice stack, provisioned by Signals after technical discovery.
Explore SIP Access →Developer proof
Build it like software.
OneML is Signals’ call-control markup language, derived from TwiML and compatible with supported TwiML applications.
Calls API request
POST /2010-04-01/Accounts/ACCOUNT_SID/Calls.json
To=+2341800000001
From=+2341700000000
Twiml=<Response><Say>Your repayment is due tomorrow.</Say></Response>OneML response
<Response>
<Say>Your repayment is due tomorrow.</Say>
<Gather numDigits="1" action="/repayment-response" />
</Response>What teams build
Voice features your product can ship.
Lending and collections platforms
Lawful debt collection, repayment reminders and borrower follow-up placed from application logic.
Explore →Logistics and delivery software
Delivery scheduling, confirmation and rescheduling triggered by events in your system.
Explore →Healthcare and appointment software
Appointment reminders and attendance confirmation, with the outcome returned to your records.
Explore →SaaS and embedded voice
Voice features inside vertical SaaS products, system integrations and client implementations.
Explore →Numbers
Provision and manage the Nigerian numbers your software calls from.
Calls go out on familiar Nigerian mobile numbers rather than staff personal lines, so the business keeps the relationship and the record.
Numbers supplied by different Nigerian providers can be purchased and managed in one Signals account, and your software chooses which number you own is used as the originating number for an outbound call.
Numbers are purchased and assigned by you. Choosing an originating number is a decision your software makes; it is not automatic failover between providers.
Phone numbers
Interface preview
Numbers purchased from Nigerian providers · originating number selected per workload
Implementation
From API credentials to your first production call.
- 01Subscribe to the Base plan, complete KYC and enable Developer Mode.
- 02Get API credentials and select a Nigerian number.
- 03Make the first test call with the public quickstart.
- 04Add OneML, webhooks and application logic.
- 05Test the product workflow.
- 06Ship the first production use case.
- 07Expand across features, products or customers.
Self-service onboarding for Programmable Voice and Automations costs nothing extra. Developer Mode is available after full KYC. Platform access is ₦500,000 per year.
A discussion with our engineers is optional. It is most useful when you are adapting an existing integration, or where SIP Access or Omni is part of the architecture.
Once the first workflow is live, the same integration can be extended to further features, products and customers without starting again.
Your team owns the product and customer experience. Signals connects the calls.
Path 01
For Programmable Voice and Automations: subscribe to the Base plan, complete KYC, enable Developer Mode and start with the public documentation.
Path 02
Optional: review your integration model, an existing call flow or a rollout plan with our engineers. Not required to start building.