Family A · Serving customers
MeshFin Serve
Customer servicing and requests
The front door. Every request on every channel identified with consent, classified, resolved where it can be and routed where it must be, with the status visible to the customer until it is closed.
MeshFin Serve (MF-02), the service for customer servicing and requests, is one of the twenty-four MeshFin services, in the "Serving customers" family, which follows the BIAN Sales and Service business area. It covers the BIAN service domains Servicing Order, Servicing Issue, Servicing Mandate, Contact Handler, Session Dialogue, Customer Workbench and Customer Event History in whole or in part. The front door. Every request on every channel identified with consent, classified, resolved where it can be and routed where it must be, with the status visible to the customer until it is closed. It replaces contact-centre crm, branch request forms, shared mailboxes and spreadsheets and separate chat, app and phone queues. AI agents carry the work end to end; a named person takes every decision with legal or financial effect on a customer, the balance sheet or a regulatory obligation. It is core for a universal and retail bank, core for a mutual and community bank, core for a non-bank lender and fintech.
BIAN service domains this service covers
In the BIAN Sales and Service business area of the Service Landscape 14.0, in whole or in part. Lay this over your own BIAN map to see what MeshFin Serve covers and what stays. BIAN has not reviewed or endorsed MeshFin.
- Servicing Order
- Servicing Issue
- Servicing Mandate
- Contact Handler
- Session Dialogue
- Customer Workbench
- Customer Event History
What it replaces
- Contact-centre CRM
- Branch request forms
- Shared mailboxes and spreadsheets
- Separate chat, app and phone queues
What it reacts to
- Request received on any channel
- Status asked for
- Account detail or authority change requested
- Deceased estate notified
- Owning service closes or stalls
The agents that carry it
Intake agent
Identifies the customer with consent, classifies the request, pulls their history from the other services and answers what it can answer at once.
Resolution agent
Resolves routine requests end to end: a statement, a limit change within policy, a card replacement, a detail change, a payment query, a document reissue.
Routing agent
Routes what it cannot resolve to the owning service, chases it against the service standard, and keeps the customer informed without being asked.
Where a person decides
No decision with legal or financial effect on a customer, the balance sheet or a regulatory obligation is taken by an agent alone. In MeshFin Serve, these decisions are held for a named person, with the agent's evidence and recommendation attached.
| Decision | Who decides | Why a person |
|---|---|---|
| Release of funds or change of authority on an account | Delegated officer | Legal and financial effect |
| Response to a complaint about conduct | Team leader | Reflects on a named person; the complaints service takes the matter |
Records it writes
Request record · Contact history · Servicing order · Service-standard breach note
Before MeshFin: the baseline this service is measured against
Illustrative figures for a mid-sized institution on the systems the service replaces. Sample data, not a customer's. A live service reports what its agents are doing instead.
Requests a year
1.4M
across app, web, phone and branch
Resolved first contact
44%
today; the rest re-keyed into another system
Median time to close
6 days
today, no status visible to the customer
Channels re-keyed
4
each with its own record of the same person
Institutions: core for a universal and retail bank, core for a mutual and community bank, core for a non-bank lender and fintech. Universal and retail bank ● · Mutual and community bank ● · Non-bank lender and fintech ●.
Questions banks ask about MeshFin Serve
- What does MeshFin Serve do?
- MeshFin Serve is the MeshFin service for customer servicing and requests. The front door. Every request on every channel identified with consent, classified, resolved where it can be and routed where it must be, with the status visible to the customer until it is closed. It reacts to events such as request received on any channel, status asked for and account detail or authority change requested, and writes request record, contact history, servicing order and service-standard breach note as records.
- Which BIAN service domains does MeshFin Serve cover?
- Servicing Order, Servicing Issue, Servicing Mandate, Contact Handler, Session Dialogue, Customer Workbench and Customer Event History, in the BIAN Sales and Service business area, in whole or in part. The mapping is to the published BIAN Service Landscape; BIAN has not reviewed or endorsed MeshFin.
- What systems does MeshFin Serve replace?
- Contact-centre CRM, Branch request forms, Shared mailboxes and spreadsheets and Separate chat, app and phone queues. Because the service runs on the MeshFin platform, the licence, integration and upgrade costs of those systems retire with them.
- What do the AI agents do in customer servicing and requests?
- The intake agent identifies the customer with consent, classifies the request, pulls their history from the other services and answers what it can answer at once. The resolution agent resolves routine requests end to end: a statement, a limit change within policy, a card replacement, a detail change, a payment query, a document reissue. The routing agent routes what it cannot resolve to the owning service, chases it against the service standard, and keeps the customer informed without being asked.
- Which decisions does a person still take?
- Agents never take a decision with legal or financial effect on a customer, the balance sheet or a regulatory obligation. In MeshFin Serve, a person decides release of funds or change of authority on an account (delegated officer) and response to a complaint about conduct (team leader). The record shows who decided, why, on what evidence and under which delegation.