An AI Assistant in Your Remittance Console: Ask Why a Transfer Is Stuck

Every money transfer business has the same three questions on repeat: why is this transfer stuck, why can't this customer send, and is the payout partner down or is it us? The answers are almost always already in the system, spread across the transfer page, the payout record, the partner's last reply and the audit log. Finding them takes a person who knows where to look. This guide is for operations, support and compliance leads who want those answers in seconds, from their own data, without handing customer details to anyone.

The principle: the assistant reads the records and explains them. Your team still decides what to do.

RemitSo, a white label remittance platform, now has an AI Assistant inside the admin panel, available as an optional add-on. An operator types a question in plain words and gets an answer drawn from the platform's own records, limited to what that operator is allowed to see. Your team still owns every decision: retrying a payout, releasing a hold, contacting a partner, or telling a customer.

Most operations time does not go on hard problems. It goes on looking up easy ones. A customer calls about a transfer sent two days ago. Someone opens the transfer, then the payout, then the partner's response, then the log of outbound calls, and finally works out that the partner accepted the payout and has not answered since.

That lookup follows the same path every time, which is exactly why it can be asked as a question instead:

• "Why is this transfer still sent for payout?" The answer needs the transfer's history, the partner's last reply and how long payouts on that route usually take.
• "Why can't this customer send?" The answer may be a sending limit, a document that expired, a screening hit waiting for a ruling, or a hold.
• "Is the payout partner failing right now, or is it us?" The answer needs the calls made to each partner in the last hour and the state of the platform's own queue.
• "Whose side was this failure on?" The platform's, a setting on your installation, or the partner's. Each one leads to a different next step.

Here is a question asked on a staging installation during testing, with the transfer reference left out.

An operator asked: "Why is this transfer still sent for payout, and whose side is it on?" The assistant read two records and answered in about twenty seconds:

• The transfer had sat at Sent for Payout since a given date, after the partner accepted it.
• Side: the partner, with its reasons. It added a caveat: the route had never paid out on that installation before, so the installation's own setup could not be ruled out.
• It noticed an inconsistency on the payment side and pointed it out.
• Its advice: do not retry, because retrying a payout the partner may already hold risks paying twice. Ask the partner instead.

The operator then asked for a transfer diagnosis report as a PDF, and it was ready a few seconds later. The answer did not fix anything on its own, and it was not meant to. It told the operator where the problem was, what not to do, and who to call.

Before anyone switches on an AI assistant in a regulated business, the compliance team will ask three questions. Here are the answers for the RemitSo assistant.

A good answer on screen is useful to the person who asked. A report is useful to everyone else. The assistant prepares three kinds of PDF:

• Transfer diagnosis: where a transfer is, how it got there, and whose side the problem is on. Useful when you escalate to a payout partner.
• Customer standing: why a customer can or cannot send right now. Useful for a support lead or a compliance review.
• Partner health: how a payout partner has been answering. Useful for a weekly partner call.

The console builds each report from its own data, under the operator's own access, and leaves personal data out. Each download is recorded.

The assistant runs on AI credits that RemitSo issues. The rules are deliberately simple:

• Every question spends one credit. A question that fails spends none, and its credit is returned.
• Credits are added with a top-up code that is checked against the platform's own signature, bound to your installation and applied once.
• Operators see the balance on the AI Assistant page. An AI Assistant Credits card under System Utilities lists every top-up, spend and return, and is where a top-up code is applied.
• The AI Credits Running Low alert warns once a day while credits are at or below the warning level, so nobody discovers an empty balance in the middle of an incident.
• When credits run out, the assistant stops answering until the next top-up. Nothing else in the console is affected.

Some teams already work in an AI assistant and would rather ask there. The AI Assistant Access page lets a staff member connect Claude, Codex, Grok, Gemini or an assistant in their code editor to the console with a token of their own, and gives step-by-step setup guides for each.

• One token per assistant, so one can be stopped without the others. Tokens last 90 days and can be revoked at any time; a revoked assistant is refused from its next request.
• One record at a time. The assistant names a transfer by its transaction number or a customer by their customer number. It cannot search or list.
• Seven tools behind it: transfer lookup, transfer diagnosis, transfer trace, customer lookup, customer diagnosis, provider health and a glossary of the console's states.
• What it never receives, however the question is put: names, dates of birth, addresses, email addresses, phone numbers, identity and document numbers, document images, account numbers, collection PINs, and notes and justifications.
• Every question is recorded in the audit log under the person's name, and the AI Assistant Queries page shows the last 30 days of questions, the tool that answered and the outcome.

1. Start with operations and support. They ask the most "why" questions and benefit first.
2. Grant permissions by role. Asking and downloading reports to the people who need them; viewing credits and applying codes to one or two people.
3. Subscribe someone to the low-credit alert on day one.
4. Rate the answers. Each answer can be rated, and a poor rating asks what was wrong. Those ratings help tune the assistant to the questions your team really asks.
5. Keep decisions with people. Write it into your procedures: the assistant explains, a named person decides.

The AI Assistant arrived in release 2026.10.9 and runs on every RemitSo installation that holds the licence. It sits alongside the tools your team already uses to find problems: Scout lists everything waiting on a person, the outbound API log records every call to a partner, and alerts say in plain language whose side a fault is on. Read the release notes, see the admin features, or book a demo to see it answer questions on a demo installation.