Connect to the systems behind the service
Connect Moozy conversations, forms and payment workflows to the systems your team already uses.
A customer finishes something
A registration, a claim, a payment step.
The record is created
In the system that owns it, without rekeying.
The follow-up fires
A confirmation, a reminder, a handover to your team.
Your systems hear about it
Where you need the event to travel further.
What connects to Moozy
Bring customer actions and business records together, from a completed form to a payment recorded against an account.
Our team handles the integration plan, from configuration and provider setup to custom connections.
| What you need | How it connects |
|---|---|
| Reach customers | WhatsApp, two-way SMS and web chat using your service numbers, accounts and sender identity, with voice-assisted options for spoken interaction. |
| Serve basic phones | Menu-driven services on supported mobile networks, set up with your operator so customers without a data bundle are not left out. |
| Take payments | Mobile money approved on the customer's handset, card payments through a hosted checkout into your own merchant account, and recurring debits the customer can pause or cancel. See how payments work |
| Pay people out | Payouts to mobile wallets, and airtime where that is what a programme distributes. |
| Confirm who someone is | Build customer identification and verification into onboarding, with the checks your service needs. |
| Keep your records straight | Connect completed forms to customer records, service requests and team notifications, with the right field mappings and review steps. |
| Reach your own systems | Connect through APIs, webhooks or exports, with authentication, record formats and failure handling built into the integration. |
Into the systems that hold the record
A conversation is only finished when the system that owns the record agrees it happened — the CRM, the core banking platform, the policy administration system.
Move events and records between Moozy and your systems so your team spends less time rekeying information.
CRM
Bring contacts, form submissions, conversation outcomes and payment results into your CRM through mapped connections.
Core banking and core insurance
Connect service journeys to actions such as recording a premium, opening a claim or starting a loan application.
Webhooks
Build event-driven connections with sender verification, duplicate handling and a clear path for failed deliveries.
APIs
Connect the operations your systems need to create, query or update records, with access managed through API permissions.
Speaking your format
Map fields and transform messages into the format each system expects.
Custom work
Our team can build connections for specialised systems and workflows, covering data exchange, testing and failure handling.
APIs, webhooks and custom work
Bring your system documentation and sample payloads. We will work through the data and actions your connection needs.
The integration plan covers supported operations, field mappings, testing and ongoing support.
Supported operations
What the connection must read, write or trigger.
Field mappings
Which answers and records correspond on each side.
Testing
How the connection is proven before customers use it.
Failure handling
What happens when the other system is unavailable or rejects a request.
Ongoing support
Who maintains the connection after launch, and under what arrangement.
What to bring
The customer action, the systems involved and the result you want recorded.
Bring one workflow to connect
Show us one customer journey and the systems behind it. We will plan the connections with you.