最近搜索
没有最近搜索

T.J. (ZenBros)
已加入2021年4月16日
·
最后活动2023年4月26日
CEO & Founder of ZenBros https://www.zendesk.com/marketplace/partners/zenbros
关注
0
关注者
2
活动总数
30
投票
5
订阅
16
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 T.J. (ZenBros)
T.J. (ZenBros) 进行了评论,
2nd level IVR seems to not be accepting dialpad input. It's getting a bit difficult to troubleshoot issues from the Partner level without a support path to engage on behalf of a Customer's account. Please advise.
Repro:
- Press 1 to direct to 2nd level IVR
- Pressing any number does not trigger group routing as configured and redirects to Level 1 (Main menu) greeting.
查看评论 · 已于 2023年4月26日 编辑 · T.J. (ZenBros)
0
关注者
0
投票
0
评论
T.J. (ZenBros) 进行了评论,
Jennifer Rowe this is a HIPAA/BAA requirement. A Global setting needs to be identified as a priority for Development, if Zendesk wishes to continue marketing to Customers who require HIPAA / HDS compliance.
查看评论 · 已于 2023年3月28日 发布 · T.J. (ZenBros)
0
关注者
0
投票
0
评论
T.J. (ZenBros) 创建了一个帖子,
已于 2021年8月17日 发布 · T.J. (ZenBros)
0
关注者
2
投票
2
评论
T.J. (ZenBros) 进行了评论,
@... would love an upvote on this feature request, as its related.
[TALK] Feature Request(s): Custom attributes for logical conditions/triggers, automations, SLAs and KPI metrics are unavailable and far overdue
查看评论 · 已于 2021年8月02日 发布 · T.J. (ZenBros)
0
关注者
3
投票
0
评论
T.J. (ZenBros) 进行了评论,
Please review this related feature request and upvote if you agree:
查看评论 · 已于 2021年8月02日 发布 · T.J. (ZenBros)
0
关注者
1
投票
0
评论
T.J. (ZenBros) 创建了一个帖子,
Summary
Zendesk talk lacks the capability for custom attributes to be applied after a Requester has made an IVR route selection.
Current
Without the capability to apply custom attributes to inbound calls/tickets, based on Requester IVR route selection, best practices cannot be followed for common use-cases.
Example use-case (eCommerce / Retail)
The below use-case is one that usually identifies as an Urgent Priority request, as not executing this in the shortest time possible, will generally result in the eComm/Retail business having to ship a single order, twice. While this can be executed by the creation of additional groups, it is not ideal. In most cases, this is the exact same group of agents as the lesser-priority requests, such as "Where is my order?".
In short, the Group should be something like "Orders & Shipping Requests" with a custom attribute identifying which subtype/category the ticket is about, allowing logical conditions to execute.
Example - IVR Main Menu:
PRESS #1: "If you have questions about an existing order, please press 1"
Example - IVR Orders Menu (subroute #1)
PRESS #1: "If you need to make a change to your order, please press 1"
PRESS #2: "If you have questions about the location of your order, please press 2"
Expected (from example) - Press #1 (change order)
These calls/tickets require an urgent response, with the highest expediency in order to avoid potentially losing money on fulfilling the order (if they have to ship twice, due to the first order being shipped before the change was made).
- Apply tag / dropdown selection
- Assign SLA policy
- Assign priority
- Assign Group
Current (from example)
Groups must be created, as they are currently the only support method to route inbound Calls/Tickets, assign SLA policies, set priority, select from multiple business schedules, trigger external alerts via webhook (extremely urgent, like medical), etc.
Highest functional impacts (without applying duct tape)
- Triggers
- Automations
- SLA Policies / Prioritization
- Business Schedules
- Brands (rerouting from one brand, to a related brand, if desired, without needing the agent to select a separate brand upon answering the call).
Desired
The capability to select custom attributes, placed at the time of the Requester's IVR route selection, allowing for the following workflow optimizations and/or benefits to be implemented/configured:
- Conditional routing / (sub)categorization that doesn't require the unnecessary creation of additional groups
- Reduce the overall time-impact of requests made via TALK/phone channel
- Reduce time/cost impacts
- Enhance the Customer experience (prioritization)
- Make it easier on agents (less manual work -- can focus on supporting the customer)
Risks/Negatives/Zendesk impacts
- Development time
- Potential bugs
- API update will be required
- Creation of new instructional knowledge content
- Happier Zendesk Customers
- Happier Customers of Zendesk Customers
- :)
- <3
Thank you for your review and consideration!
已于 2021年8月02日 发布 · T.J. (ZenBros)
19
关注者
15
投票
8
评论
T.J. (ZenBros) 进行了评论,
In full transparency, multi-brand chat functionality is in need of some serious love. Not having the capability to configure brand-specific pre-chat forms is quite painful for those who have brand-specific agents. Ducttaping triggers to assign the correct brand when a ticket is created from the Chat channel exactly fantastic either..
查看评论 · 已于 2021年7月10日 发布 · T.J. (ZenBros)
0
关注者
4
投票
0
评论
T.J. (ZenBros) 进行了评论,
Decided to give this a spin, disabling our custom Slack webhook triggers. If there is no identified method, please consider this a feature request:
Configuration of triggers to post to specific channels based on conditions.
Example:
- Received at is support@domain.com
- Send message to "Support" channel in Slack
- Received at is billing@domain.com
- Send message to "Billing" channel in Slack.
Currently all added channels get blapped.
查看评论 · 已于 2021年1月30日 发布 · T.J. (ZenBros)
0
关注者
11
投票
0
评论