Customer data platform

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.

CDP
MMariana G.PersonSubscriberLTV $840
Subscription
PlanPro
StatusActive
MRR$48
Order
Last order#10482
Items3
Events
subscription.pausedJun 24order.placedJun 11message.receivedJun 02
  • Grupalia
  • Contalink
  • Solvento
  • Vitau
  • Mattilda
  • Kontempo
  • Wallbit
  • Nexu
  • Dogelthy
  • AgendaPro
  • Treo
  • Simón
  • VitalBotanics
  • Sleep Rituals
  • Sleepy Bear Studio
  • Mubson
  • Bustin Boards
  • fitbody
  • Herbit
What it does

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.

Segment
Win-back, past due1,284 matches
Personcountry = MX
Subscriptionstatus = past_due
Plantier = pro
Entering this segment enrolls a journeyJourney
How it connects

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
Context
Assigned to AI
My plan renewed but I paused it?
I see it here. Your Pro plan is past due since Jun 24, want me to fix the payment?
MMariana G.Person
PlanPro
StatusPast due
Related records
SubscriptionPro · past dueOrder#10482 · $96
How it connects

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.

From a variable to a conversation

How a segment turns into outreach

  1. 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. 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. 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. 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.

FAQ

Questions about the data platform

Do we have to move our data into Boom?

Only what the conversation needs. Boom connects to Shopify, Skio, and a read-only copy of your own database over an encrypted bastion, and there is a REST events API for your own events. It reads on a schedule, so it is near real time rather than instant, and it never writes back to your systems.

How deep can a segment go?

Up to three relationships deep. You can segment on a person, the objects related to them, and the objects related to those, all in a builder, with no SQL. The platform is designed to surface those variables so an operator never touches a query.

Does the agent really use this data?

Yes. The data schema is injected into the agent, so it reads the person, the objects, and the events live and answers from them. The same context appears in the inbox context panel for your team.

Is it real time?

It is near real time. The platform polls its sources on a schedule rather than streaming changes the instant they happen, and it does not stitch anonymous identities together. For most lifecycle work that cadence is what matters.

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.