Overview
A European insurance and reinsurance broker, with more than 150 in-house brokers serving over 2,500 corporate clients across four offices, runs its policy administration in Salesforce and keeps its documents in SharePoint. Every policy it writes produces a family of documents: the policy itself, premium invoices, payment notices and mid-term endorsements. With CloudFiles' Document Management, each document is filed automatically into SharePoint against the right policy, Salesforce holds a record of every file, and documents and payment notifications are shared with clients as secure links, all without anyone building folders by hand.
Business challenges
- Documents kept as Salesforce attachments – years of policy paperwork were building up inside the CRM.
- Filing left to individuals – where a document ended up depended on who filed it and how they named the folder.
- Long retention requirements – documents must stay findable long after a policy lapses, for audit and regulatory reasons.
- A CRM blind to its files – a document sitting in SharePoint that Salesforce does not know about is one nobody finds.
Solution
- Automatic policy folders – a SharePoint folder is created for every policy and attached to its Salesforce record.
- Uploads that file themselves – brokers upload from the policy page and the file goes straight into the right folder.
- A Salesforce record for every file – with its link, name, related policy and document type.
- Secure sharing with clients – documents and payment notifications shared as secure links from Salesforce.
Business challenges, in depth
For a broker of this size, growing volume and strict retention requirements exposed three problems at once.
Documents that outlive the policy
Policy paperwork has to be kept for years after a policy lapses, for audits and regulators. Salesforce attachments were never meant to be that long-term home, and the volume kept growing with every new policy.
Filing that has to be predictable
When an auditor asks for a specific endorsement on a specific client's policy from two years ago, the answer cannot depend on whoever happened to file it having named the folder sensibly. The broker needed every document in the same place, every time.
A CRM that knows what exists
The team did not want a document viewer bolted onto Salesforce. It needed Salesforce and SharePoint kept in step, with Salesforce knowing every document, what kind of document it is, and which policy it belongs to.
How CloudFiles solved it
The broker's own Salesforce administrator found CloudFiles on the Salesforce AppExchange and configured it around the way the business already works, reading the policy data already in Salesforce rather than changing it.
A folder path that is its own index
Every policy's folder is built from the facts that identify it: the carrier, the client's tax ID, the policy number and the policy term. Anyone who knows the policy knows exactly where its documents are, and the client's tax ID is validated before a folder is created, so a typing mistake cannot create a folder nobody will find.
Upload once, from the policy
The CloudFiles component on the Salesforce policy page puts each file straight into that policy's SharePoint folder. Brokers never choose a location, so every file lands in the right place.
Every file known to Salesforce
For each file, CloudFiles writes a Salesforce record with its link, file name, related policy and document type (policy, invoice, payment notice, endorsement or other), recognised from the file name. Salesforce always knows what exists and where.
Files added in SharePoint still find their policy
Documents that arrive directly in SharePoint, without passing through Salesforce, are matched back to the right policy using the same identifying details.
Secure sharing in both directions
Insurer documents and payment notifications are shared with clients as secure links generated from Salesforce, and clients can upload files into SharePoint without being given SharePoint access.
Rollout & secondary impact
The setup was configured in-house and works with the broker's existing data model rather than changing it.
Configured by the broker's own administrator
The administrator set up the automation and later extended it to build folders for new enquiries as well, without outside help.
No changes to the core platform
The configuration reads existing policy fields, adding just one field on the policy and one object to track files.
Runs quietly in the background
Almost every action is automatic, so filing happens whether or not anyone remembers to do it.
Impact & results
Filing that used to depend on people now happens on its own, at scale, and every document is findable for as long as it needs to be kept.
63,000+ automated filing actions in a year
Folder creation, record links, sync checks, secure links and file retrievals, all run by the integration with no manual effort.
20,000+ folders created automatically
The full carrier, client, policy and term structure is built for every new policy without anyone creating a folder by hand.
20,000+ folders linked to their Salesforce policy records
Brokers open a policy's documents straight from the policy record, with nothing to search for.
3,100+ secure links shared with clients
Insurer documents and payment notifications go to clients as secure links generated from Salesforce, with no attachments and no manual sharing.
One predictable home for every document
Every policy document sits in the same place for its whole retention period, ready for audits and client requests.