5 ms·

Do you have an example of “polite but curt” tone? I’m struggling to see what you mean.

xyproto 2y ago
Thanks for reaching out. The issue you’ve described seems to be on your end. Please check your settings or consult our docs for further guidance. If the problem persists, feel free to get in touch.
- Gustomaximus 2y ago
  Would it be worth putting a price to investigating? Message like: "Our premium support can investigate this for $XYhr. If the fault is at our end we will waive any fees. Please let us know if you wish to proceed."
  - zie 2y ago
    Oooh, the Microsoft approach! :)
  - filoleg 2y ago
    Take my advice with a grain of salt, as I am a customer rather than someone running a product with customer support. I would say this would only feel justified if the product pricing page already had clear tiers outlined for paid support. Putting a price per hour on customer support otherwise would make me feel like I am just being milked behind closer doors for more money, and non-paying customers are getting shafted. If a paid customer support tier is something you offer, imo it should be clearly outlined on publicly available pages with explicit explanation about the differences between free vs paid customer support. You suggesting it in private communications only would feel suspicious and shady to me as a customer. However, if the customer themselves suggested to pay you extra for that personal support, that’s a different story.
    - kadoban 2y ago
      That's fair, but also: sometimes the customer going away and not using the product anymore is the correct result for both sides.
- Aachen 2y ago
  I'd 100% expect that to be a template from someone who either has no clue and can't investigate, or has 200 other tickets to get to and couldn't be bothered to look into a case that isn't in the FAQ. It also does not say what makes you have this assumption and so it works only as a brick wall to alienate any customer goodwill you may have built up. Please never write this unless it's self evident why it's on the customer's side and you have good reason to think they're just trying to annoy you by reaching out despite that
  - xyproto 2y ago
    I hate this type of communication too, including templates and chatbots. It was just an example, though.
HelloMcFly 2y ago
[flagged]
blantonl 2y ago
"Check yourself before you wreck yourself"
shash7 2y ago
Both xyproto and Gustomaximus have solid examples. Here's more: - Be direct, Hi, the xyz feature is available on the PRO plan. You can upgrade to the PRO plan at app.saas.com/billing - Be brutal, Hi xyz, your card couldn't be charged for your Saas subscription, and hence your subscription has been deactivated. To reactivate, enter your card details app app.saas.com/billing - Be honest, Hello xyz, thanks for the feature request. We'll put it in our wish list but can't guarantee it will make the cut. - Be generous, Hey xyz, thanks for pointing that out. We have identified that as a bug and have pushed a fix for it. In the meanwhile, I've extended your trial by 7 days, on the house. Couple of other tips: - Dumb down your reply as much as possible. If you can't, throw your reply through chatgpt and make it dumb down. - Unless a support issue is very basic, reply after a few minutes if you're near your computer. Usually users figure out things on their own if given some time. - But don't allow issues to go stale. To really wow customer service, reply as humanely quick as possible, especially for existing customers. - Make your support timelines clear somewhere in your product, eg: Our support will respond within max 48 hours, but most responses take 2-3 hours. - Make your terms and privacy policy pages clear. People do read this. getharvest.com is a gold standard in this area.
- hn_throwaway_99 2y ago
  Just wanted to say thanks, I think you've given great advice. In particular this bullet point: > But don't allow issues to go stale. To really wow customer service, reply as humanely quick as possible, especially for existing customers. As a customer, the absolute worst possible thing for me is to be left in limbo, not knowing if my problem will be fixed in the next minute, hour, day, or never. While I may not be thrilled if the answer is "never", at least at that point I can move on and know that I'll need to solve the problem some other way.
  - hermitcrab 2y ago
    But if you respond consistently quickly, then some lazy customers will email you rather than bothering to look in the documentation. So there can be a downside to being too responsive.
- 2y ago
benatkin 2y ago
From the sound of it, the politeness is the shallow politeness that you can easily get with ChatGPT. The curtness is defending from the users expecting too much, which can include delaying handling issues before properly checking if they're real. I experienced this with Vercel and it probably makes economic sense for them. (BTW I really should cancel my Vercel account but haven't decided to take the time to migrate yet.) https://x.com/search?q=vercel%20benjaminatkin_&src=typed_query&f=live https://x.com/search?q=vercel%20benjaminatkin_&src=typed_que... The reason it can be framed as curtness is because they're being curt about the expectations, and the real expectations are pretty low. "Sure, I can delay really addressing the issue for a couple weeks. You're only paying me 40 bucks a month, why would you expect more? The goal of responding within two days is just for a canned response." See, they were curt and didn't let me demand something more than I deserved, like being able to use the product I'm paying for in the next several days!

