If you run a shared Slack or Teams channel with a customer, you have already seen it happen. Someone on their side drops a message like "honestly this saved us three days on the launch" or "the new export is exactly what we asked for, thank you." It lands, a few teammates react with an emoji, and then the conversation moves on. That message was a testimonial. It was specific, unprompted, and emotionally genuine — everything a good testimonial needs. And it vanished into the scrollback.
The shared channel is one of the richest and most-wasted testimonial sources a SaaS company has. The reason it gets wasted is that the channel feels too casual to "work." Asking to quote a Slack message feels like showing up to a backyard barbecue in a suit. But the informality is exactly why the praise is good, and there is a way to capture it that respects the vibe instead of killing it.
Why shared-channel praise is better than survey praise
The comments customers make in a shared channel are stronger than almost anything you will get from a formal request, for three reasons.
- It is volunteered, not extracted. Nobody prompted the message. A customer who types "this saved us three days" in a working channel is telling you something they actually believe, in the moment they believe it. That is the opposite of a survey response written to be polite.
- It is specific because it is operational. People in a working channel talk about the actual work: the launch that shipped, the report that finally reconciled, the bug that stopped costing them Fridays. Specifics are what make a testimonial believable, and a shared channel produces them as a byproduct of getting work done.
- The timing is perfect and free. The single biggest factor in whether an ask succeeds is catching the customer at a high point, which is the whole argument in when is the best moment to ask a customer for a testimonial. A shared channel timestamps the high points for you. You do not have to guess when they are happy — they told the channel.
Notice and save the moment when it happens
The discipline that separates teams who mine their shared channels from teams who do not is simple: someone on your side is responsible for noticing praise and saving it. Not acting on it — just saving it.
- Star or bookmark the message. When a customer says something quotable, the person who sees it stars it or drops it into an internal "kind words" channel. This costs five seconds and means the quote still exists next week when you are ready to ask.
- Save the context, not just the line. Screenshot or copy the surrounding message or two. "This saved us three days" is fine, but "we were dreading the migration and this saved us three days" is a testimonial with a story. The context is usually one message up.
- Note who said it and their role. A quote attributed to "Priya, Head of Ops at [Company]" is worth far more than an anonymous line. The channel already tells you both.
The point of saving first and asking later is that it decouples the emotional moment from the transactional ask, so you never have to interrupt a genuine thank-you with a request for paperwork.
How to ask — in the channel, and lightly
When you are ready, ask in the same channel, in the same register the channel already uses. The worst move is to switch to a formal email; it signals that you were treating their kindness as a lead the whole time. Keep it short and low-stakes:
"Hey @priya — you mentioned last week this saved you a few days on the launch. That made our day. Would you be OK with us quoting that line (with your name and role) on our site? Totally fine if not — no need to write anything, we'd just use what you already said."
Three things make this work. First, you are quoting their own words back, so there is no blank page for them to fill — the biggest reason people say no to testimonials is the writing effort, and here there is none. Second, you gave them an easy out, which paradoxically makes yes more likely. Third, you asked in public but low-key, so a yes is one emoji or one word away.
If they hesitate on using their name, offer to attribute it by role and company only, the way you would for any reluctant or privacy-conscious customer. Most of the time, though, someone who praised you unprompted in a working channel is happy to stand behind it.
Get permission right, even when it feels casual
The casual setting does not remove the need for a clear yes. A thumbs-up react to your ask is a reasonable permission signal for most contexts, but capture it deliberately.
- Confirm the exact wording you will use. Paste the final quote back: "Great — we'll use: 'We were dreading the migration and this saved us three days.' — Priya, Head of Ops." A confirmed final version prevents the awkward later moment where they feel misquoted.
- Keep the record. Because Slack messages roll off and channels get archived, save the ask, the quote, and the approval somewhere permanent. If you ever need to show that consent existed, the scrollback may be gone.
- Respect a soft no. If the reaction is lukewarm or they go quiet, drop it. A shared channel is a working relationship you will be in for months; a testimonial is not worth making it feel transactional.
Turn one yes into a repeatable habit
The teams that consistently harvest shared-channel testimonials are not more charming — they have a habit. Once a week, whoever owns the account skims the starred "kind words" and picks one worth asking about. Over a quarter, a handful of active shared channels will produce more usable, specific, credible testimonials than a dedicated request campaign, because the praise was real before you ever asked for it.
The mistake is thinking the channel is too informal to be a source. The informality is the source. Your job is just to notice the good line, save it before it scrolls away, and ask for it in the same friendly voice the channel was already speaking in.