Community banks, regional banks and credit unions use Salesforce to see each customer or member across deposits, loans and wealth in one place. Branch staff, the contact center, commercial bankers and marketing then work from that shared view. The core banking system keeps the ledger. Salesforce holds the relationship, the service history and the next conversation. The payoff depends on a sensible core integration, clear referral rules and marketing that respects every opt-out.
What should a bank or credit union expect Salesforce to do?
Expect it to answer who this person or business is to the institution, and what should happen next. It should not post transactions, calculate interest or replace your core.
For a community bank, that usually means one record showing checking, savings, a mortgage, a small-business line and any wealth referral. For a credit union, the same record describes a member, often with joint owners and family ties.
The work falls into four streams: service in branches and the contact center, commercial relationship management, referrals between lines of business, and marketing. Most institutions start with one or two and add the rest once the data has earned trust.
How do we build a member or customer 360 across deposits, lending and wealth?
Bring a narrow, well-defined slice of account data from each source system onto the person or business record. Show balances and status, not the full transaction history.
Decide early what counts as one customer. Cores often store the same person under several customer numbers, especially after a merger or a conversion. Pick a matching key, agree on survivorship rules and resolve duplicates before anyone sees the new view.
Joint accounts, business owners and authorized signers need explicit relationship records. A deposit account can belong to two members, and a business loan can have three guarantors. Model these links on purpose, because service, sharing and marketing all depend on them.
Is Financial Services Cloud the right starting point for a bank?
Often, but not always. It fits when staff need households, financial accounts and relationship maps; core Sales and Service Cloud can serve a narrower first project.
Financial Services Cloud adds objects for financial accounts, household groupings and relationships between people and businesses. Salesforce briefly used the name Agentforce Financial Services and now calls the product Financial Services Cloud again, so expect both labels. Packaging, editions and which banking features come included change over time. Before scoping, ask your Salesforce account team which banking features your licenses cover.
A credit union focused only on contact-center service may start on Service Cloud and add the industry data model later. A bank planning a full relationship view across retail and commercial will usually save rework by starting on it. Our guide on when Financial Services Cloud fits walks through that decision in more depth.
How should Salesforce connect to the core banking system?
Start read-only and batch, then add real-time or write-back only where a specific workflow needs it. The core stays the system of record for balances, transactions and account status.
Integration options depend on your core provider, digital banking platform and any middleware you already run. Some cores expose APIs, others rely on file extracts, and many institutions use an integration platform between them.
| Pattern | Typical use | What to watch |
|---|---|---|
| Nightly read-only batch | Balances, product holdings, open and closed dates for the 360 view | Staff see yesterday's numbers; label the as-of date on every page |
| Near real-time read on demand | Current balance or recent activity when a service agent opens a record | API capacity, timeouts and what the screen shows when the core is down |
| Event-driven updates | New account opened, loan funded, card reported lost | Event volume, retries and keeping events in order |
| Write-back to the core | Address change or contact preference captured in Salesforce | Ownership of each field, validation rules and an audit trail for every change |
| Document and image links | Signature cards, statements and loan documents | Keep files in the controlled repository and store a secure link, not a copy |
Write-back deserves the most caution. Every field that two systems can edit needs one owner, a rule for conflicts and a person who reviews failures.
How do branch staff and the contact center work cases in Salesforce?
They open a case for each customer request, follow a defined queue and close it with a recorded outcome. Knowledge articles give both teams the same approved answer.
Typical case types include disputes, stop payments, address changes, debit card issues, wire questions and loan payoff requests. Each type should carry its own required fields, owner queue and service target. A request started in a branch should be visible to the contact center if the member calls about it that afternoon.
- Verify identity before anyone discusses account details, and record how it was done.
- Route cases by type, product and skill rather than by whoever answers first.
- Write Knowledge articles for policies, fee explanations and step-by-step procedures, with an owner and review date on each.
- Escalate complaints into a separate tracked process so trends reach compliance and leadership.
- Keep sensitive values such as full account or card numbers out of free-text case comments.
How can commercial bankers manage lending pipeline and treasury relationships?
Give relationship managers a business account with its owners, deposits, loans and treasury services in one view. Track new credit requests and treasury sales as opportunities with stages your credit process already uses.
Keep stages honest about who acts. Early stages belong to the banker: prospecting, needs discussion, term sheet. Later stages belong to credit and loan operations, and those may live in a separate loan system. Pass milestone dates back to Salesforce so the banker sees where a deal stands without editing it.
Treasury management is where many banks find hidden value. Record which services each business uses, such as check deposit capture, ACH origination or positive pay. Then flag commercial borrowers whose operating accounts sit at another institution. That gap is often the most useful list a commercial team can have.
How should referrals flow between branches and lines of business?
Make a referral a tracked record with a sender, a receiver, a product and a status. Without that, referrals vanish into email and nobody can measure or reward them.
A teller notices a member asking about a home purchase. The teller logs a mortgage referral in a few clicks, and it routes to the right loan officer. The loan officer accepts or declines it, and the teller can see the result. The same flow carries branch-to-wealth and branch-to-commercial handoffs.
Agree on the rules before building the screens. Decide who gets credit when two people refer the same customer, how long a referral stays open and what counts as converted. If incentives are tied to referrals, involve compliance in the design so the program rewards appropriate recommendations.
How do we run marketing journeys that respect opt-outs and compliance review?
Build every journey on recorded consent and suppression, and route content through compliance review before it sends. Salesforce can enforce those rules; your compliance and legal teams define them.
Privacy rules such as those under GLBA shape how customer information is shared and what notices are required. Fair lending awareness matters for credit offers, so review targeting criteria for anything that could act as a proxy for protected characteristics. Treat this section as design input; it is not legal advice.
- Store email, text and call preferences separately, with source and date for each.
- Apply suppression lists for opt-outs, closed accounts, deceased members and anyone in collections.
- Add a review and approval step for every new email, landing page and offer.
- Document why each segment was chosen, especially for loan and credit card offers.
A regional bank we worked with had been sending email from ActiveCampaign with no Salesforce connection. Marketing and sales worked separately, with manual data entry and no engagement tracking. We implemented Marketing Cloud Account Engagement, authenticated its sending domain and set up two-way sync for leads, contacts and prospects. Custom prospect fields captured region, current bank, revenue, employees and industry for segmentation.
We organized its programs under one campaign hierarchy covering deposits, mortgage, HELOC and commercial lending. Engagement scoring, tracking domains and suppression lists supported compliance and data hygiene. The bank can now target by region, relationship, asset level and product across its portfolio.
What happens when a digital account opening is abandoned or completed?
Your digital account opening platform should hand Salesforce a clear signal in both cases. A started-but-abandoned application becomes a follow-up task or journey; a completed one becomes a welcome and onboarding sequence.
Pass only what the next step needs: applicant identity, product, channel, status and a reference ID. Leave identity documents and verification results in the opening platform. Check consent before any abandoned-application outreach, and stop the journey the moment the account is funded.
Where can AI help bank and credit union staff safely?
Use AI to draft, summarize and suggest, with a person approving anything that reaches a customer or touches a credit decision. Start with internal, low-risk tasks.
Good early candidates include case summaries for the contact center, suggested Knowledge articles and draft follow-up emails for bankers to edit. Grounding answers in your approved Knowledge content keeps them closer to policy. Log prompts and outputs, review samples on a schedule and keep AI out of eligibility, pricing and approval decisions.
Which reports show whether the program is working?
Track product penetration, cross-sell, referral conversion, member or customer growth and service performance. Set your own baselines from current data rather than borrowing industry figures.
- Products per household or per member, by branch and segment.
- Referrals sent, accepted and converted, by sender, receiver and product line.
- New members or customers, and closed relationships, by month and channel.
- Commercial pipeline by stage, plus treasury services per business relationship.
- Case volume, resolution time and repeat contacts by case type.
- Journey engagement and opt-out rates by campaign and product.
What mistakes do banks and credit unions make with Salesforce?
Most failures trace back to unresolved data ownership and rules agreed too late. The software is rarely the cause.
- Loading every core field into Salesforce instead of the few that drive decisions.
- Launching a 360 view before duplicate customer numbers are resolved.
- Allowing two systems to edit the same field with no owner.
- Building referral screens without agreeing how credit and conversion are counted.
- Sending marketing before suppression and approval steps are in place.
- Giving every user access to every account when sharing should follow role and branch.
What belongs in phase one for a bank or credit union?
Pick one audience and one data feed, then prove it works. A focused first release builds the trust that later phases need.
- Customer or member records with duplicates resolved and a nightly read-only feed of key account data.
- Case management and Knowledge for one service team, such as the contact center.
- A simple referral process between branches and one line of business.
- Consent, suppression and approval controls before the first marketing send.
- A short set of dashboards built on data staff already maintain.
As a Salesforce Select partner since 2017 with Financial Services accreditation, we help institutions scope that first release and choose what waits. A short discovery usually settles the core integration approach and the starting cloud.
