CRM Follow-up & Pipeline Assistant

Setup inputs

• Lead sheet
• Inbox or chat exports
• Offer list
• Follow-up rules
• Owner approval rule

Sample sources

• lead spreadsheet
• recent replies
• offer list
• follow-up examples

First run workflow

1. Merge lead sources
2. Classify lead stage
3. Detect missing next action
4. Draft follow-ups
5. Queue owner approvals

Outputs

• ranked lead queue
• stuck deal list
• approval-only follow-up drafts
• pipeline summary

Owner

• First action: Approve the first proof target: A ranked pipeline showing hot leads, stuck deals, missing next actions, and drafted follow-ups for approval.
• Approval focus: Scope, price, payment route, external sends, connector writes, and first production run.
• Success signal: Owner can decide whether the worker saves time, reduces risk, or moves revenue before any recurring claim.

Operator

• First action: Collect the starting source pack: lead spreadsheet, recent replies, offer list.
• Approval focus: Confirm sample quality, missing fields, edge cases, and whether the first proof matches daily work.
• Success signal: Operator can repeat the workflow with less manual checking and fewer missed follow-ups.

Technical admin

• First action: Map the approved source boundary for sales team data before any connector access.
• Approval focus: Accounts, permissions, API/export path, audit logs, vaulting, and rollback plan.
• Success signal: Technical admin can explain what the worker can read, what it cannot do, and how every action is logged.