# Attributes {% hint style="success" icon="list-check" %} **IN SHORT** Create custom attributes that let you define your business logic directly in Fullwhere. These attributes can be linked to your customer interactions, your customers, and their purchases. Attributes can be manual fields or fields whose value is filled in by AI Completion. Attributes can be used to create fully customized conditional logic in your Workflows. {% endhint %} {% hint style="info" icon="shield-check" %} **ACCESS RIGHTS** To modify the Attributes in your Fullwhere workspace, you must be a supervisor member with Administrator rights. {% endhint %} ## Access your attributes To create or modify your custom attributes, go to the Automations > [Attributes](https://app.fullwhere.com/automation/attributes). The first table lets you access your attributes according to their target, namely: * Interactions: custom attributes linked to your customer interactions * Customers: custom attributes linked to your customers * Purchases: custom attributes linked to your customers' transactions By clicking on a category, you access the attributes of the chosen category. The attributes of this category are then shown in the following table:
ColumnDescription
NameName you gave your attribute
TypeThe type of your attribute (Text, Number, Single select, Multiple select)
AI CompletionIndicates whether AI completion is enabled (available only for attributes targeting interactions)
## Create an attribute To create a custom attribute, click the `+ Create an attribute` at the top of your screen. In the configuration menu for your attribute, you can define the following settings: ### Type The type of an attribute determines the values that can be defined for that attribute. There are 4 different types. #### Text An attribute of type **text** can be assigned any free-form value from one entity to another, whether by users of your account or by AI Completion if it is enabled. Text-type attributes can, for example, be useful for taking notes or creating summaries. #### Number An attribute of type **number** can be assigned only a numerical value, whether by users of your account or by AI Completion if it is enabled. Number-type attributes can, for example, be useful for defining custom scoring systems. #### Single select An attribute of type **single select** can be assigned one value from a list of predefined possible values, whether by users of your account or by AI Completion if it is enabled. If the[AI Completion](#ai-completion) is enabled on your attribute, you can [allow AI to generate new values](#autoriser-lia-a-generer-de-nouvelles-valeurs). Single-select attributes can, for example, be useful for defining a priority level or the team involved in the interaction. #### Multiple select An attribute of type **multiple select** can be assigned multiple values from a list of predefined possible values, whether by users of your account or by AI Completion if it is enabled. If the[AI Completion](#ai-completion) is enabled on your attribute, you can [allow AI to generate new values](#autoriser-lia-a-generer-de-nouvelles-valeurs) or not. Multiple-select attributes can, for example, be useful for detecting the products mentioned by your customers in your interactions. {% hint style="info" %} Once your attribute is created, the type of your attribute can no longer be changed. {% endhint %} ### Target entity Your attribute can concern one of the following 3 entities: * Interactions: custom attributes linked to your customer interactions * Customers: custom attributes linked to your customers * Purchases: custom attributes linked to your customers' purchases {% hint style="info" %} Once your attribute is created, this setting can no longer be changed. {% endhint %} ### Name The name of your attribute represents the value by which you can identify your attribute in your Fullwhere workspace. If AI Completion is enabled on your attribute, its name will be provided to the LLM responsible for assigning values to your attribute; in this case, make sure to use an unambiguous name. ### Possible values This setting is only available for single select and multiple select attributes. For each item, you must specify: * its value * its color {% hint style="warning" %} Changing a possible value changes it everywhere it had been assigned. {% endhint %} {% hint style="danger" %} Deleting a possible value removes it from all entities (interactions, customers, purchases) to which it had been assigned. **This action is irreversible.** {% endhint %} ### AI Completion {% hint style="warning" %} AI features are only available for attributes targeting customer interactions. {% endhint %} You can take advantage of our AI features to automatically enrich your data with AI Completion. From then on, for each interaction centralized in Fullwhere, the values of your attributes can be defined by AI analysis. #### Guidelines The **guidelines** field lets you define the prompt that will be used to determine the value to assign to your attribute. In the guidelines, it is important to clearly define what your attribute represents and how it should be analyzed by the LLM. For single select and multiple select fields, it is important in the guidelines to clearly define a description for each possible value of the field: * describe what the value represents and in what circumstances it should be selected * it may be useful to include keywords or expressions that the customer might use * it may be useful to specify what does not fall under a possible value, and therefore in which cases it should not be selected For single select attributes where AI Completion is enabled, it is recommended to have a minimum of overlap between possible values. If the values are too similar, it may be difficult for an LLM to assign the right one. Before finalizing, ask yourself the following question: "Would a human have trouble choosing between the possible values?" {% hint style="info" %} To validate your guidelines, it may be useful to submit them to an LLM chat such as ChatGPT, Gemini, or Claude to help make them as clear as possible. {% endhint %} #### Detection conditions Detection conditions let you perform AI detection of your attribute only if the customer interaction meets the conditions you define. This can be useful to specialize your attributes and avoid performing AI detection when it is not necessary. #### Allow AI to generate new values For single select and multiple select attributes, you can choose whether or not to allow AI to add new values to the list of possible values. In this case, the new values will be added to your attribute and will be used for future attribute detections. #### Overwrite already present values For multiple select fields, you can specify whether the values detected by AI should be added to the values that may already be present or whether they should replace them. ## Delete an attribute To delete a custom attribute, go to Automations > Attributes, then select the family of your attribute. In the list of attributes, click the 3 small dots at the end of the row for the attribute to delete, then in the dropdown menu click Delete. {% hint style="danger" %} Deleting an attribute removes all values that had been assigned to your interactions, customers, or purchases. **This action is irreversible.** {% endhint %} *** ## Use cases Here are concrete examples of using custom attributes with AI Completion. ### 1. Priority level This attribute automatically sorts incoming messages so that urgent ones are handled first. * Name: `Priority` * Type: `Single select` * Possible values: `Low`, `Medium`, `High` * Allow AI to create new values: `No` * **Guidelines** > "Analyze the customer interaction to determine its degree of urgency and importance. > > * Choose High if the customer expresses strong anger, reports a blocking technical issue, or requests cancellation. > * Choose Medium for common usage questions, order follow-up requests, or non-blocking issues. > * Choose Low for thank-you messages, positive feedback, or purely informational messages that do not require an immediate response." *** ### 2. Custom scoring system This attribute turns textual sentiment into numeric data to feed your reports. * Name: `Satisfaction Score (AI)` * Type: `Number` * **Guidelines** > "Evaluate the overall level of satisfaction expressed by the customer in their message on a scale from 0 to 20. > > * Assign a score close to 0 if the customer is extremely dissatisfied or aggressive. > * Assign a score of 10 if the message is neutral or purely factual. > * Assign a score close to 20 if the customer expresses strong enthusiasm or warm thanks. > > Respond only with the number corresponding to the score." *** ### 3. Detection of mentioned products Ideal for analyzing which products generate the most conversations without manual entry. * Name: `Mentioned products` * Type: `Multiple select` * Possible values: `Product A`, `Product B`, `Product C` * Allow AI to create new values: `Yes` * **Guidelines** > "Identify all specific products or services mentioned by the customer in the interaction text. > > * If the customer mentions a product from the list of possible values, select it. > * If the customer mentions a product that is not yet in the list, create a new value corresponding to the name of the detected product. > * If no specific product is identified, do not select any value." ## Use an attribute The value of your attributes can be defined/modified for each customer interaction present in Fullwhere.\ To define/modify the value of an attribute for a customer interaction: * go to the customer interaction to modify * in the information panel on the right, go to the Custom Attributes section * you can define the value to assign for each attribute Your attributes can also be used to define logical conditions in your [Workflows](/documentation/documentation-en/automations/workflows.md#conditions-portant-sur-linteraction). --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fullwhere.com/documentation/documentation-en/automations/attributes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.