CloudFiles for insurance
Adjusters dig photos, estimates and reports out of Email-to-Case threads, and each claim waits while they sort. CloudFiles files every claim document, sorts what arrives and generates policy documents in Salesforce, so claims settle sooner.
From a buried estimate to a settled claim
Insurers run every policy, claim and policyholder in Salesforce, yet claim documents pile into email threads and policy documents leave as attachments. CloudFiles stores, collects, reads and issues them on the policy and the claim itself.
The manual way
- Claims handlers scroll every reply in an Email-to-Case thread for the estimate or police report a claim needs, while one attachment repeats across five messages. The claim and the claimant both wait until the right file turns up.
- Adjusters ask claimants for photos, repair estimates and receipts over email and copy each attachment onto the claim by hand. Missing pieces arrive days apart, and the claim sits open between them while the claimant calls for updates.
- Customer service teams email policy documents and certificates of insurance to policyholders and brokers as attachments, one request at a time. Once sent, the insurer cannot tell who opened a document or recall an outdated one.
- Underwriters read applications, loss runs and schedules page by page to total prior losses and check them against what the applicant declared. The quote waits on that reading, and a broker kept waiting may place the risk elsewhere.
- Policy administrators copy coverage, limits and dates from the insurance policy into declarations pages, endorsements and certificates, one at a time. A figure copied wrong goes straight to the policyholder and comes back as a correction.
The CloudFiles way
- CloudFiles gathers every claim document into one folder, whichever email it arrived on. Each Email-to-Case attachment is copied to the case folder the moment the email lands, so handlers open one claim folder instead of the whole thread.
- CloudFiles collects every claimant document through one secure upload space on each claim. Claimants send photos, estimates and receipts with no Salesforce account, each file is saved to the claim's folder, and the adjuster sees what is still missing.
- CloudFiles keeps every policy document shared outside the insurer under the insurer's control. Policyholders and brokers open each one through a secure link tied to the insurance policy, each view is logged, and an outdated document's link is switched off.
- CloudFiles reviews every underwriting submission against what the applicant declared before an underwriter starts. Loss runs, applications and schedules sit in one dataset, prior losses are totalled, and any difference goes to review with its source page.
- CloudFiles produces every policy document from the insurance policy itself, so the figures match the record. Declarations pages, endorsements and certificates of insurance are generated from the policy and its coverages, then filed in the policy's folder.
Policy and claim documents, sorted from quote to settlement
Insurers run these six jobs as Salesforce flows on the insurance policy, the claim and the policyholder's account, with CloudFiles carrying the document work in each one.
Policy and claim folder automation
CloudFiles builds a folder structure in the insurer's storage for every policyholder account, insurance policy and claim in Salesforce, with each claim inside its policy, so a policy's whole history sits together.
- When an insurance policy is created, a record-triggered flow builds its folder with the create folder flow action, including sub-folders for claims
- Each claim's folder is nested inside its policy's folder through the get connected folder flow action, so a renewal review sees every past claim
- Underwriters and adjusters open, preview and download files from the CloudFiles widget on each policy or claim page
Email-to-Case claim document filing
CloudFiles files every Email-to-Case attachment into the claim's case folder in the insurer's storage the moment the email arrives, so handlers work from one folder instead of a thread of repeated attachments.
- Email-to-Case creates the case, and a record-triggered flow builds a folder for it in the same moment
- The copy Salesforce files flow action places every attachment from the email message into that folder, so no document stays buried in the thread
- Claim numbers and document types are written to each file as SharePoint metadata, which lets search by resource metadata find any claim document later
Claimant and policyholder document sharing
CloudFiles collects claim documents from claimants through secure upload links or the insurer's Experience Cloud portal, and shares policy documents back through tracked links the insurer controls.
- A data room opens on each claim with file requests for photos, repair estimates and receipts, which claimants fill without a Salesforce login
- Policyholders signed in to the insurer's Experience Cloud portal open their policy and claim folders through the share with community user flow action
- Every view of a shared declarations page is logged on the policy, and the update link settings flow action switches off a replaced document's link
First notice of loss document intake
CloudFiles automates first notice of loss document intake in Salesforce. Every packet is split, each estimate and report is matched to its claim, and the loss details are filled in for an adjuster to confirm.
- Combined PDFs from agents and claimants are separated into estimates, police reports and invoices by the split document using AI flow action
- A CloudFiles Document AI workflow classifies each report, matches it to the claim by number or policyholder name, and files it in the claim folder
- The loss date and estimated amount land on the claim through the document mapper flow action, held for the adjuster's review
Underwriting submission review
CloudFiles reviews underwriting submissions in Salesforce. Applications, loss runs and schedules are reviewed as one submission, prior losses are totalled, and gaps from the application are flagged before quoting.
- The create dataset flow action groups a submission's application, loss runs and schedules, so they are queried together rather than file by file
- Underwriters ask for total incurred losses, open claims or the largest single loss across every loss run at once
- Any figure that disagrees with the application waits for an underwriter, shown next to the source page, until it is approved for the opportunity
Insurance policy document generation
CloudFiles generates declarations pages, endorsements, certificates and renewal notices from the insurance policy in Salesforce, and sends claim release forms for e-signature with the signed copy filed on the claim.
- The get doc-gen templates flow action selects the template for each policy type, so auto, home and life policies share one flow
- Coverage, limits and effective dates come straight from the insurance policy and its coverage records into every document
- Renewal notices for the whole book come from one scheduled run of the generate document (batch) flow action, each filed in its policy folder
Key documents we handle for insurance
Six of the documents insurers handle most. CloudFiles takes in, reads and issues the rest of a carrier's policy and claim paperwork in Salesforce too.
First notice of loss reports
The first report of a loss from a claimant or agent, which opens the claim and sets its loss date and loss type on the record.
Repair estimates and invoices
Costs from repair shops and contractors, gathered by file request from claimants and kept on the claim beside the adjuster's figures.
Police and adjuster reports
Third-party and field reports that support a claim, filed against the claim number and easy to find later in the claim folder.
Loss runs and applications
The prior loss history and declared exposures behind a submission, grouped together so underwriting starts from totals rather than pages.
Declarations pages and endorsements
The policy's coverage summary and its changes, generated from the insurance policy record whenever coverage is issued or amended.
Certificates of insurance
Proof of coverage for policyholders and certificate holders, produced from policy data on request and shared through a tracked link.
Stay industry compliant
CloudFiles is independently audited for SOC 2 Type II, certified to ISO 27001, and compliant with HIPAA and GDPR. Data residency is supported in the US, EU, UK and AU. Your files stay in your own storage. CloudFiles never re-hosts them, and they are not used to train our AI models.
Frequently asked questions
CloudFiles keeps each claim's folder inside its insurance policy's folder in the insurer's storage, building both as the records are created in Salesforce. Adjusters and underwriters open a policy's whole claim history from the policy page. Admins build it with the create folder flow action, run by record-triggered flows on the policy and the claim.
Yes. CloudFiles stores claim photos and policy documents in SharePoint, Google Drive, Azure Blob, Amazon S3 and other storage an insurer uses, and every folder opens from its insurance policy or claim. Anything attached in Salesforce is copied over to the matching folder, so adjusters work from a single home for each document, with the insurer's storage permissions kept.
CloudFiles copies each Email-to-Case attachment to the case's folder in the insurer's storage as each claim email arrives. Handlers find estimates, photos and police reports in one folder on the case instead of scrolling the email thread. Admins set it up with a record-triggered flow on the email message that runs the copy Salesforce files flow action.
Claimants upload photos, repair estimates and receipts to a Salesforce claim using a secure link from CloudFiles; claimants need no Salesforce account. Each claim gets an upload space listing the documents the adjuster needs, and each file is stored in the claim's folder in the insurer's storage. When email verification is switched on, the claim shows which claimant sent each file.
CloudFiles shares declarations pages, endorsements and certificates of insurance from the insurance policy as secure links instead of attachments. A link can be protected with email verification and a password, can limit access to approved domains, and the insurer can switch it off when a document is replaced. Every view and download is recorded on the policy.
Yes. CloudFiles groups every application, loss run and schedule in an insurance submission into one dataset in Salesforce, so an underwriter can ask for total incurred losses or the count of open claims across the whole submission. Answers are written to the opportunity, and an underwriter reviews any mismatch with the application next to its original page.
Yes. CloudFiles automates claims intake end to end in Salesforce. Each first notice of loss packet is split into documents, and a CloudFiles Document AI workflow identifies every estimate and report, finds the matching claim by number or policyholder name, fills in the loss date and estimated amount, and routes any mismatch to an adjuster. Every run is audited.
CloudFiles builds declarations pages and endorsements from each insurance policy in Salesforce and files every one in the policy's folder. The template for the policy type fills with coverage, limits and effective dates from the policy and its coverage records, and an underwriter generates it from the policy with one click, while a record-triggered flow can issue it whenever coverage changes.
Yes. CloudFiles produces renewal notices for every insurance policy in Salesforce from one scheduled flow, using each policy's renewal date, coverage and premium from the record. Each notice is saved to its policy's folder and can be shared with the policyholder through a tracked link. Admins schedule it with the generate document (batch) flow action.
CloudFiles works on the insurance policy, claim and producer objects that Financial Services Cloud provides, and on custom objects an insurer adds. Insurers add CloudFiles from AppExchange, where it is listed as a managed package, add CloudFiles document actions to the flows they already run, and see each policy's and claim's files right on the record.
Book your personalized demo
Bring a policy and a claim from your own org, and see CloudFiles file, read and produce their documents in Salesforce.