Common Event Configuration
Event Name and Description
Provide a detailed explanation of what this event does. This is for the language models to understand when to use this event. Vague descriptions can cause the event to fire at unintended points in the conversation.Event Status
Enable the event to allow it to take actions. A disabled event is never invoked, even if its trigger conditions are met. Events can be enabled or disabled at any time without affecting other configurations.Event Processor
The Event Processor runs custom code before the platform responds to the user. Use it to transform data, enrich context, apply business logic, or tag sessions before the event’s actions execute. It runs after the event fires but before the response is delivered. To configure, enable the Event Processor toggle and click Edit Processor.
Testing the Processor : The right panel of the Edit Processor screen provides a test environment. Click Test Execution to run the script against sample data and verify the output before deploying. This lets you catch errors and validate logic without affecting live sessions.
Once configured, click Update to save the processor.
Example
The following script captures conversation summary and user tier before handoff.
- Enriching session context before the welcome message is sent
- Tagging users or sessions based on conversation data at handoff
- Transforming or validating parameters before they are passed to a receiving agent
- Logging or capturing data at the end of a conversation before the session closes
Specific configurations
Welcome Event
By default, it is triggered at the start of a session. Configurations: Under Actions, configure Send Message to User:- Select AI-generated to let the model compose the message, or
- Enter a Custom message. You can include memory store variables in the message.
Agent Handoff Event
Triggered when an agent handoff is requested. By default, the handoff fires when the user explicitly requests one or when the system cannot fulfill the request.Agent handoff is supported only via the AI for Service Platform. When triggered, the Platform sends session data to the specified automation node, which processes the transfer according to its configured connection rules.