

You can now choose whether or not tickets made via slash command post to the channel for each queue. We’ve also added more flexibility to the slash command setting. When someone publicly posts a question in an associated Slack channel, replies will automatically move to a DM, allowing end-users to comfortably raise requests while knowing their private information will not be open to the entire company. Once the setting is enabled, all conversations on tickets in that queue will only occur in the requester’s DM with the Halp bot. With Halp’s new private reply settings, teams dealing with sensitive information can ensure that confidential details are kept private.Īdmins can designate a queue as sensitive by toggling on or off the private replies” setting at the queue-level. Managing Sensitive Requests in Slack TodayĪlthough many organizations train their employees to use public Slack channels for their questions, when it comes to teams like HR, Legal, and Finance, it’s not uncommon for requests to deal with sensitive details that are best not shared publicly.įor example, an employee might go into the #ask-hr channel and say something pretty generic like “I have a benefits question.” The initial ticket title itself won’t be sensitive, but the communication that occurs thereafter might include sharing private information like the user’s address, social security number, and other Personal Identifiable Information (PII). That’s why today we’re excited to announce new privacy settings that empower teams across your business to work conversationally in Slack while keeping sensitive information confidential.

Our feature set was fo cused on making it dead simple to create a ticket and report on it.īut as we saw our usage grow beyond the traditional IT Ops use case to teams across the entire business – from Sales Ops and Customer Success, to HR and Legal – we knew our feature set would have to evolve to meet each new team’s unique needs. When we first built Halp, our user base was comprised mostly of IT professionals managing common technical support requests lik e keyboard replacements or access requests.
