Chat and Messenger are one communication system with two jobs: Chat turns unclear intent into executable work, and Messenger brings attention back to the right thread, issue, run, or decision. Use Chat when the next step is still conversational. Use Messenger when something needs attention after work has started. Messenger attention surface

​
How they fit together

SurfaceUse it forMove forward by
ChatIntake, clarification, context gathering, and issue proposalsCreating or updating an issue when the request becomes executable
MessengerReplies, issue threads, failed runs, blockers, reviews, budget alerts, and decisionsReturning to the linked issue, run, or thread with a clear next action
The boundary is simple: Chat helps make the work clear. Messenger helps keep live work from losing human attention.

​
When Chat should become an issue

Convert a conversation into an issue when it needs any of these:
  • one owner to execute the next step
  • agent runtime budget
  • review or approval
  • a recovery point after failure or blocking
  • a durable history the team can inspect later
If the request can be answered immediately and creates no follow-up work, keep it in Chat. If it becomes work to assign, run, review, or revisit, create an issue. Chat issue proposal

​
What Messenger should bring back

Messenger answers one operator question:
What needs my attention right now, and which durable work object does it belong to?
Use it to move from signal back to action:
Attention signalDurable next step
Agent asks a questionReply, then keep the decision on the issue
Run failsOpen the linked issue or run and decide recovery
Work is blockedName the missing input or owner
Review is waitingApprove, request changes, or mark blocked
Chat proposes an issueAccept, edit, or reject before execution
Messenger should not become a second task tracker. If a thread creates real work, put the next step on an issue.

​
Anti-patterns

Avoid using Chat or Messenger as:
  • a hidden backlog
  • a replacement for issue status
  • a place to run long work without ownership
  • the only record of a review decision
  • a generic chat app disconnected from Rudder work

​
Next steps

Issue Lifecycle Guide

Learn when a request is ready for assignment and review.

Issues

See the durable execution object Chat and Messenger point back to.