Case documents in Salesforce

CloudFiles for social services

Intake coordinators chase IDs by text while referrals sit in inboxes, so clients wait to start services. CloudFiles keeps each case document on its Salesforce record, with intake papers collected by link and care plans sent to sign.

Illustration of social services case work: a phone sending an ID card by secure link, a client case record on a Salesforce screen and a signed care plan on a clipboard
Trusted by Salesforce teams across industries
Case documents, before and after

Client files complete before services start

Social services teams run clients, programs and cases in Salesforce, but intake papers and referrals arrive by text, fax and email. CloudFiles collects them by secure link and from Email-to-Case, and files each one on the case.

The manual way

  • Intake coordinators collect a client's ID, proof of address and income by text and email. Papers end up on personal phones, and services wait on the last document.
  • Referrals and health plan authorizations arrive by email. Case managers save each one to a desktop, so the case file is incomplete when a supervisor needs it.
  • Provider invoices arrive as PDFs and scans. Billing staff key every line into Salesforce by hand, and payments wait while each total is checked against the plan.
  • Case managers rebuild each care plan and consent form in Word from the case. Signatures are chased in person, and the signed copy sits in a paper file.

The CloudFiles way

  • CloudFiles sends each client one secure link for every intake document. Clients upload from a phone with no login, and each file lands in the case's intake folder.
  • CloudFiles copies attachments sent to Email-to-Case into each case's own folder. Referrals open from the case record, and nothing waits on someone's desktop.
  • CloudFiles maps each invoice and its line items onto your Salesforce records. Billing staff check each line on a review screen before anything is saved.
  • CloudFiles generates each care plan and consent form from the case with your own template. Clients sign electronically, and a flow marks the case signed when every signature is in.
Social services use cases in Salesforce

From the first intake form to a signed care plan

Six jobs social services teams automate on the client, program and case records that they already use.

Case folder automation

Every case gets its own folder with the same subfolders, so case managers find a file in the same place every time.

  • The folder is created when a case is opened
  • Subfolders cover intake, consents, referrals and service records
  • Each case folder sits inside its client's folder

Email-to-Case attachment filing

Referrals and authorizations sent to Email-to-Case are copied into the case's folder in your storage.

  • Each attachment is copied when the email arrives
  • A case manager opens the referral from the case record
  • Files stay in the organization's storage, not in personal inboxes

Client intake document collection

Clients send their ID, proof of address and income documents through one secure link.

  • One link asks for every intake document still missing
  • Clients upload from a phone, with no login
  • Each document goes to the case's intake subfolder

Intake packet sorting

CloudFiles separates an intake packet scanned as one PDF into its individual documents and names each one.

  • Every document lands in the right intake subfolder for staff to review
  • Staff see which required intake documents are missing
  • The client gets a link to send what is still needed

Provider invoice processing

Provider invoices are mapped onto your invoice and line item records in Salesforce and held for a person to approve.

  • Invoices sent to Email-to-Case are picked up as they arrive
  • Each line is held for review before it is saved
  • Approved lines are saved as line items on the invoice record

Care plan and consent form generation

Care plans and consent forms are built from the case and sent for e-signature in signing order.

  • Your own Word template is filled with the client's goals and services
  • The client and case manager sign in order
  • A flow marks the case signed when signing completes
Document types

Key documents we handle for social services

The files a case team handles for every client it serves. Other program and case paperwork is handled the same way.

Client IDs

Photo IDs collected by upload link at intake and kept in the case's intake folder.

Proof of address

Utility bills and leases that confirm where a client lives, collected with the ID at intake.

Income documents

Pay stubs, benefit letters and bank statements that show eligibility, filed beside the client's intake forms.

Consent and release forms

Consents and releases of information generated from the case and signed by the client before information is shared.

Referrals and authorizations

Referrals and health plan authorizations sent by email, copied into the case's folder as they arrive.

Care plans and service agreements

Plans and agreements generated from the case, with the client's goals and services filled in from Salesforce.

Security & compliance

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.

SOC 2
Type II
HIPAA
Compliant
ISO 27001
Certified
GDPR
Compliant

Frequently asked questions

Yes. CloudFiles installs from AppExchange and works on any Salesforce object, standard or custom, through Salesforce Flow, so case, program and client records on Nonprofit Cloud or the Nonprofit Success Pack work as they are.

Yes. Case files can live in SharePoint, Google Drive, Azure Blob, Amazon S3 or other storage you run, opened from Salesforce through CloudFiles. Each case's documents sit in your own storage and open from the case record, so case managers never switch systems to find a file.

CloudFiles sends the client one secure upload link from the case, listing every intake document still needed. The client uploads from a phone or computer with no Salesforce account, and every file goes to the case's intake folder instead of a text thread.

CloudFiles copies each attachment sent to Email-to-Case into that case's folder in your storage as the email arrives. Case managers open referrals and authorizations from the case record. Admins set this up with the copy Salesforce files flow action in a record-triggered flow.

CloudFiles splits the scanned intake packet into separate documents, such as the ID, proof of address and income letters, for staff to check. Staff find each one named in the intake subfolder, and the client is sent a link for anything missing.

Yes. CloudFiles maps each provider invoice and its line items onto your invoice records in Salesforce, and holds them on a review screen before anything is saved. Billing staff approve the lines, and admins choose which checks wait for a person.

CloudFiles generates the care plan from the case using your own Word or PDF template, filled with the client's goals, services and dates from Salesforce. The plan goes out for e-signature with the client and case manager in signing order, and a flow marks the case signed once everyone has signed.

A case manager shares the case folder from the case record through a secure link limited to the partner's email address. Downloads can be blocked and a password added, and the person who created the link is told when it is opened, as often as your admin sets.

Bring one intake packet to a demo

Bring an intake packet and a care plan template with names removed. We will show both on a case in Salesforce, filed and ready to sign.