Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Business Process Automation 6 min read

CRM lead management workflow explained end to end

How a CRM lead workflow moves from capture to qualification, assignment, follow-up and handover, with the rules and evidence to configure.

E
EncryptTechBD · 0 comments
Presenter gesturing toward a wall of sticky notes
Photo: Direct Media / StockSnap

A CRM does not manage leads. People do, using the CRM as the record. The workflow is the set of rules that decides what happens next: who owns the lead, what must be true before it moves stage, how quickly someone must respond and what happens when the customer goes quiet. Configure those rules badly and the CRM becomes an expensive contact list.

This explainer follows a lead from first touch to handover through channels a Bangladeshi sales team will recognise: Facebook, WhatsApp, phone calls, referrals and walk-ins.

The workflow in one view

A workable lead workflow has seven stages. Each stage needs an owner, an exit criterion and a timestamp. Without those three, reporting becomes an opinion.

  1. Capture: record the enquiry and its source.
  2. Deduplicate: check whether this person or company already exists.
  3. Qualify: decide whether there is a real need, authority, timing and fit.
  4. Assign: give the lead to a named owner with capacity.
  5. First contact and discovery: confirm the need and agree the next step.
  6. Proposal and follow-up: send the offer and keep a dated next action.
  7. Handover or nurture: pass a won customer to delivery, or keep a not-yet-ready lead in a consented nurture path.

The stages are simple; the discipline is in the exit criteria and the exceptions.

Stage 1: capture and normalise

Leads arrive from more places than the website form: Facebook and Instagram lead ads, WhatsApp Business, phone calls, email, referrals, walk-ins and events. Each source should record the same core fields: name, mobile number, email where available, company, city, product interest, source, campaign and the date of consent.

  • Store the original source, not only "CRM". You cannot judge a channel you cannot see.
  • Normalise phone numbers to a consistent country format before saving them.
  • Record consent separately from the lead record, including what the person agreed to receive.

Exit criterion: a record exists with a valid contact method and a named temporary owner.

Stage 2: deduplicate and merge

Duplicates are expensive because two salespeople contact the same buyer with different offers. Match on mobile number first, then email, then a normalised company name plus city. Do not rely on name alone; "Rahim Traders" may exist in several districts.

Decide the merge rule before go-live. Usually the oldest record keeps the history, the newest record contributes the current contact details, and the merged record keeps the strongest consent status.

Exit criterion: one lead record, one owner and a visible source history.

Stage 3: qualify

Qualification is a judgement recorded as evidence, not a score invented to fill a field. Use a short framework consistently: does the buyer have a problem worth solving, can they decide or influence, is there a credible timeline, and does the deal fit our product and margin?

For each answer, record the evidence: what the buyer said, who else is involved, the deadline and the budget range discussed. A lead that fails qualification should be closed with a reason, not left in the pipeline to distort forecasts.

Exit criterion: qualification notes exist and the lead is either accepted or disqualified with a reason.

Stage 4: assign and start the clock

Assignment rules should consider territory, industry, language, existing relationship and current workload. Round-robin is easy to configure and easy to abuse: it ignores capacity and can send a large enterprise enquiry to the newest representative.

Once assigned, the response clock starts. Define a first-response target by channel and priority, then escalate when it is missed. The escalation should reach a manager, not only the salesperson's notification tray.

Exit criterion: a named owner has acknowledged the lead and a first-contact attempt is logged.

Stage 5: first contact and discovery

The first call or message has one job: establish whether a real opportunity exists and agree the next step. Capture the current process, the cost of the problem, the decision group, the timeline and the buying process. Log the outcome in the lead record, not in a personal notebook.

Use WhatsApp where the customer prefers it, but keep the CRM as the record. If the customer is not ready, set a specific follow-up date with a reason, and move the lead to nurture rather than leaving it open indefinitely.

Exit criterion: a discovery summary, a next step and a dated follow-up exist.

Stage 6: proposal and follow-up

A proposal stage needs version control. Record what was sent, when, to whom and at what price, including discounts and approvals. Follow-up cadence should be planned, with a stop rule when the buyer asks for space.

Every open opportunity should have a next action date. Close lost deals with a reason from a controlled list so the pattern is visible across the team.

Exit criterion: proposal sent, decision date known and next action scheduled.

Stage 7: handover or nurture

A won deal is not the end of the workflow. Handover to delivery or onboarding should carry the commitments made during the sale: scope, dates, contacts and any special terms. The receiving team should acknowledge the handover, not discover it on the start date.

A lost or dormant lead stays in nurture only with a lawful basis and a frequency the person accepted. Suppression rules belong in the workflow, not in one person's spreadsheet.

Exit criterion: handover acknowledged, or nurture status and review date recorded.

The rules layer that makes it work

  • Required fields by stage: ask for data when it is needed, not all at capture.
  • Stage exit criteria: written in plain language and enforced by validation where possible.
  • Duplicate rules: one matching method, one merge rule and one owner for exceptions.
  • Response targets: by channel and priority, with escalation paths.
  • Consent and retention: purpose, channel, date and deletion rules.
  • Automation limits: humans approve discounts, disqualification and handover exceptions.

A worked example

A distributor receives a Facebook lead for a product usually sold through dealers. The form creates a record with the source campaign, the buyer's district and a mobile number. The deduplication check finds an existing dealer account with the same number, so the lead is linked to that account rather than creating a second one.

Because the dealer already has an owner, the lead routes there with a task. The owner calls, discovers the buyer needs a trial quantity before committing to a monthly order, and records the trial request, the decision-maker and the review date. The opportunity moves to a sample stage. When the order arrives, handover includes the trial feedback and the agreed delivery schedule.

Workflow metrics

  • Median time to first response, by channel and owner.
  • Lead-to-qualified conversion, using a fixed qualification definition.
  • Age of open leads by stage, and the number with no next action date.

Where this fits in our work

If the workflow crosses several systems or the current CRM cannot enforce the rules, start with Business Automation. The pricing page explains how discovery and implementation are scoped. For a messaging-led example, read how WhatsApp workflow automation matures with the business.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes