Four Agentforce agents for banks and insurers, and their guardrails

29 October 2026
Arcsen

A Gulf bank’s contact centre answers the same requests all day: block my card, where is my replacement, why was I charged this fee. An insurer’s claims line spends the first call on each motor claim collecting the same details and photos. Relationship managers build meeting briefs from several systems, and complaints arrive on every channel, each logged its own way.

Agents can take much of this work in Arabic and English. The harder question in financial services is where they stop. Advice, credit and claims decisions, complaint outcomes and customers in vulnerable situations are regulated, and they belong with qualified people. This guide covers the four agents we would build first, what each needs, the lines to agree with compliance and how to test them, going further than the agent section of our Financial Services Cloud guide.

Four agents worth building first

Card and account service, for customers on the website and WhatsApp. Salesforce’s Banking Service Customer Assistance template verifies the customer’s identity, reviews deposits, withdrawals and payments, locks a card temporarily and reactivates it, and reports a card lost, stolen, destroyed or captured by an ATM. With Agentforce Voice it can also take calls. Anything it cannot finish becomes a case for a banker, with the conversation attached.
First notice of loss (FNOL) intake, for policyholders. Claims Management for Insurance includes prebuilt FNOL flows by line of business, and Trailhead walks through one that pulls the policy, takes the loss details and photos, checks coverage, creates the claim and assigns it to a claims handler by rules. Salesforce also lists claims templates for voice intake and for claims staff. The agent collects the facts and confirms the claim number, and the handler decides cover and payment.
Relationship manager assist, for RMs and advisers. In the same template set, Financial Advisor Assistance summarizes a client’s portfolio, goals, plans and life events before a meeting, and Banking Relationship Assistance structures the notes, writes the interaction summary and creates follow-up tasks. We add a draft follow-up message that the RM edits and sends. If your RMs also work in Claude, our Claudeforce guide explains how Salesforce in Claude asks the user to approve each change before it is written.
Complaint triage, on any channel. Salesforce lists a Complaint Management template to capture, triage and resolve complaints. We use the first two: the agent records the complaint in the customer’s words, classifies it, gives the reference number and routes it. A person resolves it, every time.

Agent	Channel	Data and systems it needs	Actions it may take	Where a person takes over
Card and account service	Web chat, WhatsApp, voice	Customer and card records, recent transactions from the core and card systems, fee rules	Verify identity, show transactions, lock a card and reactivate it, report it lost or stolen, open a case	Disputes, fraud, fee waivers above the limit, advice, any sign of vulnerability
FNOL intake	Web chat, WhatsApp, voice	Policy and cover from policy administration, the FNOL flow, photo and document upload	Verify the policyholder, collect loss details and photos, create the claim, give the claim number	Coverage, liability, settlement, injuries, suspected fraud
Relationship manager assist	Salesforce, for RMs	Households, holdings, recent interactions and meeting notes	Prepare the brief, structure notes, draft follow-ups and tasks	Every client message and every recommendation
Complaint triage	Every service channel	Complaint categories, deadlines and owners, the customer’s history	Record, classify, acknowledge with a reference, route	Investigation, outcome, redress and the final response

What the agents need

A verified customer. The household and account model from Financial Services Cloud, and an identity check before any personal data, as the banking template does. If the check sends a one-time password by text message, SAMA’s rules require the message to state its purpose.
Systems of record behind every action. Core banking, cards, policy administration and claims stay the record, and the agent calls the same APIs as your app, with the same limits and logs. With MuleSoft, developers define an API’s agent actions and instructions as they design it, then sync it so Agentforce can call it, as a Salesforce Developers post from June 2025 explains.
Approved content. Terms, fees and policy wording come from approved content in Arabic and English, each item with a named owner in product or compliance, and the same wording as your website (see our guide to bank and insurer websites on SitecoreAI).

Guardrails and handover

