Context attributes
Create custom context for values to use across intent flows in NLX's Dialog Studio
Last updated
Create custom context for values to use across intent flows in NLX's Dialog Studio
Last updated
Context attributes allow for bots to retain context about something without the need to repeatedly run API calls or ask the user questions in order to recall the information. These are intended to be collected in a flow once and used throughout a session to better route users or personalize the conversation, including context passed along during escalation events. Within the Context attributes tab, you create the name and define the data type of the context attribute, allowing you to reference it in any intent flow across your workspace as you design your conversations.
For example, after authenticating a user, you can reference a context attribute that sets their authentication status as "true." In any intent flow that requires an authenticated person to complete a process, conditional logic can simply check the context attribute rather than re-running a series of steps with the user to determine this context.
Other examples that may be collected once from user input or an API call and set for the duration of the conversation session:
User information, including name, address, ID, email, reward/member tier, DOB, etc.
Device/phone type
Issue, topic, or reason
A counter (keeping track of retries, etc.)
To create transient context that is not shared across flows or retained for escalation, consider using the Define node.
Begin by selecting + Add context attribute from the Context attributes tab:
Expand new attribute > Enter name
Expand Schema section > Select type from the dropdown
Click Save
Delete a context attribute from your workspace by expanding its details and selecting the Delete context attribute link.
Need to edit a context attribute?
After creating your context attribute, you may expand its details and overwrite any fields or swap schema type(s) and click Save.
Once a context attribute has been created, you may reference it easily in nodes when building an intent flow by selecting it from placeholder dropdowns or entering an open curly brace { in any message field. All context attributes in your workspace are color-coded pink:
