What it does
One thing Ody can do in Customer.io.
Add person
Create or update a Customer.io person (Pipelines identify keyed by email) from a consenting Ody contact.
Up and running in under two minutes.
Paste your API key
Grab a key from Customer.io's settings and paste it into Ody's Connect window. The form tells you exactly where to look.
Pick your options if needed
Most connections need nothing else. When they do (a channel, an audience, a board) the options appear right after you connect.
It runs on its own
Imports stay on a schedule. Tickets, tasks, logs, and alerts fire when the call ends. Astra can use Customer.io on a live call, too.
Why it matters
The phone stops being someone's job.
Lists grow from real conversations
A caller who asked to hear from you is worth more than a purchased list. Ody adds consenting contacts to Customer.io.
Consent first
Only people who opted in are pushed to Customer.io. Double opt-in stays on where the destination requires it.
The phone can trigger the flow
Call outcomes become events or new records, so journeys run on what actually happened, not on a form fill from last quarter.
Questions about Customer.io.
Still stuck? Talk to us. A human answers.
Ody never sees your Customer.io password. You paste an API key into a secure form. Credentials live in an encrypted connection store; Astra and the rest of the product never read them. Disconnect anytime and access is revoked immediately.
More ways to grow a list
All 43 integrations →
Import ActiveCampaign contacts and add consenting callers and texters to your account.
Callers into ActiveCampaign.
Import a Beehiiv publication's subscribers and subscribe consenting callers to your newsletter.
Callers into your newsletter.
Import Brevo contacts and add consenting callers and texters to your Brevo account.
Callers into Brevo.
Import Klaviyo profiles, push consenting callers, and track call events for flows.
Profiles in, call events into flows.