For Fintech and Lending
Build recovery and repayment calls into your lending platform.
Trigger lawful debt collection, repayment reminders and borrower follow-up from the systems that already know when a customer needs to be contacted.
Live in Nigeria.
Call path
Loan or repayment event
Your lending platform
Signals
Nigerian phone networks
Borrower
Outcome returned to software
The workflow problem
Your lending system already knows who needs a call.
Loan status, due dates, repayment state and customer records already exist inside lending, collections and servicing software. The moment a borrower needs to be contacted is usually recorded precisely.
The phone call is often the part that falls outside the system. It is handled through a disconnected dialler, an exported call list, or the personal line of whoever is on shift. The outcome of that call rarely returns to the workflow that created it.
Signals makes the call itself programmable, so it is initiated by the originating workflow and its result comes back to the same place. Signals reads nothing from your systems: you decide which events trigger a call and what information the call carries.
Where the break happens today
Repayment falls due in the lending system
Record exported to a list or a dialler
Call placed manually, often from a personal line
Outcome recorded separately, if at all
For platforms serving lenders
Integrate once. Make voice available to every lender using your software.
If you build software that microfinance banks and lending institutions run their operations on, the telephony layer does not need to be rebuilt for each customer. You integrate Signals once, then expose controlled calling inside your own product.
Each institution keeps working inside the interface it already uses. Calls are initiated by your product, on numbers that are purchased and selected deliberately, with records available for review.
Provisioning, separation between institutions and commercial arrangements remain part of your product design. Signals does not provide native subaccounts, automated tenant billing or one-click provisioning.
Read the Software Providers page →Distribution path
Signals
Your lending platform
Microfinance and lending institutions
Borrowers
Priority workflows
The calls a lending operation makes every day.
Lawful debt collection
Initiate controlled recovery calls directly from a loan or collections workflow, using numbers the institution owns and records it can review. Fraudulent or harassing collections are prohibited on Signals.
Repayment reminders
Remind a borrower before or after a due date and return supported responses, such as keypad input, to the software that triggered the call.
Borrower follow-up
Trigger a call after an onboarding, servicing or repayment event, so the follow-up happens as part of the workflow rather than a separate manual list.
Human escalation
Use supported call control to connect a borrower to an authorised human team where the workflow requires a conversation rather than an automated message.
Three ways to build
Choose the level of control the workflow needs.
Path 01
Programmable Voice (Twilio Compatible)
Create and control calls directly from your application when the logic lives in your own codebase.
- Create calls through the Calls API.
- Control the call with OneML.
- Receive webhooks and status callbacks.
- Retrieve recordings and call records where enabled.
Path 02
Automations
Configure a repeatable workflow when the pattern is stable and does not need bespoke application logic.
- Event triggers the workflow.
- Call is placed from a selected number.
- Keypad response is captured.
- Outcome is returned to your systems.
Path 03
SIP Access
Connect a lending or collections platform that already runs its own dialler or voice system.
- Managed SIP connectivity to Nigerian networks.
- Keep your existing dialler and agent tooling.
- Nigerian mobile numbers held in one account.
- Call records and usage visible in Signals.
Numbers and records
Use controlled Nigerian mobile numbers instead of staff personal lines.
Calls run on familiar Nigerian mobile numbers the institution owns. Additional numbers backed by different Nigerian providers can be held in the same Signals account, and you choose which owned number is used as the originating number for a given workload.
Because the numbers belong to the business, the call history belongs to the business too. Call logs, recordings where enabled, usage and number history stay central and reviewable rather than sitting on a handset.
Signals does not select numbers or providers on your behalf, and makes no claim about how a particular number affects whether a borrower answers.
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.
Compliance and quality
Collections traffic must remain lawful and controlled.
- Lawful debt collection, repayment reminders and borrower follow-up are supported workloads.
- Harassment, fraudulent collections, caller-ID spoofing and unsolicited bulk voice advertising are prohibited.
- The customer remains responsible for lawful use, call content, consent and the behaviour of its agents and workflows.
- Signals uses KYC and acceptable-use controls to protect network quality and legitimate customers.
Prohibited use
Caller-ID spoofing, harassment, fraudulent collections, unsolicited bulk voice advertising and international revenue-share fraud are prohibited on Signals.
Signals is a telephony platform. It is not a collections agency, a lending platform or an automated collections agent.
Read the acceptable use policy →Implementation
From the triggering event to a production workload.
- 01Identify the loan or repayment event that triggers a call.
- 02Complete KYC and enable Developer Mode.
- 03Choose Programmable Voice, Automations or SIP Access.
- 04Configure numbers, messages or call control, and callbacks.
- 05Test in the documented environment.
- 06Move a controlled workload into production and expand.
Self-service onboarding is available and costs nothing extra. Developer Mode is enabled after full KYC, after which you can purchase numbers and configure call workflows yourself.
A technical discovery call is optional. It is most useful where a platform serves several lending institutions, or where an existing dialler needs to be connected over SIP.
Put your first recovery or repayment workflow into production.
Path 01
Review your lending workflow, numbering and integration approach with our engineers.
Path 02
Subscribe, complete KYC, enable Developer Mode and build your first repayment workflow.