01
People, objects, and events
Store people, orders, subscriptions, and policies, plus an event log that never overwrites history.
The agent answers with your customer data already in view
People, your objects, and events from Shopify, Skio, your database, or an events API. The agent sees the order or balance live.
What it does
A data model shaped like your business
People, your objects, and an event log, in one place the agent reads live.
02
Connectors for your data
Pull data from Shopify, Skio, a read-only Postgres connection, or a REST events API.
03
Three-hop segments, no SQL
Segment from a person to their objects and related objects, without writing SQL.
04
The agent reads it live
The agent reads the record live, so it never asks for what you already have.
How it connects
Segments feed the workflow builder
Entering a segment enrolls the customer into a journey of sends, delays, and branches. A change in a record can start a conversation on its own.
- Segment entry enrolls a journey
- Segments are re-evaluated on a schedule
- Frequency caps prevent over-contacting
How it connects
The same data opens inside the inbox
The context panel shows the teammate the same person, objects, and deep links the agent reads, right next to the messages.
From a variable to a conversation
How a segment turns into outreach
- 01
Connect the source
Connect Shopify, Skio, your read-only database, or the events API. Data syncs on a schedule.
- 02
Build the segment
Pick variables up to three relationships deep. Boom re-evaluates the segment on a schedule.
- 03
Entry enrolls a journey
A customer who enters the segment is enrolled into a workflow builder journey.
- 04
The agent carries the context
The agent starts the conversation with the person, objects, and events in view.
FAQ
Questions about the data platform
Do we have to move our data into Boom?
Only what the conversation needs. Boom reads Shopify, Skio, a read-only copy of your database, and a REST events API on a schedule, and never writes back.
How deep can a segment go?
Up to three relationships deep: a person, their objects, and the objects related to those. It is all in a builder, with no SQL.
Does the agent really use this data?
Yes. The schema is injected into the agent, so it reads the person, objects, and events live. Your team sees the same context in the inbox.
Is it real time?
Near real time. It polls sources on a schedule instead of streaming changes, and does not stitch anonymous identities. That cadence fits most lifecycle work.
See what the data platform connects to
See the data platform on your own customers
In 15 minutes we connect a source and build a segment that starts a real conversation.