Collections and variables
Collections, variables, files and shared project information
Updated October 22, 2026
Collections
The project's tables: leads, bookings, reviews
User variables
What they chose, what they answered, where they stopped
Events
Joined, clicked, opened, paid — every metric is built from these
Collections
A collection is a project table for custom data: leads, bookings and reviews. Fields are described by you or the agent; records are added by people through the site, by flows, or by you.
Collections are read by the site, answered from by the agent, and used to build segments.
Products and orders
Use the built-in Products, Offers and Orders in Data for sales. They are shared by the project and connected to payment and access. Do not replace them with a duplicate catalogue or order ledger in a custom collection. See products, offers and payment.
Files and knowledge
Project files, including images, videos, documents and other materials, are available in Data. Reuse a file in a broadcast and on the site without uploading a separate copy for each bot.
Business information, contacts and frequently asked questions live in the shared project knowledge base: Settings → Knowledge base. It provides context for the agent rather than replacing products, orders or collection records.
User variables
Every user carries a set of values: what they chose, what they answered in a form, which step they stopped at. Flows and the site write them; you can read them on the user card and use them in flow conditions.
Events
Everything that happens is recorded as an event: joined, clicked, opened a page, paid, received a broadcast. Events feed the metrics on user cards, broadcast reports and funnels.