Canned replies: saving the answers your team types every day

Updated 2026-09-24 · 4 min read · By the Convo360 team

The tax of typing the same sentence forty times

Watch a support agent for an hour and count how many times they write essentially the same thing. Opening hours. Return policy. How long a refund takes to reach a bank account. The exchange process for a size swap. In most Indian support teams, somewhere between a third and a half of all outgoing messages are variations on a dozen answers.

Each one takes thirty to sixty seconds to type properly, and typing it properly is the problem. Under pressure the fourth version of an answer is shorter and blunter than the first, and by the fortieth it has lost the sentence that actually prevented the follow-up question.

This is what saved replies are really for. The time saving is pleasant, but the consistency is the point. The customer who writes at 6 pm on a Saturday should get the same clear explanation as the one who wrote at 10 am on Monday, and a tired agent should not have to reconstruct it from memory.

Building the library from real messages

Do not sit in a room and imagine the list. Export a week of outgoing messages and read them.

You are looking for sentences that appear again and again with small variations. Group them, and for each group write one good version, the version you would want a customer to receive on your best day. That becomes the saved reply.

• Start with the eight to twelve most repeated answers.
• Write each one properly, with the detail that prevents the follow-up question.
• Give it a short shortcut an agent can type without thinking: hours, refund, exchange, cod.
• Stop. Add more only when the team asks for them.

Libraries fail by growing. Past twenty or thirty entries, finding the right reply takes longer than writing a fresh one, and agents quietly stop using them.

Using them on Convo360

In Convo360 the saved replies live in the reply box itself rather than in a settings page somewhere else. Type a forward slash and the list appears, narrowing as you keep typing. Type the shortcut and press Enter and the reply lands in the box, filled in and ready.

There is also a lightning button beside the box for anyone who would rather browse than remember shortcuts. Both open the same list, ordered by how often your workspace actually uses each one, so the reply your team reaches for most sits at the top rather than whichever happens to start with an early letter.

Writing and editing happen in that same popover. The moment an agent notices they are retyping an answer is the moment they want to save it, and sending them to another screen to do that is how libraries never get built.

Placeholders without the robot voice

A saved reply that begins "Dear Customer" announces itself as a template. Placeholders fix that, but only if they are handled carefully.

Convo360 offers four: the customer's name, their first name, your name and your business name. You insert them from a menu rather than typing them, so nobody has to remember the exact spelling, and they are filled in the moment the reply lands in the box. That last detail matters: the agent reads the finished sentence and can still change it before sending, rather than discovering a stray placeholder in the customer's chat.

The other half of the problem is what happens when a value is missing. A customer who wrote from a number with no saved name would otherwise produce "Hi ,". Convo360 drops the placeholder and the space it sat in, so the sentence simply reads "Hi, your order is on its way." It is a small thing that is very visible when it goes wrong.

The habits that keep replies from feeling canned

The failure everyone has experienced as a customer is the reply that answers a question you did not ask. It happens when an agent matches on a keyword rather than reading the message.

Three rules prevent most of it. Always read the whole message before inserting anything. Always edit the inserted text, even if only to add one line that shows you read it. And never use a saved reply for bad news, because apologies written in advance read exactly like apologies written in advance.

It also helps to review the library quarterly. Policies change, delivery partners change, and a saved reply quoting a seven-day refund window after you moved to five is worse than no saved reply at all. Give one person ownership of the list and twenty minutes a quarter.

Measuring whether it worked

The obvious metric is handling time, and it will improve. The more interesting one is variation.

Pick one common question and read ten answers your team sent last month. If the quality swings widely between agents or between morning and evening, saved replies will do more for your customers than any training session. Read the same ten a month after introducing them and the spread should be visibly narrower.

Watch reopen rate too. If a saved reply is technically correct but leaves something out, tickets using it will come back more often than others. That is the cheapest possible signal that a particular reply needs rewriting, and it is invisible unless you are measuring resolution rather than response.

Step by step

1. Export a week of outgoing messagesRead them and group the sentences that repeat with small variations. Those groups are your library.
2. Write eight to twelve properlyOne good version of each, including the detail that prevents the follow-up question.
3. Give each a short shortcuthours, refund, exchange, cod. Something an agent can type without thinking.
4. Insert placeholders from the menuUse the name, first name, agent and business placeholders rather than typing them, so spelling is never wrong.
5. Review the library quarterlyOne owner, twenty minutes. Delete what is unused and fix anything quoting an out-of-date policy.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.