Skip to main content
GullySystem
Financial services

Contact & Account Management for Banks

Keep organisations and their individual contacts connected.

CRM

Does this function belong in your operation?

Use when accounts have several contacts or owners change.

A business relationship or contact is added.

A retail depositor, a working capital borrower and a trust account holder each appear once, with linked accounts, nominees and relationship manager. Branch staff open one screen to answer any query. Duplicate customers are merged.

Bring the records the workflow depends on.

  • Account identifiers
  • Contact roles
  • Ownership rules

Outputs to check

  • Account and contact directory
  • Ownership and interaction history
  • Duplicate-review list

Follow the contact & account management workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Register the organisation

    Check identifiers and possible duplicates.

  2. 2. Add contacts

    Record each person's role and permitted communication details.

  3. 3. Assign ownership

    Identify who maintains the relationship and next actions.

  4. 4. Record interactions

    Keep history against the correct account and contact.

  5. 5. Maintain changes

    Handle moves, departures and mergers without transferring unrelated history.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

Sales executive

Opens the account before a visit and sees the last order, the pending amount and the last complaint.

Accounts assistant

Finds the right person to call about a bill, and the tax ID that belongs on the invoice.

Owner

Reviews important account relationships, ownership changes and unresolved customer actions.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Duplicate account names

Compare identifiers before merging and preserve linked transactions.

Contact changes employer

End the former relationship without moving its history to the new account.

Account owner leaves

Reassign responsibility while retaining prior interaction authorship.

Can this work independently?

The directory can stand alone with controlled imports and updates. Leads, opportunities, billing and support use the same account identifier when connected. A person may have several business relationships, so contact identity should not be confused with one account's financial responsibility.

Systems and records it connects with

  • Lead management: Enquiry sources, owners and qualification decisions.
  • Quote and proposal management: Commercial proposal versions and acceptance details.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Accounting software: Posted financial entries and reconciliation references.

Configure, test and introduce the workflow.

  • Share your customer sheet or software. A summary lists the firms, people and branches found inside.
  • Decide which roles and terms matter in your trade. Try a trial account. It holds people, branches and terms. After a trial load your staff merge the flagged duplicates. The cleaned list returns for sign-off. Only then does the real load run.
  • Sales staff, accounts and the owner see their own part. Every role takes home a sheet. It is short and written for their work. Calls and visits are logged on the account from now on. The owner and team go through some accounts. Fields are adjusted as needed.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Contacts remain distinct from organisations.
  • Duplicates are flagged.
  • History survives reassignment.
Banks

How the business operates.

A bank serves people and businesses through branches, relationship managers, call centres and digital channels. Each channel keeps its own notes, yet the customer expects one institution. Records built around the account number rarely show who the customer is, which sanction is pending or what was asked last month.

Customer records

Hold each person or business once, with linked accounts, guarantors, contacts, relationship manager and branch, so every team in every department starts from the same customer file.

Applications and approvals

Take account opening and loan applications, route them by amount and role, and keep each decision with the approver’s name, date, covenants and note.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Customer records. Hold each person or business once. Linked accounts, nominee details, contacts, relationship manager and home branch sit on one page that every team opens.
  • Enquiries and product applications. Record every enquiry with its channel and product, carry it forward to an application, and spot the enquiries that have stopped moving after a rate quotation went out.
  • Documents and identity checks. Store identity, address, income and specimen signature papers against the customer. Note who verified each one, and flag documents close to their expiry date.
  • Credit applications and approvals. Route each application by amount and role, and collect the reviewer’s notes on collateral and covenant terms. The final sanction stays with the approver’s name, tenor and date.

Operational bottlenecks to check

Customer details sit in several tools

The branch, the loan desk and the complaints team each keep their own notes. A new mobile number given at one teller counter never reaches the other two desks, and statements and calls go to the old one.

Approvals leave a thin trail

A sanction given by email or in a committee meeting is hard to find later. The file shows the outcome but not the reviewer, the limit applied, the collateral taken or the reason. Audits need all four.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Enquiry

    A person asks about a savings account, a card or a term loan at a branch, on the phone or online. The enquiry is logged against the customer and the product asked for.

  2. 2. Application and documents

    The application is entered once. Identity, address and income papers are attached, a collateral valuation is added for secured lending, and each paper is marked as checked with the verifier’s name.

  3. 3. Review and approval

    The request routes to the officer or committee its amount requires. Each sanction is recorded with the approver, the tenor, the covenant terms, the date and the reason for the decision.

  4. 4. Servicing

    Service requests become tickets. A cheque book, a card replacement, a passbook reissue or an address change each gets an owner and a promised date.

  5. 5. Follow-up

    Complaints are answered by their reply date. Accounts past due are listed by age, and every call, promise and moratorium request is noted against the account for the next officer to read.

  6. 6. Reporting

    Branch managers and head office read the same counts of applications, sanctions, complaints and arrears, taken straight from the records, so nobody rebuilds them from sheets at month end.

Industry reports to connect with

  • Applications by product, branch and stage
  • Sanctions by level, approver and turnaround
  • Complaints open, closed and past ombudsman date
  • Collateral valuations due for renewal

Questions before implementation.

When should banks consider contact & account management?

Use when accounts have several contacts or owners change. A business relationship or contact is added.

What should we bring to the requirements discussion?

Bring anonymised examples of Account identifiers; Contact roles; Ownership rules. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Keep organisations and their individual contacts connected. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Storage does not establish marketing consent or permission to share data.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Contacts remain distinct from organisations. Use this check when reviewing the first working version.

Talk to us

Discuss contact & account management for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements