Salesforce Dictionary - Free Salesforce GlossarySalesforce Dictionary
Full Complaint Management entry
How-to guide

How to roll out Complaint Management

Implementing Complaint Management is more about process and compliance configuration than clicking through Setup. The technical install is straightforward; the discipline of categorization, timers, and exports is what makes it actually work.

By Dipojjal Chakrabarti · Founder & Editor, Salesforce DictionaryLast updated May 20, 2026

Implementing Complaint Management is more about process and compliance configuration than clicking through Setup. The technical install is straightforward; the discipline of categorization, timers, and exports is what makes it actually work.

  1. Install Financial Services Cloud

    Complaint Management is a feature inside FSC. Install through the AppExchange managed package, assign Financial Services Cloud licenses to the users who need it, and run the post-install setup wizard.

  2. Configure the Complaint object

    From Setup, Object Manager, Complaint. Adjust the picklist values for Category, Sub-Category, Severity, and Regulatory Classification to match the regulator schema you are reporting against (CFPB categories for US consumer finance, FCA categories for UK).

  3. Set up the intake-to-Complaint promotion flow

    Build a Flow on Case that creates a Complaint record when Case Reason equals Complaint, or when an email keyword triggers it. Map the originating Case to the new Complaint through a lookup field.

  4. Configure compliance timers

    Use Entitlement Processes or a scheduled Flow to count down against the regulator-mandated deadline from the Date Received field. Escalate to a supervisor at 75 percent and the compliance team at 90 percent.

  5. Build the regulatory export report

    Create a custom report type that joins Complaint, Investigation, and Resolution. Group by regulator category. Schedule the report to email the compliance team weekly so the regulator submission file is always pre-built.

  6. Enable Field Audit Trail

    From Setup, search for Field Audit Trail, enable it for the Complaint, Investigation, and Resolution objects, and configure the retention policy for 10 years (or whatever your regulator requires).

Gotchas
  • Complaint Management is licensed per FSC user. Service Cloud only orgs cannot use the standard Complaint object without a license uplift.
  • Field History on the standard Complaint object retains 18 months by default. Enable Field Audit Trail before go-live or you will lose history you may need for an audit.
  • Categorization drift kills regulatory reports. If reps invent their own sub-categories, the quarterly summary stops matching the regulator schema.
  • Most regulators require evidence of the resolution offered to the customer, not just an internal note. Attach the customer-facing letter or transcript to the Resolution record.
  • Reopening a closed Complaint resets some timers but not others. Map this out before go-live or you will under-report time-to-resolution.

See the full Complaint Management entry

Complaint Management includes the definition, worked example, deep dive, related terms, and a quiz.