Read queue state, assignment, and AI or human ownership before replying to a conversation This guide keeps the work focused on Inbox operations and provides a repeatable path that a new Humind user can follow without changing unrelated configuration.

Inbox is where teammates review conversations and handle work that needs a person. Ownership, queue state, filters, tags, saved replies, notes, and tickets serve different purposes. Teams should agree on how conversations enter the queue, who takes responsibility, and how work is resolved or returned to AI.

Before you begin

Access: Inbox read access is required. Taking over or changing assignment requires the corresponding write permission.

• Know the team's handoff and coverage policy.
• Set your operator availability accurately.
• Open a conversation that represents the state you need to understand.

Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.

Step-by-step workflow

1. Confirm the scope and current state

   Use the Inbox navigation and queue segments to identify whether the conversation is waiting, assigned, handled by AI, or under human takeover.

   • Confirm the active company and Agent before editing.
   • Record the current state so the result can be compared after the change.
   • Stop if the screen or permission does not match the intended task.

2. Prepare the change

   Read the latest messages, internal context, tags, tickets, assignee, and visible ownership state before choosing an action.

   • Use the smallest change that completes the customer task.
   • Keep authoritative information in its owning source.
   • Review labels, dates, language, and customer-visible wording before saving.

3. Save and allow required processing to finish

   Assign or take responsibility according to team policy, then use a customer reply for customer communication and a note for internal collaboration.

   • Wait for the interface to confirm that the change is saved.
   • If synchronization, indexing, or publication is required, wait for its final state.
   • Reload the area and confirm the saved values persist.

4. Test the complete customer journey

   Resolve, hand back to AI, or leave the thread in the correct queue state so another operator can understand what remains.

   • Use a fresh session and a realistic customer scenario.
   • Check desktop and mobile when the result appears on a storefront.
   • Capture the exact failing step if the outcome differs from the expectation.

Important limits and operating notes

• A successful save confirms persistence, not every downstream synchronization or public update.
• Workspace permissions can hide an area or allow reading without allowing changes.
• Do not copy volatile catalog, account, or customer facts into narrative content as a workaround.
• Test only supported capabilities that are visible and configured for the current company.
• Keep changes in Inbox operations separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.

Verify the result

• The visible assignee and ownership match the operating decision.
• Customer replies and internal notes appear in the correct channel.
• The conversation is not left ambiguously between AI and human handling.
• The final queue or resolution state matches team policy.

Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.

Troubleshooting

A conversation cannot be found

Clear restrictive filters, search with another known identifier, and check the relevant queue and date range. Confirm that your role permits the conversation segment.

A reply is rejected or ownership changes unexpectedly

Recheck current takeover state and permissions, then refresh before retrying. Another operator or a server-side ownership change may have occurred.

Related guides

• work from the inbox
• take over a conversation and return it to ai
• manage operator availability
• create and use inbox views and filters