Customer.io, worked by an AI employee
Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Customer.io account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.
- Marketing Automation
- Connects with a key
- 14 ready-made tools
- Asked in Slack or Teams
An illustration of how the conversation reads, not a transcript from a client account.
What Customer.io is
Customer.io is a customer engagement platform that enables businesses to send targeted messages to their customers through various channels, including email, SMS, and push notifications.
You paste in a key from your own Customer.io account. It is kept encrypted, and you can withdraw it from inside Customer.io whenever you like.
One message in, the work done in Customer.io.
- 01
You ask
You message your AI employee in the chat your team already has open, in one sentence, in your own words.
- 02
It works out the step
It decides what the job needs in Customer.io. You do not pick anything from a menu or wire anything together.
- 03
It does the work
Signed in to your own Customer.io account, inside the access you granted it, doing the thing you asked for.
- 04
It reports back
It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.
What it can do in Customer.io
These are the ready-made tools your AI employee already has in Customer.io. It is not limited to them, but it never has to be taught these.
- Get Customer.io Workspace WebhooksTool to retrieve a list of webhooks. use after setting up reporting webhooks to fetch current webhook configurations in your workspace.
- Get IntegrationsTool to retrieve a list of integrations in your workspace. use when you need to discover configured integrations.
- Get MessagesTool to retrieve a list of messages sent from your workspace. use when you need paginated delivery metrics for messages, e.g., list email messages delivered between two timestamps.
- Get Segment DetailsTool to retrieve details of a specific segment. use after identifying the segment id from list segments.
- Get Segment MembershipTool to retrieve people in a specific segment. use when you need to page through segment membership after identifying segment id.
- Get SegmentsTool to retrieve a list of segments in your workspace. use when you need to fetch all segments after configuring segment rules.
- Get TriggerTool to retrieve details about a specific trigger. use after triggering a broadcast to confirm its status and metadata.
- Get TriggersTool to retrieve a list of triggers for a specific broadcast. use after identifying broadcast id to inspect associated triggers.
- List CollectionsTool to list all collections metadata. use when you need to retrieve current details of each collection in your workspace.
- List NewslettersTool to list all newsletters. use when paginating through newsletter metadata.
- List SnippetsTool to list all snippets in your workspace. use when you need to retrieve all reusable content snippets for templating or dynamic content insertion.
- List Transactional MessagesTool to list all transactional message templates. use when you need to fetch available transactional messages.
- Suppress Customer ProfileTool to suppress a person. use when you need to permanently delete a customer's profile and prevent them from being re-added.
- Trigger BroadcastTool to manually trigger a broadcast. use when you need to override the default audience and provide personalization data after confirming the broadcast id.
You stay the boss of your Customer.io account.
Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.
How we handle your data- It signs in to your own Customer.io account. You are not moving anything into ours.
- You grant access one app at a time, and you can take it back the same way.
- Everything it does in Customer.io is written down, with what it did and when.
- Anything you tell it to check with you first, it checks with you first.
It works in Customer.io and the rest of your software in the same job
A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.
Questions people ask about Customer.io
- Can an AI employee really work inside Customer.io?
- Yes. It signs in to your own Customer.io account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
- Do I have to move anything out of Customer.io?
- No. Nothing moves and nothing is replaced. Your records stay in Customer.io, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
- How does it get into my Customer.io account?
- You paste in a key from your own Customer.io account. It is kept encrypted, and you can withdraw it from inside Customer.io whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
- What can it actually do in Customer.io?
- It has 14 ready-made tools in Customer.io today, among them Get Customer.io Workspace Webhooks, Get Integrations and Get Messages. The full list is on this page. It is not limited to those, but it never has to be taught them.
- Can it use Customer.io and the rest of my software in the same job?
- Yes, and that is usually the point. Reading a message in one app, checking a record in Customer.io and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
- Who decides what it is allowed to do in Customer.io?
- You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Customer.io is written down with what it did and when.