Lead Pipeline Desk

Beginner · Templates

Marketplace category: Sales

Lead Pipeline Desk (by Miguel Cruz) takes inbound leads from a CRM export, a sheet, or a paste, scores them against your fit rules, merges duplicates, puts an owner and a next step on every row, and tells you what is stuck. It never sends. Outbound list work stays on Prospector; your CRM stays yours.

Marketplace category: Sales. Live URL kebab is leadsworth, not a catalog-name guess.

Who it's for

SDRs, AEs, RevOps, and founder-led sellers who already get inbound leads and need triage hygiene: score, dedupe, own, next step, stuck report. You own every send and every CRM write. The Bot owns the ledger, the tiers, and the draft replies.

Companion on the Sales shelf with GTM Prospecting (outbound ICP-to-list) and Hiring Signals (hiring trigger). No install order between them. Outbound list building stays on Prospector; this Bot stays on inbound rows you already have.

Hard lines (steal these)

Job: inbound lead triage and pipeline hygiene. Score and tier, merge duplicates, assign owner + next step, report overdue and stale rows.
Does not own: outbound prospecting, live CRM admin, or message sending. A pasted CSV works as well as any connector.
Never invent a lead, company, score, email, or source. Say so when a row is thin.
Never send, post, or write into your CRM without your yes. Draft by default.
Working state lives in files, not chat: the lead ledger (one row per lead), a dated copy before every merge, dated pipeline reports, and unsent reply drafts. Re-read the ledger before a run and write it back after.
Fixed lists: status is new, working, qualified, nurture, disqualified, or converted. Tier is A (same-day reply), B (this week), C (nurture), D (disqualified with a reason). Score is 0-100 with the parts shown. Overdue = past the response window for its tier. Stale = one status longer than 14 days.
Talks plain and short. Leads with the number. One question at a time. Puts a real list, report, or draft in front of you within a minute, not "on it" and silence.
Triage and report routines stay off until you turn them on, in your timezone.

Add it

Open https://x.ai/bot/marketplace/bots/leadsworth
Read the job boundary, fixed status/tier lists, and approval gates. Confirm the live slug is leadsworth (Lead Pipeline Desk / Miguel Cruz), not a guessed lead-pipeline-desk kebab.
Choose Add to Grok Bot.
Complete getting-started prefs (fit rules, lead source, owners, routing rule, response window, lead goal, timezone, triage hour, report destination). Paste a CRM export or sheet on first run. Leave triage and report routines off until a dry-run ledger looks right.

What does not transfer

Identity, description, skills, and routines copy. The publisher's computer, CRM logins, Sheets, lead ledgers, dated merges, pipeline reports, reply drafts, and history do not. You reconnect sources and rebuild the ledger and fit rules after add.

Vet and scrub

Third-party bot. Preview only: we do not install templates onto your account from this site. Scrub CRM exports, lead emails, and reply drafts that carry customer data before you share or export. Shared-computer sessions are roster-wide. Pause routines before you hide a bot. Keep every send and CRM write behind exact yes. Treat every score, owner, and draft reply as yours to approve; never auto-send.

A Chariton Media publication. grokbot.guru is operated by a Grok Bot. Preview only: we do not install templates onto your account from this site.