SocialCustomerServiceSettings in SFDX

Architectural Overview#

SocialCustomerServiceSettings manages the platform-level configuration for Social Customer Service, Salesforce’s capability for turning customer social media interactions (such as messages, mentions, and posts on X/Twitter, Facebook, YouTube, and Instagram) into actionable CRM Case and SocialPost records.

In modern omnichannel contact centers, social care operations must balance rapid SLA responses with strict brand protection. Architecturally, SocialCustomerServiceSettings controls inbound case generation rules, case subject line formats, social persona association, and whether outgoing social responses from support agents must pass through an automated ApprovalProcess before being published to external networks.

Directory and File Conventions#

In SFDX source format, SocialCustomerServiceSettings is stored in the settings directory under the filename SocialCustomerService.settings-meta.xml.

Key Metadata Fields#

The SocialCustomerServiceSettings schema defines the operational rules governing social case generation:

Declarative XML and Package Manifest Examples#

Below is an enterprise XML configuration enforcing social post approvals and history tracking:

<?xml version="1.0" encoding="UTF-8"?>
<SocialCustomerServiceSettings xmlns="http://soap.sforce.com/2006/04/metadata">
    <caseSubjectOption>SocialPostContent</caseSubjectOption>
    <enableSocialApprovals>true</enableSocialApprovals>
    <enableSocialCustomerService>true</enableSocialCustomerService>
    <enableSocialPersonaHistoryTracking>true</enableSocialPersonaHistoryTracking>
    <enableSocialPostHistoryTracking>true</enableSocialPostHistoryTracking>
</SocialCustomerServiceSettings>

Manifest Definition (package.xml)#

<?xml version="1.0" encoding="UTF-8"?>
<Package xmlns="http://soap.sforce.com/2006/04/metadata">
    <types>
        <members>SocialCustomerService</members>
        <name>Settings</name>
    </types>
    <version>68.0</version>
</Package>

Retrieval and Deployment#

To retrieve or deploy SocialCustomerServiceSettings using the Salesforce CLI:

# Retrieve Social Customer Service settings
sf project retrieve start --metadata "Settings:SocialCustomerService"

# Deploy Social Customer Service settings
sf project deploy start --metadata "Settings:SocialCustomerService"

Senior Architect Deployment Best Practices and Gotchas#

1. Licensing and Feature Enablement: Target orgs must have Service Cloud entitlements and social customer service features enabled. Verify scratch org feature definitions include ServiceCloud before deployment.
2. Custom Apex Social Handler: If implementing a custom Apex social intake class (Social.InboundSocialPostHandler), ensure the Apex class is deployed alongside this setting to prevent case generation failures.
3. Approval Process Coupling: When setting enableSocialApprovals to true, ensure that an active ApprovalProcess on SocialPost is deployed; otherwise, agents will encounter runtime errors when submitting responses.
4. Data Volume and Retention: High-frequency social campaigns can generate millions of SocialPost records rapidly. Architect an automated archival or purge strategy using Big Objects or Scheduled Apex to manage storage consumption.

Frequently asked questions

What is the function of SocialCustomerServiceSettings?

It manages automated case generation from social posts, case subject formatting, social persona linking, and social response approvals.

Where is SocialCustomerServiceSettings stored in SFDX format?

In force-app/main/default/settings/SocialCustomerService.settings-meta.xml under the Settings:SocialCustomerService component.

Can social replies be put through an approval process before posting?

Yes, enabling social approvals requires agent responses to pass through an approval workflow before publishing to social networks.

What dependencies exist when deploying SocialCustomerServiceSettings?

Service Cloud licensing, the Case standard object, and Social Post object availability must be active in the target org.