Held leads and the Leads tab
Where single leads wait for a yes or no, why a lead is held, the fix for each reason, and what the Today card's speed to lead measures.
By Operelio team · Updated October 20, 2026
On this page8
Where the Leads tab is
Open Trails and click Leads on the top row. The tab lists every lead your trails took in one at a time, by webhook or email, from every trail. Files go through runs instead, on each trail's page, but rows of a file that the Scorecard sends to review wait in To review too.
A trail's page links here from Recent leads, and opening the tab from a trail shows only that trail's leads. Show every trail clears it. Search leads finds a lead by its whole email address, an @domain or part of a name, from the last 90 days.
| View | What it lists |
|---|---|
| To review | Leads waiting for a yes or no, oldest first, with each lead's score and the rules behind it. The owner is picked after your yes. |
| Held | Leads that can't go on until something is fixed, each with the reason it's held. |
| All | Every lead from the last 90 days, newest first, with where it is now. |
Leads that scored 1 or 2, and leads someone chose to keep, show only in All, marked Kept here.
Saying yes or no
A lead lands in To review when its score is set to wait for review (score 3 unless you change the scorecard) or a routing rule sends it to Review queue, and every lead does during a trail's first week. Yes, send sends it on to its owner in your CRM. No has two choices: Drop leaves it out for good, and Keep in Operelio keeps it in All, never sent.
To decide on several at once, select them, or click Pick every lead on this page, then click Yes, send or No to, which show the number you picked. A bulk No drops the leads. One decision takes up to 100 leads.
Anyone in the workspace can say yes or no, retry a lead or pick its owner.
A trail's first week
For seven days after a trail is first switched on, every single lead it takes in waits in To review, whatever its score. The Leads tab names the trail and the day its first week ends. After that, each lead follows the trail's scorecard and routing rules.
Why a lead is held, and the fix
The Held view shows each lead's reason. Retry runs the lead again from the step that held it. No leaves it out.
| Reason | What to do |
|---|---|
| A rule names an owner who isn't active in your CRM any more. | Click Pick an owner and choose someone from your CRM, or Send with no owner. To stop it happening again, change the routing rule. |
| Your CRM connection has expired. | An admin clicks Reconnect. Everything waiting on that connection then goes, in the order it arrived. |
| We tried your CRM 9 times over about 2 days and couldn't reach it. | Each try waits longer than the one before. Press Retry once your CRM is back. |
| Your CRM refused this lead, with the CRM's message. | Fix what the message names, usually in your CRM or the trail's mapping, then press Retry. |
| A step in the trail couldn't run on this lead. | Fix the step on the trail, then press Retry. |
| No email or name arrived. The form may have changed. | Check what the form or sender now sends, and press Retry or No. |
| A new source arrived with different columns. | Open the trail and map the source on its Map sources tile, or click Run without mapping. Every lead waiting on that source then goes on. |
| This month's lead allowance and jobs are used up. | Add a job pack or move up a plan, then press Retry. |
| Arrived before this trail could run it. | The lead waited more than 24 hours for its first run. Press Retry to send it. |
| This trail has no CRM set up for single leads. | An admin opens the push tile's What gets created tab, clicks Use these settings and puts the sandbox live, then clicks Send the N leads there. |
| Single leads can't be sent to Pipedrive yet. | Press No. Leads that arrive one at a time can only go to HubSpot or Salesforce. |
| Your plan doesn't run trails on live leads. | Free keeps these leads for 24 hours. Move up to Starter by then and they go to your CRM on their own. |
A lead that's retrying on its own shows Retrying, and its page lists each try. Retry now tries again at once.
A lead's page
Click a lead to open its page. What happened lists each stage it went through: arrived, read, checked against your CRM, scored, routed, sent or held. This lead shows its trail, where it came from, its score and owner, and its record in your CRM once it's there. As it arrived shows what was sent in.
The Today card and speed to lead
The Today card sits above the views and counts single leads since midnight. Which trail narrows it to one trail when you have more than one.
Speed to lead is the median time from a lead arriving to it reaching your CRM with an owner: half of today's leads that reached your CRM got there faster. Below it is last week's figure. A lead that waited for a yes or no counts its waiting time too.
By stage counts how many leads arrived, were checked against your CRM, were scored, were routed to an owner and reached your CRM today. The bar under it splits the scored leads into routed, to review, kept here and held. Click to review or held to open that view.
Who hears about held leads
When a lead is held for a reason someone has to fix, the people who hear about the trail get a note in Operelio and an email, at most once an hour for each trail. An expired CRM connection is told once a day. Leads waiting for a yes or no send a reminder in Operelio once a day when the oldest has waited 24 hours.
Related
Frequently asked questions
How long does a held lead wait?
Until someone sends it or says no, up to your plan's retention. A lead still waiting when its details reach your plan's retention is left out, because there is nothing left to send.
Can I edit a lead before it's sent?
No. Fix the step, mapping or rule that held it, then press Retry.
Ready to get started?
Upload a file and run your first transformation. Free, no credit card required.