Read a transcript

What this does for you

A transcript holds every message you and a bot have exchanged, and this page covers reading it, reacting to a message, and finding your way back to an earlier one.

Before you start

• You have a bot with at least one message already in it (see Start here).
• This page is about a one-to-one conversation with a bot — a group conversation reads differently (see Group chats).

Steps

1. Hover over a message to show its row of controls. React, reply and more appear outside the bubble, on its trailing side, always in that order, and the row stays visible while any of its menus is open.

<!-- shot: transcript-01-phone.png | Hovering a message to reveal react, reply and more, on a phone --> <!-- shot: transcript-01-desktop.png | Hovering a message to reveal react, reply and more, on a desktop -->

2. React to a message. The react control opens six fixed emoji in a set order, followed by a control that opens a fuller picker; picking one adds a chip beneath the bubble, and clicking your own chip again removes your reaction.

<!-- shot: transcript-02-phone.png | Picking a reaction from the quick picker, on a phone --> <!-- shot: transcript-02-desktop.png | Picking a reaction from the quick picker, on a desktop -->

3. Reply to a message. The reply control attaches that message as a quote in the composer below, ready to go out with your next message — see Send a message for what happens next.

<!-- shot: transcript-03-phone.png | Starting a reply from a message's hover row, on a phone --> <!-- shot: transcript-03-desktop.png | Starting a reply from a message's hover row, on a desktop -->

4. Copy a message, or copy the id behind it. The more control opens exactly two items: Copy, which copies the message's text with its markdown flattened to plain text, and Copy request ID, which copies the id support needs to look into that message — shown disabled, with a reason, on a message with no run behind it yet.

<!-- shot: transcript-04-phone.png | The message's "more" menu, on a phone --> <!-- shot: transcript-04-desktop.png | The message's "more" menu, on a desktop -->

5. Read a structured result. A finished task can render as five fixed sections — Facts, Assumptions, Done, Awaiting and Open — each shown only when it has something in it, so a simple answer still reads as a simple bubble.

<!-- shot: transcript-05-phone.png | A five-part result in the transcript, on a phone --> <!-- shot: transcript-05-desktop.png | A five-part result in the transcript, on a desktop -->

6. Redirect a bot that is already working. Sending a message while a run is active queues it instead of interrupting; the queued list can be reordered or removed, and Stop now halts the running task without undoing what it already did.

<!-- shot: transcript-06-phone.png | The send queue beneath an active run, on a phone --> <!-- shot: transcript-06-desktop.png | The send queue beneath an active run, on a desktop -->

7. Jump to this conversation's own settings from search. Open the search palette and switch to its Actions scope: Members and Chat Settings are listed first, under Current chat, but they belong to a group conversation — in a one-to-one conversation with a bot they are shown disabled, with a reason.

<!-- shot: transcript-07-phone.png | The search palette's Actions scope, on a phone --> <!-- shot: transcript-07-desktop.png | The search palette's Actions scope, on a desktop -->

A worked example

Facts
- The support inbox had 42 unread messages this morning.

Assumptions
- A message from support@ is always high priority.

Done
- Replied to the three time-sensitive threads.

Awaiting
- Your approval to archive the newsletter thread.

Open
- Should low-priority senders be muted going forward?

What can go wrong

See also

• Send a message
• Start here
• Bot settings
• Group chats
• Approval cards