SALES
Contract Value Routing: Enterprise Slack War Room vs. Self-Serve Email
On a signed deal, this branches on contract value — large accounts get a dedicated Slack onboarding channel with the success team invited.
How it runs
The automated pipeline, trigger to output.
- TriggerSalesforce deal marked Closed WonSalesforce
- ActionRead contract value + account fieldsSalesforce
- LogicBranch on ACV vs enterprise threshold
- ActionEnterprise: create Slack war room + invite teamSlack
- ActionSelf-serve: send automated welcome emailGmail
- OutputPost handoff confirmation summarySlack
What it does
Not every new customer deserves the same handoff. This workflow reads the signed contract's annual value and routes accordingly: enterprise deals get a high-touch Slack channel spun up with the CSM, solutions engineer, and account exec pulled in, while self-serve tier customers get a clean automated welcome email with onboarding links — no human bottleneck.
When to use it
Use this when one onboarding motion doesn't fit every customer and your team wastes time manually deciding who gets white-glove treatment. It encodes your tiering rules once and applies them consistently to every closed deal.
How it works
- 1A Salesforce opportunity is marked Closed Won, triggering the flow.
- 2The flow reads the contract's annual contract value and account fields.
- 3A logic branch compares ACV against your enterprise threshold.
- 4Above threshold: it creates a dedicated Slack channel named for the account and invites the CSM, SE, and AE.
- 5Below threshold: it sends a self-serve welcome email via Gmail with setup guides and a booking link.
- 6Either path posts a confirmation summary so the team knows the handoff fired.
Set it up
What you configure once, before turning it on.
- 1Connect SalesforceAccounts, opportunities, cases.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect GmailRead, draft, send, label.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Sales workflows
API-Usage Surge PQL Router
When an account's API call volume surges past a rolling baseline in the product DB, it qualifies the account as a product-qualified expansion lead.
Seat-Limit Approaching Upsell Alert
Fires the moment an account's active-seat count crosses 90% of its contracted limit in the product database.
Enrich new MAP steps with Salesforce deal context on creation
When a new card is added to the mutual action plan Trello board, it looks up the linked Salesforce opportunity and writes deal owner, amount, and close date onto the card…
Power-Feature Adoption Expansion Digest
Each Monday, finds accounts that started heavily using a premium or add-on feature in BigQuery, ranks them by expansion potential.
Send buyers a weekly mutual action plan health recap
Each week it reads the MAP Trello board, computes completed, on-track, and overdue steps, and emails the buyer champion a clean recap of progress and what is due next.
Escalate to the deal team when the buyer side of a MAP stalls
Detects when buyer-owned mutual action plan steps have been idle past their due date and escalates with a Slack alert to the AE plus an email summary to the account executive's…
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.