How-toMessenger

Run Messenger workflows

Create groups, use AI and support, attach and manage messages, and control archive and block state.

Last updated 2026-08-19 7 min read

These workflows create and manage Messenger rooms without confusing a visible notification with a durable write. They cover groups, Ori and support, local attachments, message actions, archive, and block state.

Before you begin

You need a signed-in account and access to every room you plan to use. Review participant identities, message content, files, and report details before submitting them. Most Messenger rooms follow participation, not an organization-admin title; linked fund conversations can also use the fund’s separate resource-access policy.

For destructive actions, confirm the selected room and message first. Delete for everyone cannot be undone, and successful destinations in a partial forward are not rolled back.

Create a group

Select New chat, then New group chat.
In Create group chat, enter a nonblank Group name.
Under Select members, search for and select at least one eligible account.
Review the Selected list.
Select Create group.

The creator is included automatically. Creation immediately writes the room, its creator record, and all initial memberships; it does not send a message or push notification. Messenger reports Created NAME and opens the stored group.

Manage group and support members

Open an ordinary group or support room.
Select the N members control to open Chat members.
Under Add members, use Search by name or email…, then select Add NAME. Ordinary groups and support rooms both permit eligible person additions, and this search excludes bots.
In an ordinary group, eligible bots appear separately under Available AI agents. Support rooms do not expose that AI-agent addition path.
To remove another ordinary member, the room creator selects Remove NAME. Other participants can add eligible people but cannot remove them.
To remove yourself, close the member picker, open Chat options, and select Leave group.

The creator cannot remove themselves through the member picker. If the creator leaves, ownership transfers atomically to the earliest-joined remaining member. The last member cannot leave or be removed, and Ori cannot be removed from a support room. Use these steps only for ordinary groups and support rooms; other group-shaped room headers can show Leave group even when that action is unsupported.

Use Ori and support

Select the pinned AI row when it shows Ori. If another AI conversation is pinned, do not send an Ori request there: select New chat → New support request for a fresh support room, or ask support to restore access to the personal Ori room. When Ori is selected, enter a request and select Send.
While Ori is responding, select Stop to cancel that response. Your submitted message remains stored.
In a group, add an eligible agent under Available AI agents, then mention it in the message. A first valid mention can also add an eligible agent that was not yet a member.
To open a fresh case, select New chat → New support request. New support request immediately creates a new support room with you and Ori before you send any text.
To resume a known support room, select its row under Support. The header Help and support action searches only the currently loaded inbox tab: it opens the most recent support room in that tab, or creates a fresh one when that tab contains none. From Blocked, it therefore creates a new support room.
Send the support question. While the original requester and Ori are the only participants, each requester message invokes Ori. While anyone else remains, mention Ori explicitly when an AI response is required. Direct mode resumes if the room returns to only the requester and Ori.

AI generation and any later handoff banner or agent-driven room rename happen after the message write. They are not required for the user message to be durable.

Attach local files

Open a room where you can send.
Select Add attachment, then Add files or photos.
Choose no more than five local files, each no larger than 10 MiB. Supported extensions are .pdf, .doc, .docx, .odt, .jpg, .jpeg, .png, .webp, and .heic.
Optionally add text in Write a message….
Select Send.
Wait for every intended attachment chip to appear in the transcript. Then reload the room and confirm that all of them remain with the stored message. If a file never appears or an inline error occurs, inspect the original selection before sending anything again.

These limits describe the local picker. Do not assume that a separately enabled cloud-import path applies identical count, size, or failure handling; verify that every expected attachment appears in the stored message.

Manage a message

Open the message-actions menu for a persistent, nondeleted message.
Select a reaction emoji to store your reaction; selecting your existing reaction again removes it. Archived rooms, either direct block, the pending receiver state, and hidden or deleted targets keep reactions read-only or refuse the write.
Select Reply to quote its context, then send the reply. Select Copy text for a nonempty message when no server write is intended.
For your own nonbot message, select Edit, change the text, and select Save. The update succeeds only strictly before 15 minutes have elapsed and records edit history.
From a group or fund message, select Forward. In Forward message, choose up to 20 distinct destination rooms offered by the picker and select Forward. The source room is excluded and access is rechecked for each destination. Each destination is written independently, so partial success is not atomic and successful destinations remain written.
For an incoming direct message, select Report. In Report message, confirm that it is another participant’s direct message, choose the accurate reason, optionally add up to 1,000 characters of context, and select Submit report. Success creates a pending moderation record; it does not hide, delete, or block the message.
Select Delete for me to hide the message only from your view. For your own nonbot message, Delete for everyone removes it for every participant and cannot be undone.

The forward picker has no optional-comment field. Deleting for everyone is a soft removal with no 15-minute limit; editing has the time limit.

Archive or block

To archive a room, open Chat options and select Archive chat. The room leaves your All list but remains available to its other participants.
To restore an unblocked room, open Archived, select the room, open Chat options, and select Unarchive chat. If that direct contact is also blocked, open Blocked first and select Unblock user; the archive timestamp remains, so then return to Archived and select Unarchive chat.
To block a human direct contact, open that direct room, open Chat options, and select Block user. Messenger returns to the inbox and the contact appears under Blocked for the blocker.
To remove your block, open Blocked, select the contact, open Chat options, and select Unblock user.

Archive is per-user and does not delete the transcript or membership. Blocking is directional as a record but prevents direct sends in either direction while either participant has a block; it does not remove shared group membership or history. Bots cannot be blocked.

Success check

Verify the durable result for the workflow you ran:

a created group or support room appears in the inbox with the intended members;
every intended attachment remains visible with its stored message after a reload;
an edit shows the updated text, while a forward appears in every successful destination;
a report shows Reported the message and leaves the original message in place;
an archived room appears under Archived, unless the current user also blocked that direct contact and Blocked therefore takes precedence;
a contact you blocked appears under Blocked until you use Unblock user.

Do not use a push notification, AI reply, transient support banner, or another participant’s read state as the success check.

Troubleshooting

If group membership fails, confirm that the target is still eligible and that only the creator is attempting removal. If AI does not answer in a multi-member room, mention the intended agent. If a forward partially succeeds, inspect the successful destinations before retrying so they do not receive duplicates.

If an intended attachment is missing after reload, verify each file’s extension and size before deciding whether to send it again. For report, archive, block, edit, and request-state problems, use Troubleshoot Messenger.