For Healthcare
Put appointment reminders and confirmations inside your healthcare workflow.
Trigger calls from appointment and patient-management systems, capture supported responses and return the outcome to software.
Signals provides telephony infrastructure, not clinical software or medical advice.
Call path
Appointment event
Healthcare platform
Signals
Patient
Confirmation or follow-up outcome
The workflow gap
The appointment exists in software. The reminder should too.
Scheduling and patient-management software already holds the appointment, the time and the contact details. The system knows precisely when a reminder is due.
In practice, the reminder is often made by administrative staff working through a printed or exported list, sometimes from personal handsets. Whether the call happened, and what the patient said, is recorded informally or not at all.
Signals allows the platform itself to trigger the call and receive the outcome, so the reminder becomes part of the same record as the appointment. Signals makes no claim about attendance rates or clinical outcomes.
Today's manual path
Appointment scheduled in software
List printed or exported for the front desk
Staff call manually, sometimes from personal lines
Patient response captured informally
Priority workflows
Administrative calls around the appointment.
Appointment reminders
Call a patient ahead of a scheduled appointment with the details the organisation has decided to include in the message.
Attendance confirmation
Capture a supported keypad response indicating whether the patient intends to attend, and return it to the scheduling system.
Rescheduling follow-up
Where a patient indicates they cannot attend, return that response to software so the administrative team can offer another slot.
Post-appointment administrative follow-up
Trigger an administrative follow-up call after a visit, for matters such as confirming a return date or completing paperwork.
These workflows are administrative. Signals is not used to deliver diagnostic, clinical or medical advice.
How it works
Event, call, supported response, outcome returned.
- 01The appointment or patient-management system emits an event or scheduled trigger.
- 02Signals places the call from the number the organisation selected.
- 03The call plays the configured message or executes OneML call control.
- 04The patient responds through supported keypad input.
- 05The outcome returns to software through a webhook or status callback and appears in the call log.
Automation run
Event received
webhook
Call placed
outbound
Input gathered
keypad
Outcome recorded
call log
Which building block
Automations suits configured, repeatable reminder workflows that a clinic or hospital administrator can set up without writing application code.
Programmable Voice suits application-level control, where a healthcare software product creates the call through the Calls API, returns OneML and handles callbacks itself.
Numbers and records
Keep patient calls on the organisation’s numbers, not personal handsets.
Calls run on familiar Nigerian mobile numbers the organisation owns. Numbers from different Nigerian providers can be held in one Signals account, and you select which owned number a given workflow calls from.
Call history remains central and reviewable, with recordings available where they have been enabled on the account. Number management sits in the same place.
Signals does not make claims about data residency, encryption standards, healthcare compliance certifications or privacy guarantees beyond the terms and controls it actually provides.
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.
Responsible implementation
Build the call around the minimum information the workflow needs.
- The customer controls the message content and any patient data sent to Signals.
- Avoid exposing unnecessary sensitive information in a voice message; include only what the workflow needs.
- Use the KYC, access controls and account permissions already available in the platform.
- The customer remains responsible for applicable privacy, healthcare and consent obligations.
A practical example
A reminder can confirm that an appointment exists, when it is and where to attend, without naming a condition, a department or a treatment. The keypad response can be a simple confirmation the workflow interprets on its own side.
Product paths
Three ways healthcare organisations connect.
Path 01
Automations
Configured appointment workflows that run without bespoke application code.
- Scheduled or event-based trigger.
- Call from a selected owned number.
- Supported keypad response captured.
- Outcome returned to your systems.
Path 02
Programmable Voice (Twilio Compatible)
Application-level control for healthcare software products and integrators.
- Calls API for call creation.
- OneML for call control.
- Webhooks and status callbacks.
- Recordings and records where enabled.
Path 03
SIP Access
For healthcare contact centres or organisations already running a voice system.
- Managed SIP connectivity to Nigerian networks.
- Keep the existing contact-centre platform.
- Nigerian numbers held in one account.
- Call records and usage visible in Signals.
Implementation
From a single reminder workflow to routine use.
- 01Identify the appointment event that should trigger a call.
- 02Complete KYC and enable Developer Mode.
- 03Purchase the Nigerian numbers the organisation will call from.
- 04Configure the workflow in Automations, or build the call with Programmable Voice.
- 05Test in the documented environment.
- 06Run one appointment workflow in production, then extend it.
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, and is most useful where integration architecture spans several sites, systems or software vendors.
Connect your appointment workflow to Nigerian phone networks.
Path 01
Review your appointment events, numbering and integration approach with our engineers.
Path 02
Subscribe, complete KYC, enable Developer Mode and configure your first reminder workflow.