Define Support Commitment

Create and Configure Support Commitments

Overview

Support Commitments define the scope, duration, and coverage of support services for products. Within Service Assurance Hub, support commitments are tied to specific products and include detailed assurance scopes that outline which components, rework codes, and services are covered.

Key Concept: Support commitments can include multiple assurance scopes, each specifying coverage percentages for parts and labor, applicable solution areas, and project components.

Phase 1: Access Support Commitments

Step 1. Navigate to the Service Assurance Hub application in Salesforce.

Step 2. Locate and click the 'Support Commitments/SLA Rules' tab.

Support Commitments/SLA Rules Tab Location

Phase 2: Create a New Support Commitment

To create a support commitment, complete the following required fields:

FieldDescription
ProductSelect the product for which you want to create this commitment (mandatory)
NameUnique identifier for the support commitment
Commitment TypeSet to 'Product' for product-based commitments
DescriptionProvide detailed information about the commitment terms and scope

Support Commitment Basic Information Form

Phase 3: Set Commitment Duration and Start Date

Configure the temporal aspects of your support commitment:

FieldDescription
Commitment Start Date TypeSelect the trigger date: Installed Date, Purchased Date, Registered Date, etc.
Commitment Duration (Days)Enter the number of days this commitment will remain active

Commitment Duration and Start Date Configuration

Phase 4: Activate and Configure Provider

Complete the commitment configuration:

1. Set the 'Commitment Status' to Active to enable this commitment.

2. Select the 'Commitment Provider' - this should be the account of your organization in Salesforce.

3. Set the 'Commitment Creation Date' to today's date or the appropriate start date.

Commitment Status and Provider Configuration

Completed Commitment Configuration

Best Practice: Always activate support commitments and verify the commitment provider account is correctly set before saving.

Phase 5: Add Assurance Scopes

Support commitments consist of one or more assurance scopes, each defining specific coverage areas. To add an assurance scope:

1. Locate the 'Assurance Scopes' related list on your support commitment record.

2. Click the New button to create a new assurance scope.

Assurance Scopes Related List

Phase 6: Configure Assurance Scope Details

Complete the assurance scope form with the following information:

FieldDescription
Scope NameUnique name for this assurance scope
Scope DescriptionDetailed explanation of what this scope covers
Scope Duration (Days)Number of days this scope is valid
Parts % CoveredPercentage of parts costs covered by this commitment (0-100%)
Labor % CoveredPercentage of labor costs covered by this commitment (0-100%)
Solution AreaSelect the applicable solution area
Deliverable TypeSelect the applicable deliverable type

Assurance Scope Basic Configuration

Phase 7: Add Scope Details (Rework Codes & Components)

After completing the basic scope information, add the specific rework codes and project components that are included in this scope:

1. Click Add/Edit Details to configure scope details.

Add/Edit Details Button

2. Select a 'Solution Area' and 'Deliverable Type' to populate available options.

3. The system will automatically load:

  1. Available Rework Codes related to the selected solution area and deliverable type
  2. Available Project Components for those selections

4. Select the appropriate Rework Codes to include in this scope.

5. Select the appropriate Project Components to include in this scope.

Rework Code Selection

Project Component Selection

Important: Ensure all relevant rework codes and components are selected, as these define the actual services covered under the commitment.

Phase 8: Review Scope Details

After adding rework codes and project components, review the complete scope details:

Complete Scope Details Record

Success Checkpoint: Verify that all scope details are correctly recorded before saving. The commitment is now ready for use.

Key Takeaways

  1. Support commitments are product-based and define the scope of support services
  2. Each commitment must have at least one active assurance scope
  3. Assurance scopes define coverage percentages for parts and labor
  4. Rework codes and project components are attached to scopes to specify deliverables
  5. Commitment duration is calculated from a start date type (Installed, Purchased, Registered, etc.)
  6. Always activate commitments and verify all scope details before deployment


View this article in the article tree to explore related topics