One package. Six verticals. Same code.

B2B SaaS Sales

A sales rep is working a 30-account named territory. The economic buyer just opened the pricing page for the second time this week. The rep doesn't know — until the SDR mentions it in standup the next morning. CIO Pipelines closes that gap by surfacing the engagement signal inside the Account and Contact records the rep already lives in.

The problem

A CFO at a target account opens an "ROI calculator" campaign and clicks through. They spend ten minutes on pricing, then view the enterprise plan page twice. They never request a demo. The AE who owns that account doesn't see any of this — by the time the weekly campaign report lands, the prospect has booked a meeting with a competitor.

The fix

1. The buyer opens the campaign — the open syncs into Salesforce via the Customer.io App API.
2. The buyer clicks through — the AE's My Active Contacts widget lights up with a HOT row.
3. The buyer views pricing twice — the Engagement Banner on the AE's home page reads: "Sarah Johnson is back on pricing — viewed /pricing/enterprise 4 minutes ago."
4. The AE clicks the row, lands on Sarah's Contact record, and sees the Contact Activity Panel: every page she's viewed, every email she's opened, the engagement state, and the right CTA.
5. The AE reaches out while she's still evaluating.

Configuration

• URL pattern: pricing, demo, contact, signup, trial, plan, enterprise, integration
• Owner field: OwnerId (Account-based)
• Team scope: Manager Hierarchy
• Pipeline widget: scoped to the rep's named accounts via standard sharing
• HOT banner: "{name} is evaluating product — viewed {pageTitle} {minutes} min ago — schedule the demo."

Outbound triggers

• New Trial_Activation__c → track event "Trial Started"
• Opportunity Stage = "Demo Scheduled" → track event triggers Customer.io confirmation series
• Account Health_Score__c change → group event updates company-level traits

Quantifiable outcomes

• Time-to-first-touch measured in minutes, not days
• Engagement coverage: every AE sees engagement signal for 100% of their owned accounts
• Customer.io ROI surfaced internally: every rep watching the widget sees the value daily

Staffing & Recruiting

Staffing agencies and in-house recruiting teams run their recruiter desks in Salesforce. Customer.io powers their candidate marketing and nurture. CIO Pipelines bridges the two — so the recruiter sees the moment a candidate engages, and reacts before the moment passes. Works equally well for healthcare staffing, tech recruiting, executive search, and high-volume retail hiring.

The problem

A candidate opens a "New roles this week" campaign and clicks through to the careers site. They view three job postings in the next ten minutes. They never fill out the apply form. The recruiter who owns that candidate doesn't see any of this — by the time the weekly campaign report lands, the candidate has signed with another firm.

The fix

1. The candidate opens the campaign — the open syncs into Salesforce via the Customer.io App API.
2. The candidate clicks through — the recruiter's My Active Contacts widget lights up with a HOT row.
3. The candidate views three job pages — the Engagement Banner on the recruiter's home page reads: "Sarah Johnson is actively job-shopping — viewed /jobs/senior-engineer 4 minutes ago."
4. The recruiter clicks the row, lands on Sarah's Contact record, and sees the Contact Activity Panel: every page she's viewed, every email she's opened, the engagement state, and the right CTA.
5. The recruiter calls Sarah while she's still on the careers site.

Configuration

• URL pattern: job, career, position, role, opening, hiring, apply (extend with industry terms as needed)
• Owner field: Recruiter__c or OwnerId
• Team scope: Public Group (per desk or office)
• HOT banner: "{name} is actively job-shopping — viewed {pageTitle} {minutes} min ago."

Outbound triggers

• Lead_Status__c = "Submitted" → track event into Customer.io
• Placement Opportunity closed → track event exits active-recruiting nurture, enters post-placement onboarding

Quantifiable outcomes

• Time-to-first-touch measured in minutes, not days
• Engagement coverage: every recruiter sees signal for 100% of their owned candidates
• Reduced candidate ghosting: real-time response correlates with placement rate

Commercial Real Estate

Brokers manage hundreds of leads across multiple property types. When a prospect returns to a specific listing twice in a day, that's a buying signal — but the broker only sees it if they're checking the marketing dashboard.

Configuration

• URL pattern: listing, property, home, address, mls, neighborhood, open-house, agent
• Owner field: Listing_Agent__c
• Team scope: Manager Hierarchy
• HOT banner: "{name} is browsing listings — viewed {pageTitle} {minutes} min ago."

Outbound triggers

• New Showing_Request__c → track event "Showing Requested" with property ID
• Opportunity Stage = "Under Contract" → track event exits nurture and enters post-contract drip

Freight & Logistics Brokerage

Freight brokers nurture carrier networks via email. When a carrier hits the load board, the broker who owns that carrier needs to know — fast. The freight market moves in hours, not days.

Configuration

• URL pattern: load, lane, freight, shipment, route, dispatch, broker, quote
• Owner field: Broker__c (custom user lookup on Carrier Contact)
• Team scope: Public Group ("Atlanta Brokerage Desk")
• HOT banner: "{name} is reviewing freight options — viewed {pageTitle} {minutes} min ago — quote them now."

Outbound triggers

• Carrier Status__c = "Available" → identify updates the trait
• New Load_Booking__c record → track event "Load Booked" with lane and rate properties

E-commerce / DTC

Customer service reps respond to inbound tickets without knowing whether the customer is a high-engagement repeat buyer or a one-time browser.

Configuration

• URL pattern: product, shop, cart, checkout, order, collection
• Place the Contact Activity Panel on the Case record page (via the related Contact)
• Banner shows whether the customer was browsing in the last hour, which categories, and email engagement

Outbound triggers

• Case opened with high-value Contact → track event triggers VIP support routing
• Order Refunded → track event exits the standard re-engagement series

Financial Services / Wealth Management

A wealth advisor manages a book of 200 clients. When a client opens an "Upcoming market volatility" email and clicks through to planning resources, that's a signal — they're worried, and they want to talk.

Configuration

• URL pattern: planning, retirement, market, volatility, portfolio, risk, education
• Owner field: Advisor__c
• Team scope: Public Group ("Western Region Advisors")
• HOT banner: "{name} engaged with planning resources — viewed {pageTitle} {minutes} min ago — call them."

Outbound triggers

• New Case (client-initiated) → track event "Client Question Submitted"
• Account Risk_Profile__c change → identify updates Customer.io for segment targeting

The pattern, in five steps

1. Pick the URL substrings that matter to your business
2. Pick the owner field (default OwnerId or a custom recruiter/broker/advisor field)
3. Pick the team scope (manager hierarchy, group, queue, or all users)
4. Rewrite the banner templates to match your domain language
5. Build the trigger configs to ship operational events to Customer.io

Same Apex, same LWCs, same security model — adapted in admin UI, not in code.