Support teams repeat useful information every day: delivery times, setup steps, refund rules, links, and answers to common questions. Rewriting it wastes time, while blind copy-paste makes the conversation sound robotic.
The repeated work saved replies remove
Saved replies now live directly in the Lavenity composer. Type / on a new line and continue with a few letters. The picker searches both the reply title and its body, so operators do not need to remember an exact command name.
Use the arrow keys to move through results, Enter or Tab to insert, and Escape to close the picker. The reply is inserted into the draft rather than sent immediately. You can adjust the greeting, remove an irrelevant sentence, or add context before the customer sees it.
Search and insertion inside the composer
Replies are shared across the workspace and managed from Settings. Give each one a short, recognizable title and keep the body focused on a single job. A small library of reliable answers is faster to search and easier to maintain than dozens of near-duplicates.
The best saved replies preserve room for judgment. Store the facts and the proven structure, then let the operator adapt tone and detail to the person in front of them. Speed should remove repetitive typing, not remove the human from support.
How to preserve a personal response
This workflow keeps knowledge close to the conversation and gives new teammates a useful starting point from their first shift — without asking anyone to maintain a separate document full of snippets.
Build a useful saved-reply library
Start with ten questions the team genuinely receives every week. Give each response a short searchable title, store only verified facts, and leave room for details the operator must personalize. One reply should solve one job; large universal templates are difficult to find and even harder to adapt.
Assign a regular library review. If a price, return policy, link, or product interface changes, an outdated saved reply spreads the error faster than manual typing. Remove duplicates and update the source response instead of creating another version with an almost identical title.
Frequently asked question
Is a saved reply sent immediately after selection?
No. Lavenity inserts it into the composer draft. The operator can change the greeting, remove an irrelevant paragraph, add customer-specific detail, and then make a deliberate decision to send.