Sales Ask Orchestrator
Sales Orchestrator: group-chat control tower that routes each sales ask to exactly one specialist and gates outbound sends
What it does
Traffic control for a sales team made of several bots. It replies first in the group and routes each request to exactly one specialist. It stops dogpiles and chatter, gates handoffs and outbound sends, and keeps usage down by waking only the bot that's needed.
- Who it's for
- RevOps / GTM Ops, GTM Engineer
- GTM motion
- Outbound/ABM
- Building blocks
- Bot templates, Multi-bot teammates/channels
- Complexity
- Advanced
Setup + template 🧩 Installable template
🔒 Prerequisites, trigger, step-by-step setup and the installable template.
More Bot teams use cases
Enterprise Sales Chief of Staff
GTM Chief Of Staff: enterprise-sales chief of staff for meeting prep, inbox and post-call drafts, coordinating specialist bots
A chief of staff for enterprise sellers. It owns meeting prep, the inbox, and post-call drafts, and it hands deck and other GTM work to specialist bots. It never sends anything or changes Salesforce or any CRM without the owner.
From: Sultanov (@thekuchh), GTM Chief Of Staff template
10-Agent Outbound Chain
10-agent outbound chain with 3 human checkpoints: ICP pattern → anti-ICP → list → fit score → trigger → opener → sequence → send → reply classifier → objection drafts
A ten-agent outbound chain where the human steps in at exactly three points. First, the ICP pattern read from your last 15 closed-won accounts, because every agent downstream reads it. Second, every opener before it gets near the send. Third, every objection reply. In between: an exclusion builder (anti-ICP from churned and ghosted deals), list builder, 0–100 fit scorer, 'why now' trigger finder, sequence builder, send layer and a reply classifier he eyeballs each morning.
From: Upamanyu Roy, LinkedIn post (Sep 9, 2026)
Four-Bot Outbound Desk Team
Outbound desk team: List, Research, Draft and Stop bots in one group chat; a weekday 08:00 Stop check removes repliers before any drafting
A four-bot outbound team. List builds a fit-based target list every Monday and rejects anyone in an open opportunity. Research finds the one specific thing worth mentioning. Draft writes the message and never sends. Stop drops anyone who replied or asked to stop, every weekday before any drafting runs.
From: botteams.io 'Outbound desk' team (sales-outbound), source github.com/ellelion/botteams
Coordinator and 9 Specialists
Coordinator + 9 specialists: 96 first-touch drafts in 3 weeks, nothing sent without approval
For three weeks a consultant ran nine specialist AI agents under one coordinator for lead research, outreach drafts, pricing research and ops. They drafted 96 personalized first-touch emails, plus research and admin work he estimates at about 115 hours. Nothing reached a prospect without his approval.
From: Eddy Kawira, via AI Business Plays (Olga Pearson)
Clinic Revenue Morning Brief
Ronin chief of staff: 7:30am revenue brief + 8am new-clinic scan with first-touch drafts
Every weekday at 7:30am the bot sends a revenue brief with 1–2 'quick wins' to act on that day. At 8:00am it scans SoCal for newly opened clinics and drafts first-touch emails (he sent 2 that week). It also built a 3-email newsletter nurture: 434 enrolled, ~20% open, 2.6% click, 1 booked call. It cut 9 X clips and 16 LinkedIn drafts from raw footage, preps calls and tracks follow-ups. His rule: everything outbound is a draft and he hits send.
From: Justin French (@JustinRFrench), via AI Business Plays (Olga Pearson)
CSM Priority Staff Meeting
Staff meeting: account bots and specialists debate how a CSM spends their one free hour
A CSM asks her chief-of-staff bot to start a staff meeting: a group chat where each account bot and specialist argues for the CSM's one free hour. The bots are told to disagree instead of agreeing by default. In the demo, two accounts say "don't spend it on us." The follow-up bot says a pending follow-up must go out now, and the account with an SSO issue makes its case. The chief of staff returns a ranked plan: SSO first, send the next-step email already drafted in Gmail, park the rest. This also checks for bias toward one customer.
From: Blake Schuller, Grok Bot for Post Sales session