Start a direct conversation
Find a participant, send the first direct message or local attachment, and verify the durable conversation state.
This guide starts or resumes a direct conversation. At the end, the room and first message are stored in Messenger; a notification, read receipt, or request-state change is not required for success.
Before you begin
You need:
- a signed-in Infra One account;
- the reviewed name or email of the intended participant;
- content that the participant is authorized to receive;
- for a local attachment, a supported file no larger than 10 MiB.
Messenger is not scoped by the organization currently shown in the app shell. Search results can include eligible active accounts outside that organization and can include bot-backed accounts, so review the identity carefully before sending.
Start the conversation
- Open
https://messenger.infra.one/. - Select the plus control labelled New chat.
- Select New direct message.
- In Search by name or email…, enter enough information to distinguish the intended account.
- Review the name and email, then select the account. An existing pair opens its current room; a new pair opens an unsaved draft.
- Enter text in Write a message…. To send a local file instead of or alongside text, select Add attachment, then Add files or photos.
- Review the recipient and content, then select Send. Enter also sends; Shift+Enter adds a line break.
For a new person-to-person pair, the first message or attachment creates the direct room and a pending message request. The requester can continue sending unless either participant blocks the other. The receiving participant can read the thread, but Messenger refuses their sends while that pending state remains.
The current web surface displays request-state banners but does not expose controls for changing that state. Do not treat the visible composer as proof that the receiving participant can send.
Success check
The browser moves to /chat/ROOM_ID, and your message appears in the transcript. A new or explicitly unarchived person-to-person pair appears in All; an existing archived person-to-person pair remains under Archived until you explicitly unarchive it, while a rejected pair is excluded from All. An active bot-backed direct appears in the separate pinned AI row; an archived bot-backed direct remains under Archived. After sending an attachment, wait for every intended attachment chip to appear, then reload the room and confirm that all of them remain with the stored message. These durable records prove the write; delivery, a push notification, the other participant’s read state, and an AI response are separate outcomes.
Troubleshooting
If search returns no result, check the spelling and email. Messenger returns at most 20 active accounts with complete names and excludes the signed-in user.
If sending fails, confirm that the message is not blank unless a file is attached, its text is at most 50,000 characters, neither participant has blocked the other, and you are not the receiver in a pending request state. For attachment errors, use one of the supported local file types and stay within five files of 10 MiB each.
For a rejected-state banner, do not infer a recovery path from the visible composer. The frozen web surface does not present a complete, supported recovery flow; preserve the exact banner and ask support to inspect the room.
See Troubleshoot Messenger for archive, block, group, AI, and message-action failures.