A complaint-intake Virtual Employee can do useful work before anyone reaches a conclusion. It can register the case, issue an approved acknowledgment, gather permitted records and prepare a clean investigator handoff. It should not decide whether the complaint is valid, write the institution's reasons as fact or choose redress.
That boundary matters in the UAE SME customer-protection context. The CBUAE SME Customer Protection Regulation applies to banks and finance companies licensed by the Central Bank when they provide covered products or services to SME customers. Its complaint rules, shown as effective from 13 September 2026, require a written acknowledgment within two business days and a unique tracking reference.[1] This operating note is not legal advice. An institution should confirm the current rule, its own scope and its approved complaint procedure before using the design.
The intake-to-investigator workflow
- Receive. Accept complaints only from approved channels. Preserve the original message or call record, received time, channel and any attachments. Record whether the person is the customer or an authorized representative.
- Register once. Check for an existing case using observable identifiers such as customer reference, product, transaction reference and received time. Create one case only when the duplicate check is clear.
- Acknowledge. Assign the institution's unique reference and prepare the approved acknowledgment. Record the delivery result rather than treating a sent command as proof of delivery.
- Assemble evidence. Link the original complaint, account or transaction records, prior communications, the policies supplied by the institution and a list of anything still missing. Apply the case's privacy and access rules to every record.
- Hand off. Give a named complaints investigator the source material, a chronology, open evidence gaps and the next due date. Separate extracted facts from the customer's allegation and from any draft analysis.
- Monitor. Track due dates, requested customer updates, unresolved evidence and review states. The final response remains a human-owned action.
The current regulation says a final written response must contain detailed reasons and sets a 30-business-day deadline unless the Central Bank prescribes another limit.[1] It also says the response must accept or reject validity, state redress where appropriate and explain the available external escalation route.[1] A named complaints investigator assesses the evidence, and an authorized complaints manager approves the finding, reasons, redress, final response and closure.
The CBUAE's AI guidance supports that separation. It calls for meaningful human oversight where decisions may significantly affect consumers and says consumers should be able to request human review or an explanation of an AI-generated decision.[2]
Filled example: complaint-to-investigator handoff contract
This is an illustrative SME-customer example built with synthetic values. It is not a real customer, institution, account, outcome or MAJLS deployment.
Intake record
| Field | Filled value |
|---|---|
| Approved channel | Secure web complaint form |
| Received | 28 September 2026, 09:14 Gulf Standard Time |
| Complainant | Customer identity matched to the institution's approved process |
| Representative authority | Not applicable; complainant is the customer |
| Product or service | Payment card |
| Expression of dissatisfaction | Customer disputes a fee shown on the September statement |
| Requested outcome | Review the fee and explain or reverse it |
| Original record | Form submission and attachment preserved under case access controls |
| Privacy class | Customer-confidential; complaints team access only |
| Stop condition | Identity mismatch, representative authority missing, malware check failed or channel record incomplete |
Registration and acknowledgment
| Control | Filled value |
|---|---|
| Duplicate check | No open case with the same customer, card token, fee reference and received date |
| Case reference | CMP-2026-00417, synthetic reference |
| Accountable queue | Card Complaints Team |
| Clock start | 28 September 2026, 09:14 Gulf Standard Time |
| Acknowledgment | Institution-approved template with the case reference and complaint contact route |
| Delivery evidence | Secure-message event ID and timestamp |
| Exception owner | Complaints Operations Lead |
The acknowledgment step should use the institution's approved text, not model-written promises. The two-business-day regulatory requirement is a control input, not a performance claim about this illustrative workflow.[1]
Case-evidence register
| Evidence item | State | Access | Investigator note |
|---|---|---|---|
| Original complaint | Present | Complaints team | Preserve the customer's wording unchanged |
| September statement line | Present | Complaints team | Fee line linked by synthetic transaction token TX-0417 |
| Fee schedule in force on transaction date | Present | Complaints team and policy owner | Version and effective date recorded |
| Card agreement supplied by records owner | Present | Complaints team | Source file hash and retrieval time recorded |
| Prior communication about the fee | Missing | Customer-service records owner | Due 29 September, 12:00 GST |
| Internal fee posting event | Restricted | Named investigator | Request through approved case-access route |
The Virtual Employee may summarize what each record contains, but every summary links back to the source. Missing or restricted evidence stays visible. A blank field never becomes "not applicable" without the investigator's recorded decision.
Decision and approval boundary
| Virtual Employee may prepare | Authorized person must decide |
|---|---|
| Complaint chronology with source links | Whether the complaint is valid in whole or in part |
| List of missing or conflicting evidence | Which evidence is persuasive and why |
| Draft acknowledgment from approved text | Any nonstandard customer commitment |
| Draft investigator questions | The institution's detailed reasons |
| Due-date reminders and update drafts | Whether redress is due and its form or amount |
| Final-response assembly after approval | Final response, external escalation information and closure |
Consequential approval stays with the authorized complaints manager. The Virtual Employee cannot suppress a complaint, approve redress, issue the final response or close the case.
Monitoring and closure record
The case remains open while any of these conditions exists:
- required identity or representative authority is unresolved;
- the duplicate check returns more than one plausible case;
- an evidence owner has not supplied a required record by the due time;
- two records conflict on the fee date, amount, policy version or prior communication;
- the investigator has not recorded a finding and reasons;
- the complaints manager has not approved the final response and any redress;
- delivery of a required customer update or final response has no recorded evidence;
- the institution's fairness-verification step is incomplete.
Escalation is triggered by those observable conditions, policy deadlines and named-owner states. Model confidence alone never escalates, approves or closes a complaint.
At closure, retain the original complaint, evidence register, investigation record, approvals, response, delivery evidence, external escalation information and fairness-review result under the institution's retention controls. The regulation states that registered complaint details must be retained for at least five years from resolution or closure, whichever is later.[1]
First-run checklist
- Confirm the regulation's current status, institutional scope and internal legal or compliance interpretation.
- Name every approved intake channel and preserve the original complaint record.
- Define the duplicate rule, reference-number source and acknowledgment template.
- List the records the role may access and the owner for restricted evidence.
- Separate extracted facts, customer allegations, summaries and human findings in the case packet.
- Assign a complaints investigator and an authorized complaints manager to every case.
- Test missing identity, duplicate case, conflicting evidence, missed deadline and failed delivery with synthetic records.
- Close only after the named human approvals and delivery evidence are present.
The narrow role orders intake and handoff while leaving validity, reasons, redress and final communication with accountable people.