The teammate who actually remembers the call.
Connect Slack and Tenali becomes someone you can message. Ask it in a DM what a customer said last Tuesday. Tag it in #sales-help and it answers the thread from your company’s own knowledge — so the same question stops landing on the same person.
What you get
The gap
Your team already asks these questions. In Slack.
“Do we support SSO on the starter plan?” “What did Acme say about the security review?” “What’s our line on the new competitor?” The answers exist — in a call someone ran last week, in a doc someone wrote in March. They just aren’t where the question is.
So the question goes to the one person who knows, who context switches, digs it out, and answers it again. Six weeks later someone asks the same thing in a different channel.
Tenali sits in Slack and answers it instead — in a DM from your meetings and your documents, and in a channel from the knowledge your company has published for everyone.
Two surfaces, two boundaries
A DM is yours. A channel is everyone’s.
Tenali answers differently depending on who can read the reply. That difference is enforced in the product, not left to whoever configures it.
Everything you can already see
A direct message is yours alone, so Tenali answers from your full working context — the calls you were on, the documents you've added, your open follow-ups and your pipeline.
Can draw on
- Your meetings, summaries and transcripts
- Your documents and connected sources
- Your action items
- Your CRM records
- The thread's earlier messages, so follow-ups work
Cannot reach
- Anything your Tenali account couldn't already open
Only what the company has published
Tag Tenali in a channel and the whole room sees the reply — so it answers strictly from knowledge your organization has published for everyone. This is a hard boundary in the product, not a setting someone can loosen.
Can draw on
- Sources published to the whole organization
- The earlier messages in the thread it was tagged in, so follow-ups work
Cannot reach
- Meetings, calls and transcripts — though answers auto-captured from calls are part of shared knowledge
- CRM records
- Anyone's private files — including yours, including admins'
- Anything said elsewhere in the channel — only the thread it's tagged in
Setup
Connected in about a minute.
One authorization, no configuration files, and nothing for your Slack admin to build.
Connect Slack in Tenali
Open Integrations in Tenali and click Connect on the Slack row. You authorize once in a new tab — there's nothing to install from the Slack side first.
Say hello
Tenali DMs you the moment you're connected. Ask it about a meeting, your action items, or an open deal and you'll get an answer in the DM.
Put it where your team asks questions
Invite Tenali to a channel and publish the docs it should answer from. Now the questions that used to interrupt someone get answered in the thread.
What you can ask
Plain language. No syntax to learn.
Catch up on a deal
- “What did we discuss with Acme last week?”
- “What did the customer say about pricing on the Contoso call?”
- “Summarize my most recent meeting.”
Stay on top of follow-ups
- “What are my open action items?”
- “What did I commit to on Tuesday's calls?”
- “What deals do we have open?”
Answer the team's questions
- “@Tenali what's our current stance on SOC 2?”
- “@Tenali do we support SSO on the starter plan?”
- “@Tenali what's the latest pricing for enterprise?”
Update the CRM
- “Log yesterday's Contoso meeting on their deal.”
- “Set the next step on Acme to send the MSA.”
- “Create a deal for Northwind in HubSpot from today's call.”
Knowledge from Slack
Your best answers are already in a channel.
Competitive intel, pricing decisions, the fix for that customer issue. Point Tenali at the channels where that gets decided and it answers from them — in chat, in Slack, and live on a call.
Signal filtering, built in
Slack channels are mostly not answers. Tenali reviews messages before indexing them and keeps the ones carrying real information — decisions, explanations, pricing, customer context — and leaves out the standup threads and the +1s. Nothing to configure.
Channel by channel, never the whole workspace
You choose which channels Tenali learns from, one at a time. Public channels and the private ones you belong to are both fair game — Tenali reads through your own Slack access and nothing beyond it.
And it records your huddles
Slack is a fully supported meeting platform for the Tenali desktop app. Start a huddle and Tenali detects it on its own, captures audio and screen with no time limit, then writes the summary and action items like any other call.
Send it a document in the DM
Drop a PDF or a deck into the Tenali DM and it becomes one of your sources, then Tenali messages you when it's ready to answer from. Files you send stay private to you until an admin shares them with the team.
CRM updates
Update the CRM without opening the CRM.
Tell Tenali what happened — “log yesterday’s Contoso call on their deal” — and it drafts the change from what was actually said, then shows you the card before anything moves.
Each row carries the record it matched, the field-by-field before and after, the quote from the call it came from, and how confident it is in the match.
In Slack, nothing is written until you approve — including additive changes like notes and tasks.
Works with HubSpot and Salesforce; creating new companies and deals is HubSpot-only today. Enabled per workspace — talk to us to switch it on.
Proposed CRM changes
3 changes · 1 higher-risk · review before I apply anything
“We’ll get the MSA over to legal this week and aim to close mid-August.”
match confidence: 94%
Security & control
Built so a channel reply can never embarrass you.
The risk with an assistant in Slack isn’t that it won’t answer. It’s that it answers with something the room shouldn’t see. That’s the constraint we designed around first.
A channel reply can't leak private work
In a channel, Tenali can only reach your organization's shared knowledge. It can't open meetings, CRM records or individuals' files on that surface — even for admins. Answers auto-captured from your calls are part of that shared knowledge, so admins review them before Tenali goes into a channel with outsiders.
Everyone connects their own account
Tenali answers each person through their own access. Connecting doesn't grant anyone a view of anyone else's meetings, files or pipeline.
It never wanders your workspace
Tenali reads the channels you explicitly add and replies in channels it's been invited to. It doesn't join channels by itself and it doesn't browse the rest of Slack.
No CRM change happens behind your back
Every CRM update proposed in Slack waits on an approve-or-discard card — including additive ones — showing the record, the before and after, and the quote from the call it came from.
Frequently Asked Questions
What teams ask before putting Tenali in their workspace
Put the answers where the questions are.
Connect Slack once and your team can ask Tenali about any call, any document, any deal — right in a DM. Tag it in a channel and it answers the room from your company’s published knowledge, where they were already going to ask someone else.
Included with any Tenali plan that has AI chat. CRM write-back is enabled per workspace.