Compliance by design. Auditable by default.

Moozy is built for organisations that answer to a regulator, an auditor or the public. Consent, access control, human oversight and a complete record are part of how every customer journey runs, not features added afterwards.

Audit trail · one customer

  1. SMSConsent to be contacted recorded
  2. WhatsAppIdentity check passed
  3. SystemApplication scored 72 of 100, two reasons, held for review
  4. ReviewerApproved by a credit officer
  5. PayP120.00 confirmed by payment provider

Recorded stepA person decided

Illustrative record.

Governance that runs with the journey

When a message, a form, an identity check and a payment live in separate tools, the evidence does too. Reconstructing what happened to one customer becomes a project.

On Moozy those steps are one journey on one platform, so they produce one record. The same rules apply on WhatsApp, SMS, USSD and web. The same roles decide who can see what. The same log shows what the system did and what a person did.

  • Complete audit trail, exportable for review
  • Consent tracked per customer and per channel
  • Role-based access to customer information
  • Advisory scoring that shows its reasons
  • Human escalation and oversight
  • Encryption and hosting chosen for data protection law

A complete audit trail

Every event is logged with its time, its channel and its actor, whether that actor is the customer, the platform or a member of your team. The trail can be exported for an auditor or an investigation.

What happenedWhat the record holds
ConversationsMessages sent and received, the channel, delivery outcome, and any handover to a person.
ConsentOpt-in and opt-out, when it was given and on which channel.
Forms and documentsAnswers as submitted, validation results, and the documents or media collected.
Identity checksWhich checks ran, the result returned by the verification provider, and who reviewed a referral.
Scores and flagsThe score, its band, the inputs and reasons behind it, and the person who made the decision.
PaymentsRequests, customer approvals, provider confirmations, failures, retries and mandate changes.
Actions by your teamWho replied, who took over a conversation and who approved, and when.

Role-based access

Roles decide who can see customer information, who can act on it and who can export it. Sensitive items such as identity documents are limited to the roles that need them.

Example roleWhat it is for
AgentTakes over conversations and replies to customers. Sees the conversation, not the identity documents.
ReviewerDecides referred cases. Sees the documents, check results, score and reasons for the cases assigned to them.
AnalystWorks with reports and exports, without access to individual documents.
AdministratorManages users, roles, journeys and connections.

Example roles. Yours are agreed and configured during setup.

Automation you can explain. People who decide.

Moozy automates the routine. It does not take consequential decisions away from your team.

AI replies can be imperfect, so chatbots answer from your approved information and hand over when a question is out of scope or sensitive.

Scoring is advisory

A score informs a person. It never approves, rejects, prices or underwrites, and it never triggers a payout.

Reasons, not just numbers

Each score comes with its band, the reasons behind it and any flags, so a reviewer can agree or disagree with it.

Held for review

Anything flagged waits for a person. Failed identity checks and exceptions are routed the same way.

Escalation on every channel

Customers can ask for a person, and your team can take over a conversation at any point.

Signals raised as evidence

Conversations can be watched for fraud, scam and compliance signals, which are raised to a person with the evidence.

Data protection

Your organisation is the data controller and decides what is collected and why. Moozy is the data processor and handles that information only to deliver your service.

Encryption

Data is encrypted in transit. Encryption at rest is available as a deployment option.

Hosting

Moozy is hosted in regions approved under Botswana’s Data Protection Act. Tell us about residency requirements in other markets during scoping.

Card details stay out

Card payments run through a hosted checkout into your own merchant account, so card details never reach Moozy.

Retention and deletion

Retention periods are set by you as controller. Information that is no longer needed is deleted or anonymised. Data deletion requests

Questions from risk, compliance and IT

Is Moozy certified to ISO 27001, SOC 2 or PCI DSS?

No certifications are claimed on this website. We answer due-diligence questionnaires directly during procurement.

Where is customer data hosted?

In regions approved under Botswana’s Data Protection Act. If you operate in another market with its own residency rules, raise it during scoping so the deployment can be planned around it.

Is data encrypted?

Data is encrypted in transit. Encryption at rest is available as a deployment option and is agreed during setup.

Can we export the audit trail?

Yes. The audit trail of conversations, consents, payments, automated actions and team actions can be exported for review.

Can the platform make a decision about a customer on its own?

Not a consequential one. Scoring is advisory and carries its reasons. A person approves, rejects or prices, and anything flagged is held for review.

Does using Moozy make us compliant?

No platform can do that for you. Moozy provides the controls and the evidence. Your obligations are decided by your regulator and your own policies, and we configure journeys to fit them.

Where these controls apply

Send us your due-diligence questions

Bring your risk, compliance and IT teams to the demo. We will walk through the controls against one of your own journeys.