Where does the CRM sit next to the core system?
The fund administration or policy administration system is the record for balances, contributions, policies, premiums and claims. It must stay that way. The CRM holds the relationship around it: who the member is, how they prefer to be contacted, what they have asked, which communications they have received and what life events they have told you about.
The integration is the design decision that matters most. Decide which fields the CRM may read, which it may never hold, and how quickly status changes reach the member record. Many organisations choose to show a member's segment or status in the CRM rather than the underlying balance. See our integration approach.
How do you protect financial data?
Financial data is sensitive in every market, and financial regulators add their own expectations. The Monetary Authority of Singapore, for example, issues outsourcing guidelines that it says provide “expanded guidance to the industry on prudent risk management practices for outsourcing, including cloud services” (MAS). Other regulators in the region publish their own technology and outsourcing requirements. Involve risk, compliance and information security from the first workshop, not at sign-off.
On the platform side, HubSpot offers Sensitive Data properties with a financial data category on Enterprise subscriptions, with stricter Highly Sensitive Data for the most critical values; HubSpot notes that once enabled, the setting cannot be turned off (HubSpot Knowledge Base). HubSpot hosts data in the EU, Canada, Australia and the United States (HubSpot), so a cross-border transfer and an outsourcing assessment are usually part of the project. Our data protection answer covers the main privacy laws.
Where can AI agents help, and where must they stop?
Members and policyholders ask many general questions that an agent can answer well from approved content:
- How to update contact details or nominate a beneficiary.
- Which forms are needed for a withdrawal or a claim, and where to find them.
- Office hours, branch locations and how to reach an adviser.
- What a published product feature or term means, in plain language.
Agents must stop before anything that could be read as advice: whether to switch funds, change contributions, buy or cancel cover, or how a rule applies to a member's own circumstances. Advice is regulated across the region, and an agent is not licensed to give it. Disputes, complaints, claims decisions and vulnerable customers go to people.
HubSpot's Customer Agent supports custom handoff triggers alongside its defaults, with live or asynchronous handoff (HubSpot Knowledge Base). We write the trigger list with compliance, test it against real historical questions and review handoff reasons weekly.
How do you make engagement relevant?
Relevance comes from segments built on life stage and behaviour, not product alone. A member in their first job, a member who has just changed employer and a member nearing retirement need different messages. So does a policyholder whose renewal is close and one who has just made a claim.
HubSpot's customer success workspace lets teams “build unique customer health scores” (HubSpot). For funds and insurers we adapt that idea into engagement scores: logins, opened statements, service contacts and responses to campaigns. The score tells the team who is drifting before renewal or retirement arrives. Where advisers or agents serve members, HubSpot's partitioning can limit records and inboxes to the right teams (HubSpot Knowledge Base).
How do you handle consent and preferences?
Funds and insurers send two kinds of communication: those they must send, such as statements and policy notices, and those they choose to send, such as education, campaigns and offers. Members need to be able to tell them apart, and the CRM needs to record the difference.
We keep a clear set of subscription types on the member record: service and regulatory messages, general education, product marketing and partner offers, each with the date, the source and the channel of consent. Preferences are easy to change, and every campaign checks them before it sends.
Channel preference matters as much as consent. Some members want everything by email, others only read messages on WhatsApp, and some prefer a call. Recording that preference, and honouring it, does more for engagement than any single campaign.
What should a fund or insurer measure?
- Time from application to an active, onboarded member.
- Digital activation among new members.
- Engagement score distribution, and how it moves after campaigns.
- Service resolution time, and handoff reasons on agent conversations.
- Retention at renewal, or engagement in the years before retirement.
Where to start
Bring risk and compliance in first and agree what the CRM may hold. Then design the member record and the integration with the core system, build two or three life stage segments and run one onboarding journey. Add an agent for general service questions once the handoff rules are signed off.
