Skip to main content
GullySystem
Financial services

Contact & Account Management for Mutual fund distributors

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.

Each investor is linked to family members, nominees, folios and the bank used for debits. A relationship manager opens one profile before a call. Changes of address or phone are dated.

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.
Mutual fund distributors

How the business operates.

Your book is hundreds of SIPs across families, fund houses and folios. It earns trail only while those SIPs keep running, and keeping them running is follow-up work done on the 5th, 10th and 15th of every month.

SIP failure and cessation alerts

Flag mailback entries every morning with the client’s number beside them, so the call happens before the next debit date.

KYC, mandate and nominee board

List every investor’s KYC, debit mandate and nominee status in one place, with the missing item named.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Family and folio register. Group every folio of a household together, with fund house, plan type, holder names and the goal each holding was opened for.
  • SIP calendar and failure alerts. List each plan against its debit date and flag rejections or lapsed registrations in the morning, with the client’s number beside the line.
  • Debit mandate register. Track each mandate from form to approval, with bank, limit, validity and the plans that depend on it, and chase any stuck for too long.
  • KYC and nominee board. Show every investor’s KYC status and nominee declaration in one list, with the missing item named and the person who will chase it.

Operational bottlenecks to check

Failed SIP debits are spotted too late

After two rejected instalments the registration lapses, and the client has quietly stopped investing. You hear about it at the next review.

KYC on hold blocks the next purchase

A KYC record shows on hold, or the nominee declaration was never given, and you learn when a fresh purchase is rejected. The client asks what went wrong.

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

    Each referral or walk-in is recorded with where it came from, what the family wants and the next step promised. The reminder fires on the date the owner set.

  2. 2. Onboarding

    The investor’s KYC status, nominee choice, bank account and debit mandate are recorded, with the missing item named. Scanned forms are kept on the client’s file.

  3. 3. Plans and folios

    Each regular plan is entered with its folio, fund house, amount and date, and grouped under the family. The goal each plan was started for is noted beside it.

  4. 4. Report reading

    Reports from the registrars and platforms are loaded each morning. Rejected debits, ceased plans and status changes become tasks on a named staff member’s list.

  5. 5. Reviews and statements

    Before a review, the family page shows plans, dates and notes from the last meeting. At year end, holding and gains statements are gathered family by family.

  6. 6. Brokerage check

    Expected trail is worked out per folio and compared with what each fund house paid. Folios with a gap go onto a query list for that fund house.

Industry reports to connect with

  • Failed and lapsed plans by client, fund house and week
  • Mandates and KYC items outstanding, oldest first
  • Enquiries by source, goal and stage
  • Follow-up tasks open and closed by staff member

Questions before implementation.

When should mutual fund distributors 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