The complete path a lead travels from first contact to closed deal — and how a TeleSales agent, a manager, and the super admin each watch it happen.
It isn't a straight line. A lead loops through follow-ups until a decision is reached, and it can branch out to reassignment at two different points — when the owning agent is on leave, and when follow-ups keep getting missed.
flowchart TD
A["Lead Source
website · call-in · referral · campaign"] --> B{"New or existing
customer?"}
B -->|new number| C["Lead created
status: New"]
B -->|existing customer| C
C --> D{"Assignment engine"}
D -->|round robin| E["Assigned to agent
status: Assigned"]
D -->|owning agent on leave| D2["Reassigned to
next available agent"]
D2 --> E
E --> F["Agent notified · lands in
My Leads queue"]
F --> G["Follow-up N: contact attempt"]
G --> H["Outcome + note logged
mandatory, every attempt"]
H --> L{"Decision reached?"}
L -->|not yet| I{"Next follow-up
due on time?"}
I -->|on time| G
I -->|missed| J["Marked Overdue
reminder sent to agent"]
J --> K{"3 consecutive
misses?"}
K -->|yes| ESC["Escalated to manager
+ reassigned"]
ESC --> F
K -->|no| G
L -->|customer ready to buy| M["Converted"]
L -->|declines / no budget / lost| N["Not Converted
reason captured"]
M --> O["Deal created
value · product · close date"]
N --> P{"Worth revisiting
later?"}
P -->|yes| Q["Recycled to Nurture pool"]
P -->|no| R["Closed – Lost"]
O --> S["Reports & dashboards"]
Q --> S
R --> S
J --> S
What actually happens at each stage, told from the seat of the TeleSales agent doing the work.
A lead is captured from a defined lead source — website enquiry form, inbound call, referral, ad/campaign click, or manual entry by an admin for a walk-in. The source is a required field on every lead, not free text, so later reporting can trust it.
Before a new record is created, the phone number is checked against existing leads and customers. A genuine duplicate links back to the existing customer record instead of spawning a second, disconnected thread. A first-time number creates a fresh lead with status New, timestamped and unassigned.
The assignment engine runs round robin across active TeleSales agents by default, skipping anyone currently marked on leave and handing their turn to the next agent in rotation. A manager can override with a manual assignment when needed.
On assignment, status moves New → Assigned, and the record stamps the owning agent and the assignment time — the clock every later "day since assignment" and overdue calculation is measured from.
A My Leads queue: today's due follow-ups surfaced first, overdue items visibly flagged, and a count of anything freshly assigned. Opening a lead shows the customer's details (including any dynamic/custom fields captured for that source), the full note and call history, and any attached call recordings — so the agent never starts a call blind, even on a reassigned lead.
Follow-up 1 is the first contact attempt, due within a set number of days of assignment. The agent calls, logs the outcome — connected, no answer, busy, switched off, wrong number — and if connected, records what the customer said. If the call doesn't end in a decision, the agent schedules Follow-up 2 with a due date before the lead can be closed out for the day.
Needs confirmation · exact day-offset for Follow-up 1Follow-ups are not capped at two. Follow-up 2, 3, 4… continue on a defined cadence until the lead reaches a decision or is explicitly closed. Every follow-up opens with the full history of the ones before it, so cadence and rules stay consistent no matter which agent is holding the lead by the third or fourth attempt.
Needs confirmation · day-offset cadence per follow-up numberA note is mandatory after every contact attempt, connected or not — the lead can't be marked done for that follow-up with a blank note. Entries are timestamped, attributed to the agent, and append-only: an edit adds a new entry rather than silently overwriting the old one, so the trail stays trustworthy for whoever reads it next, including a manager auditing a lost deal.
Each attempt is logged with its channel (call, SMS, email, WhatsApp where applicable), an outcome tag, and — where telephony is integrated — duration and a call recording. The recording attaches directly to the lead's timeline, so a Converted or Not Converted decision can be checked against what was actually said on the call, not just the agent's summary of it.
Two layers. A recurring due-soon / overdue nudge goes to the owning agent by phone-style alert and email as a follow-up date approaches and passes. Separately, an escalation reminder fires once a lead racks up a defined number of consecutive misses — at which point the manager is looped in too, not just the agent.
Needs confirmation · notification interval & miss thresholdA follow-up not completed by its due date is marked Overdue — never silently dropped. The owning agent keeps the lead through the first miss or two while reminders nag at the set interval. Once misses hit the threshold, the system escalates automatically: the manager is notified, and the lead is re-queued through round robin to a fresh agent, carrying its full miss history so nothing gets re-tried blind.
Conversion is recorded the moment the customer commits, not as a separate closing step. The agent sets the lead to Converted, and the system requires the minimum deal details — product/service, agreed value, expected close date — before it accepts the change. That requirement is what turns a verbal "yes" into a record the business can act on.
Status locks to Converted and the follow-up cadence on it stops — no more overdue nagging on a won lead. A Deal record is created and linked back to both the lead and the customer; if the customer doesn't yet exist as a standalone record, one is created from the lead's details so future business sits under their name, not buried inside an old lead thread.
The agent sets Not Converted and must give a reason — price, no budget, lost to a competitor, bad timing, unresponsive after N attempts, or invalid/junk. "Not converted" alone tells a manager nothing; the reason is what makes the number useful. Recoverable reasons (timing, budget) route the lead into a Nurture pool for a scheduled re-attempt; dead ends (invalid number, hard no) close permanently as Closed – Lost.
Automatically, not as a re-entry task. The instant a lead flips to Converted, the system opens a Deal pre-filled with the customer, source, owning agent, and the value/product/close-date captured at conversion. The Deal becomes the object pipeline and revenue reporting is built on; the original Lead stays intact as the historical record of how that deal was actually won.
The same data, at two wider angles — one runs the sales floor, the other configures the system underneath it.
A team dashboard: every agent's queue and load balance, overdue and missed counts per agent, conversion rate by agent and by source, and the ability to manually reassign or rebalance leads when round robin alone isn't cutting it. Managers can review notes and call recordings for any lead on their team, and step in on an escalation — but they don't touch system-wide configuration.
Super Admin sits above every team. That's where lead sources, the round-robin pool, dynamic/custom field definitions, notification cadence, and message templates (including the leave-coverage message) actually get configured. Visibility is org-wide — every team, every agent, every lead, every deal — plus an audit trail of who reassigned what, edited a field, or changed a status, which a manager-level view has no need for.
| Capability | TeleSales agent | Manager | Super admin |
|---|---|---|---|
| Lead visibility | Own leads only | Own team's leads | All teams, org-wide |
| Log calls & notes | Own leads | View any, on team | View any, org-wide |
| Manual reassignment | — | Within own team | Any lead, any team |
| Call recordings | Own leads | Team's leads | All leads |
| Configure round robin / sources | — | — | Full control |
| Define dynamic/custom fields | — | — | Full control |
| Manage message templates | — | Request/suggest | Full control |
| Reports scope | Own performance | Team performance | Org-wide, all filters |
| Audit trail | — | — | Full access |
Reports read off the same status and activity data the flow above already produces — nothing gets entered twice for reporting's sake. Six roll-ups cover what's asked for:
Customer-wise lead report · every lead and deal tied to one customer, in one place.
Source-wise performance · which lead sources actually convert.
Converted vs. Not Converted · with the loss-reason breakdown behind the "not converted" number.
Pending / overdue follow-ups · by agent, by age, so nothing quietly goes cold.
Agent performance · conversion rate, average follow-ups to close, missed-follow-up rate.
Deal pipeline & revenue · open deals by stage, closed-won value by period.
Each report scopes to whoever's viewing it — an agent's own numbers, a manager's team, or Super Admin with every filter open — per the visibility table above.
Every state a lead, a follow-up, a contact attempt, or a deal can sit in. Statuses marked proposed aren't in the original notes — they're gaps a working CRM needs filled, carried over from the earlier requirements review.
| Status | Meaning |
|---|---|
| New | Captured, not yet assigned |
| Assigned | Owner set, no contact yet |
| In Progress | At least one follow-up logged, decision pending |
| Overdue | Next follow-up missed |
| Escalated | 3+ consecutive misses, reassignment in motion |
| Converted | Committed; deal created |
| Not Converted | Declined; reason captured |
| Nurture proposed | Not converted, worth a future re-attempt |
| Closed – Lost | Not converted, no future value |
| Junk / Invalid proposed | Duplicate, wrong number, spam |
| Status | Meaning |
|---|---|
| Scheduled | Due date set, not yet due |
| Due Today | Falls due today |
| Completed | Contact attempt made & noted |
| Missed / Overdue | Not actioned by due date |
| Rescheduled | Due date moved, at customer's or agent's request |
| Cancelled | Lead closed before this one came due |
| Outcome |
|---|
| Connected – Interested |
| Connected – Needs more time |
| Connected – Not interested |
| No answer |
| Busy |
| Switched off / unreachable |
| Wrong number |
| Status |
|---|
| Draft / Created |
| In Progress |
| Won / Closed |
| Lost / Fell Through (edge case: converted lead, deal doesn't finalize) |