A Salesforce-native extension of Customer.io.

Drives Customer.io adoption inside Salesforce-first organizations

Many of Customer.io's enterprise prospects are Salesforce-first companies whose internal champions need to demonstrate Customer.io's value to a Salesforce-resident sales/recruiter team. Today, that team only sees Customer.io's value when a campaign report lands in their inbox. With CIO Pipelines, every recruiter watching the Active Candidates widget sees Customer.io's signal in real time, every day.

When the recruiter spots a HOT candidate and closes the placement, the credit goes to the email Customer.io sent. That story plays out daily inside the org and increases internal advocacy for the Customer.io subscription.

Targets a vertical Customer.io may not be deeply penetrated in

Our flagship use case is healthcare and staffing recruiting. Healthcare staffing agencies typically run their recruiter desks in Salesforce (or a Salesforce-derived ATS) and use Customer.io for candidate marketing. The integration gap between the two is real, painful, and well-understood by the people who feel it daily.

We've built defaults specifically for this vertical:

• Default job-page URL pattern includes nurse, physician, locum, healthcare
• Banner templates speak to the recruiter persona
• Engagement scoring prioritizes job-page views over generic email engagement

We expect to expand into adjacent verticals — B2B sales, freight/logistics, real estate, financial services — but healthcare staffing is where the first traction will come from.

Two-way integration leverages Customer.io's APIs as designed

• Outbound: Apex triggers send identify, track, and group events via the Pipelines CDP API, asynchronously, with field mapping and filtering built into the admin UI.
• Inbound: LWCs read from the App API to surface activities, customer profiles, and page views inside Salesforce record pages.

We're not screen-scraping. We're not reverse-engineering. We're not forking Customer.io. We're using the public APIs as the documentation suggests and packaging the result for a Salesforce-native distribution channel.

Co-marketing potential

We've designed the package to wear the Customer.io brand visibly:

• The product is named CIO Pipelines — a clear nod to Customer.io's Pipelines CDP product
• Every UI surface includes a "Built for Customer.io" tag
• Marketing materials position Customer.io as the primary brand and CIO Pipelines as the integration layer

We're not building a competitor — we're building a Customer.io accelerator

Several integration vendors in the Salesforce ecosystem (notably ones backed by VC) compete head-on with Customer.io's core messaging product. CIO Pipelines does not. We don't store messages. We don't run journeys. We don't replace Customer.io's authoring experience. We surface what Customer.io already knows about a person, in the place where Salesforce-resident teams already work.

The package would lose its value if Customer.io ceased to exist. That's the right shape for a partner.