Thanks for reaching out. The issue you’ve described seems to be on your end. Please check your settings or consult our docs for further guidance. If the problem persists, feel free to get in touch.

Gustomaximus 2y ago
Would it be worth putting a price to investigating? Message like: "Our premium support can investigate this for $XYhr. If the fault is at our end we will waive any fees. Please let us know if you wish to proceed."
- zie 2y ago
  Oooh, the Microsoft approach! :)
- filoleg 2y ago
  Take my advice with a grain of salt, as I am a customer rather than someone running a product with customer support. I would say this would only feel justified if the product pricing page already had clear tiers outlined for paid support. Putting a price per hour on customer support otherwise would make me feel like I am just being milked behind closer doors for more money, and non-paying customers are getting shafted. If a paid customer support tier is something you offer, imo it should be clearly outlined on publicly available pages with explicit explanation about the differences between free vs paid customer support. You suggesting it in private communications only would feel suspicious and shady to me as a customer. However, if the customer themselves suggested to pay you extra for that personal support, that’s a different story.
  - kadoban 2y ago
    That's fair, but also: sometimes the customer going away and not using the product anymore is the correct result for both sides.
Aachen 2y ago
I'd 100% expect that to be a template from someone who either has no clue and can't investigate, or has 200 other tickets to get to and couldn't be bothered to look into a case that isn't in the FAQ. It also does not say what makes you have this assumption and so it works only as a brick wall to alienate any customer goodwill you may have built up. Please never write this unless it's self evident why it's on the customer's side and you have good reason to think they're just trying to annoy you by reaching out despite that
- xyproto 2y ago
  I hate this type of communication too, including templates and chatbots. It was just an example, though.

HelloMcFly 2y ago

[flagged]

blantonl 2y ago

"Check yourself before you wreck yourself"

shash7 2y ago

Both xyproto and Gustomaximus have solid examples. Here's more: - Be direct, Hi, the xyz feature is available on the PRO plan. You can upgrade to the PRO plan at app.saas.com/billing - Be brutal, Hi xyz, your card couldn't be charged for your Saas subscription, and hence your subscription has been deactivated. To reactivate, enter your card details app app.saas.com/billing - Be honest, Hello xyz, thanks for the feature request. We'll put it in our wish list but can't guarantee it will make the cut. - Be generous, Hey xyz, thanks for pointing that out. We have identified that as a bug and have pushed a fix for it. In the meanwhile, I've extended your trial by 7 days, on the house. Couple of other tips: - Dumb down your reply as much as possible. If you can't, throw your reply through chatgpt and make it dumb down. - Unless a support issue is very basic, reply after a few minutes if you're near your computer. Usually users figure out things on their own if given some time. - But don't allow issues to go stale. To really wow customer service, reply as humanely quick as possible, especially for existing customers. - Make your support timelines clear somewhere in your product, eg: Our support will respond within max 48 hours, but most responses take 2-3 hours. - Make your terms and privacy policy pages clear. People do read this. getharvest.com is a gold standard in this area.

hn_throwaway_99 2y ago
Just wanted to say thanks, I think you've given great advice. In particular this bullet point: > But don't allow issues to go stale. To really wow customer service, reply as humanely quick as possible, especially for existing customers. As a customer, the absolute worst possible thing for me is to be left in limbo, not knowing if my problem will be fixed in the next minute, hour, day, or never. While I may not be thrilled if the answer is "never", at least at that point I can move on and know that I'll need to solve the problem some other way.
- hermitcrab 2y ago
  But if you respond consistently quickly, then some lazy customers will email you rather than bothering to look in the documentation. So there can be a downside to being too responsive.
2y ago

benatkin 2y ago

From the sound of it, the politeness is the shallow politeness that you can easily get with ChatGPT. The curtness is defending from the users expecting too much, which can include delaying handling issues before properly checking if they're real. I experienced this with Vercel and it probably makes economic sense for them. (BTW I really should cancel my Vercel account but haven't decided to take the time to migrate yet.) https://x.com/search?q=vercel%20benjaminatkin_&src=typed_query&f=live https://x.com/search?q=vercel%20benjaminatkin_&src=typed_que... The reason it can be framed as curtness is because they're being curt about the expectations, and the real expectations are pretty low. "Sure, I can delay really addressing the issue for a couple weeks. You're only paying me 40 bucks a month, why would you expect more? The goal of responding within two days is just for a canned response." See, they were curt and didn't let me demand something more than I deserved, like being able to use the product I'm paying for in the next several days!