Multi-Pipeline

Running multiple pipelines transforms how you track different business lines, service offerings, and customer journeys. Instead of cramming every opportunity into a single workflow, you create dedicated pipelines that match each distinct sales process, keeping your team organized and your reporting accurate.

What Multi-Pipeline Does

Access pipelines from Opportunities > Pipelines in any sub-account. The HighRise design system (enable via Sub-account > Labs) provides faster navigation and safer editing. The pipelines list view shows all active pipelines, number of stages in each, and last modified date.

Multiple pipelines let you separate sales processes (new client acquisition vs. upsell workflows), track different products (dedicated pipeline per service line), organize by team or territory (each sales team or regional office gets own pipeline), standardize workflows (clear stages for every process), and improve visibility (see exactly where each opportunity stands without filtering through unrelated deals).

Each pipeline supports its own automation, custom fields, and stage-based triggers. This separation prevents workflows from interfering and lets you tailor automation to specific business line needs.

Key Configuration Options

Create pipeline: Click Create new pipeline, enter unique name (Consulting Sales, Onboarding Process, Service Delivery), save. Pipeline names must be unique within sub-account.

Define stages: Click Add stage and enter action-oriented labels. Common structures include Sales Pipeline (Lead Capture, Qualification, Appointment Scheduled, Proposal/Negotiation, Closing), Onboarding Pipeline (New Client, Discovery Call Booked, Service Selected, Payment Collected, Onboarding Complete), or Service Delivery Pipeline (Project Kickoff, Requirements Gathering, Implementation, Review/Approval, Closed).

Reorder stages: Use up and down arrows. Keep to 5-7 stages representing major milestones, not every micro-action.

Dashboard visibility: Toggle funnel and pie chart icons next to stages to control which stages appear in opportunity dashboards and performance reports.

Pipeline permissions: Click Key icon next to pipeline name to open Manage permissions panel. Choose sharing mode: Share with All Users (grant everyone View Only, Edit, or No Access), Share with Selected Users (pick individual users or roles), or Exclude Specific Users (available to everyone except manual exceptions).

Separate Workflows

Each pipeline supports its own automation. Use Pipeline Stage Changed workflow trigger and filter by pipeline name to target only the workflow you want to automate.

Add to Pipeline action places contact into selected pipeline and stage. Remove from Pipeline action pulls opportunities out of specific or multiple pipelines. This supports complex customer journeys where a single contact moves through multiple pipelines over time.

For example, new lead starts in Prospect Pipeline and moves through qualification stages. Once they become client, automation removes them from sales pipeline and adds them to Onboarding Pipeline. After onboarding completes, they enter Client Success Pipeline for ongoing relationship management.

Cross-Pipeline Reports

Dashboard widgets honor pipeline permissions and visibility settings. Configure reporting to include all pipelines or drill down into specific workflows.

Funnel charts visualize conversion rates for each pipeline separately. Track where opportunities drop off and identify bottlenecks unique to each sales process. Compare funnel performance across pipelines to see which workflows convert most efficiently.

Pie charts show opportunity distribution by pipeline and stage. Reveals where team attention is focused and helps balance workload across different business lines.

Win rates by pipeline show which offerings or processes perform best. If onboarding pipeline has higher win rate than cold outreach pipeline, you know where to invest resources.

Stage duration by pipeline shows which workflows move fastest. Long durations indicate process issues or insufficient follow-up. Compare similar stages across pipelines to identify best practices worth replicating.

Pro Tips

• Limit pipelines to what you truly need. More pipelines mean more configuration and more places to look. Start with 2-3 core workflows and add more only when business line is distinct enough to warrant separate tracking.
• Use consistent naming across pipelines. If one uses “Proposal Sent” and another uses “Quote Delivered” for same concept, team members waste time figuring out difference. Standardize terminology wherever possible.
• Document progression rules for each pipeline. Write criteria required before advancing to next stage. Share documentation during onboarding and reference during pipeline reviews. Clear rules prevent inconsistent data.
• Review pipeline health regularly. Weekly or monthly, remove outdated opportunities, update stage definitions as process evolves, and review conversion data to spot trends. Pipelines are living structures that should adapt as business changes.
• Track stage duration to identify bottlenecks. If “Proposal Sent” takes three weeks average but goal is one week, investigate delays and test solutions like automated reminders or better proposal templates.

Common Questions

Can I move an opportunity from one pipeline to another?

Yes. Use Add to Pipeline workflow action to place opportunity into different pipeline and stage. Use Remove from Pipeline to pull from original workflow. This supports customer journeys crossing multiple business processes.

Do I lose opportunities when I delete a pipeline stage?

No. When deleting stage, you choose another stage to move all existing opportunities to. System automatically transfers opportunities before completing deletion, preventing accidental data loss.

What’s the difference between View Only and No Access permissions?

View-only users can still move or update their assigned opportunities inside pipeline but cannot modify stage names, add new stages, or delete pipeline. No Access hides pipeline completely in all views, reports, and API responses.

Can I bulk-assign permissions to a role instead of each user?

Yes. Roles appear in permission selector. Everyone in that role inherits chosen access level, simplifying permission management for large teams.

Can I use the same stage name in multiple pipelines?

Yes. Stage names only need uniqueness within their own pipeline. You can use “Closing” in both sales pipeline and onboarding pipeline without conflict. When setting up workflow triggers, filter by pipeline name to avoid accidentally triggering automation in wrong workflow.