With Outcome-Based Contracts, service providers can provide their customers with an easy
way to assess the compliance of a service contract by letting them track and measure service
outcomes. Compliant service contracts ensure high quality of service and customer
success.
Required Editions
Available in: both Salesforce Classic (not available in all orgs) and Lightning
Experience
The Field Service core features, managed package, and mobile app are available in
Enterprise, Unlimited, and Developer Editions.
Outcome-based contracts are result-based and focus on the outputs, quality, and outcomes of a
provided service.
Service providers can provide their customers with measurable business KPIs to track and
assess the quality of service they’re getting.
For example, letting customers track the charging speed of an electric vehicle ensures the
on-time replacement of its battery.
Tying the quality of service to the achievement of specific, measurable performance standards
and requirements also helps customers to better evaluate payment, contract extensions, or
contract renewals.
You can evaluate the compliance of a service contract by creating contract line outcomes that
capture data in an automated process that runs according to the criteria, frequency, and
calculation method that you define.
When a service contract starts, the automated process records data and evaluates the
compliance of the contract. The results that show whether the contract is compliant appear in
the Compliance Status field of the contract line outcome.
Set Up Outcome-Based Contracts Assign users permissions to manage contract line outcomes for Outcome-Based Contracts and create recordset filter criteria that allow you to define the criteria to evaluate contract compliance.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.