Collaboration

Notes, Discuss and private requests

Thorpe gives every request from a customer channel an internal thread, so your team can talk it over in Slack before anyone answers. Notes sit next to the request, in Slack and in the web app, and they never reach the customer.

Join the waitlist Read the docs

Discuss on a triage card starts an internal thread, and the replies are saved as notes on the request

Why internal talk goes wrong in shared channels

A shared channel has your customer in it. When a support engineer needs a second opinion, the choice is to ask in the channel, where the customer reads every word, or to start a side conversation in a DM or another channel, where the context is lost.

Thorpe keeps that conversation attached to the request, in a place customers can't see.

The card thread is internal

Each request has a card in your triage channel, and customers are not in that channel. Thorpe saves every reply in the card's thread as an internal note on the request. Your team can paste logs, ask who knows the account, or agree on an answer, and it all stays with the request.

Notes are not replies to the customer, so they don't stop the SLA clocks. The clock keeps running until someone answers in the customer's thread.

Discuss on the card
Posts in the card's thread that you started a discussion and that replies there stay internal
Discuss internally
The message shortcut, in the message's more actions menu, posts the same line in the request's card thread and shows you a link to it that only you can see
The customer channel
Nothing is posted there

Notes in the web app

The same notes appear in the web app at app.usethorpe.com. On a request's Activity tab, the Internal note box reads Only your team sees this. Add note saves the note and posts it in the card thread, so people working in Slack see it too. On the Conversation tab, notes show with a Note tag, and the search in the requests list finds note text.

One thing to know: notes work only in the card thread and in the web app. A message that starts with note: in the customer channel is an ordinary reply, and the customer sees it.

A note added on the Activity tab is posted in the card's thread, and a reply there is saved as a note too

Private requests

Some questions a customer would rather not ask in front of everyone in the shared channel. With private requests on, a customer sends Thorpe a direct message in Slack, and your team answers from a card in a private triage channel. The customer sees only the answers, in their DM with Thorpe.

Because that card thread goes to the customer, a private request has no Discuss button. Start a line with note: or 📝 to keep it internal. Private requests follow the same SLA policies as other requests.

Private requests are a paid feature, and paid access is not open yet. Until then, the settings are shown but can't be changed.

A customer asks Thorpe privately, and the team answers from a card in the private triage channel

How it works

  1. Step 1

    A customer asks a question in a shared channel, and Thorpe posts the request's card in your triage channel.

  2. Step 2

    Choose Discuss on the card, or Discuss internally on the customer's message.

  3. Step 3

    Talk it over in the card's thread. Each reply is saved as an internal note.

  4. Step 4

    Add context from the web app with the Internal note box. It appears in the card thread as well.

  5. Step 5

    When you have the answer, reply in the customer's thread as usual.

Details

Card thread replies
Saved as internal notes
Internal note in the web app
Up to 4,000 characters, also posted in the card thread
Discuss
On every open card for a request from a customer channel
Notes and the SLA
Notes don't stop the clocks
Enable private requests
Off. A paid feature, not open yet
Private triage channel
Workspace triage channel
Greeting DM to new external members
Off

Get started

Bring your shared channels into one triage view.

Tell us about your team and we will get in touch to set Thorpe up with you.

Join the waitlist