Operating rule
A Telegram lead state machine moves people through observable states: observed, reviewed, eligible, queued, contacted, replied, qualified, and closed. Every transition needs an event, owner, timestamp, and next action. Suppressed and incident-held are control states that override campaign eligibility. Automate factual transitions such as delivered or replied, but keep fit and outcome decisions reviewable.
Labels such as warm and promising feel useful until two teammates interpret them differently. A state machine replaces vibes with events and makes the next action predictable.
The model is not a sales methodology. It is an operational contract between research, campaigns, inbox, tickets, and reporting.
Workflow essentials
01A practical Telegram lead-state model.
02Mechanical versus judgment transitions.
03Override states for suppression and incidents.
04Audit fields that keep the pipeline trustworthy.
The core states
| State | Entry event | Required next action |
|---|---|---|
| Observed | Identity appears in an approved source | Review source and minimum evidence |
| Reviewed | A reviewer records fit decision | Exclude, recheck, or mark eligible |
| Eligible | Fit and contact appropriateness pass | Assign campaign or owner |
| Queued | Approved campaign-recipient record exists | Attempt or cancel |
| Contacted | Delivery is confirmed | Wait, follow decision tree, or handle reply |
| Replied | Inbound response arrives | Stop sequence, assign, classify |
| Qualified | Human confirms fit and a plausible next step | Advance, park, win, or lose |
| Closed | Final outcome or approved sequence end | Feed reason into learning |
Use override states
Overrides should block queue creation regardless of the ordinary stage. A new import must not move a suppressed person back to Eligible.
- Suppressed: direct-marketing objection or other no-contact rule prevents eligibility.
- Incident hold: account, data, client, or security issue freezes action while evidence is preserved.
- Ownership hold: the lead cannot advance until workspace or client ownership is resolved.
- Data review: conflicting identity or stale evidence requires manual resolution.
Automate facts, record judgment
Record the criteria version and reason for human decisions. This allows the team to improve qualification without rewriting history.
| Automatic | Human reviewed |
|---|---|
| Queued to Contacted after confirmed delivery | Observed to Eligible |
| Contacted to Replied after inbound message | Replied to Qualified |
| Cancel follow-ups after reply or suppression | Qualified to Won or Lost |
| Incident signal to Hold | Release from Hold |
Require five transition fields
State alone is not enough. A lead marked Qualified with no owner or next action is a reporting artifact, not managed work.
- Previous and new state.
- Triggering event.
- Actor or service.
- Timestamp and workspace context.
- Reason, next action, and due time where applicable.
Audit impossible transitions
- Closed to Queued without a new approved review.
- Suppressed to Contacted.
- Observed directly to Contacted with no qualification or approval.
- Replied while follow-ups remain active.
- Qualified with no human decision.
- Cross-workspace state change.
Trust test: select twenty leads and reconstruct every transition. If the system cannot explain who changed the state and why, the pipeline is not auditable.
Research note
The states are an adaptable TeleBoost framework. Organizations may add stages, but should preserve explicit triggers, ownership, control overrides, and terminal reasons.
Make the handoff operational
Replace one ambiguous status with a mechanical entry rule this week. Then automate only the transitions the system can observe reliably.
A useful CRM state tells the next operator what happened and what must happen next.
Keep states close to events: TeleBoost lead management connects lists, campaign contact, replies, tickets, and team ownership.
Continue the operating system
Related TeleBoost guides
Evidence base