CRM

No-Show Escalation: Outlook Empty Meetings to Salesforce Tasks

Catches Outlook calendar meetings nobody attended and creates a tiered set of Salesforce follow-up tasks for the deal owner.

CategoryCRM
Enginesim
Difficultyintermediate
Triggerschedule
Steps6
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled read of just-ended Outlook eventsOutlook
  • LogicIsolate meetings with no attendee present
  • ActionIncrement no-show count on Salesforce opportunitySalesforce
  • LogicBranch on first vs. second no-show
  • ActionCreate owner task or escalate to managerSalesforce
  • OutputNotify owner in Microsoft TeamsMicrosoft Teams

What it does

When an Outlook meeting ends with no one on the invite side present, this workflow records the no-show on the related Salesforce opportunity and creates a follow-up task for the deal owner. If the same contact has now no-showed twice on the same opportunity, it raises a higher-priority task and loops in the owner's manager.

When to use it

Reach for this when your org runs on Outlook and Salesforce and you need no-show follow-up to be owned, dated, and accountable — not buried in a rep's inbox. The two-strike escalation is for deals worth a manager's attention before they slip.

How it works

  1. 1A scheduled job reads Outlook calendar events that have just ended and checks attendance signals.
  2. 2A filter isolates meetings where every external attendee declined or never responded.
  3. 3The workflow matches the attendee to a Salesforce contact and increments a no-show counter on the linked opportunity.
  4. 4A branch checks the counter: first miss creates a normal reschedule task for the owner; second miss creates a high-priority task and adds the manager as a follower.
  5. 5The created task and escalation status are delivered back to the owner via Microsoft Teams.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect OutlookMail, calendar, contacts.
  2. 2
    Connect SalesforceAccounts, opportunities, cases.
  3. 3
    Connect Microsoft TeamsChannels, chats, files.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.