Skip to content

Tutorial: Lead approval workflow

When a rep finds an outlet in the field that is not on the campaign list, they submit a lead request. Managers review those requests in Approvals before the lead enters the pipeline.

Reps follow the complementary guide: New lead, approval, and visit.

flowchart LR
A[Rep submits lead] --> B[Pending in Approvals]
B --> C{Manager decision}
C -->|Approve| D[Lead created on campaign]
C -->|Reject| E[Rep sees reason]
E --> F[Rep resubmits]
F --> B
D --> G[Rep logs visit]
  1. Sign in as a sales manager or admin.
  2. Go to Workspace → Approvals.
  3. Filter by Status → Pending and optionally by Campaign.

Approvals queue with status and campaign filters

The page lists every lead creation request waiting for review.

  1. Click a request in the list.
  2. Read the creation fields the rep filled — name, address, identifiers, contacts.
  3. Confirm the outlet is not a duplicate of an existing lead on the campaign.

If you need to create a lead yourself (no rep submission), use Leads → Create lead instead:

Create lead dialog for managers

Managers can create leads directly without the approval queue.

ActionWhen to useResult
ApproveOutlet is valid and newLead is created; rep sees it on their list
RejectDuplicate, wrong territory, or incomplete dataRep sees your reason and can resubmit

After Approve, assign the lead to the submitting rep (or bulk-assign) if it is not auto-assigned.

Once the lead exists, the rep opens Leads → [lead] → Visits → Add visit to log field activity. Visits feed team Dashboard KPIs and Reports.

Visits list after the lead is in the pipeline

  • Pending queue reviewed regularly (daily or per campaign rhythm)
  • Duplicates rejected with a clear reason
  • Approved leads assigned to the correct rep
  • Reps notified implicitly when the lead appears on their book