Our Financial Services Cloud guide covers the CBUAE’s rules on suitability and qualified advice. The same regulation also requires institutions to monitor for misleading or aggressive sales practices and for exploitation of consumers due to their vulnerabilities. In February 2026 the CBUAE issued a guidance note on AI for licensed financial institutions, built on governance and accountability, fairness and non-discrimination, transparency and explainability, effective human oversight, and data management and privacy. And SAMA’s Financial Consumer Protection Principles ask for special attention to low-income and less educated people, older people and those with special needs, and for complaints resolved fairly and without delay.

Decisions that stay with people. The agent gives no advice or recommendation on products, investments or cover. It makes no credit decision and promises no limit, rate or approval. It decides nothing on claims: coverage, liability and settlement belong to the claims handler. It never resolves a complaint: it records, acknowledges and routes, and a person investigates and writes the final response. When a customer shows signs of vulnerability, such as age, illness, bereavement, hardship or confusion, it hands over to a trained person at once. Confirm the detail with your compliance team.

Write these triggers into an escalation subagent (subagents are what Salesforce used to call topics). Salesforce’s deployment unit shows the escalation flow passing the session and conversation history to a queue, and says escalation is attempted only once per session: if no one is free, the agent carries on. So a complaint never waits for a free banker. The agent opens the case and gives the reference number and the handling period, which SAMA’s rules require institutions to send by text message. Lost cards and fraud keep their own route too: SAMA requires banks and card issuers to run a 24/7 toll-free number for both, so the agent offers it alongside its own actions. Record every line and trigger in the agent’s charter.

Testing before launch, measuring after

Salesforce lists Arabic as Beta for Agentforce and warns that beta languages may retrieve information inconsistently. Build the test set from your own conversations: Gulf dialects, mixed Arabic and English, product names, and the hard cases on purpose, such as a customer asking which fund to choose, a claim with an injury, an angry complaint, or an older customer confused by a transfer. Our notes from Agentforce World Tour Dubai list what to test in Arabic.

Salesforce’s testing tools cover the build. The Agentforce Builder preview simulates a conversation or tests it on live data, session tracing records each step and needs Data 360 (formerly Data Cloud), and Test Suites, labelled Beta, run batches against the expected subagent and action in a sandbox.

After launch, measure containment by request type, handover quality (whether the banker had to ask again), complaints about the agent, time to first contact on new claims, and the routing of regulated requests, where the target is that every one reaches a person. Review a sample with compliance each week.

Our work in financial services

Arcsen is a Salesforce Summit partner with 170+ consultants and 400+ certifications and offices in Dubai, Riyadh, Jeddah, Doha and Cairo. For e-finance, Egypt’s digital payments infrastructure group, we are migrating the integration layer from TIBCO to MuleSoft. Our financial services clients also include Allianz Saudi Fransi, SICO and Boubyan Takaful. See how we deliver Agentforce in Arabic and English.

Where to start

Rank your service requests, claims notifications and complaints by volume, and mark each as information, transaction or regulated decision.
Agree the regulated lines with compliance first: advice, credit, claims, complaints and vulnerability, with trigger phrases in Arabic and English.
Start with one agent that reads before it acts, such as card status and lost-card reports, or FNOL intake for motor claims.
Write the charter and the test set before anyone builds, and rerun the tests after every change.

Planning agents for a bank or insurer? The free Agentforce Readiness Assessment picks your first three use cases, checks the data and permissions behind them and gives you a costed pilot plan in ten working days. See our financial services work, talk to our financial services team or send us your RFP.

Frequently asked questions

Which banking agent should we build first?

One that reads and answers before it changes anything, such as card status and lost-card reports for verified customers, with a case and a handover for everything else.

Can an agent decide an insurance claim?

We advise against it. Let the agent take the first notice of loss, photos and documents, create the claim and give the claim number. Coverage, liability and settlement stay with the claims handler.

How should an agent handle complaints?

It records the complaint, classifies it, gives the reference number and the handling period, and routes it to the complaints team. A person investigates, decides and writes the final response.

What does the CBUAE expect when financial institutions use AI?

Its guidance note on AI for licensed financial institutions rests on governance and accountability, fairness and non-discrimination, transparency and explainability, effective human oversight, and data management and privacy.