Recent searches
No recent searches

Abraham K.
Joined Apr 16, 2021
·
Last activity May 31, 2023
Following
0
Follower
1
Total activity
19
Votes
0
Subscriptions
6
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by Abraham K.
Abraham K. created an article,
Issue symptoms
I want to enable the side conversations feature, and don't see the option to activate it in Admin Center. What are the subscription requirements to enable side conversations?
Resolution steps
Side conversations is a feature available on Suite Professional plans and higher. For more information on our current Suite plans and features, see the article: About the Zendesk Suite plan types.
If the option to enable side conversations is missing, your Zendesk account may be on a legacy version that requires the Collaboration add-on to access this feature. For more information, see the article: About Zendesk product legacy add-ons.
Edited Sep 01, 2023 · Abraham K.
0
Followers
2
Votes
0
Comments
Abraham K. created an article,
Question
What's the difference between ticket merging and ticket threading?
Answer
Ticket merging is when separate existing tickets are manually combined. A ticket merge is common when two tickets with the same issue are created. Merging tickets will create a comment in both tickets indicating the merge event and result in a closed status of the merged ticket. For more details on merging tickets, see the article: Merging tickets.
Ticket threading is when an inbound email update is automatically applied to a specific ticket record as part of an ongoing conversation. If a ticket update seems out of place for the conversation on your ticket, see the article: Why do emails thread to the wrong ticket?
Edited May 22, 2023 · Abraham K.
0
Followers
2
Votes
1
Comment
Abraham K. commented,
If the email is somehow entered incorrectly notification of this depends on the server for the email domain. Some will send a "bounce-back" message advising that you have contacted an invalid email address, and if this does happen you would find that message in the Suspended view as it would be detected as an automated sending system (and thus suspended to prevent looping automated responses). You can find out more about this here: https://support.zendesk.com/hc/en-us/articles/4408834888730-Common-issues-with-email-deliverability
If you get most of your traffic by web form submissions from your users the most effective way of making sure typos or blatantly incorrect emails are not getting into your system is to require email verification as a part of the submission process. This is just a simple message sent to the address of the submitting user asking them to confirm that the email address is correct and they have access to the account. Once a user profile has the email verified they are not asked to perform that action on future contact with your system. You can find out more about this option here: https://support.zendesk.com/hc/en-us/articles/4408886752410-Verifying-an-end-user-s-email-address
I hope this helps!
View comment · Posted Nov 06, 2021 · Abraham K.
0
Followers
0
Votes
0
Comments
Abraham K. commented,
View comment · Posted Oct 28, 2021 · Abraham K.
0
Followers
0
Votes
0
Comments
Abraham K. commented,
Hi Amelia: Unfortunately the Twitter handle information from the contact details in a User profile do not populate into search information at all at this time.
View comment · Posted Oct 28, 2021 · Abraham K.
0
Followers
0
Votes
0
Comments
Abraham K. commented,
This may be where building a ticket view would be more reliable for the post-4:30 workflow as that will display all active information in your system without requiring alteration of the ticket data, as opposed to system triggers which would only shift tickets if they received an active update during the "off hours" portion of a programmed schedule.
View comment · Posted Oct 27, 2021 · Abraham K.
0
Followers
0
Votes
0
Comments
Abraham K. commented,
Because time definitions are relative based on timezone there are no direct automation conditions which reference clock time for activation. Automations also only run once an hour at the start of the hour so there is no guarantee that the automation will start processing exactly at a specified time.
You would likely be best served creating a ticket view that allows your agent that is monitoring things after 4:30 pm full visibility to tickets regardless of who is assigned to the ticket. This would allow them to see items which still require responses, have replied outside after 4:30 pm, and not disrupt ticket ownership when staff are back the next day.
Another option is to have an office schedule (see https://support.zendesk.com/hc/en-us/articles/4408842938522-Setting-your-schedule-with-business-hours-and-holidays) set with hours ending at 4:30 pm and a trigger that activates if you are outside of Office Hours when a ticket is updated by a customer response. You could have the action on this be assigning the ticket to your agent directly, or just sending them an email update to check the ticket. However, this would only apply to tickets that receive an update when you are outside of business hours and not ticket that have been unanswered or are waiting on action before office hours end.
I hope this helps!
View comment · Posted Oct 26, 2021 · Abraham K.
0
Followers
0
Votes
0
Comments
Abraham K. commented,
An indefinite reminder set for a specific interval would not be possible as that sort of function would be too easily exploited or just misconfigured to create spam traffic from our systems. You can modify the automations to have a larger number of reminders, but there must be a finite number of business hours between the last interaction from the customer and when the events run. The best practice under our current logic and ticket structure is define a point where the ticket will get closed out from non-communication and if they reply after that point our system will be able to build a new Follow-Up ticket that links back to the older request in the system.
Hope this helps you understand things a bit better!
View comment · Posted Oct 26, 2021 · Abraham K.
0
Followers
0
Votes
0
Comments
Abraham K. commented,
Hi Patrick,
"Immediate" is a bit inaccurate. Automations run one at a time, checking all non-closed tickets in your system one entry at a time. In a small database this could take less than 30 seconds to do the full run. But as a ticket database gets larger, and as you add more automations, this checking period has the potential to get longer. While this use of a "gap break" trigger may not be needed for most cases and may not be needed if you have limited ticket traffic now, down the road you might run into edge cases that slip through and cause confusion without a trigger like this in place.
Abraham K. | Customer Advocate
View comment · Posted Sep 22, 2021 · Abraham K.
0
Followers
0
Votes
0
Comments
Abraham K. commented,
Hi Patrick,
You've got a logic there that I think has a lot of promise, though there is a strong potential for a timing gap with how you have it written. The gap is a potential for between the activation of automation 1 and 2 the end-user may reply in on the open ticket while the tag is present, then it would return to Pending automatically and cause a potential miss. Adding in a trigger that would detect an end-user update while that tag is present and then clear the tag could break this potential automation gap.
I hope this helps!
Abraham K. | Customer Advocate
View comment · Posted Sep 21, 2021 · Abraham K.
0
Followers
0
Votes
0
Comments