Home Tags, attributes and custom fields How to Create Multi-Select Custom Attributes for Conversations

How to Create Multi-Select Custom Attributes for Conversations

Last updated on Sep 02, 2026

Multi-select custom attributes let you classify a conversation with more than one value at the same time, making organization, filtering, and analysis easier.
You can also create conditional attributes, which depend on the selection of another attribute.

See how to set up Custom Attributes by watching this video or by reading this post.

When to use multi-select

Use this type of attribute when a conversation can have:

  • More than one reason

  • More than one topic involved

  • More than one valid classification at the same time

How to create a multi-select attribute

  1. Go to Settings → Custom Attributes → Conversations

  2. Click Create new attribute

  3. Fill in:

    • Attribute name

    • Type: Multi-select

    • Options (the values that can be selected)

  4. Save the attribute

Done. The attribute will now be available for use in conversations.


How to create a conditional (dependent) attribute

Conditional attributes are used when a field only makes sense after another one has already been set.

Example:

  • Category → Subcategories (multi-select)

Step by step:

  1. Make sure the “parent” attribute already exists

  2. Create the “child” attribute (it can be multi-select)

  3. In the attribute settings, define:

    • Which attribute it depends on

    • Which values of the parent attribute activate this field

  4. Save and validate the behavior

The child attribute will only be used when the context makes sense.

How to use the attribute in a conversation

  1. Open a conversation in Cloud Chat

  2. Find the custom attributes section

  3. Select one or more values in the multi-select attribute

How the "Contains" filter works

When you filter conversations by a multi-select attribute using the Contains operator, the results include conversations that have any of the chosen values — a conversation does not need to have all of them at the same time.

Quick best practices

  • Prefer short, objective names for the options

  • Avoid very long lists without a conditional

  • Use conditionals to keep classification clear and consistent