Miguel Cordero Collar

Hello,

In general I really do not understand many of the design choices, it really looks very old-fashioned and not following typography best practices.

• Colors
• Font size and line heights: headings way to big + too many different font sizes
• Mix of random serif and non-serif font families
• The paddings, margins and locations of certain elemnts makes components ocuppy too much space…
• I hate the huge zendesk at the bottom, I love zendesk, but i don't need that huge logo there…
• Several broken components when interacting with navigation bar:
  • 
  • 

Overall I'm really dissapointing with the overall design, I would have expected much better design choices from Zendesk, the Zendesk Support UI is amazing…

Our agents make quite a high volume of outgoing calls, so they encounter quite often the “error” notification of "Cannot connect to number" or “No answer”.

This notification needs to be dismissed manually, intead of dissapearing after X seconds like other notifications.

They would like for this to be changed.

Hello,

According to the documentation it is possible to dynamically change the app icon the location "ticket_editor".

I have followed the documentation:

• Using file name icon_ticket_editor.svg
• I used the correct format for the svg

<svg xmlns="http://www.w3.org/2000/svg">  <symbol id="default" viewBox="0 0 18 18">    <circle cx="9" cy="9" r="5"/>  symbol>
  <symbol id="mySymbol" viewBox="0 0 18 18">    <path d="M0 0h9v3H0zM0 7h18v3H0zM0 14h18v3H0zM15 3l3-3h-6"/>  symbol>svg>

And it does not work. The icon is not displayed and if I try to use the function

client.set('iconSymbol', 'mySymbol')

I get the error:

client.js:160 Uncaught (in promise) APIUnavailable: Could not find handler for: "iconSymbol"

Probably this function is no longer supported and the docs are outdated, but if there was a solution that'd be amazing.

I also tried in the app to test "client.set('iconSymbol', 'mySymbol')" in location "top_bar" and it is working without any issue, so I think it is not my fault.

+1 this is a very useful and probably easy to implement feature

Hi, a user on our instanced reported the following problem.

He was trying to add someone in CC who was not an existing user, so he clicked create user:

1. Click on CC

2. Add user on CC selection menu

3. Add name and email and click Add user

4. Nothing happens, no feedback

In the console you get a 403 error because the user is not authorized to create user based on the setting for his role:

There should be some feedback informing the User that he has no right to perform this action and he should contact the Admin or the option to add user should not be there.