Skip to main content

Resources / Documentation

setup-your-crm-pipeline


title: "Setup Your CRM Pipeline"

Set Up Your CRM Pipeline

This guide helps business users create a clear pipeline so leads are tracked, assigned, and moved efficiently.


Step 1: Open Pipelines / CRM

  • Instruction: Click CRM or Pipelines in the left menu, then Create Pipeline.
  • Expected: A pipeline canvas or list appears where you can add and reorder stages.
  • Why it matters: A visible pipeline structure lets you map your sales process and measure progress.
  • Troubleshooting: If the canvas fails to load, refresh and confirm your permissions.

Step 2: Add a few clear stages

  • Instruction: Add stages like New Lead, Contacted, Qualified, Proposal, Won.
  • Expected: Each stage displays as a column or list and can accept new leads.
  • Why it matters: Clear stages simplify handoffs and reporting.
  • Troubleshooting: Consolidate similar stages if reporting becomes noisy.

Step 3: Set the default entry stage

  • Instruction: In pipeline settings, set the default stage where new leads land (usually New Lead).
  • Expected: New contacts created by forms or imports appear in the chosen stage.
  • Why it matters: Ensures leads enter the correct workflow for timely follow-up.
  • Troubleshooting: If contacts land in the wrong stage, verify form mappings and import settings.

Step 4: Assign owners or teams

  • Instruction: Assign an owner or enable round-robin assignment so leads are distributed automatically.
  • Expected: Incoming leads are assigned and show up on assignees' dashboards.
  • Why it matters: Ownership drives accountability and faster follow-up.
  • Troubleshooting: If assignments fail, check user availability and role permissions.

Step 5: Add simple automations

  • Instruction: Create automations that notify owners on stage changes or move stalled leads into nurture flows.
  • Expected: Owners receive notifications and the automation runs when conditions are met.
  • Why it matters: Automations reduce manual work and prevent stalled deals.
  • Troubleshooting: Test automations with a sample lead and inspect automation history if steps fail.

Step 6: Test with a sample lead

  • Instruction: Create a test lead, watch it land in the default stage, and trigger stage changes to validate automations.
  • Expected: The test lead moves through the pipeline and triggers any configured notifications or tags.
  • Why it matters: Testing verifies mapping and automation behavior before using production traffic.
  • Troubleshooting: If the test fails, check logs and field mappings.

What success looks like

  • Leads consistently appear in the correct stage and are assigned to owners.
  • You can filter by stage to prioritize outreach and see stage conversion rates.

Back to Documentation