deal-followup-automation

name	deal-followup-automation
description	Automates post-meeting and post-touch follow-ups for sales deals. Use when the user asks to "follow up with everyone I met", "send follow-ups", "chase my open deals", "draft follow-up emails", "log next steps in Salesforce", or "close the loop after my meetings". Produces tailored follow-up emails plus matching Salesforce follow-up tasks, and logs next steps on the opportunity.
license	MIT
metadata	{"author":"Scott Adams, Microsoft","version":"1.0"}

Deal Follow-up Automation

What this skill does

Turns "I just had a bunch of meetings" into finished follow-ups: a tailored email to each contact (drafted with Cowork's built-in email skill) and a matching Salesforce follow-up task, with next steps logged on each opportunity. This is co-work, not chat — it writes to both Outlook and Salesforce across multiple records.

Inputs to gather

• Which deals/contacts? (a named account, "this week's meetings", or a list)
• Time window for recent activity (default: last 7 days).
• Tone and any specific asks (pricing, legal, next meeting, references).

If the user is vague, resolve context first with search_reference_records.

Workflow

1. Identify the deals. Use search_reference_records to map names to IDs, or get_open_opportunities / search_opportunities for a set. For one account, use get_account_360 to pull the full picture in one call.
2. Read recent signals per deal. Call get_activity_timeline and get_open_tasks to see what happened and what's outstanding. Use get_contact_activity_history for the specific contact when needed.
3. Summarize the meeting context. Call prepare_email_summary to get a grounded, deal-specific summary you can base the email on. Never invent facts — only use what the connector returns.
4. Draft one follow-up email per contact using the built-in email skill. Follow references/email-templates.md for structure (recap → value → clear next step → single CTA). Keep each email under ~150 words.
5. Create a matching Salesforce follow-up task for each: build it with draft_create_task, review the draft, then commit with create_record (object Task), linking it to the contact/opportunity (WhatId/WhoId) with a due date from the agreed cadence in references/followup-cadence.md.
6. Log the next step on the opportunity. Use get_opportunity_for_update then update_record to set the NextStep field.
7. Confirm before sending/writing. Show the user every email draft and the list of tasks. Only send emails and commit tasks after explicit approval.

Output format

Present a single review table before any write:

Contact	Account	Email subject	SF task	Due	Next step logged
Emma Clarke	NorthBridge AM	"Recap + pricing next steps"	Call: confirm pricing pack	+3d	"Book decision committee review"

Then: "Reply send to deliver all emails and create the tasks, or tell me what to change."

Guardrails

• One CTA per email. Don't stack asks.
• Match the cadence in references/followup-cadence.md; don't over-contact.
• Never fabricate commitments, prices, or dates — pull them from Salesforce.
• create_record, update_record and sending email are consequential: confirm.

Additional resources

• references/email-templates.md — follow-up email patterns by scenario.
• references/followup-cadence.md — timing and task-type guidance.