P1 Template Beginner Doing/Managing All

Writing Customer Communication Templates That Protect Your Metrics and Your Brand

Message templates for common scenarios (delay, damage, wrong item, cancellation) that stay compliant with marketplace review-solicitation rules while sounding human.

Published 2026-09-05 Last updated 2026-09-05 Last verified 2026-09-05 ● Evergreen review

Who this is for

Sellers who want consistent, on-brand replies to common scenarios without writing each one from scratch.

Time to complete

20 minutes to build your own set

What you'll need

Your current common message scenarios (pull from your last month of actual buyer messages)

Key terms

Review solicitation policy, Templated response, Personalization token

Why templates need to exist — and why they can't just be copy-pasted verbatim

A template solves a real problem: writing a thoughtful, well-structured reply from scratch every time is slow, and under time pressure the quality of an improvised reply tends to drop exactly when a customer is already frustrated. But a template that's copy-pasted with zero customization reads as exactly what it is — most buyers can tell a fully generic "we're sorry for the inconvenience" from a reply that actually engaged with their specific situation, and the generic version does measurably less to defuse frustration or prevent a negative review.

The fix isn't avoiding templates — it's building templates with explicit personalization points baked in, so using one is fast but never fully generic.

Core templates worth having ready

Shipping delay:

Hi [name], thanks for your patience — I want to give you a real update on your order for [product]. [Specific reason if known: a carrier delay, a supplier issue, etc.] Your new expected delivery is [date]. I'm sorry for the wait, and I'll follow up if anything changes before then.

Item arrived damaged:

Hi [name], I'm sorry to hear your [product] arrived damaged — that's not the experience we want you to have. I'd like to make this right: I can send a replacement or issue a full refund, whichever you'd prefer. [If needed: a photo of the damage helps us flag it with our shipping process.]

Wrong item shipped:

Hi [name], I'm really sorry — it looks like [wrong item] was sent instead of [correct item] you ordered. That's on us. I'll get the correct item out to you right away [or: issue a full refund], and you're welcome to keep or donate the item you received at no charge.

Seller-initiated cancellation (e.g., stockout):

Hi [name], I'm sorry to say we need to cancel your order for [product] — [brief, honest reason: we're temporarily out of stock / a pricing error]. Your refund has already been processed and should show up within [platform's typical refund timeframe]. [If relevant: expected restock date, or a comparable alternative product link.] I'm sorry for the inconvenience this causes.

Return/refund acknowledgment:

Hi [name], I've received your return request for [product] and it's approved — no need to wait for further confirmation. [Return instructions if a physical return is required, or: no return needed, your refund is already processing.] Thanks for letting us know, and sorry the item didn't work out.

Backorder / pre-order status update:

Hi [name], quick update on your order for [product]: [current status]. Expected to ship by [date]. Thanks for your patience — happy to answer any questions in the meantime.

Personalization points to always fill in

At minimum, every template should have the buyer's name, the specific product, and a specific reason or next step filled in before sending — these three details take seconds to add and are usually the difference between a reply that reads as genuine versus one that reads as canned regardless of the underlying tone.

Staying compliant with review-solicitation rules

Most marketplaces have specific, and sometimes strict, rules about what a seller can say regarding reviews — many prohibit offering a refund, discount, or any incentive in exchange for a positive review, or even asking a dissatisfied buyer to "update" or remove a negative review in exchange for a resolution. Build your templates to avoid any language that could be read as conditioning a resolution on review behavior in either direction — for example, resolve the underlying issue first and unconditionally, and if you do send a general "we'd appreciate your feedback" request afterward, keep it unconditional and platform-compliant rather than tied to the specific resolution you just provided.

Because review-solicitation rules differ by platform and are enforced seriously (violations can trigger account action, not just a warning), review each marketplace's current policy directly rather than assuming one platform's rule applies to another.

Building a lightweight scenario-to-template map

As you accumulate real buyer messages, build a simple reference (a shared doc or a saved-replies feature in your helpdesk tool) mapping common scenarios to their base template, so a new team member handling messages can quickly find the right starting point rather than reinventing a reply style for a situation someone else has already handled well before.

Reviewing and updating templates over time

Revisit your template set periodically against the actual messages coming in — a scenario that keeps showing up without a ready template is a signal to write one, and a template that keeps needing heavy editing before sending is a signal it needs a rewrite, not just continued patching in the moment.

Common mistakes

Sending a template completely unedited, with no personalization, which reads as generic and can worsen an already-frustrated buyer's sentiment.
Including language that conditions a refund, discount, or resolution on the buyer leaving or changing a review.
Assuming one marketplace's review-solicitation rules apply identically on another platform.
Never revisiting the template set as new recurring scenarios emerge.

Best practices

Build in explicit personalization points (name, product, specific reason) rather than a fully static block of text.
Resolve the underlying issue unconditionally before ever mentioning reviews or feedback, and keep any feedback request separate and unconditional.
Maintain a shared, easily searchable template reference so template quality doesn't depend on one person's memory.
Review and refresh templates periodically against real incoming messages.

Checklist

Base templates written for your most common scenarios (delay, damage, wrong item, cancellation, return)
Each template includes explicit personalization points, not just static text
Templates checked against current review-solicitation rules for each marketplace used
Templates stored somewhere shared and searchable for anyone handling messages
Periodic review scheduled to update templates against real recurring scenarios

Related tools & guides

FAQs

Can I ask a satisfied customer to leave a review?

Generally yes, within each platform's specific rules — most allow a neutral, unconditional request for feedback, but check the current policy for each marketplace, since some restrict even neutral solicitation methods (like which channel you can use to ask) more than others.

How many templates do I actually need to start?

Five or six covering your most frequent scenarios (delay, damage, wrong item, cancellation, return, backorder) covers the large majority of real messages — build more as new recurring scenarios show up rather than trying to anticipate every possible case upfront.

Next recommended guide

Customer Service Automation and Helpdesk Tools for Ecommerce

→