Lead and sales ops
Sequences and routing
Who gets the lead, and when it expires.
ops.reckap.com/auto/sequences
Lead queue, CRM write-back
Reckap auto desk| Lead | Score | Route |
|---|---|---|
| Acme LLC | A | AE, west |
| North Co | B | SDR queue |
| Vista Inc | Hold | Expire 7d |
One system of record - not a second inbox.
Assignment, nudges, and expiry so leads do not rot in a queue.
Who gets the lead, and when it expires.
Problems we hear, outcomes we ship
Buyer problems
- Leads never expire, so nobody feels urgency.
- Routing ignores territory or skill.
Outcomes
- Route rules with owners.
- Expiry and recycle path.
What is included
- Assign rules
- Nudge cadence
- Expiry
- Recycle path
How this work is shaped
Same desk language as the parent lane - scoped to this package.
ops.reckap.com/auto/sequences
Route + expire
AssignNudgeExpire
Who owns the lead.
How we deliver
Click a step - the desk below updates. That panel is a preview, not another step.
Step preview
01, Assign
ops.reckap.com/auto/map
Map, current path
Reckap auto desk| Step | Owner | Today |
|---|---|---|
| Request | Ops | Email thread |
| Approve | Manager | No log |
| File | Shared drive | Manual |
Draw the path before you connect another tool.
More in this lane
Other packages under Lead and sales ops.
FAQ
Next step
Ready to talk scope?
Bring the job, the systems you already run, and who owns the handoff. We write the rest.