CRM

Weekly buying-committee coverage report from Zoom history

On a schedule, aggregates the last 90 days of Zoom call attendees per open Salesforce opportunity, computes a stakeholder-coverage score.

CategoryCRM
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule
  • ActionQuery open opportunities past stageSalesforce
  • ActionGather 90-day Zoom participants per dealZoomZoom
  • ActionStore coverage scoresPostgreSQLPostgres
  • LogicRank deals below coverage threshold
  • OutputPost risk report to leadershipSlack

What it does

This is a leadership-facing rollup. It walks every open opportunity in Salesforce, gathers all Zoom call participants tied to each deal over the past quarter, and scores how many distinct customer-side stakeholders each deal has touched. Deals with thin coverage are ranked and reported.

When to use it

Run it weekly when sales managers need a forecast-quality view of which late-stage deals are dangerously dependent on a single contact, so they can coach reps to broaden relationships before close.

How it works

  1. 1A weekly schedule starts the run.
  2. 2The flow queries open opportunities past a chosen stage from Salesforce.
  3. 3For each deal it retrieves Zoom recordings and participant lists from the last 90 days.
  4. 4It computes a coverage score from distinct customer-side attendees and stores results in Postgres.
  5. 5A branch ranks opportunities below the coverage threshold by deal value.
  6. 6The ranked single-threaded-risk report is posted to the leadership Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect ZoomMeetings, recordings, transcripts.
  2. 2
    Connect SalesforceAccounts, opportunities, cases.
  3. 3
    Connect PostgresAny Postgres URL — query, write, migrate.
  4. 4
    Connect SlackChannels, DMs, threads, mentions.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    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.