Stream and topic threading

Zulip groups every conversation into streams, then splits each stream into named topics so related messages stay together. A Beam agent watches the streams you designate, reads incoming messages by topic, and applies your approved rule about which topics warrant a canned reply, a linked ticket, or an owner ping. It posts the answer inside the same topic and marks the thread handled. When a topic mixes several questions or the intent is unclear, the agent leaves it untouched and hands the thread to a chosen teammate for judgment, keeping the whole exchange in one place.

Catch-up and unread tracking

Zulip records what each account has and has not read, letting people catch up one topic at a time instead of scrolling a single feed. A Beam agent taps that same unread state to sweep a backlog on a schedule, reading only the topics your rule marks important. It compiles the open items, drops a short recap into a chosen stream, and pings the owner of anything past its response window. Threads whose priority is genuinely debatable stay flagged for a person, so the agent never silently closes a conversation that needs human eyes.

Mentions and direct messages

Zulip carries @-mentions, private direct messages, and emoji reactions on top of its public streams. A Beam agent reads mentions and direct messages aimed at a shared account, weighs each against your approved playbook, and replies in the same place, adding a reaction to acknowledge receipt where that fits your convention. Requests it can resolve, like pointing a question to the right stream or confirming a status, it finishes on its own. Anything involving a decision, a sensitive topic, or a person outside the agreed scope goes to a human, with the original message linked.