Design lead stages and appointment results

A lead status describes where a contact sits in your pipeline. An appointment type describes the kind of visit. A result reason explains the outcome of a visit or sales conversation. A job type describes the work being sold. Keeping these lists distinct makes reports easier to interpret.

Open Settings → Lead Statuses. The list supports names, colors, display order, active status, and a default. Use short names with a documented action attached to each stage.

Use Settings → Appointment Types for visit labels and colors. Use Result Reasons for outcome labels grouped as won, lost, or pending. Examples include Sold, No Decision, and Not a Fit; adapt them to your process.

Decide how a result should affect the lead, then configure that mapping in Rules. Selecting a result and changing a lead stage are separate actions unless a rule connects them.

Prefer deactivating a retired option over removing historical context. Avoid renaming a status to mean something entirely different; old reports may then appear to describe a process that did not exist. Review rules, forms, and queues when changing a status.