Live data from Hacker News

Slack Shared Channels

slackhq.com

31–40 of 72 posts

Re: Slack Shared Channels

#31
post #27
post #12

Earlier quoted context omitted.

Don’t blame the tool for mismanaged expectations.

No, don't use a instant messaging tool like an answering machine. You set the expectations when you open up slack as a support avenue.

Is this intended for support? We use single channel guests at the moment to collaborate on projects with external companies without any issue. This seems to be geared towards that.

Re: Slack Shared Channels

#32
post #31
post #27

Earlier quoted context omitted.

No, don't use a instant messaging tool like an answering machine. You set the expectations when you open up slack as a support avenue.

Is this intended for support? We use single channel guests at the moment to collaborate on projects with external companies without any issue. This seems to be geared towards that.

I imagine it's intended for any use case in which you want to communicate with people outside your company via slack, but don't want to invite them into your org. I was responding to these comments:

>You customers are feeling like they can ask any question and get an answer in 1 minute, and if you dont answer them straight away then they are unhappy. Definitively not something I recommend

>Don’t blame the tool for mismanaged expectations.

Re: Slack Shared Channels

#34
post #2

It was beta before today? These channels have been a thing for forever, I assumed it was already GA.

Had the same thought. We have had it at our company for almost a year and I just thought it was a feature of Slack..

I have to wonder what "beta" or "moved out of beta" in this context means.

I suspect this announcement was just "oops we forgot to move this feature out of beta, lets announce that its GA"

Re: Slack Shared Channels

#35
post #8

The issue with the channels are the same than communicating over slack: You customers are feeling like they can ask any question and get an answer in 1 minute, and if you dont answer them straight away then they are unhappy. Definitively not something I recommend

I took over a customer who previously only got answers over email in 1 week, and they were useless crappy answers even then. When I started slacking them they got useful answers in 1 minute and the customer was much happier.

My point is that even if the customer feels they can only get an answer in 1 week so they don’t expect any more than that, that feels shit especially if the answer sucks.

Re: Slack Shared Channels

#36
post #8

The issue with the channels are the same than communicating over slack: You customers are feeling like they can ask any question and get an answer in 1 minute, and if you dont answer them straight away then they are unhappy. Definitively not something I recommend

It's all about setting expectations. I use this both to let customers in our Slack, and talk to people we're we are the customer. In the later case, the bigger company said "our reps will only reliably respond within these hours, may be delayed by x minutes".

Once we know the ground rules, we're all happy. I've taken to doing the same with our customers, so they know not to ask each and every tiny question with a @here ping, or whatever, and that our employees don't live in Slack 24x7.

Re: Slack Shared Channels

#37

Earlier quoted context omitted.

How do you communicate about things related to the project, but doesn't need to have the client involved in? Do you have a separate internal channel per client?

My company has this, and I highly recommend it in general for security and data loss prevention purposes. Any channel that may have external to the company users must have `-ext` at the end of the name and there should also be a non `-ext` channel for internal discussion that relates. This ends up working really well because the channels sort together next to each other and you can tell very clearly from the name if…

I feel like they should just have different themes for private and public channels. That way, you know at a glance!

Re: Slack Shared Channels

#38
I think this is a great idea and I'm biased because I came up with the same idea when brainstorming Slack new features in a job interview. One thing that concerns me about it is the amount of confidential information that people bandy about on their corporate Slack that could accidentally be leaked to a shared channel. Is that something that comes in practice?

Re: Slack Shared Channels

#39
post #18

Earlier quoted context omitted.

This is spot on. You should blame the tool for mismanaged expectations if the tool inherently sets the expectations. I'm just trying to imagine ways you could use slack and not set an expectation of having someone online to chat to. Use a bot to resond with "we'll get back to you when we can"? There's no option that doesn't feel like an incredibly frustrating experience for the user.

No matter how you look at it, if you can't reply in under a few minutes, you shouldn't be presenting your support as a chat. Just use email.

Other support chat tools have solved this for quite some time with a queue and display of estimated waiting time. You may not get an initial response immediately, but once an agent becomes available they're assigned the chat and do communicate synchronously.

In comparison, Slack has no way to indicate that an agent is already working with someone else in another channel, nor any good way to assign a specific owner--customer questions are dumped into a channel with X support agents as members, one of whom will hopefully respond.

Re: Slack Shared Channels

#40

Earlier quoted context omitted.

My company has this, and I highly recommend it in general for security and data loss prevention purposes. Any channel that may have external to the company users must have `-ext` at the end of the name and there should also be a non `-ext` channel for internal discussion that relates. This ends up working really well because the channels sort together next to each other and you can tell very clearly from the name if…

I feel like they should just have different themes for private and public channels. That way, you know at a glance!

In the shared channels it says right above the text input: `foo is in this channel` (with their logo) where `foo` is the name of the other company.

It makes it really obvious at a glance before you type into the textbox.

Post reply on HN