Entitlement Contact
An Entitlement Contact is the junction record linking a specific Contact to an Entitlement, restricting which individual people at a customer Account can use that Entitlement when opening Cases.
Definition
An Entitlement Contact is the junction record linking a specific Contact to an Entitlement, restricting which individual people at a customer Account can use that Entitlement when opening Cases. The standard model is: an Entitlement belongs to an Account; any Contact on that Account can theoretically reference it. With Entitlement Contacts active, only Contacts explicitly added to the Entitlement Contact list are eligible to use it. This is how enterprise service contracts enforce named-user support: the contract covers 5 named technical contacts, not the entire 200-person Account.
The Entitlement Contact list lives as a related list on the Entitlement record. Adding a Contact creates an EntitlementContact junction record. The Case form filters the Entitlement picklist based on the Contact selected: pick the customer's main Contact and only the Entitlements they are named on appear. Without Entitlement Contacts, every Account Contact can use every Account Entitlement. Most B2B service teams enable this restriction; B2C and small-business deployments often skip it because the per-contact precision adds configuration burden without operational value.
How Entitlement Contacts restrict SLA access to named individuals on a customer Account
The named-user support pattern
Enterprise service contracts commonly limit who can log support tickets. A 50,000-employee customer with a Gold support contract typically negotiates 3 to 5 named technical contacts who can open cases. Other employees route through those named contacts or via a community portal. Entitlement Contacts is the Salesforce feature that enforces this contractual model: only Contacts on the Entitlement Contact list can use the Entitlement when their Cases open.
The EntitlementContact junction object
Behind the scenes, EntitlementContact is a standard junction object with a lookup to Entitlement and a lookup to Contact, plus Start Date and End Date for time-bound named-contact assignments. A senior engineer who leaves the customer can have their Entitlement Contact End Dated rather than deleted, preserving the historical record. Reports on EntitlementContact show who held named-contact status when.
How Case forms filter Entitlements
When a Case is created, the Entitlement picklist filters to Entitlements that match the case''s Contact (and Account, and Asset where applicable). If Entitlement Contacts are configured, the filter further restricts to Entitlements where the Contact appears on the Entitlement Contact list with an active date range. This is what enforces named-user support operationally; agents picking a customer Contact who is not named on the Entitlement see no eligible Entitlements and either log the case without one or escalate to a manager.
When to enable Entitlement Contacts
Enable when the business sells named-user support tiers and needs to enforce them. Skip when every Account Contact gets the same support level. Mid-market B2B is the sweet spot for the feature; enterprise B2B almost always needs it; B2C deployments rarely benefit. Adding the feature later is straightforward but requires populating the Entitlement Contact list for every existing Entitlement, which on large orgs is a meaningful data project.
Start Date, End Date, and contact rotation
Each Entitlement Contact has Start Date and End Date fields. End Dating a contact removes their eligibility going forward without deleting the record. This is the right pattern when a customer rotates their named technical contacts: end-date the departing engineer, add the replacement. Cases open before the rotation keep their original Entitlement reference; cases after the rotation pick from the new active named contacts.
Communities and customer-facing portals
On Experience Cloud sites where customers self-serve Cases, Entitlement Contacts restrict the customer-side experience similarly. A Contact logging into the community portal sees only the Entitlements they are named on; case forms surface only those Entitlements. This is what makes self-service contractually safe; customers do not accidentally consume Entitlements they were not granted access to.
Reporting and audit considerations
Standard reports on EntitlementContact let support operations monitor named-user lists per customer. Build reports of Entitlement Contacts with End Date in the past versus active; identify customers who have not rotated to current named contacts. For audit, the date-tracked junction provides a clear historical record of who held named-contact privileges when, which is useful during contract renegotiations or compliance reviews.
Configuring Entitlement Contacts on a customer Entitlement
Setup is two phases: enable the Entitlement Contacts feature in Setup, then add Contacts to the Entitlement Contact list on each Entitlement that should restrict by named user.
- Enable Entitlement Contacts
Setup, Service Setup, Entitlement Management, Entitlement Settings. Check Enable Entitlement Versioning and Verify Entitlement Contacts. The Entitlement Contact related list appears on the Entitlement record layout.
- Add Contacts to an Entitlement
Open the Entitlement record. Scroll to the Entitlement Contacts related list. Click New. Pick the Contact, set Start Date (when their named-user status begins) and End Date (optional; blank means indefinite).
- Configure Case form filtering
Verify the Case page layout includes the Contact lookup, the Entitlement lookup, and the Verify Entitlement Contact behaviour. The platform handles the filtering automatically; admins typically do not need additional configuration.
- Educate the support team
Agents and managers need to understand that an unnamed Contact has no Entitlement, even if the Account has one. Document the named-user policy and the escalation path when an unnamed Contact opens a case.
- Build the rotation workflow
When customers change their named contacts, end-date the departing contact and add the replacement. Build a flow or scheduled job that flags Entitlements with all-expired contacts; these need attention before the next case opens.
Org-wide toggle that enforces the named-user check. Off by default; turning on changes Case form behaviour across the org.
When the Contact''s named-user status begins. Defaults to today if unset.
Optional. When the named-user status expires. Blank means indefinite. Use End Date for rotation rather than deleting records.
No platform-enforced cap. Contract size dictates it: 3 to 5 for Bronze support, 10 to 20 for Premium. Sales operations sets the policy, not Salesforce.
- Enabling Verify Entitlement Contacts retroactively means every existing Entitlement needs Contacts populated. Plan a data project for large orgs.
- Contacts not on the Entitlement Contact list have no Entitlement match. Cases opened by them have a blank Entitlement field unless overridden.
- End Dating, not deleting, is the rotation pattern. Deleted EntitlementContact records lose audit history.
- The feature applies across both internal Case creation and Experience Cloud self-service portals. Customer-facing impact needs communication.
- Reports filtered to Entitlement Contacts can miss Cases without Entitlements. Build separate compliance reports for unentitled Cases.
Trust & references
Cross-checked against the following references.
- Entitlement Contacts OverviewSalesforce Help
- Set Up Entitlement ManagementSalesforce Help
Straight from the source - Salesforce's reference material on Entitlement Contact.
- Add Entitlement ContactsSalesforce Help
- EntitlementContact Object ReferenceSalesforce Developer Docs
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is an Entitlement Contact?
Q2. Why use Entitlement Contacts?
Q3. Where do Entitlement Contacts fit in Service Cloud?
Discussion
Loading discussion…