If your team picked Slack and your CRM is anything other than Salesforce, you already know how this works. Microsoft’s Copilot is in Outlook and Teams. Salesforce-in-Slack is for Salesforce data. The team that lives in Slack on top of someone else’s CRM gets the second-class AI experience by default. Henoyo runs as a Slack app in your workspace, invoking the same Prompts your team already uses on voice and MCP, against whatever your CRM actually is.
Coming · in design. Help shape what ships.
Microsoft’s AI doesn’t reach Slack first-class. Copilot is in Outlook, in Teams, in Word, in the M365 graph, and Slack sits outside that graph by design. Salesforce in Slack is a strong product if your CRM is Salesforce. It’s built for Salesforce data, by the Salesforce team. If your CRM is NetSuite or Dynamics or anything else, Salesforce-in-Slack isn’t the AI layer for you.
That’s most mid-market companies, by the way. The tooling stack picks up team-by-team, and the team that picked Slack often did it independent of the rest of the stack (different generation, different hire, different culture). The AI vendors don’t see that team. They see “Microsoft-shop” or “Salesforce-shop,” and they ship accordingly.
Henoyo runs in your cloud, holds the connection to your CRM, and exposes the same Prompts on every surface. The Slack app is one rendering of one Prompt library. Your CRM is whatever it is. Your AI doesn’t care.
It’s 11:15am. Marcus on support sees a customer email forwarded into #support-escalations. Acme is asking why their order is delayed and the tone is hot. The thread already has two replies that are mostly “let me check on that.” Marcus runs a message shortcut on the email.
Marcus message-shortcuts the email:“/henoyo proposed resolution from this thread”
Henoyo replies in-thread about fifteen seconds later, posted as a Slack Block Kit message:
Henoyo through Slack:Order 4502 for Acme is currently in fulfillment, two-day delay caused by a backorder on the linked SKU. Acme is a $180k account, no prior escalations on the relationship, six successful orders in the last twelve months. Recommended response: acknowledge the delay specifically, share the new committed ship date (Tuesday May 6), offer to expedite at no charge given Acme’s history. Suggested draft below. Three sentences, no hedging, ends with a direct line for any further questions.
Marcus reviews the draft, edits one phrase, sends it from his support inbox. The escalation defuses. The whole exchange (email forward, shortcut, draft, send) happened inside Slack. Marcus never opened the CRM, never opened the ERP, never typed a tracking number into a fulfillment dashboard.
Three things, mostly.
#support-escalations, #stuck-deals, #renewals-watch: the channels where conversations already happen become the channels where answers also happen. Block Kit messages with the actual customer facts, not links to a CRM tab nobody’s going to click.
Forward an email to a Slack channel. Hover, run a shortcut, get a proposed-resolution draft back in-thread. The team’s existing habit (drag-drop emails, mention people) gets a second move that’s just as fast.
Different channels see different Prompts. Your admin pins which Prompts are exposed where; nobody has to remember which slash commands are appropriate in which room. The right surface, the right tools.
Three example invocations: slash command or message shortcut, Block Kit response in-thread, audit trail in your cloud.
/henoyo proposed resolution (message shortcut on a forwarded email)
Block Kit reply in-thread with a draft response, KB citations, prior case history, and a recommended escalation path.
Read logged in your Henoyo audit trail under the agent’s Slack identity.
/henoyo brief Acme
Block Kit Account 360 readout (open opps, recent activity, last touch, the recommended-next-step paragraph) posted in-channel for the deal team to see.
Read logged in your Henoyo audit trail; Slack sees only the rendered Block Kit message.
/henoyo at-risk this quarter
Block Kit list of accounts where renewal signals and cash collection diverge, pinned to #renewals-watch for the team to triage.
Read logged in your Henoyo audit trail. Pinned messages stay scoped to the channel’s Slack OAuth permissions.
Same Prompts, every surface.
Three answers, in case you’re forwarding this page to your Slack admin.
In your AWS or Azure account. The Slack app is installed in your workspace through the standard OAuth flow your admin already uses for every other Slack app; the Henoyo container that handles the request runs in your cloud. Tokens to your CRM stay in your secrets store inside that account. Henoyo’s servers see none of this.
The Slack app appears in your workspace’s Apps admin like any other installed app. Removing it goes through the same admin path. The Henoyo container can also be torn down independently from your cloud console. Two independent levers, each in your control.
Slash-command text, posted responses, and any uploaded attachments: the same things Slack sees for every other installed app. The reads against your systems of record happen inside the Henoyo container running in your cloud and are logged there. Salesforce’s purchase of Slack doesn’t change this. Slack as a workspace doesn’t get visibility into your CRM via Henoyo.
No. Slack is a channel. The same per-tenant Henoyo subscription covers all channels. Your users don’t get individual Henoyo seats; they invoke Henoyo through whichever channel they’re in.
Yes. Per-channel Prompt allowlists are part of channel deployment. A Prompt deployed to #sales isn’t automatically available in #support; your admin pins which Prompts go where.
It doesn’t directly. The Slack app sends the user’s request to the Henoyo container running in your cloud. The container holds your CRM tokens in your secrets store, executes the Prompt, returns the response to Slack. The user’s Slack identity is logged in the audit trail; the CRM call is made under your service identity, the same way it works on every other channel.
Salesforce in Slack is Salesforce’s native Slack-built CRM surface, scoped to Salesforce data. It’s a strong product if your CRM is Salesforce and you don’t need anything from outside Salesforce. Henoyo runs in your cloud and reads whatever your CRM, your ERP, and your warehouse actually are. If your CRM is Salesforce, the two products coexist. Most of our customers run both. If your CRM is anything else, Henoyo is the layer that gives your Slack workspace meaningful AI from your real systems of record.
Two weeks if you pick the right starting Prompt. For Slack-native teams the first win is usually the proposed-resolution shortcut on forwarded emails. Every support agent uses it three to five times a day, and the time saved per use is on the order of fifteen minutes.
Get on the early-access list. We’ll show you the Slack app installation, walk through Prompt-to-channel pinning, with your IT lead in the meeting if you want, and answer the questions your workspace admin is going to ask.