WhatsApp messaging and customer engagement

OmniLink

OmniLink runs customer conversations, payment collection, and structured data capture on WhatsApp from one tenant workspace: registered messaging through Meta as a Tech Provider, Pay by Link and Scan to Pay for remote collection, conversation bots for regulated onboarding, and WhatsApp Flows for in-chat forms, with role-based access and an audit trail underneath.

Sign in to your workspace

Download the OmniLink prospectusPDF, 3.9 MB
Managed platformTenant-aware enterprise rolloutAPI and webhook integration model
sellable modules
9
channels: WhatsApp, SMS, email, voice
4
automated tests across platform and portal
2 700+
durable message delivery
24/7

Built to improve trust, speed, and operational control.

A multi-tenant WhatsApp Business Platform for customer messaging, Pay by Link and Scan to Pay collections, conversation bots, and digital forms, running on a direct Meta Cloud API rail alongside an independent business solution provider connection.

Consolidate WhatsApp messaging, payment collection, and conversation bots into one tenant workspace

Keep messaging live on two independent rails instead of a single point of failure

Give operations and finance teams one audit trail across conversations, payments, and workflow actions

The workflow pressure this product is designed to remove.

A multi-tenant WhatsApp Business Platform for customer messaging, Pay by Link and Scan to Pay collections, conversation bots, and digital forms, running on a direct Meta Cloud API rail alongside an independent business solution provider connection.

Teams running WhatsApp for customer engagement usually stitch together a messaging vendor, a separate payment-link tool, a bot-building platform, and a spreadsheet for who has access to what. Each piece is billed and administered separately, and none of them share an audit trail.

The operating capabilities that make the product usable in production.

  • Registered Meta Tech Provider messaging with a dual rail: the direct WhatsApp Cloud API and an independent business solution provider
  • Pay by Link and Scan to Pay collection, tracked from send through to settlement
  • Collections and promise-to-pay workflows, including debit-order mandate capture
  • Conversation bots with a template library for insurance, lending, and financial-services onboarding
  • WhatsApp Flows and native in-chat forms for KYC and structured data capture
  • Multi-tenant RBAC, TOTP step-up, invite-only team access, and Microsoft Entra / SAML SSO

What ships inside OmniLink.

Messaging

Campaigns and conversations across WhatsApp, SMS, email and AI voice from one template and campaign surface.

Pay by Link

Send a payment link into the live conversation and track the transaction through to settlement.

Scan to Pay

Present a scannable code in branch, on a statement or in a document so a customer can pay without leaving the channel.

Document Distribution

Deliver statements, notices and letters to the customer's channel with delivery evidence attached.

Commerce

Catalogue, cart and order flows inside the conversation so customers can buy where they already are.

Collections

Dunning journeys, DebiCheck mandates and promise-to-pay arrangements run as one tracked workflow.

Collections Trace

Locate and re-contact customers who have gone quiet, with every trace attempt kept on the case record.

Collections Bureau

Book-level oversight across portfolios, with performance visible per campaign and per agent.

Estate Management

Levy billing, notices and AGM communication for managing agents and bodies corporate.

What the product looks like in use.

OmniLink capability toggles generating a live WhatsApp menu preview
Configure, then preview. Toggle workflow packs and see the customer's WhatsApp menu update live.
OmniLink flow builder template gallery
Start from a template. FICA onboarding, claims first-notice-of-loss, NCA lending and agent handoff.
OmniLink agent workspace showing a collections conversation handed from bot to human, with the in-progress arrangement alongside
Bot to human, with context. The agent inherits the whole thread and the arrangement already in progress: balance, proposed amount, disputed date and mandate.
OmniLink loan assessment view showing an affordability worksheet
Regulated depth. Affordability worked against declared, extracted and bureau figures with consent captured.

Where this product fits in live workflow environments.

Lenders

Run origination, servicing and collections in one thread. Application, affordability, disbursement notice and repayment arrangement stay in the same conversation instead of moving the customer between channels.

Insurers

Take first notice of loss on WhatsApp and collect supporting documents in the same conversation. Claim and policy servicing updates stay on the channel the policyholder already uses.

Collections and receivables businesses

Gyms, schools and internet service providers can work arrears with dunning journeys, mandates and promise-to-pay arrangements, then take payment inside the same thread.

Managing agents and bodies corporate

Distribute levy statements, notices and AGM material to residents, and collect levies through the same conversation with delivery evidence retained.

How the product fits into live regulated operations.

Dual-rail WhatsApp

Messages route across two independent rails, so a provider outage or a commercial change does not strand your channel.

Deterministic flows, AI where it helps

An AI intent layer routes conversations, but the deterministic flow remains the auditable spine.

Built for regulated collections

DebiCheck, dunning, promise-to-pay and Section 129 notices with delivery evidence attached.

What buyers validate before this product moves into rollout.

One messaging rail, two providers

Two independent delivery rails run side by side, so a single provider outage does not take down the messaging channel.

Payments inside the conversation

Pay by Link and Scan to Pay requests are sent, tracked, and reconciled without leaving the same workspace used for the conversation itself.

Access that stays governed

Team access is invite-only with role-based permissions and TOTP step-up on sensitive actions. There is no open registration path into a live tenant.

Reliability and isolation by design

No message is silently lost. Durable outbox and inbox delivery, tenant isolation enforced at the API layer rather than in the interface, and a deterministic flow that stays the auditable spine even when the AI intent layer routes a conversation.

  • Durable outbox and inbox delivery so messages are not silently dropped
  • Tenant isolation enforced at the API layer, not the interface
  • POPIA consent ledger, data-subject erasure and a PAIA manual
  • NCA-aware collections with Section 129 delivery evidence

Related solutions and supporting reading.

Use these links to move from product capability into workflow fit, operating context, and the supporting material buyers usually need before implementation planning begins.