The agent answers with your customer data already in view
Boom holds people, your own custom objects, and an append-only event log, fed by Shopify, Skio, a read-only connection to your database, and an events API. The agent reads it live, so it replies with the order, the plan, or the balance in front of it. And you segment on those variables up to three relationships deep, without writing a line of SQL.
A data model that fits how your business actually works
People, your objects, and an event log, one place the agent reads live.
- 01
People, objects, and events
A person record, the objects your business runs on, subscriptions, orders, policies, and an append-only event log that never overwrites history.
- 02
Connectors that bring the data in
Shopify and Skio out of the box, a read-only connection to your Postgres over an encrypted bastion, and a REST events API for everything else.
- 03
Segment up to three hops, no SQL
Build a segment up to three relationships deep, person to objects to related objects, with no SQL.
- 04
The agent reads it live
The data schema is injected into the agent so it replies with the order, plan, or balance already in view, not by asking for things you have on file.
Segments feed the workflow builder
When a customer enters a segment, the platform enrolls them into a journey and the workflow builder takes over: sends, delays, branches, the agent navigating the dialog. A change in a record can start a conversation without anyone lifting a finger.
- Segment entry enrolls a customer into a journey
- Segments are re-evaluated on a schedule
- Frequency caps keep a customer from being over-contacted
The same data opens inside the inbox
The record the agent reads is the record a teammate sees. The context panel resolves a conversation to the right person, shows their objects and deep links, right next to the messages. AI and human, same context. A customer is never asked for something the platform already holds.
How a segment turns into outreach
- 1
Connect the source
Point Boom at Shopify, Skio, your read-only database, or the events API. People, objects, and events start flowing in on a schedule.
- 2
Build the segment
Pick the variables that matter, up to three relationships deep, and Boom evaluates the segment on a cron. No SQL, no analyst in the loop.
- 3
Entry enrolls a journey
When a customer enters the segment, they are enrolled into a journey in the workflow builder, which decides what happens next.
- 4
The agent carries the context
When the conversation starts, the agent already has the person, the objects, and the events in view, and answers from them.
A warehouse stores your data. A CDP for conversations puts it to work.
Where the Boom data platform differs from a warehouse query or a marketing CDP.
| SQL on a warehouse | A marketing CDP | Boom data platform | |
|---|---|---|---|
| Who builds a segment | An analyst writes SQL | A marketer in a UI | An operator, up to three hops, no SQL |
| What a segment does | Returns rows | Triggers an email blast | Enrolls the customer into a journey |
| Does the agent read it | No | No | Yes, schema injected, read live |
| Connects to your database | It is the database | Usually one-way sync | Read-only over an encrypted bastion |
Questions about the data platform
See the data platform on your own customers
Book a 15-minute walkthrough and we will connect a source and build a segment that triggers a real conversation.