You can now configure coaching forms to capture information that aligns with your organization’s coaching workflow. This update introduces Coaching as a new asset type in the Custom Fields editor, enabling you to create and manage fields specifically for coaching sessions.

With flexible customization across the coaching lifecycle, you can ensure that each stage captures the right information in a structured and meaningful way.

Key Capabilities

• Coaching as an asset type: Create custom fields specifically for coaching sessions by selecting Coaching as the asset type.
• Lifecycle-based customization: Configure fields for different coaching stages such as Schedule, Ongoing, Review, or Completed.
• Flexible field configuration: Add, remove, modify, and reorder fields to match your workflow.

• Advanced visibility control: Control when and for whom fields appear using:

  • Value-based visibility
  • User or user group targeting
  • Conditional logic based on other fields

• Standardized data capture: Ensure consistent and structured coaching data across sessions.

Create Coaching Custom Field

Follow these steps to create and configure a custom field for coaching:

• Navigate to the Custom Fields record manager from the Sprinklr launchpad.

• Click the Add Custom Field button in the top right corner to create a new custom field.

• Configure the Input Fields as explained in the sections below.

• Once done, click Save to save your Coaching Custom Field.

​

The configuration screen divided into the following sections:

Configure Basic Information

​

​

Provide the basic details for your custom field:

• Field Type: Determines the type of input the field will accept. Select the required option from the dropdown.

• Name: Defines the label of the field as it appears to end users.

• Enable for Platform Concierge: Allows AI-powered features to use this field’s description to generate more relevant outputs. When enabled, the system uses the Description field as context input for AI-driven recommendations or automation.

• Description: Provides additional context about the custom field.

• Asset Types: Select Coaching from the dropdown. It specifies where this custom field will be applied.

• Placeholder: Displays a hint inside the input field before a value is selected.

• Help Text: Displays additional guidance to users, typically below or next to the field.

• Category: Groups the custom field under a specific category.

​

Configure Set Values

This section controls both the available options in the custom field and when those options appear during the coaching workflow.

Set values

Use this section to define the complete list of values for the field.

• Type: Select how values are added. Manual allows you to define and manage values directly.

• Values: Add all possible options for the field (for example, Option 1, Option 2, Option 3). This list represents the full set of values that the field can use across all scenarios.

• Default Value: Select the value that is automatically applied when a new record is created. This helps standardize data entry and reduces manual effort.

• Sort Order: Control how values appear in the dropdown. As displayed preserves the order configured in this section.

These values act as the source list for the field. The system will only display values defined here.

Map with controlling field values

Use this section to make the field context-aware by linking it to another field.

• Controlling field: Select the field that determines when specific values should appear. In this configuration, the controlling field is Coaching Session Stage.

• Controlling field value mapping: Define how values change based on the selected stage.

  
  Example behavior:

  • When the stage is Schedule, the field shows Option 1, Option 2, and Option 3.
  • When the stage is Review (Mark as Complete), the field shows a defined set of values. These can be the same or different from other stages.

The system evaluates the selected stage and displays only the mapped values. As the stage changes, the available options update automatically.

• + Add controlling field: Extend the configuration to include additional controlling fields for more complex conditions.

How it works together

The Set Values section defines all possible options.

The mapping configuration filters those options based on the coaching session stage.

This ensures that:

• Users see only relevant values at each stage.

• Data entry remains consistent and accurate.

• A single field can serve multiple purposes across the coaching lifecycle without duplication.

Visibility Control

The Visibility Control section determines who can see the custom field and its values, and under what conditions the field appears in the coaching workflow. This section operates at two levels: overall field visibility and conditional (rule-based) visibility.

Space Visbility

This section controls where the custom field is available across the platform.

• Global level field vs workspace level field

  Defines the scope of the field. A global field is available across all workspaces, while a workspace-level field is restricted to specific workspaces.

• Visible in all workspaces

  When enabled, the field is accessible across all workspaces.

• Workspaces / Workspace Groups

  Restrict visibility to selected workspaces or workspace groups if needed.

• Users / User Groups

  Limit visibility to specific users or user groups. This ensures that the field is available only in the relevant operational contexts.

Advanced Visibility Filters

This section allows you to define conditional visibility rules based on other fields.

• Criteria: Set the logic that determines when the field should appear. In this configuration, visibility is based on another custom field and its values.

• Condition: Define how multiple conditions are evaluated (for example, AND).

• Custom Field: Select the controlling field. In this case, select Coaching Session Stage.

• Custom field Values: Specify the values that trigger visibility. The field is visible when the coaching session stage matches values such as: Schedule, Ongoing, Log, Suggest, Completed, Review (Mark as Complete)

​

The system evaluates the selected stage and displays the field only when the condition is met. If the condition is not satisfied, the field remains hidden.

Custom Field “Value” Visibility Control

When this setting is enabled, you can restrict the visibility of specific field values to selected users or user groups.

• Value Visibility Criteria: Define which values are visible to which users.

  The system evaluates the selected users or user groups and displays only the mapped values when those users access the field. Other users will not see these values in the dropdown.

• Add Value Visibility Criteria: Create additional rules to handle different user groups and value combinations. This capability helps tailor the experience so that users only see values relevant to their roles or responsibilities.

How it works together

The configuration ensures that visibility is controlled at multiple levels:

• The value-level control restricts what options users can select.

• The field-level control determines who can access the field.

• The advanced filters determine when the field appears based on workflow conditions.

Together, these controls enable a highly targeted and context-aware experience, ensuring that users see only the fields and values that are relevant to their role and the current coaching stage.

Asset Level Configuration

The Asset Level Configuration section defines how the custom field is applied to specific asset types and how it behaves within those assets. In this context, the configuration is scoped to Coaching, which means the field will only be available within coaching-related workflows.

Asset Types: Specifies where the custom field will be used. In this configuration, select Coaching. The custom field is available only within coaching records and does not appear in other asset types.

Additional Settings

• Mark as a mandatory field: Ensures that users must provide a value before saving or progressing in a coaching record. This helps enforce required data capture.

• Include as a part of filtering/faceting: Adds this field to filtering and search options within the platform. Users can use this field to refine views, reports, or lists.

• Enable for content replacement: Allows the field to be used in dynamic content replacement scenarios. This is typically used in templates or automated content where values are substituted at runtime.

• Enable auto-fill without mandatory: Automatically populates the field based on predefined logic, even if the field is not marked as mandatory. This reduces manual input while still allowing flexibility.