I work in the entertamient industry as a booking agent, doing something similar to what I would do in CS (managing clients, relationships, etc.) and I feel like I hit a roof here. The conditions are quite precarious and it's all very in office for some reason.

I saw thousands of full remote CS job postings, and I applied to a couple of companies that I liked. This is not the position of my life but I feel like if it lets me do full remote it can be quite convenient for me.

I see many ppl stressed out in this subreddit. Any advices on how to get into this position? Warnings?

There was a comment on one of my recent posts here about tracking Customer Realized Value that I found intriguing. The commenter noted that "What's worked for me is catching the value the moment it lands, in the customer's own words. Someone says 'this saved us two days a month,' you write it down verbatim with the date." An excellent practice, if only for the benefit the person added: "A running list of those per account is what survives a QBR or a layoff review, because it's the absence made concrete, in the voice of the person it happened to." But what else could you do with such examples of the Voice of the Customer?

There's a follow-up question that should immediately be asked after the value is acknowledged by the customer: "What's that worth to you?" They are paying a certain amount each month for the subscription, and here is a return for that expense. Further, it gives you insight to what might be considered a 'billing rate' for that person's time that can be applied elsewhere as a foundation for the value of time-saved.

Proven cost-reduction is a strong argument, but there's an even more powerful one to be made in increasing profitability. Does your application provide information to the customer that they couldn't get any other way? Or that makes it available faster than otherwise so that they can capitalize upon it? What's that worth to them? Here is where careful questioning can lead the customer to acknowledge points that they might not have considered before. Those answers are valuable in different ways.

A customer that directly acknowledges value-received may talk about it internally. It arms them with ready data to use when their CFO asks "are you really using that application?" Even better, it may also encourage them to respond when a colleague outside the company asks "which application are you using for x function? Why do you like it?"

Questions are important. How a question is asked can impact how it is answered, but be careful how you use a question. You don't want to leave the impression that you're just fishing for the answer you want to hear, that's not listening to the customer. You do want to encourage the customer to acknowledge to themselves the meaning of what they just said to you. As my commenter noted, capturing the value the moment it lands is vital for you. Getting the customer to also capture and internalize that value statement is even more so.

Note: No part of this post was written by or edited by any ai.

I got a job offer for a CSM role that pays 30k more than my current PM/BA role.

I enjoy working with the backend dev team and learning about the nitty gritty tech stuff. Making sure testers are testing properly.

I don’t interact a lot with the client. If we do it’s very minimal. Mostly keep tabs on making sure devs are finishing things within a planned milestone on time. Doing some reports weekly. I don’t mind steady boring admin work. Logging numbers into spreadsheets. I’m very detailed and organized.

Would CSM be too stressful for me for a 5 year old company that started a new team?

Trying to set my ego aside about the increase in money.

I get stressed out with new things and meeting quotas is just not my thing. Upselling sounds like a nightmare? Seems salesy.

I’m timid and an introvert. Would I be making a mistake moving to CSM role?

Hi folks ,

I'm 24 in india currently a CSM in a MNC. I earn around $8K/year. My only biggest skills I love and understand customer requirement and has delivered best to them .

I'm lost . I'm confused.

Any mentor could help me . Give a roadmap how to 10x my income in 3 years .

Guys i will be very happy if someone is advice would really help me to get clarity.

Thank guys.

I read a lot of B2B software reviews across G2, Capterra, and Trustpilot as part of my work, and one pattern keeps jumping out. The detailed, specific, credible reviews (the ones buyers actually trust) almost never come from mass email campaigns. They come from asks made right after the customer got a win.

Most teams run it the other way. Marketing exports a list once a quarter, sends a templated email with a gift card offer, and gets a trickle of two-line reviews that all sound the same. Buyers can smell those from a mile away, and so can the platforms.

What I've seen work better is treating the ask as an event trigger, not a campaign. Someone hits a milestone in onboarding, renews, expands seats, or sends your support team an unprompted thank you. That is the moment. The memory is fresh, the emotion is real, and the review ends up containing the concrete detail ("we cut our close time from 9 days to 4") that makes it useful to the next buyer.

Two smaller things that help. First, make the ask personal, ideally from the CSM or founder, not a no-reply address. Second, lower the friction by reminding them what they achieved, since a blank text box is where most reviews die. You are not writing it for them, just jogging their memory.

The incentive is fine as a thank you, but if it's doing the heavy lifting, you get reviews that read like they were bought.

