--- title: "7 Ways Sales Teams Use the Fours Slack Bot" url: https://www.fours.com/resources/blog/fours-slack-bot-for-sales-and-partner-teams/ canonical: https://www.fours.com/resources/blog/fours-slack-bot-for-sales-and-partner-teams/ type: Blog description: "Seven ways sales, GTM and partner teams use the Fours Slack bot: offer status, call prep, co-sell checks, weekly digests and alerts, without leaving Slack." --- # 7 Ways Sales Teams Use the Fours Slack Bot > Canonical HTML version: https://www.fours.com/resources/blog/fours-slack-bot-for-sales-and-partner-teams/ 1. [Home](/) 2. [Resources](/resources/) 3. [Blog](/resources/blog/) 4. 7 Ways Sales and Partner Teams Use the Fours Slack Bot # 7 Ways Sales and Partner Teams Use the Fours Slack Bot Offer status mid-deal, a pre-call brief, a Monday digest of expiring offers, a co-sell referral that stalled: seven questions sales, GTM and partner teams ask the Fours Slack bot without leaving Slack, and what each one saves. [![Stacy Wu](/authors/stacy-wu.jpg)](/resources/blog/author/stacy-wu/) [Stacy Wu](/resources/blog/author/stacy-wu/) Oct 13, 2026 ![7 Ways Sales and Partner Teams Use the Fours Slack Bot](/images/blog/fours-slack-bot-for-sales-and-partner-teams/hero.png) Explore AI Summary [![](/logos/company/openai.svg)](https://chat.openai.com/?q=Read%20and%20summarize%20https%3A%2F%2Fwww.fours.com%2Fresources%2Fblog%2Ffours-slack-bot-for-sales-and-partner-teams%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Cloud%20GTM%2C%20AI%2C%20Co-Sell. "Summarize with ChatGPT")[![](/logos/company/anthropic.svg) ](https://claude.ai/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.fours.com%2Fresources%2Fblog%2Ffours-slack-bot-for-sales-and-partner-teams%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Cloud%20GTM%2C%20AI%2C%20Co-Sell. "Summarize with Claude")[![](/logos/company/gemini.svg)](https://www.google.com/search?udm=50&aep=11&q=Read%20and%20summarize%20https%3A%2F%2Fwww.fours.com%2Fresources%2Fblog%2Ffours-slack-bot-for-sales-and-partner-teams%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Cloud%20GTM%2C%20AI%2C%20Co-Sell. "Summarize with Gemini")[](https://www.perplexity.ai/search/new?q=Read%20and%20summarize%20https%3A%2F%2Fwww.fours.com%2Fresources%2Fblog%2Ffours-slack-bot-for-sales-and-partner-teams%2F%2C%20then%20cite%20the%20source.%20Focus%20on%20what%20it%20says%20about%20Cloud%20GTM%2C%20AI%2C%20Co-Sell. "Summarize with Perplexity") Table of Contents - [What is Fours Agent in Slack?](#what-is-fours-agent-in-slack) - [1\. Check a deal’s marketplace status mid-conversation](#1-check-a-deals-marketplace-status-mid-conversation) - [2\. Get a brief before a customer call](#2-get-a-brief-before-a-customer-call) - [3\. Roll up the numbers for standup or pipeline review](#3-roll-up-the-numbers-for-standup-or-pipeline-review) - [4\. Find out why a co-sell referral is stuck](#4-find-out-why-a-co-sell-referral-is-stuck) - [5\. Draft and send an update, with a check before it goes out](#5-draft-and-send-an-update-with-a-check-before-it-goes-out) - [6\. Turn a recurring question into a weekly digest](#6-turn-a-recurring-question-into-a-weekly-digest) - [7\. Route real-time marketplace alerts to the right team](#7-route-real-time-marketplace-alerts-to-the-right-team) - [Is it safe to let an AI agent work in Slack?](#is-it-safe-to-let-an-ai-agent-work-in-slack) - [Frequently asked questions](#frequently-asked-questions) - [How do you get started?](#how-do-you-get-started) _Fours Agent in Slack, also called the Fours Slack bot, is the Fours agent, reached by direct-messaging the Fours app or @mentioning it in a channel. Sales, GTM and partner teams use it to answer marketplace questions where the deal is being discussed: offer status, a buyer’s entitlements, a co-sell referral’s progress, a pre-call brief, a weekly digest. Here are seven of those questions, and what each one saves._ * * * Most marketplace questions don’t come up in the Fours console. They come up in Slack: a rep in `#deal-acme` asking whether the private offer went out, a partner manager asking why a referral is still pending, a VP in standup asking how many new entitlements landed this week. Until now, each one meant someone leaving the conversation, logging in, finding the record and pasting a screenshot back. The Fours Slack bot answers in the thread instead. It isn’t a separate bot with its own setup. It is the same Fours agent your team uses in the console, so it reaches the same marketplace data, the same CRM and call-recording connections, and respects the same permissions. ## What is Fours Agent in Slack? **Fours Agent in Slack is the Fours agent, answering in Slack instead of the browser.** You message it directly, or @mention it in a channel, and it reads your Fours offers, entitlements, buyers, revenue and co-sell records through the connections you set up in the console. Three things make it useful to a revenue team rather than just novel: - **It works where the question is asked.** The answer lands in the same thread as the discussion, so the context stays together. - **It answers from the system of record.** It reads the offer or referral itself and reports what it finds, rather than relying on someone’s memory of the last status update. - **Everyone gets their own access.** Each person’s questions run on their own connections and their own Fours permissions, so the bot never shows anyone more than they could see in the console. ## 1\. Check a deal’s marketplace status mid-conversation **Ask “has the Acme private offer been accepted?” in the deal channel, and the answer arrives in the thread.** No console login, no screenshot, no waiting for the one person who knows where to look. Typical questions: - “What’s the status of the private offer we sent Globex on AWS?” - “Which products is Initech subscribed to, and when does their entitlement renew?” - “Did Umbrella’s offer expire, or is it still open?” **The benefit:** account executives and deal desks stop context-switching for routine status checks, and the whole deal team sees the same answer at the same time. ## 2\. Get a brief before a customer call **Ask for the picture before a call, and the Slack bot combines what each connected system knows.** If you have connected Salesforce and Gong to your own account, one question pulls the opportunity, the last call’s discussion and the buyer’s marketplace entitlements together. > Brief me on Acme before my 2pm: open opportunity, what we discussed on the last call, and what they already buy through the marketplace. **The benefit:** call prep that used to mean three tabs and ten minutes becomes one message. The answer is only as complete as what you have connected, so connect the tools you actually use for prep. ## 3\. Roll up the numbers for standup or pipeline review **Ask for a count or a summary, and it rolls the records up for you:** new entitlements this week, offers awaiting acceptance, pipeline by partner. Ask for the count when that is all you need; ask for the list when you want to drill in. - “How many new AWS entitlements did we get this week?” - “Which private offers are still waiting for the buyer to accept?” - “Break down open co-sell pipeline by partner.” When an answer is a large table, the Slack bot attaches it as a CSV file instead of a wall of text, with links to each record kept intact. **The benefit:** RevOps doesn’t have to build a one-off report for every question someone asks in a meeting. ## 4\. Find out why a co-sell referral is stuck **Give it the referral and ask what went wrong; it reads the record and reports what it finds rather than guessing.** For partner and alliance teams, this is the question that usually sends someone into a portal hunt. - “How is the Globex co-sell referral progressing?” - “Why did the referral we submitted for Initech fail?” **The benefit:** partner managers get a diagnosis in the channel where the partner conversation is happening, and can decide the next step without escalating to whoever owns the integration. ## 5\. Draft and send an update, with a check before it goes out **Ask the Slack bot to draft a win announcement, a partner update or an outreach email, and to post it where it belongs.** Before it sends any Slack message on your behalf, it stops and shows you an approval card: the exact message, and the exact channel or person it is going to, with **Allow** and **Deny**. > Summarise this thread as a short win announcement and post it in #sales-wins. Only the person who asked can approve. If nobody answers within three minutes, the request expires and nothing is sent. **The benefit:** the AI writes the first draft, but a person still decides what goes out and where. The right message never lands in the wrong channel by accident. ## 6\. Turn a recurring question into a weekly digest **If you ask the same question every Monday, ask the Slack bot to ask it for you.** Describe what you want and when, and it creates an automated job for you. There is no form to fill in. > Every Monday at 9am, summarise the private offers that expire in the next 14 days. The Slack bot picks the matching trigger itself: a recurring schedule, an incoming marketplace event, or a single run you start yourself. The job is yours alone. It runs with your access and your connections, and only you can see, run, edit or delete it, org admins included. When a run finishes, the bot sends you a direct message in Slack with the result, or the error, and a link to the job in the console. (Jobs triggered by an incoming event send no message; their run history is in the **Jobs** app.) Good candidates from the Fours docs: a daily check for new entitlements or expiring offers, a weekly revenue or usage report, and a scheduled review that flags stale co-sell referrals. **The benefit:** the follow-ups that slip through the cracks, such as the offer that quietly expired or the referral nobody touched for two weeks, get surfaced on a schedule instead of being remembered by someone. ## 7\. Route real-time marketplace alerts to the right team **Alongside the agent, the same Slack installation sends instant Fours notifications, and an admin can route each type to a different channel.** Each notification type pairs an action with what it happened to, such as `CREATE.OFFER` or `CANCEL.ENTITLEMENT`. A common setup: Event Channel Who acts on it New offer or new subscription (`CREATE`) `#sales-wins` Sales, leadership Cancellation or suspension (`CANCEL`, `SUSPEND`) `#customer-success` Customer success Private offer expired unaccepted (`EXPIRE`) `#deal-desk` Deal desk, account executive Co-sell registered, accepted, declined or won `#partnerships` Partner and alliance managers **The benefit:** each team hears about the events it owns as they happen, without everyone watching one noisy channel. And when an alert raises a question, the Slack bot is in the same Slack workspace to answer it. ## Is it safe to let an AI agent work in Slack? **Yes, because the guardrails are set in Fours and Slack only inherits them.** Four defaults keep it conservative: - **Read-only unless you choose otherwise.** The connection that gives the Slack bot your marketplace data defaults to read-only. To let it create or update offers and referrals, each person reconnects with **Read & write**. - **In a channel, changes wait for you.** Anyone in a channel can write the messages the bot reads there, so before it creates or changes anything from a channel mention, it asks on an approval card that only you can answer. Lookups and answers go ahead. - **Sending waits for you.** Every Slack message it wants to send on your behalf goes through the approval card described in use case 5. - **Your access, never more.** Two people asking the same question in the same channel can get different answers, because each runs on their own connections and permissions. That is the model working, not a fault. One thing to remember: an answer in a channel is visible to everyone in it, and it can draw on anything your connections can read, private messages and email included. Ask in a direct message about anything you wouldn’t post in that channel yourself. ## Frequently asked questions ### Can the Fours Slack bot change records from a Slack channel? Only with your approval. In a channel, anything the bot cannot recognize as a read waits on an approval card that only you can answer. It also needs a read and write connection to create or update an offer or referral. ### Does the Fours Slack bot post to Slack without asking? Not when you are chatting with it. Before it sends a Slack message on your behalf in a DM, a channel mention or the console, it shows an approval card that only you can answer. Unanswered requests expire after three minutes. ### Why did a teammate get a different answer to the same question? Each person runs on their own connections and their own Fours permissions. If one of you has connected Salesforce or Gong and the other has not, the answers will differ. That is by design. ### What does an admin need to set up? An org admin connects Slack once under Settings, Integrations in the Fours console. After that, each person makes sure their Slack email matches their Fours account and connects the tools they want the Slack bot to use. ## How do you get started? **An admin connects Slack once, then each person connects the tools they want the Slack bot to use.** Nothing is configured per channel. 1. **An org admin connects Slack** in the Fours console under **Settings ▸ Integrations**. In Slack, the app still appears under its former name, Suger. 2. **Each person’s Slack email must match their Fours account.** That is how the Slack bot knows who is asking. 3. **Each person connects their data.** The Fours MCP server gives the Slack bot your offers, entitlements, buyers, revenue and co-sell records. Salesforce, Gong, Gmail and Google Calendar are optional, personal connections. 4. **Invite the app to private channels** with `/invite @Suger`. Public channels work as soon as you @mention it. The [Fours Slack bot documentation](https://doc.fours.com/insulin/slack-bot/) covers step-by-step setup and troubleshooting. For the engineering view (how tools, approvals and job notifications behave under the hood), see [the technical guide on insulin.dev](https://www.insulin.dev/blog/insulin-slack-bot-tools-approvals-jobs/). ## Sources Primary sources for the platform rules cited above. Last verified October 14, 2026. Cloud providers change fees, eligibility, and program terms without notice — check the source before relying on a figure. - [Fours Insulin docs: Slack Bot](https://doc.fours.com/insulin/slack-bot/) — The bot is the same Insulin agent as the console, inheriting its connections; DM and @mention behaviour; in a channel, anything not recognized as a read waiting for an approval card, and channel answers able to draw on private messages your connections reach; the Fours MCP server's Read (default), Read & write and Read, write & delete access levels; per-person connections; large tables as CSV; the approval card before sending a message, answerable only by the asker, expiring after three minutes; creating a job by asking; the direct message with the result when a run of a job you own finishes, except event-triggered, goal and channel-owned jobs - [Fours docs: Slack integration](https://doc.fours.com/integrations/slack/) — Notification scopes as ACTION.ENTITY, including offer, entitlement, co-sell and commission scopes; routing scopes to different channels; the Slack capabilities the agent has, and sends waiting for approval in the console, a Slack DM or a Slack mention - [Fours Insulin docs: Jobs](https://doc.fours.com/insulin/jobs/) — Jobs created by asking the assistant; manual, cron and push triggers; a job private to its owner; the use cases for marketplace monitoring, recurring reports and co-sell pipeline tracking ## Keep reading - [Co-SellAWS vs Microsoft Inbound Co-Sell Referrals: Acceptance Clocks and Triage PolicySep 29, 2026](/resources/blog/aws-microsoft-co-sell-referral-triage/) - [Cloud GTMWhat Marketplace Data Lands in HubSpot, and What Doesn'tSep 13, 2026](/resources/blog/marketplace-data-in-hubspot/) - [Cloud GTMMCP for Cloud GTM: Connecting Agents to DataAug 16, 2026](/resources/blog/mcp-for-cloud-gtm/) - [Co-SellHow Co-Sell Works on AWS, Azure, and Google CloudAug 10, 2026](/resources/blog/how-co-sell-works/) [Browse every post on the Fours Blog](/resources/blog/) ### Stay Updated New posts, product updates and marketplace strategy are shared on LinkedIn as they publish. [Follow Fours on LinkedIn](https://www.linkedin.com/company/suger-inc)