2025-10-06 – Weekly Customer Service News : Remote roles are on the rise!

Last week in our community, we saw a rise in discussions about the increasing availability of remote roles in customer service. Members shared insights on adapting to this trend and the skills required to excel remotely. Additionally, the forum buzzed with tips on managing real-time churn alerts and the quirks of call transfers. Practical advice on keeping automated responses personal also drew significant interest.


This Week’s Hot Topics

Weekly Customer Service Jobs: Remote roles increasing this week
There’s a noticeable uptick in remote positions, and members are discussing how this shift is changing the landscape of customer service careers.
Read more here

Real-time churn alerts that work
Explore practical solutions for implementing effective churn alerts that can help you stay ahead of customer turnover challenges.
Read more here

Accidentally transferred a call to… me
A humorous thread where members share their mishaps with call transfers and what they’ve learned from these experiences.
Read more here

Shortcut snippets that still feel human
Discover how to maintain a personal touch with shortcut responses in customer interactions—without sounding like a robot.
Read more here

Auto-merge rules for support contacts
Discusses best practices for setting up auto-merge rules to streamline support contact management efficiently.
Read more here

FAQ/Guidelines
A refresher on the community guidelines to ensure a positive and productive forum experience for all members.
Read more here

Admin Guide: Getting Started
New admins can find a helpful guide to kick-start their journey in managing the platform effectively.
Read more here

Thinking About a Career in Customer Service? Here’s What You Need to Know!
A comprehensive look at what to expect when considering a career in customer service, from skills to job satisfaction.
Read more here

How Did You Get Your First Customer Service Job?
Members share their first steps into the customer service world, offering inspiration and advice for newcomers.
Read more here

Is Customer Service a Good Long-Term Career?
Engage with diverse viewpoints on the sustainability and growth potential of a career in customer service.
Read more here


Thank you for being a part of our community. Looking forward to another week of engaging discussions and shared learning.

For “remote roles”, we run a 4-hour overlap; cuts handoff pain, but squeezes APAC coverage.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠‌‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‌‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍​⁠‌‌‌‍⁠‍‌⁠‌​‌‌‌‌‌‍‌​‌‌​​‌‍​‌‌‍​⁠‌‍⁠⁠‌​​‌‌​​⁠‌​‌‍‌​‍⁠‌‌‍‌‌​‌⁠‌‍⁠⁠​‍​‍‌⁠⁠‌​​

We killed most call-transfer pain by making every transfer “warm” and adding a 90‑second context macro in Zendesk — , blind transfers were tanking CSAT. For the remote shift, we also pipe real-time churn alerts into Slack with a 5‑minute throttle so reps don’t get spammed during handoffs, @Guide. It adds about 30 seconds to handle time, but our CSAT bumped +0.4 and APAC doesn’t need extra overlap as often.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠‌‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​​​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌⁠‌‌‌‍‌‍‌⁠‌⁠‍‍‌‌‌⁠‌‌​​‌​‍⁠​⁠‍‌‌​‍​‌⁠​‌‌​​‍‌​‌‍‌⁠‍‌‌‍⁠‌‌​⁠‌‌‌‍‌​‍​‍‌⁠⁠‌​​

@levi1866 We’ve been using a 60-second baton-pass Loom clip attached to churn-alert tickets so the next time zone gets context fast; it cut first-response misses about 25%, though you have to guard against people turning it into a 5-minute monologue — anyone else try video handoffs?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠‌‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠​⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌​‌‌​​‌‌‍‌‌‌⁠‌‌‌​⁠​‌​‍‍‌​​⁠‌​⁠‌‌‌​​‌‌⁠⁠​‍⁠‌‌​‍⁠‌‌‌​​‍⁠‌‌‍‍‍‌​​⁠​‍​‍‌⁠⁠‌​​

On the ‘real-time churn alerts’, we route them to a Slack channel with a 30-minute SLO and trigger a single ‘auto-reply once’ in Zendesk that ACKs in under 2 minutes with owner + next step; that alone cut surprise cancels about 15%. Works great for remote, but only if you de-dupe alerts and cap pings per ticket, @perez85.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠‌‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍⁠​‌‍⁠⁠‌⁠​​‌‍⁠⁠​⁠‌‌‌⁠‌⁠‌​‌⁠‌‌‌‌‌⁠​‍‌⁠‌⁠​⁠‍​‌‌​‌​⁠‌‍​⁠​​‌‌⁠⁠‌‌‌⁠​‍​‍‌⁠⁠‌​​

Quick example: we require the first line of every internal note to read ‘Owner • Next step • ETA’, and a simple trigger blocks the handoff if that’s missing so remote teammates don’t chase ghosts. @lmartinez this pairs nicely with a short “open huddle” window for live consults; only caveat is it needs occasional audits — like flossing for your queue.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌‍​⁠‌⁠​⁠‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠‌‌​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​​​⁠​‌​⁠‍​​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍‍‌‌⁠‌‍‌‌‌​‌⁠‌​‌‍‌⁠‌‍⁠⁠‌‍‍‍​⁠‌⁠‌​‍‌‌‌‌⁠‌‌​‍‌‍‍​‌​‍‍​⁠‌​‌​​‍‌​‍​​‍​‍‌⁠⁠‌​​