Skip to main content
The Text ecosystem generates two types of native system activities sent to users as events: System events are an extension and a future replacement for system messages.

System events

The payload of the system event is a serialized JSON string stored in the details property, and its format depends on the source, subtype, and version. The sources send the newest available version, but existing chat documents may contain older versions. Later version numbers indicate more recent versions.
Sample system event body
The list of system event subtypes grouped by source:

ai_agents

The ai_agents source includes system events related to AI Agent activity, including custom skill execution. Agents can see custom skill system events.

custom_skill_awaiting_feedback

Generated when a custom skill is waiting for human feedback before continuing.
Sample custom_skill_awaiting_feedback payload

custom_skill_completed

Generated when a custom skill completes successfully.
Sample custom_skill_completed payload

custom_skill_failed

Generated when a custom skill fails.
Sample custom_skill_failed payload

custom_skill_rejected

Generated when an agent rejects a custom skill execution.
Sample custom_skill_rejected payload

custom_skill_started

Generated when a custom skill execution starts.
Sample custom_skill_started payload

cdp

CDP stands for Customer Data Platform. It collects customers’ data and emits events related to their interactions with the Text ecosystem.

store_order_was_created

Generated when a customer creates an order in an organization’s store.
Changes from Version 1: The title property in order’s line items became mandatory. A mandatory product_id property in order’s line items was added.
Sample store_order_was_created payload

store_product_added_to_cart

Generated when a customer adds one or more products to their cart in an organization’s store.
Sample store_product_added_to_cart payload

store_product_removed_from_cart

Generated when a customer removes one or more products from their cart in an organization’s store.
Sample store_product_removed_from_cart payload

messaging

Messaging source includes system events related to messaging activities, such as information about the generation of thread summaries.

summary

Generated when a thread summary is requested for an active thread.
Sample summary payload

ticketing

The ticketing source includes system events related to tickets created from active chats. Agents can see these events.

ticket_created

Generated when a ticket is created for an active chat thread. The event has a custom_id in the format ticket_created:<ticket_id>. If a ticket is created for an inactive thread, Text does not generate the ticket_created event. Instead, Text updates two properties on the thread: ticketing.last_ticket_id and ticketing.last_ticket_created_at (in ISO 8601 format).
Sample ticket_created payload

System messages

This section lists the system message types generated in the Text ecosystem. In addition to system messages generated by Text, applications can define their own system messages. The content of the system message event is a string stored in the text property, and its format depends on the system_message_type. The variables used to generate the text are specified in the text_vars property. The list of system message types, sorted alphabetically:

Agent

Customer

Chat

Rating

Routing

routing.archived

routing.assigned

routing.idle

routing.unassigned

Transcript