SALES

Escalate stale discount approvals in Microsoft Teams

Runs on a schedule to find discount approval requests that have sat unanswered past their SLA and escalates each to the next approver in Microsoft Teams.

CategorySales
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerHourly schedule fires
  • ActionQuery Salesforce for pending approval requestsSalesforce
  • LogicFilter to requests past SLA / escalation window
  • ActionReassign escalated approvals to backup approverSalesforce
  • OutputNotify approvers and post summary in TeamsMicrosoft Teams

What it does

This workflow scans open discount approval requests on a schedule and finds any that have exceeded their response SLA. For each stale request it pings the original approver, and if the wait has crossed the escalation window it reassigns the approval to that person's backup or manager — posting the handoff in Microsoft Teams so the deal keeps moving.

When to use it

Use it when discount approvals quietly pile up and reps lose deals waiting on an out-of-office manager. It guarantees every pending request gets a nudge and a clear escalation path without anyone manually chasing approvers.

How it works

  1. 1A scheduled run (e.g. hourly) queries Salesforce for approval requests in a pending state.
  2. 2The workflow calculates time-in-queue for each and filters to those past the SLA.
  3. 3For requests just over SLA it sends a reminder to the assigned approver in Teams.
  4. 4For requests past the escalation threshold it reassigns to the backup approver and updates the opportunity.
  5. 5It posts the escalation summary to the deal-desk Teams channel for visibility.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect SalesforceAccounts, opportunities, cases.
  2. 2
    Connect Microsoft TeamsChannels, chats, files.
  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.