Working a single lead
Read and work one lead — stage, owner, the SLA clock, the timeline, calls, email and SMS threads, and where the lead actually came from.
Clicking a row in LeadsLead Manager opens that lead's own page. Everything about the person lives here across four tabs, and the quick actions along the top are how you act on them without leaving.
Before you start
You need the leads permission to open a lead, and edit to change the
stage, the owner or any field. Owners have both.
Quick actions
The buttons in the header are the things you actually do to a lead: Email, Text, Log call, Begin onboarding, Convert and Voice agent.
Each one appears only when its prerequisites are met — a Text button needs a phone number and an armed messaging channel, a Voice agent button needs the voice feature. A missing button almost always means a missing prerequisite rather than a missing permission.
Overview
The working tab. A hero panel runs down one side — the lead id, the name and status, the engagement score, the stage stepper and the first-touch SLA line — with the editable cards beside it.
| Card | What is on it |
|---|---|
| Hero | The engagement score on an arc gauge, the stage stepper, and the first-touch SLA as the line underneath |
| Stage | The status combobox — the lead's position in the pipeline |
| Assignee | Who owns the lead. Unassigned leads show up under the Unassigned queue lens |
| Key fields | Email, Phone, Website, Company and Updated, editable in place |
| Next step | Next follow-up, Last touch and Last activity |
The engagement score
A number from 0 to 100 that Zyan keeps for every lead. The gauge carries the number; one word beside it carries the judgement.
| Band | Score | Reads as |
|---|---|---|
| Cold | Under 40 | Nothing much has happened yet |
| Warm | 40 to 69 | There is real engagement to work with |
| Hot | 70 and above | Worth calling today |
A lead can also be marked hot in its own right, in which case it reads Hot whatever the number says. Either way it lands in the Hot lens back in the queue, under FiltersQueueHot.
Beside the gauge you get the score's movement over the last 7 days, and under it a 14-day line. The line is absent until the score has actually moved: no trend to draw is not the same as a flat one.
The seven statuses
| Status | Means |
|---|---|
| New lead | Just arrived. Nobody has made contact yet |
| Contacted | First touch has happened |
| Qualified | You have established there is real work here |
| Proposal sent | A proposal or quote is with them |
| Negotiation | Terms are being worked out |
| Won | The lead closed. This is the stored converted value |
| Lost | Dead. Hidden from the queue unless Include lost leads is on |
There is no separate Converted status
Won is the converted value. Moving a lead to Won and using Convert are two different acts: the status records the outcome, Convert creates the client record. Do both.
Activity & Calls
The timeline of everything that has happened to this lead — form submissions, emails, texts, logged calls, stage changes and automation runs, newest first.
A Calls sub-tab appears only once the lead has voice calls against it.
Call recordings are not available
Zyan does not store call recordings, so there is no audio to play back from the Calls view. Plan any review of what was said around the call notes and the timeline instead.
Messages
Email and SMS conversations scoped to this lead, so you can read the whole thread without going to the shared inbox.
Attribution
Where this lead came from. This is the tab to open when you are arguing about which channel is working.
| Field | What it tells you |
|---|---|
| Source | The intake route — website form, capture API, a provider, prospecting, visitor ID, manual |
| Form | The capturing form, where there was one |
| Area / Niche / Route | For prospected leads, the search that found them |
| Contact action and confidence | How the contact details were obtained and how sure Zyan is about them |
| Last synced | When the attribution record was last refreshed |
Capture API leads carry no form
A lead that arrived through the raw capture endpoint has a source but no Form — the endpoint does not know which of your pages the visitor was on. This is also why form-scoped automations never match those leads.
Deep-linking a view
The page writes its state into the URL, so you can send a colleague the exact view you are looking at rather than telling them where to click.
| Parameter | Controls |
|---|---|
?tab= | Which of the four tabs is open |
?section= | Which section within the tab |
?channel= | Which message channel on the Messages tab |
?filter= | The filter applied to the timeline |
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| A quick action button is missing | Its prerequisite is not met | Check the lead has the field it needs — a phone number for Text, an email for Email |
| The Calls sub-tab is not there | The lead has no voice calls yet | It appears with the first call |
| The lead's Email or Phone is blank after a form submission | The form field was never mapped to a lead column | Set Maps to lead field in the form's Build tab, then save and publish |
| There is no Form on the Attribution tab | The lead came through the capture API | Expected — raw-endpoint leads carry no form id |
| The lead vanished from the queue after you converted it | Converted leads leave the queue | Open it from the client record |