정문균

Recently, the JWT calling method is being changed from GET to POST through a notice mail.

The way we're using it right now is
SAML: Default Login Method
JWT: When accessing from the mobile app, log in to JWT through the landing page

However, when you proceed with POST JWT, you get the JavaScript syntax that goes to the SAML login page.

The response data are as follows.

We need to use both JWT and SAML at the same time as we need to support both PC and mobile apps.

 

SSO in JWT format allows customers to log in and re-access previously viewed pages using return_to

However, with SSO in SAML form, there is no return_to property, so the customer will be moved to the main page after logging in.

There are a lot of inconveniences for customers in this regard, but we can't solve that problem in any way.

I repeat that there is no way to contact Zendesk Support, and I would like to add this to the next feature improvement roadmap.

Hi.

Is the document "A" excluded from the recommendation when a customer searches the Help Center, reads the document "A" and generates a ticket by pressing the "submit request" button at the bottom of the document?

Also, will "A" be excluded from the automatically recommended documents after registering the inquiry?

If the document I've been reading is recommended, the customer may be angry, so I'm going to remove the recommendation function after checking it in advance.

 

 

 

We are responding to customers by receiving inquiries and answers from others through side conversations.

but, there is a problem that some side conversation answers are generated with new tickets.

I inquired about the cause to Support, but there was no clear answer and only repeatedly answered that it was normal ticket generation.

What else can we check out?