Engage+
The Daily Action Plan is the centerpiece of your dashboard: five leads, picked for you, refreshed every day at midnight in your timezone. Each lead is scored by audit urgency, fleet size, contactability, and how recently you've touched it. Work through the five and you've done your most important outreach for the day.
Why These Five Leads? #
| Signal | Score boost | Why |
|---|---|---|
| Hot lead window (audit deadline near) | +100 | Carriers with audit deadlines are most likely to need help now. |
| Recent authority (under hot window) | +70 | Brand-new carriers haven't locked in a clinic yet. |
| New entrant (under 18 months) | +40 | Still building their compliance program. |
| High utilization (1.5x+ drivers/truck) | +30 | Indicates driver turnover — ongoing physical demand. |
| 10+ drivers | +25 | Volume opportunity. 5–9 drivers gets a smaller +12. |
| Unsatisfactory safety rating | +25 | Compliance crisis = strong outreach moment. |
| Phone on file | +15 | You can actually reach this lead by phone. |
| HAZMAT carrier | +15 | Premium-tier physicals = higher revenue per visit. |
| Email on file | +10 | Email outreach is a backup channel. |
| Daily rotation factor | +0 to +20 | Pseudo-random factor that varies the queue day to day. |
What's Excluded From the Queue #
- Removed from your lists — if a lead was removed from your list, it doesn't come back through the queue
-
Already won or lost — leads in
converted,disqualified,not-interested, orarchivedstages are skipped (unless you updated them today) - No phone AND no email — if there's no way to reach the carrier, they can't be the most important lead today
- Skipped today — leads you explicitly skipped reset at midnight, but not before
Each Lead Card #
- Rank number (1 to 5) on the left — click to manually mark the lead contacted
- Carrier name + DOT number
- City and state
- Driver count + fleet size
- Quality badges (Hot, High Value, New Entrant, HAZMAT, At Risk)
- Action buttons — Contact Card, Call, Email, Skip
Rank-click vs. action buttons
Clicking a card's rank number manually marks the lead as contacted but doesn't open anything. Clicking an action button (Call, Email, Contact Card) opens the matching tool and logs the contact automatically when you complete the action.
Working Through the Queue #
Open the dashboard
The queue is the first card on your dashboard once you log in.
Pick lead 1
Read the rank-1 card. Decide call vs. email vs. contact card based on what's on file.
Take the action
Use the action button. The matching modal opens with all the lead context already loaded.
Log the outcome
Add a note (or use the call modal's built-in outcome buttons). The card's progress dot turns green.
Repeat for leads 2–5
All five dots filled = you're done for the day. The queue refreshes tomorrow.
Skip if needed
If a lead really doesn't fit (wrong area, duplicate, etc.), use Skip. It hides for today only.
Automatic Status Updates #
attempted. A "Contacted via Daily Action Plan" note is also added to the lead's activity feed. Leads that are already past the New stage keep their existing status — the action plan never demotes a lead. Daily Refresh & Rotation #
Same five all day, fresh five tomorrow
The queue is generated once per day using a date-based seed. If you refresh the page mid-day, you get the same five — minus anyone you've already actioned. At midnight in your timezone, the seed changes and a new five appears.
- Lead rotation: a small random factor in the score keeps the queue fresh; you won't see the same "perfect 5" every day even if no data changes
- Skipped leads stay skipped only for today — they re-enter the candidate pool at midnight
- Contacted leads drop out for longer; "attempted" leads can come back, but converted/lost leads are gone unless you updated them today
Trial-Plan Behavior #
Trial users get 3 unlocks
On the Trial plan, the daily queue still shows five leads — but contact info is masked. You can use up to 3 unlock credits during your trial to reveal full contact info on three leads of your choice. The unlocks-remaining counter appears in the queue header.