File, find and update tickets from Slack

• Mention @Tengu Bot in a thread (“@Tengu Bot the export button is broken in Safari”) and it drafts a ticket from the thread. By default it shows a preview with Create and Cancel; the ticket links back to the thread.
• Choose Create ticket in a message’s More actions menu to file a ticket from that message.
• Add to Today and Save as note, in the same menu, open a box with the message’s words, which become a to-do on your Tengu Today or one of your private notes, with a link back to the message, only when you press Add or Save.
• Tengu’s Today lists the threads Tengu Bot is in that wait on you, from someone who @-mentioned you or asked you something. Reply there as yourself: Tengu posts it, with a token you give it for that, only when you press Send.
• /tengu new creates a ticket, /tengu find searches open tickets, /tengu link links your Slack account, and /tengu help shows what it can do in that channel.
• Ask it in a thread to find tickets, change a status or an assignee, or add a comment. It asks before bigger changes.
• Ask it to set up an automation (“every Monday, post a status report here”). Once you confirm, it posts in that channel or DMs people on a schedule or when tickets change. In a channel, each post says who set it up.
• “@Tengu Bot push to production” opens the release pull request on GitHub for a repository the channel’s lists link. It doesn’t merge it: a person does, on GitHub. Only the list’s Release people and admins can ship.
• “@Tengu Bot run Claude Code on ACME-12” starts a Claude Code session on the ticket, as Run in Claude Code does on the board, and links it. It runs on your company’s own Claude account, for the person who asked, and only on tickets their Tengu account can see.
• Links to Tengu tickets show a preview with the status, assignee and due date.
• Linked members get direct messages for what they turn on in Tengu: assignments, mentions, reviews, Claude runs that need them, and clients’ requests and comments; and, on Studio, from the meetings they are in.
• DM it to ask who does what on your lists and, on Studio, questions your team’s docs answer.
• An admin can set a channel to Every message. Tengu Bot says so in the channel, then reads each message there and proposes a ticket when someone asks for work.

• Meetings: send it to a Zoom, Google Meet, Microsoft Teams or Webex call with /tengu join and the link. In a channel where an admin turned Meetings on, a linked member who pastes a call link sends it too. It joins as “Tengu Bot (recording)” and says in the call’s chat that it records; on Webex, where it can’t write in the chat, only its name says so. After the call it posts the minutes and suggests tickets.
• Tickets from a screen recording shared in a thread.
• Answers from Google Drive files your team picks, and from tools an admin connects (such as Linear, Notion or Intercom). Anything that changes data in those tools runs only after you press Run.
• Budget alerts and a Monday brief for owners and admins, as DMs.

Agencies and product teams whose work lives in Tengu and whose talk happens in Slack: client channels, support channels, the team’s own. Tengu Bot comes with Board ($9 a seat a month, $7 on annual) and Studio ($15 a seat a month, $12 on annual); Free doesn’t include it. Studio adds meetings, video tickets, docs, connections and budget DMs. Both include $2 of AI each month per seat for Tengu Bot, in one pool for the organization. Pricing has the rest.

1. Sign in to Tengu as an owner, an admin or someone in Operations. Install Tengu Bot, above, signs you in and opens Admin › Tengu Bot.
2. In Admin › Tengu Bot, press Add to Slack, choose your Slack workspace and press Allow. Your Slack account is linked to you as you add it, and Tengu Bot sends you a DM with what to do next.

You need a Tengu organization on Board or Studio.

1. Add a channel: in Admin › Tengu Bot, pick a channel you’re in, the Tengu lists its tickets go to, and whether Tengu Bot listens to @mentions or reads every message. It joins a public channel then; for a private one, run /invite @Tengu Bot there first.
2. Ask your team to link: each person runs /tengu link in Slack, so the tickets they ask for are theirs.
3. Try it: mention @Tengu Bot in a thread, or run /tengu help.

• It joins a public channel only when an admin who is in that channel connects it, and never joins channels on its own. It says so in the channel, in one message naming who connected it, how it listens and, with Meetings on, what a pasted call link does; and again if an admin sets the channel to Every message or turns Meetings on.
• Removed from a channel, it turns that channel off in Tengu and stays out. To bring it back, invite it there and turn the channel on again in Admin › Tengu Bot.
• In a channel set to Every message, it reads each message and proposes a ticket when someone asks for work.
• In a channel with Meetings on (Studio), a call link a linked member pastes sends its recorder into the call, as above.
• Automations post and DM as their maker set them up, on a schedule or when a ticket changes.
• A meeting in Tengu (Studio) DMs its linked people: that they were added, reminders to answer, the votes and check-ins that need them, its wrap-up and word of its calls, and, as a call on their Google Calendar starts, the offer of its meeting space. Its recap goes in its channel only when the host asks at wrap-up, saying who wrapped it up.

It acts only in channels an admin connects, in DMs sent to it and on messages you pick from More actions. Slack also sends it other messages from channels it is in, and profile changes; it discards what it doesn’t act on as it arrives, or within seconds. It keeps the threads it is mentioned in or takes part in, and DMs to it, for 30 days; in a channel set to Every message, it keeps every message for 30 days. It reads names, and whether each member of a connected channel is a guest or from another company, so it keeps team-only details out of channels a client can read. It never asks for email addresses. A token you give it to reply as you is kept until you disconnect it. Tengu never uses Slack data to train AI models.

When Tengu Bot is removed from a Slack workspace, its token, and the tokens members gave it to reply as them, are deleted at once, and its Slack data 7 days later, call recaps with their minutes and suggested tickets included. Tickets your team made from Slack stay in Tengu, and so do the to-dos and notes members made from Slack messages, and meetings in Tengu, only without the channel. The privacy page has the details.

Tengu Bot uses AI models (Anthropic’s Claude and Google’s Gemini) to read messages and draft tickets, answers and meeting minutes. It drafts replies on Today too, for you to change first. AI can get things wrong: check what it drafts before you rely on it.

In Slack, /tengu help shows what Tengu Bot can do in a channel, and “help” in a DM to it does the same. Anything else: write to hello@tengu.work and we answer within 2 business days. The support page says what to send us and how to remove Tengu Bot, and the privacy page what it keeps.