Create, import, and maintain saved replies
Prepare reusable operator replies that remain accurate, personal, and easy to maintain Follow a safe workflow, verify the customer-facing result, and isolate common problems.
Prepare reusable operator replies that remain accurate, personal, and easy to maintain This guide keeps the work focused on Inbox saved replies 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 settings write access is required to manage saved replies. Operators need Inbox access to use them.
- Collect approved recurring replies from the support owner.
- Remove customer-specific details and obsolete policy text.
- Decide whether each reply should be created manually or imported from a reviewed file.
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 the saved or canned response management area and search for existing replies before adding another version.
- 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 concise titles and reply bodies with clear placeholders that an operator must review before sending.
- 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
For import, validate the supported file structure with a small sample, review the resulting records, and correct duplicates before a larger batch.
- 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
Insert replies in realistic conversations, personalize them, verify links and language, and schedule a content-owner review for future policy changes.
- 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 saved replies separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.
Verify the result
- Each saved reply has a unique, searchable purpose.
- Imported and manually created replies render correctly.
- Operators can find, insert, edit, and send the reply.
- No reply contains stale promises, unexplained placeholders, or customer data.
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
An import creates errors or missing replies
Check the expected columns, encoding, required values, and row limits using a small clean file. Do not repeatedly import the same full file without resolving duplicates.
A saved reply is correct but the sent message is wrong
Confirm the operator reviewed placeholders, language, links, and conversation context. Saved replies are editable starting points, not automatic final answers.