Hacker News new | comments | show | ask | jobs | submit login

Good question. Each visitor gets a dedicated channel. It makes it easy to respond back to them. When conversation is ended, we archive the channel. If they ever come back we unarchive it and you have previous chat history.



So I love the idea and execution but have one major worry before signing up.

If you're creating an entirely new channel and archiving it every time, does that mean my archived channels list will be full of potentially thousands of channels? Ignoring that I'll struggle to find channels I may want to revive (we archive channels a lot here), will Slack cope well with this? (We've seen what happens if they have over a certain user count.. so I'd be worried what would happen here.) Is it possible to entirely wipe a channel after a certain period of time rather than archive?

Update: OK, I'm an idiot. I just realized I could spin up a second free Slack account just for this use..


It's nice to read about people using other apps as primary interface to their own. And all the quirks they are forced to do to make it work.

I run this small email-helpdesk<-->Trello app [1] and I thought I was the only one trying to come up with the best ways to map features from what Trello has builtin to what my app needs.

Users sometimes find it awkward, but in the end it works very well.

[1]: http://boardthreads.com/


Awesome. I wanted to build this for ourselves, but I'll just sign up and use your product. Great job.


How does it identify the user when they come back?


We store a UUID in their browser and send that along so if they chatted before we un-archive their previous channel to give the Slack operator all the context.


Is there any way to get/set this UUID so I can allow the user to use the same channel if I have my own way of identifying them?


This is in the works. We will provide a way for you to "sign" a request with a userId, so we can guarantee you set the id, and not someone else.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: