One package. Six verticals. Same code.

Healthcare & Staffing Recruiting

Healthcare staffing agencies and recruiting firms 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.

The problem

A nurse opens an "ICU openings in Tampa" 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 nurse doesn't see any of this — by the time the weekly campaign report lands, the nurse has signed with another agency.

The fix

1. The nurse opens the campaign — the open syncs into Salesforce via the Customer.io App API.
2. The nurse clicks through — the recruiter's My Active Candidates widget lights up with a HOT row.
3. The nurse views three job pages — the Engagement Banner on the recruiter's home page reads: "Sarah Johnson is actively job-shopping — viewed /jobs/icu-tampa 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.

Recruiter-day experience

Morning standup. The recruiter opens the CIO Pipelines app. The home page shows "3 of your candidates are browsing right now", top owned candidates by score (HOT first), and team-wide engagement.

Throughout the day. Widgets auto-refresh every 60 seconds (configurable). When a HOT row appears, the recruiter sees it.

On a Contact record. Every Contact has the Contact Activity Panel above the layout. No tab-switching to Customer.io. No CSV exports. No "let me check the campaign report and get back to you."

Outbound: Salesforce informs Customer.io

The same package handles the other direction. When the recruiter updates Lead_Status__c to "Submitted", Customer.io receives a track event. When they close the placement Opportunity, Customer.io receives a track event that exits the active-recruiting nurture and enters post-placement onboarding.

Quantifiable outcomes

• Time-to-first-touch measured in minutes, not days
• Engagement coverage: every recruiter sees engagement signal for 100% of their owned candidates
• Customer.io ROI surfaced internally: every recruiter watching the widget sees the value daily
• Reduced candidate ghosting: real-time response correlates with placement rate

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.

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

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.