Get every message you sent a customer, in order

What did we actually send this person?

The companion resolves the email address to a profile, pulls the messages that went to them across campaigns, broadcasts and transactional sends, and lays out the sequence in order with what each one was. Twenty minutes becomes a paragraph, and the paragraph has campaign names in it rather than a vague impression.

It does not stop at the Customer.io boundary either. The same run checks the CRM record you are signed into, looks at whether support tickets were open during that window, and reads the customer's own site for what changed. What comes back is a timeline of what your company did to somebody, assembled from three tools that each held a third of it, which is data extraction pointed at your own stack.

• "Everything we sent this address in the last ninety days, in order, with the campaign each came from."
• "Which segments is this person in, and how big is each one?"

Every tool here is a read, on purpose

That boundary earns its place on a platform like this one.

A mistaken write in a lifecycle tool arrives in forty thousand inboxes within seconds and cannot be recalled, so the send stays on the human side of the line, and connecting this is a five-second decision rather than a meeting.

In practice: a companion answers the question and a person acts on the answer in Customer.io. Asked to enrol somebody or fire a broadcast, it says it has no tool for that.

How do you look somebody up?

By exact email address.

Not a name, not a partial match, not an attribute filter. One address, returning the profile behind it. Any workflow that begins with a cohort sources that cohort elsewhere and hands the addresses over.

That elsewhere is usually a tab the companion can already read: a churn list exported from your warehouse, a spreadsheet of accounts, the CRM view your team lives in. It walks the addresses one at a time and builds the comparison, which for the forty that matter this week is an afternoon of work finished before lunch.

Campaign and segment reads are broader. Campaigns come back with their flow steps and status, segments with their type and member count, and broadcasts and newsletters list too, which answers "what is running right now" without opening the interface at all.

Run the churn post-mortem as a habit

The question needs three other tabs open, which is the argument for running it from the browser as an operations habit rather than a manual dig. A companion writes what happened to this person and why it looks different from what anybody intended, with the campaign names and the timestamps in the paragraph.

Customer.io's own reporting keeps computing deliverability, conversion and engagement across the whole audience on data it already holds. That is the aggregate view. This is the one that used to eat twenty minutes at a time.

Frequently asked questions