Write quick replies that still feel human
Use reusable WhatsApp replies to save time while still answering the customer’s actual question, protecting trust, and moving the conversation toward a clear next step.
What you will leave with
- A small library of reusable replies for common customer moments
- A practical rule for what should and should not be automated
- Better ways to personalise price, order, delay, and follow-up messages
- A workflow that keeps templates helpful without turning conversations robotic
Step 01
Use quick replies for repeated information, not for every conversation
Quick replies work best when the same accurate information needs to be sent repeatedly.
Good uses include business hours, service areas, information needed for a quotation, payment-verification wording, pickup instructions, delivery expectations, and a polite acknowledgement while you check availability. These are details that should stay consistent from customer to customer.
Do not use a saved reply simply because it exists. If a customer asks a specific question, answer that question first. A long generic message can make the customer feel ignored even when the information inside it is technically correct.
- Save repeated factual information.
- Answer the customer’s actual question first.
- Keep replies short enough to scan.
- Do not replace judgment with a template.
Step 02
Write each quick reply around one purpose
A reusable reply is easier to use when it has one clear job.
Create separate replies for quotation details, current hours, delivery areas, deposit terms, payment verification, order confirmation, delays, and follow-up. Avoid one giant message that covers pricing, policies, payment, delivery, and marketing at the same time.
Give each reply a simple internal shortcut or name so you can find it quickly. The customer should receive only the wording, not your internal label.
- One reply for one common situation.
- Simple internal shortcut names.
- No unrelated information bundled into the message.
- One clear next action for the customer.
Step 03
Personalise the first line and the decision-making details
A template should remove repetitive typing, not make every customer sound interchangeable.
Use the customer’s name when appropriate, reference the product or service they asked about, and update the details that affect the decision. A quotation reply should reflect the actual job. A delivery message should use the real date and location. A payment reminder should use the correct invoice or amount.
Never leave placeholders such as [Customer Name], [Amount], or [Date] in a message you send. If you are moving quickly, pause long enough to confirm the variable details before sending.
- Customer name where appropriate.
- Actual product, service, or order reference.
- Correct amount and date.
- Correct location, timing, or next step.
Step 04
Create a quotation-information reply
A good quotation reply asks only for the information that changes scope or price.
For example, a cleaning business may ask for area, property type, number of rooms, preferred date, and a few photos when condition affects the work. A catering business may ask for guest count, menu preference, date, venue, and service level. A designer may ask for deliverable type, deadline, content readiness, and intended use.
Do not send a twenty-question form for a simple enquiry. Start with the minimum information needed to decide whether you can quote accurately.
- What service or product is needed.
- Quantity, size, or scope.
- Location and timing.
- Only the extra details that materially change the price.
Step 05
Create a price reply that explains what the customer gets
A price without scope can create more questions than it answers.
If the offer has a fixed price, pair it with the main inclusions. If the price varies, explain what determines the final amount and offer to prepare a quotation after collecting the necessary details.
Avoid a generic 'price depends' reply. Tell the customer what it depends on. Also avoid automatically offering a discount before understanding the customer’s concern.
- State the standard price when it truly applies.
- List the main inclusions.
- Explain variables that require a quotation.
- Do not hide compulsory costs.
Step 06
Use a payment-verification reply instead of trusting screenshots
A saved message can make payment verification consistent and respectful.
A useful reply can thank the customer, explain that the business will confirm the transaction through its own payment channel, and state that the order or receipt will be updated after verification. This avoids accusing the customer while still protecting the business.
Do not ask the customer to send passwords, PINs, or one-time security codes. A screenshot may help identify a transaction, but it should not replace checking the trusted payment source.
- Acknowledge the customer’s message.
- Verify through your own trusted channel.
- Record partial payments accurately.
- Issue a receipt only after verified payment.
Step 07
Prepare delay and problem messages before you need them
Difficult conversations are easier to handle well when the basic wording has already been considered.
Create a short starting template for a delayed order, unavailable item, rescheduled service, supplier issue, or correction to an earlier mistake. The message should explain what changed, what you know, what you do not yet know, and what options the customer has.
Do not hide behind a template when the problem is serious. Customers need a specific update, not a vague apology copied to everyone.
- State what changed.
- Give the current realistic timing.
- Offer the available options.
- Promise only the next update you can actually provide.
Step 08
Use order-confirmation replies to prevent misunderstandings
A reusable confirmation structure helps you remember the details that need to be checked before fulfilment.
Confirm the exact item or service, quantity or scope, total amount, payment status, date or deadline, location, and next step. Ask the customer to correct anything that is wrong.
The confirmation message is useful communication, but the important transaction should still be represented by the appropriate quotation, invoice, payment, or customer record when those records are needed.
- Item or service.
- Quantity or scope.
- Amount and payment status.
- Date, location, and next action.
Step 09
Keep follow-up replies contextual
A saved follow-up should remind you of the structure, not erase the reason for contacting the customer.
Reference the real context: the quotation sent on Tuesday, the stock they asked you to check, the booking date they wanted, or the time they asked you to contact them again. A message tied to the customer’s previous request feels more useful than a generic 'any update?'
If the customer already declined or asked not to be contacted, do not send the saved follow-up simply because it is scheduled.
- Mention the prior conversation.
- State the specific pending decision.
- Use the agreed timing.
- Stop when there is no legitimate next action.
Step 10
Review saved replies when the business changes
Templates become risky when old prices, addresses, policies, or payment details remain hidden inside them.
Review quick replies after a price change, bank-detail change, service-area change, new business hours, updated delivery policy, or major offer change. Search for old amounts and old contact details instead of assuming every template was updated.
Remove duplicate replies and wording nobody uses. A small reliable set is safer than a large library of outdated messages.
- Check prices and payment details.
- Check hours and service areas.
- Check delivery and cancellation wording.
- Delete duplicate or obsolete replies.
Step 11
Use templates as a starting point, then keep the record in LaunchBOS
Fast customer communication is useful, but the business still needs connected records when a real transaction or future action exists.
Use LaunchBOS quotation, invoice, payment, receipt, customer, and follow-up records when the conversation reaches those stages. That keeps the important history connected even if the WhatsApp wording changes.
LaunchBOS does not currently send WhatsApp quick replies automatically. Use its customer message templates for wording support and keep WhatsApp as the channel where you personalise and send the message.
- Use message templates for wording support.
- Create the customer record when appropriate.
- Create documents for scope and money.
- Create a follow-up for a dated future action.
Chat → next action
Use the reply, then save what needs to happen next.
Quick replies help with communication. When the conversation creates a real customer task, save it as a follow-up with a date.