Configure a case type

This article explains how to configure a case type to guide agents through a structured series of tasks.

Each task is built on a Workflow you create in the Admin Center and is designed to help agents collect and organize customer information efficiently. Once your Workflows are ready, you can combine them into a case that reflects your business process from start to finish. For help creating Workflows, see Create a Workflow for a case task.

Configuring a case type

To configure a case type:

1. In the Admin Center, click Cases.
   The Cases page opens.

2. Click + Case type.
   

3. Name your new case and click Done.
   

   The new case opens.

4. Type a title and description (optional) for your first task.

   The description field has a 250-character limit.

5. Click Select Workflow.
    
   The Select Workflow window appears.

6. Navigate to and select the Workflow you’d like to associate and click Select.
   

7. If required, create a condition for enabling this task. See below.

8. Click Create new task to add another task to the case.

9. Add as many tasks as required for this case type.

10. Click Publish.

    The case becomes available to case agents, but must be associated with a team before they can access it in Case Manager.

    See Associate a case to a team.

Delete a case type

To maintain a clean and accurate environment, administrators can delete case types that are no longer needed. This action is performed directly within the case type builder.

What happens when a case type is deleted?

It is important to understand the impact of deletion on your existing data and active workflows:

• In-flight and completed cases: Deleting a case type does not delete the cases themselves. Any existing cases created from that type will remain visible in Case Manager and continue to function normally until they reach their end-state.

• Case creation: Once deleted, the case type is removed from the "Create new case" options for all users. You cannot restore a deleted case type; you would need to rebuild the structure manually.

• Team access: The system automatically removes the association between the deleted case type and any assigned teams.

• Configuration cleanup: Deletion is permanent and helps ensure that agents only see the most relevant and up-to-date case structures.

Note

We recommend verifying that no automated external integrations are specifically calling for a Case Type ID before you proceed with deletion.

To delete a case type:

In the Cases page, click the three-dot menu for the relevant case and select Delete.

Configure task behavior

When configuring a case, you can control how each task behaves in the Case Manager UI by applying conditions. Task conditions determine whether a task is:

• Available to open (Disabled behavior)

• Editable (Read-only behavior)

Both behaviors use the same condition framework, but control different aspects of task behavior.

Task behavior types

Editable (default)

• The task can be opened and edited at any time.

Read-only (controls editability)

• The task can always be opened and viewed.

• The task cannot be edited until the condition is met.

• Use this to keep tasks visible for context while controlling when changes are allowed.

Disabled (controls access)

• The task appears in the task list

• The task cannot be opened until the condition is met.

• Use this to control when a task becomes accessible in the process.

Note

If both behaviors are configured, Disabled overrides Read-only.

How task conditions work

• Conditions are configured per task in the case type builder.

• Conditions are evaluated continuously in real time.

• Evaluation is based on case data, such as:

  • Case state

  • Attributes (including values collected in previous tasks)

  • Ownership and system values

When a condition evaluates to true, the defined behavior is applied immediately.

Example: including dependent details only when selected in an insurance plan

In an insurance plan enrollment process, you might include an optional task to collect Dependent details.

In an earlier task, you include a checkbox (Boolean Attribute) with the title: "Include dependents to your insurance plan"

You can then configure a Disabled condition on the Dependent details task:

• The task is only available if the checkbox is selected

In this setup:

• If the customer selects Yes, the task becomes available and can be opened and completed

• If the customer selects No, the task remains unavailable and cannot be opened

This ensures that:

• Agents only see and access tasks that are relevant to the selected plan

• Irrelevant tasks are excluded from the working flow

Example: allowing edits only during early stages of a mortgage onboarding process

In a mortgage onboarding process, agents may need to complete and review a task such as Income information while the application is still being collected and verified.

For example, the task should be editable during the Onboarding and Verification stages, but locked once the case reaches Decision.

You can configure a read-only condition such as:

• CASE_STATE_NAME = Onboarding

  -OR-

• CASE_STATE_NAME = Verification

In this setup:

• During Onboarding and Verification, agents can enter and correct income details

• In later stages (such as Decision), the task becomes read-only

This ensures that:

• Agents can update data while the mortgage application is still being reviewed

• Finalized information cannot be changed once the case reaches a decision stage

If the case returns to an earlier stage (for example, because additional verification is required), the task becomes editable again automatically.

Configure task behavior

1. In the Admin Center, on the Cases page, open the case and select the task you want to configure.

2. Under Condition rules, turn on the toggle for the behavior you want to control (Read-only or Disabled).
   
   The condition dialog opens.

3. Build the condition:

   • Select a field type (Attribute or System value)

   • Choose the field

   • Select an operator (for example: equal to, not equal to, contains)

   • Enter or select the value

4. (Optional) Click + to add additional clauses and combine them using AND/OR.

5. Click Save.
   

The task behavior updates dynamically based on the condition.

Examples of conditions

• Attribute-based (Boolean):

  • include_dependents = true

• State-based (System value):

  • CASE_STATE_NAME = Verification

Allow agents to re-send a task

You can allow agents to re-send a customer-facing task when a submission needs to be corrected.

Turn on Allow agents to resend workflow in the task settings.

When enabled:

• Agents can re-send the task to the customer from Case Manager

• The same task is sent again for completion in the Collaboration Room

Configuration rules:

• Available only for customer-facing tasks

• Not available for internal (agent-only) tasks

• When disabled, the re-send option is not available to agents

Use this setting for tasks where customers may need to resubmit information, such as document uploads or form completion.

Q & A