Live data from Hacker News

Slack Shared Channels

slackhq.com

11–20 of 72 posts

Re: Slack Shared Channels

#11

Our whole company has relied on this for the past few months in order to communicate with some of our clients, rather than invite them into our private Slack. It's been wonderful.

When companies are having to hire people and set policy to police their Slack channels for endless discourse by their employees, that is NOT wonderful.

Why is that worse than corporate governance over communication via email or other instant messaging?

Re: Slack Shared Channels

#12
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

Don’t blame the tool for mismanaged expectations.

Re: Slack Shared Channels

#13

Our whole company has relied on this for the past few months in order to communicate with some of our clients, rather than invite them into our private Slack. It's been wonderful.

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?

Re: Slack Shared Channels

#14
post #12
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

Don’t blame the tool for mismanaged expectations.

If the tool is presented as an instant messenger, people often get upset when responses aren't instant.

Re: Slack Shared Channels

#15
post #14
post #12

Earlier quoted context omitted.

Don’t blame the tool for mismanaged expectations.

If the tool is presented as an instant messenger, people often get upset when responses aren't instant.

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.

Re: Slack Shared Channels

#16
This is new? I assumed Slack would already have had this for some time. What’s their story around security and compliance? - it’s good to see another choice emerging alongside Bloomberg/Eikon/Symphony for inter-firm chat but it’s hard to justify having more than a couple of these on any given desktop.

Re: Slack Shared Channels

#17

Our whole company has relied on this for the past few months in order to communicate with some of our clients, rather than invite them into our private Slack. It's been wonderful.

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 you are talking "publicly" or not.

Re: Slack Shared Channels

#18
post #14

Earlier quoted context omitted.

If the tool is presented as an instant messenger, people often get upset when responses aren't instant.

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.

Re: Slack Shared Channels

#19
post #14
post #12

Earlier quoted context omitted.

Don’t blame the tool for mismanaged expectations.

If the tool is presented as an instant messenger, people often get upset when responses aren't instant.

Would be an interesting slack integration to enable setting SLAs. Say a message prefaced with (question) starts a timer and then you can track an SLA against that.

I would actually love that for open channels.

Re: Slack Shared Channels

#20
post #12
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

Don’t blame the tool for mismanaged expectations.

If you expect to not reply immediately (or "soon"), what's the point of using any chat program instead of email?

Either you're fine with short, possibly intense (maybe even urgent) conversations, and chat works well.

Or, people want to communicate more async and you can take a day or two to answer. People generally use forums/emails for this.

Post reply on HN