SALES

Mutual Action Plan Overdue Milestone Auto-Nudge

Each morning it scans open opportunities for mutual action plan milestones whose committed date has passed without completion.

CategorySales
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekday morning schedule
  • ActionQuery open opportunities + MAP milestonesSalesforce
  • LogicKeep milestones past committed date and not Done
  • LogicGroup overdue items by deal + buyer owner
  • ActionDM deal owner the slipped-milestone digestSlack
  • OutputLog nudge as a Salesforce taskSalesforce

What it does

Reads the mutual action plan (MAP) milestones stored on your Salesforce opportunities, finds any whose committed date is in the past but status is not Done, and identifies the buyer-side owner responsible. It posts a tidy digest to the deal owner so a stalling deal never slides unnoticed.

When to use it

Run this when your team manages MAPs as structured records on the opportunity and you want a daily safety net that surfaces slipped commitments before a forecast call, instead of relying on reps to manually re-read every plan.

How it works

  1. 1A daily schedule fires each weekday morning.
  2. 2Query Salesforce for open opportunities and their related MAP milestone records.
  3. 3Filter to milestones where committed_date < today and status != Done.
  4. 4Group the overdue milestones by deal owner and buyer-side owner.
  5. 5For each owner with slipped items, post a Slack DM listing the deal, the silent buyer contact, and how many days past commit.
  6. 6Write a summary line back as a Salesforce task so the nudge is auditable.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SalesforceAccounts, opportunities, cases.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.