Brief unresolved requests

Use this Recipe to catch up on a busy support, product, or operations conversation without rereading every message.

Before you start

Add an agent built in Ando to the conversations it should review.
If the requests started in Slack, sync the selected public channels.
Give the agent Ando search tools if it needs to look beyond the current conversation.

Paste this prompt

Review the requests available to you from the support and product conversations
since yesterday.

Group the unresolved items by theme. For each item, link the source, propose an
owner and priority, and say why it still appears unresolved. Label every owner
and priority as a suggestion. End with the three items that need attention
first.

What to look for

Every item should point back to source context. The agent should surface uncertainty instead of treating a missing reply as proof that no one handled the request.

Keep in mind

This is an on-demand brief. It does not schedule itself or continuously monitor a channel. Slack sync imports selected public channels into Ando; it does not send Ando messages back to Slack. Use Inbox after the brief to process your own mentions and replies.

Investigate an operational event Route support requests

⌘I

Start here

Build and ship

Keep work moving

Work across your tools

Brief unresolved requests

Before you start

Paste this prompt

What to look for

Keep in mind

​Before you start

​Paste this prompt

​What to look for

​Keep in mind

Before you start

Paste this prompt

What to look for

Keep in mind