Integrations/Customer.io

Control what your AI agents do in Customer.io.

Let your team build AI agents for Customer.io. Bollard AI controls what each one can do, area by area.

Request early accessSee how it works →
Customer.io
Lifecycle Agent
People Marketing areaOffReadFull use
Segments Marketing areaOffReadFull use
Broadcasts Marketing areaOffReadFull use
Send messages
What agents can do

Set what each agent can do across your marketing.

Each area of Customer.io, like people, segments, or broadcasts, gets one of three levels: Off, Read, or Full use. Anything not allowed is denied, and messaging is a separate switch.

Off
No access
The agent can't see that part of your marketing.
Read
Read-only
The agent can read people and segments in that area. It can't change or send anything.
Full use
Create and update
The agent can add and update people and events in that area.

Some actions stay off until explicitly turned on

Each one messages people, removes them for good, or triggers a campaign, so it could override the limits set elsewhere.

Sending messages and broadcastsDeleting or suppressing peopleTriggering campaigns
Set up & manage

Connect once. Manage everyone from there.

Connect once, then control access person by person. No new keys to hand out.

Step 1 · Set up

Connect once, company-wide

An admin connects your company's Customer.io a single time. Bollard AI lays out the areas of your workspace, and anything you don't allow stays out of reach for every agent.

Step 2 · Manage

Control access per person and agent

From one dashboard, set what every person and their agents can reach. Change it any time, with no new keys for anyone.

OffNo access
ReadRead-only
Full useRead, add, and update in a single area
Example

A lifecycle marketing agent.

A lifecycle agent updates people and can read your segments, but it can't send a broadcast or trigger a campaign.

People Marketing areaOffReadFull use
Segments Marketing areaOffReadFull use
Broadcasts Marketing areaOffReadFull use

Manage access

ALLOWEDLifecycle Agent updated a record in People
ALLOWEDLifecycle Agent read a Segment
BLOCKEDLifecycle Agent tried to open Broadcasts, denied by default

Monitor activity

The security model

Top-tier security.

Bollard AI is access control for AI agents. It sits between your agents and Customer.io, so they never hold your Customer.io keys and never reach Customer.io directly.

Everything runs through Bollard AI

Agents send their requests to Bollard AI, not to Customer.io. Bollard AI checks each one against your rules and passes only the allowed requests through.

Denied by default

Every area starts off-limits, and messaging people is held back on top of that. An agent gets in only where you've allowed it, and anything Bollard AI doesn't recognise is refused and held for review, never waved through on a guess.

Your keys stay sealed

Your Customer.io keys are sealed in a vault unique to your company and never shown again. Bollard AI unlocks them only for the instant an allowed request needs it.

Activity you can read

Every attempt is recorded in plain English: who or which agent, what they tried, which person or segment, and the decision. The record is readable and can't be edited after the fact.

Questions

Customer.io, answered.

Does connecting Customer.io hand Bollard AI your whole workspace?+
Only the areas you allow. An admin connects your Customer.io, and you decide which areas, like people or segments, each agent can reach. Bollard AI doesn't browse or copy your workspace. It sits in front of it and checks every request the agents make, passing or blocking each one.
Can an agent message people on its own?+
Not unless you turn it on. Sending messages and broadcasts, and triggering campaigns, are held off by default, so an agent can manage people and read segments without ever messaging anyone, until you explicitly allow it.
Can an agent see more than the person who owns it?+
No. An agent reaches only what its owner reaches. An explicit Off always overrides an inherited permission.
Where do our Customer.io keys live?+
Sealed in an encrypted vault, behind a key unique to your company. It's never shown again once connected, and Bollard AI unseals it only for the instant an allowed request needs it.
What happens when an agent tries something it's not allowed to do?+
Bollard AI blocks the request before it reaches Customer.io, and the blocked attempt lands in the activity record with the reason.
How do we connect Customer.io?+
An admin connects the company's Customer.io once. Bollard AI seals the connection and lays out the areas of your workspace to set rules for. From then on, all management happens in the Bollard AI dashboard.
Early access

Put your team's agents to work in Customer.io, without the risk.

We're onboarding our first development partners now. Tell us about your setup and we'll be in touch.

Request early accessAll integrations →