Features / Support
Tore for SlackSlack
Work the queue where your team already is
Conversations reach your team in Slack, and replies from Slack land back in the conversation. Nobody has to keep a second tab open all day.
ToreAPP10:42 AM
@here new bug report from Sarah K. at Acme Corp
Login page blank on mobile Safari
Widget · replay 0:18 · console · network · Safari 17, iOS 17
What it does
- Notifications routed to the right channel or person
- Reply from Slack and it reaches the customer
- Actions on the message, assign, resolve, escalate
- Connects with your own workspace permissions
Without it
Your engineers are already in Slack and will not leave it
Your team lives in Slack; the queue does not
The support tool is the tab everyone closes by Tuesday. Somebody pastes a customer screenshot into #support, three people react to it, and that is where it stays.
The escalation is a paste
An engineer gets pinged directly with a screenshot and no ticket. They fix it that afternoon, and the customer never hears back, because the conversation was never in the system to close.
You read it on your phone and answer it tomorrow
The notification arrives in Slack at 8pm and you know the answer immediately. Replying means opening the dashboard on a laptop, so it waits until morning.
How it works
Connect your workspace, keep your permissions
Install through Slack's own authorization flow. Each Slack account is linked to a Tore member, so anything done from Slack carries that person's real role and product access rather than a shared bot identity.
Choose which events post, and where
A new conversation, a bug captured with a session replay, a satisfaction response, a conversation escalated into a ticket, a fix pull request opened. Send them to the channel that should care, and let each teammate route their own notifications somewhere different.
What that includes
- A new conversation
- a satisfaction response
- a fix pull request opened
Reply in the thread and it reaches the customer
Each conversation gets one Slack thread. Your reply goes back out on the channel the customer actually used, email or the chat widget, without them ever seeing Slack. Message actions cover assign, resolve, snooze and close, plus turning any Slack message into a ticket, and there are slash commands for assign, snooze and status.
What that includes
- Message actions cover assign
- resolve
- snooze
- close
- status
It refuses the things it should refuse
A message from an unlinked Slack account, or from someone without the role to reply, is dropped rather than sent to your customer as an anonymous answer. Every Slack event is recorded by id, so Slack retrying a delivery cannot send the same reply twice.
What it means for you
The queue comes to you.
You work support from the window you already had open, on the device you already had in your hand.
The engineer's fix reaches the person who reported it
Because the Slack thread is the conversation, resolving it in Slack closes the loop with the customer instead of ending in a channel.
A bad day at Slack is not your customer's problem
Duplicate deliveries are ignored, and unauthorized messages are dropped. The failure mode is a message that does not send, not a message that sends twice or from the wrong person.
The honest limit: Slack Connect, a shared channel per business customer that becomes a tracked conversation, is marked coming soon in the product and is not built. Today the integration works inside your own workspace.
Also in Support