移除中差评模板(参考)
很多亚马逊的新手卖家都对于撰写 移除差评 的电邮感到十分烦恼,这次我们特别以BQool 的优秀卖家为例来说明,并附上模板,让更多的新手卖家作为参考,并且设计出自己最适合的电邮模板。当然,旧的卖家也可以考虑修正,模板并不是一个模板通用到底,而是依照实际碰到的状况来做修正的!
首先是移除差评(Feedback)
主旨的部份尽量语气直接用字简明,让买家收到时再收信匣的预览界面就可以一目了然。再来是内容的部份,以下是请买家提供 SKU / ASIN 来做查询,可以依照您的需求来做内容调整。首先都是要先表达歉意,以及还有愿意积极处理的诚意,最后再表达由衷地感谢给予改进的机会。(以下为参考模板)
电邮主旨:Regarding your AMAZON.COM order feedback with 店铺名称
Dear Customer,
You recently left us a negative feedback regarding your order placed with 店铺名称 on AMAZON.COM. We are sorry about the inconvenience.
Please kindly provide us with the SKU number under the bar code label on the item packaging or on the box or plastic wrapping the item was in. Please let us know exactly what's the model of your device and we will look into this matter.
Sorry for the inconvenience and thank you for giving us the opportunity to rectify the matter.
Sincerly yours
店铺名称 Customer Service Team
接着是移除负评(Product Reviews):
主旨当然也是一样简明扼要,不要添加太多无谓的赘字。
因为留下 Reviews 是比较需要多步骤的操作,也不需要购买就能留评!
[BQool 分享]什麽是「amazon verified purchase」的商品评论?
记得!不管买家留下好评跟差评!首先先表明对对方愿意花时间写下 Reviews 致谢(基本礼貌先做好,老外有些吃软不吃硬,有时后你愿意提供免费商品给他,她还会跟 Amazon 检举你..)要这样的思路想,买家已经花时间帮你写评论,他们是无偿的,写下来不管好评或者差评,不管麦家有没有办法心平气和的去看待,都要感谢一下!作为改善产品的基准!
之后再开始表明对于 Reviews差评的歉意与具体改善的方法(如真诚地道歉、提供退款),之后就是展现客服的诚意,让对方了解他的意见是被认真重视的,给予顾客被尊重的感觉。(以下为参考模板),比较重要的是,千万不可以跟买家协商:退款给您,但是请您留好评,这样的字句在。
电邮主旨:Regarding your Amazon Product Review
Dear Customer,
Thank you for your purchase and taking the time to write a product review. We are terribly sorry to hear the product you received is defective and would like to know if we can send you a free replacement or assist you with a refund.
Customer reviews is important to us and we value your response. All responses will be used to further improve the quality of our service and products.
Please let us know how we may assist you to resolve the issue you have experienced.
Sorry for the inconvenience and thank you for giving us the opportunity to rectify the matter.
Sincerly yours
店铺名称 Customer Service Team
资料来自互联网
热门文章
2022-11-21 17:17
2022-11-21 16:41
2022-11-21 16:32
2022-11-21 16:23
2022-11-21 15:58
2022-11-21 15:38
2021-11-27 11:08
2021-11-12 11:20
2021-10-21 11:20
2021-10-12 14:50