/henoyo stuck deals over $50k
Adaptive Card lands in-channel: three deals with stage, last activity, deal value, and a one-tap link to each Salesforce record.
Read logged in your Henoyo audit trail under the AE’s Teams identity.
CHANNELS · MICROSOFT TEAMS
Stop waiting for your CRM vendor to ship a Teams app.
Your sales team works in Teams. Your support team works in Teams. Your CRM is Salesforce. The Teams app from Salesforce has been catching up for years, and the AI in it is catching up to a different finish line. Henoyo runs as a Teams app in your tenant, invoking the same Prompts your team already uses on voice and MCP, against the CRM you actually have.
On the roadmap · Phase 3 in the platform PRD. Join the early-access list.
Salesforce in Teams shouldn’t be a permanent backlog item.
If your CRM is Salesforce and your team works in Teams, you already know how this story goes. Salesforce ships a Teams app. The Teams app is partial. The AI inside it, when it arrives, will be Agentforce, scoped to Salesforce data, optimized for the Salesforce-native experience. Microsoft’s own Copilot for Teams is the same picture from the other side: scoped to M365 data, scoped to Microsoft’s models.
Neither vendor has a structural reason to make the other’s product great. They have the opposite reason. So Salesforce-on-Teams stays catching up, to a different finish line each year.
Henoyo isn’t catching up to either side. It runs in your cloud, holds the connection to your CRM, and exposes the same Prompts on every surface: voice, MCP, REST, Copilot, and Teams. The Teams app is one rendering of one Prompt library. Whatever your CRM is, whatever your AI vendor is, the team in the channel gets the same answer.
What your Tuesday will look like once this lands.
It’s 9:50am. Your Acme deal team is on a kickoff Teams channel, two AEs, the SE, your legal lead, and your VP of Sales. The thread has gone a little quiet. One of the AEs surfaces what’s stuck.
An AE types in the channel:“/henoyo what’s stuck this week?”
Henoyo replies in the thread about ten seconds later, posted as an Adaptive Card with deal links:
Henoyo through Teams:Three deals over $50k with no movement in 14 days. Acme: $180k expansion, last touch 17 days ago, awaiting legal redlines. Northbrook Logistics: $95k, no champion call this week, AE is Mark. Cascade Industries: $1.2M renewal, three invoices over 60 days overdue and nobody on the deal team has flagged it yet. Each deal name on the card is a one-tap link into Salesforce.
The deal team reads the readout in the channel they were already in. The VP replies with a question about Cascade. The AE on Cascade types /henoyo cash collection brief Cascade, gets the AR breakdown back as an Adaptive Card, and the conversation moves to what to do about it. Nobody opened Salesforce. The deal-team channel is the workspace; Henoyo is just a participant.
What changes about your week.
Three things, mostly.
The deal team’s channel becomes a working surface, not a status board.
Stuck deals, account briefs, cash collection readouts, WISMO answers: all show up where the conversation already is. The thread has the data, not just a link to the data. The next message is a real reply, not “let me pull that up and get back to you.”
Slash commands and @mentions, not a separate app to learn.
Reps already know how to type / and pick a command. They already know how to @mention a bot. The first day looks the same as any other day in Teams, just with different replies coming back.
Per-channel scoping, so the right Prompts live in the right rooms.
The sales channel sees the sales Prompts. The support channel sees the case Prompts. The CFO’s deal-review channel sees the renewal-risk and cash-collection Prompts. Your admin pins which Prompts go where. Reps don’t have to remember.
What it looks like in a Teams channel.
Three example invocations: slash command in the thread, Adaptive Card response, audit trail in your cloud.
/henoyo brief Acme
Account 360 readout as an Adaptive Card in a 1:1 chat ahead of a call: open opps, recent activity, last touch, recommended next step.
Read logged in your Henoyo audit trail; Teams sees only the rendered card.
/henoyo at-risk this quarter
Adaptive Card listing accounts where renewal signals diverge from cash collection, flagged a quarter before they’d show up in the forecast.
Read logged in your Henoyo audit trail; flagged accounts can be pinned to the deal channel via the Card action.
Voice. MCP. REST. And Teams, next.
Same Prompts, every surface.
- Voice (browser) — Live, today
- MCP — Live
- REST — Live
- Mobile — This quarter
- Microsoft 365 Copilot — Next quarter
- Microsoft Teams — On the roadmap · Phase 3 in the platform PRD. Join the early-access list.
- Slack — Coming, no quarter
- Telephony (PSTN) — Phase 2
What your IT team will ask. The short version.
Three answers, in case you’re forwarding this page to your M365 admin.
“Where does the install actually live?”
In your Azure subscription (or AWS account), separate from your Microsoft 365 tenant. The Teams app is registered in your Microsoft Entra ID tenant; the Henoyo container that handles the request runs in your cloud. Tokens to your CRM stay in your Azure Key Vault or AWS Secrets Manager. Henoyo’s servers see none of this.
“How does revocation work?”
The Teams app is a registered application in your Entra tenant. Disabling it goes through the same admin path your team already uses for every other Teams app. The Henoyo container can also be torn down independently from your cloud console. Two independent levers, each in your control.
“What does Microsoft see?”
The Teams app sees the rendered Adaptive Card and the slash-command text the user typed. The reads against your CRM and other systems happen inside the Henoyo container running in your cloud and are logged there. Microsoft Purview captures what flows through the Teams surface; Henoyo’s audit captures what was read to produce the answer. Your CRM tokens never traverse the Microsoft tenant.
Common questions.
Do I need a separate Henoyo subscription for Teams users?
No. Teams is a channel. The same per-tenant Henoyo subscription covers all channels (voice, MCP, REST, Copilot, Teams). Your users don’t get individual Henoyo seats; they invoke Henoyo through whichever channel they’re in.
Can I restrict which Prompts are available in which Teams channel?
Yes. Per-channel Prompt allowlists are part of channel deployment. A Prompt deployed to the sales-team channel isn’t automatically available in the support-team channel. Your admin pins which Prompts go where.
How does the Teams app authenticate to my CRM?
It doesn’t directly. The Teams 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 Teams. The user’s Teams 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.
How is this different from Microsoft Copilot for Teams?
Copilot for Teams is Microsoft’s native AI inside Teams, scoped to M365 data and Microsoft’s models. Henoyo runs in your cloud and reads whatever your CRM, your ERP, and your warehouse actually are (Salesforce, NetSuite, Dynamics, multi-vendor). The Teams app it provides is one of several surfaces (voice, MCP, REST, Copilot) where your governed Prompts get invoked. If your stack is fully Microsoft and you don’t need cross-CRM, Copilot for Teams is a strong native option. If your reality is Salesforce-on-Teams or a multi-vendor mid-market, Henoyo handles it the same way every other channel does.
How long until I prove it’s working?
Two weeks if you pick the right starting Prompt. The deal-team channel readouts (stuck deals, cash collection, WISMO) are usually the fastest first win. The conversation that used to require three tabs and two replies turns into one slash command and one Adaptive Card.
Want this when it ships?
Get on the early-access list. We’ll show you the Teams app registration in your Entra tenant, with your IT lead in the meeting if you want, walk through Prompt-to-channel pinning, and answer the questions your M365 admin is going to ask.