Use canned responses consistently
Keep reusable replies short, searchable, and easy for every operator to insert from the inbox.
Canned responses are shared building blocks, not a script to read word for word. Write the part that should stay consistent, then leave room for the operator to answer the actual question.
Review the library first
Open Canned responses to see replies grouped by category. Each card shows the title, shortcut, usage count, and current text. Remove old replies before adding new ones. A small library is easier to keep up to date.
Search before you create
Use the search field to find a response by title, message, or shortcut. Search for a word an operator would actually type, such as welcome or billing, rather than an internal project name.
Add a response with a clear shortcut
Select New response. Give the reply a title that describes the situation, choose a category, and add a shortcut such as /welcome. Keep the body in plain language and use variables only when the value is safe to show to a visitor.
With one content version, the editor stays single-language. If your sites use additional content languages, keep the translated reply variants together instead of creating separate canned responses for each language. See Manage content languages.
Check the message after inserting it
A shortcut such as /welcome should refer to one clear situation. Read the text in the conversation composer after inserting it. Visitor variables can be unavailable, so check the resolved message before you press Send.
If TopSoft4U serves both Polish and English visitors, put both versions under the same canned response. An operator inserts a saved reply. A Rule can send prepared text automatically. These workflows have different owners and triggers.
Preview the reply before saving. Ask one operator to use it in a real conversation, then adjust the wording if it sounds stiff or makes the next step unclear.
Was this page helpful?