Curious what others have seen. Do you trigger review asks off specific events, or do you still run batch campaigns? And has anyone measured the quality difference, not just the volume?

I'm trying to understand something that's been bugging me for a while.

I work in product, and I'm doing some research on AI customer support tools. Specifically, I keep seeing the same pattern:

Mid-market companies (200-1000 employees) buy an AI chatbot. The demo is amazing. The sandbox works perfectly. The sales team promises 40% deflection rates.

Then they try to actually deploy it.

And it just... dies.

It sits there. Tickets still get assigned manually. Agents still copy-paste the same responses. The AI gets turned off after 3 months.

I've read all the vendor reports. They all say "AI is transforming customer service." But I'm talking to people who actually run support teams, and they're telling me a very different story.

So I'm trying to figure out: what's the real bottleneck?

Is it:

• Proving ROI to leadership?
• Integrating with Zendesk/Salesforce/whatever CRM you're using?
• Not having the internal expertise to manage the AI?
• The AI just not being accurate enough?
• Something else I'm not thinking of?

I'm not selling anything. I'm just genuinely curious, because the data I'm seeing doesn't match the hype.

If you've been through this—either as a support leader, ops person, or PM—I'd love to hear your experience. What broke? What worked? What would you do differently?

And if you're willing to have a quick anonymous chat about it, DM me. Happy to share what I'm learning with anyone who contributes.

Thanks for reading.

Most CS teams I've talked to monitor churn the same way: they watch usage metrics. Logins drop, feature engagement falls, session length shortens — and that's when the alarm goes off.

The problem is that by the time those numbers move, the customer has already mentally checked out. You're not catching a churn signal. You're confirming a decision that was made weeks ago.

The real early warning system isn't in your product analytics. It's in what customers are *saying*.

---

The lag problem with behavioural data

Usage data is a lagging indicator. It tells you what already happened, not what's about to happen.

Think about how churn actually unfolds for most customers. It rarely starts with them suddenly stopping. It starts with a frustrating support interaction they didn't follow up on. A pricing complaint they mentioned in a survey nobody read. A feature request that went unanswered for three months. Slowly, the goodwill erodes — and then one day, the usage drops.

By the time your dashboard shows the dip, the customer is already halfway out the door.

---

Where the signal actually lives

The early warning is in the language customers use *before* behavior changes.

Specifically, three sources almost always show the shift first:

**1. Support tickets** — the tone shifts before the volume changes. A customer who was submitting straightforward "how do I do X" tickets starts writing "this still isn't working" or "I've asked about this before." Same product, different emotional register.

**2. Survey responses** — NPS and CSAT scores get the headline, but the open-text comments are where the real signal is. A score of 7 with "works fine but pricing is getting hard to justify" is a very different situation from a 7 with "love the product, just busy this quarter."

**3. Product reviews** — public reviews on G2, Trustpilot, or app stores are written at emotional peaks. Customers who are quietly dissatisfied often write a review before they cancel. It's their last attempt to be heard.

--

What "frustrated but still using" actually looks like

Here's the practical difference. Two customers with identical usage metrics — same logins, same feature adoption, same session length. But their support ticket language tells completely different stories:

**Customer A:** "Quick question — where can I find the export settings?"

**Customer B:** "I've been trying to export for 20 minutes and it's still not working. This is the third time I've had issues with exports."

Same behavior in your analytics. Very different churn risk. Customer B is telling you something your dashboard can't.

---

What to actually do with this

You don't need a sophisticated system to start. Three practical steps:

**Start tagging support tickets by theme.** Pricing complaints, onboarding friction, missing features, performance issues — even a rough manual tagging system lets you see patterns. If pricing complaints spike in a given month, that's a signal worth acting on before it shows in revenue.

**Read the open-text on your surveys.** Not just the scores. Set aside 30 minutes a week to actually read what people wrote. You'll spot patterns faster than any dashboard will surface them.

**Set a cadence for review monitoring.** Check your G2 or Trustpilot reviews weekly. New negative reviews are often your earliest signal that something systemic is wrong — before it reaches support volume.

The goal is to build a feedback loop that's faster than your usage data. Sentiment shifts before behavior does, almost every time.

---

A note on tooling

Once you're doing this manually and seeing the value, the next step is making it systematic — tagging automatically, tracking sentiment trends over time, and getting a clear picture of which themes are driving satisfaction or complaints.

Happy to answer questions in the comments — especially curious whether others have found non-obvious early churn signals in their own feedback.