Configure Smart Tags for triage
Create focused automatic triage labels and verify that they improve rather than obscure Inbox work Follow a safe workflow, verify the customer-facing result, and isolate common problems.
Create focused automatic triage labels and verify that they improve rather than obscure Inbox work This guide keeps the work focused on Inbox Smart Tags 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 configuration write access is required. Operators need Inbox read access to validate results.
- Define the operational decision each tag should support.
- Collect positive and negative conversation examples.
- Review existing manual and automatic tags for overlap.
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
Confirm the scope and current state
Open Smart Tag configuration and search for an existing rule that already covers the intended topic or outcome.
- 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.
Prepare the change
Create a specific name and description that distinguish qualifying from non-qualifying conversations without using customer personal data.
- 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.
Save and allow required processing to finish
Save the rule and allow the supported classification process to run on eligible conversations.
- 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.
Test the complete customer journey
Review tagged and untagged examples in Inbox, refine overly broad wording, and document how operators should use the tag in views or follow-up.
- 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 Smart Tags separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.
Verify the result
- Known positive examples receive the tag.
- Known negative examples remain untagged.
- Operators understand the tag's action and limitations.
- The tag improves a view or workflow without replacing conversation review.
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
Too many conversations receive the tag
Narrow the definition around the operational signal and test near-miss examples. Avoid a broad topic label when the team needs a specific outcome.
Recent conversations are not tagged
Check whether the rule is active and which conversations are eligible for processing. Do not assume a newly created rule retroactively classifies every historical thread.