Recent searches
No recent searches

Nick S
Joined Oct 16, 2021
·
Last activity Oct 04, 2024
Following
0
Followers
0
Total activity
141
Votes
33
Subscriptions
62
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Nick S
Nick S commented,
+1 on this. We need visibility if there is no email to send the notification for the request. In a similar way we receive an internal note if an SMS has not been sent, I'd love to see this logged in the ticket.
View comment · Posted Oct 04, 2024 · Nick S
0
Followers
0
Votes
0
Comments
Nick S commented,
I appreciate the workarounds listed to route some Messaging tickets using Skill Based Routing. We are already using Skill Based Routing for out team (and have already set the Skills Timeout function), so this wouldn't suit our use case.
The tickets we are looking to avoid routing are assigned to our more Technical team via the group, so changing the group also doesn't suit as they need to remain assigned to those users under that group.
Furthermore, those agents in the Technical team need to have Messaging capacity to assist with our general Support queries via Messaging channel (but not be routed any Messaging tickets belonging to the Technical group).
I understand this is quite a niche situation, are there any other workarounds which may help?
View comment · Posted Aug 26, 2024 · Nick S
0
Followers
0
Votes
0
Comments
Nick S commented,
Following along for an answer to Noelle Cheng ‘s question. We have several webforms and I’d love if we can choose which support address gets added to new webform submissions. Agents have advising using the app to check and change support address for all of their tickets is time consuming.
View comment · Posted Aug 21, 2024 · Nick S
0
Followers
0
Votes
0
Comments
Nick S created a post,
User Stories
As a Salesperson, I need to use Slack to engage our support teams using Zendesk as it is my channel of choice and easiest for me to use.
As a Salesperson, I need to use Slack to make it easier to collaborate with my peers in a way where all activity is logged against my existing ticket with support teams on Zendesk.
As an Agent, I need to be able to use Zendesk to respond to our sales staff on Slack as this was the channel they submitted their original request, as they may not want large amounts of email traffic.
Problem Definition
The specific problem we’re looking to address is to create a way where our Slack-oriented users who do not use Zendesk can create a ticket via Slack in a channel, have the ticket managed in Zendesk by our agents where all replies go to the original Slack conversation, and allows collaboration from multiple Slack users which all update the original ticket.
Current State
Whilst there are different ways to integrate Slack and Zendesk, neither seem to be effective in allowing seamless collaboration for users between the two systems.
There are four different integrations between the two systems, and neither of them is a ‘complete’ solution in the way it allows users to create a ticket from Slack which can be managed entirely via Slack with an agent who is working via Zendesk:
- Slack to Zendesk Ticket (manually via Slack Message Shortcuts)
- This method allows for a Zendesk ticket to be created via Slack, however this needs to be manually triggered by an agent in Slack, and there is no way for the agent to send replies via this same method. Despite creating the ticket via Slack, there is no way for agents to send replies to Slack from Zendesk. It can be confusing for our internal staff who use Slack to submit their requests via this channel, only to receive updates via email.
- Slack to Zendesk Ticket (via Slack Workflows)
- Like the above, if a Zendesk ticket is created via Slack Workflow, Zendesk does not recognise Slack as an option in the omnichannel composer to send a reply. We have a workflow where we invite users of Slack who do not use Zendesk to submit their requests via a Slack Workflow, however when the ticket is created all replies are received via email.
- Slack Direct Messages Channel
- This method allows us to create a ticket in Zendesk where the agent can opt to send replies via Slack, however the user is forced to use DMs which limits functionality in circumstances where they need to collaborate with other Slack users.
- Zendesk Side Conversations to Slack
- This workflow is the closest in which it allows users who primarily reside in Slack to send comments which are added to a Zendesk ticket (in the form of a side conversation). It resides in a Slack channel and allows all members to view the conversation and contribute with their own comments, all of which are added to the Zendesk ticket for agent visibility. The only issue with this is that this needs to be manually triggered by an agent in Zendesk as a side conversation, since Side Conversation via Slack is not an option in Zendesk triggers.
Desired Outcomes
Considering the above, we’d like Zendesk to consider possible changes to the integration. A desired path may look like:
- Slack user posts in a channel or submits a workflow to initiate a ticket.
- Zendesk ticket is created (manageable via triggers for routing etc).
- Slack channel automatically logs the ticket has been created via a post.
- Zendesk ticket contains Slack as an option in the omnichannel composer.
- Agent replies via Zendesk using the above option.
- The original Slack post receives an update in the form of a thread.
- Subsequent replies from the Slack user (or other collaborators) in that thread appear in Zendesk.
- Agent can view all responses to Slack thread via Zendesk.
- When the agent Solves the ticket, the Slack thread is updated for a final time, acknowledging the ticket is closed.
We acknowledge that there may be limitations from Slack which may not be feasible to resolve.
Posted Jul 25, 2024 · Nick S
3
Followers
5
Votes
5
Comments
Nick S commented,
+1. Even an error message to advise when an SMS can't send if the default number is a landline could be helpful.
View comment · Posted May 03, 2024 · Nick S
0
Followers
0
Votes
0
Comments
Nick S commented,
Hi all, just confirming the out of hours messaging only applies prior to the creation of a ticket? If a messaging ticket is already underway with a ticket number generated and back-and-forth responses, is there a way to let the end-user know they have replied while the agent who is assigned the ticket is currently offline or it's outside of business hours?
View comment · Posted May 02, 2024 · Nick S
0
Followers
0
Votes
0
Comments
Nick S commented,
+1. Would be very helpful for our end-users.
View comment · Posted Apr 30, 2024 · Nick S
0
Followers
1
Vote
0
Comments
Nick S commented,
Is there any way to report on the number of translations? (ie how many times it has been used?)
View comment · Posted Apr 17, 2024 · Nick S
0
Followers
0
Votes
0
Comments
Nick S commented,
Also noticed the comments do not seem to be sorted correctly - despite having Date selected in the drop-down the dates are all over the place. I find comments to be as helpful as the content, so would like the ability to view more at once and have them displayed in a proper chronological order.
View comment · Posted Apr 02, 2024 · Nick S
0
Followers
1
Vote
0
Comments
Nick S commented,
Definitely a refreshed view! Is there any way we can set the number of comments on articles? I like to read other Zendesk users' experiences and tips/tricks and the 5 comment limit per page is quite low.
Was there a change to default spacing, or is it the new background colour playing tricks? Everything seems a bit more compact now which makes it a bit less readable (in my opinion anyway).
I'm all for the change though, nice to freshen things up!
View comment · Posted Mar 26, 2024 · Nick S
0
Followers
0
Votes
0
Comments