Help center JavaScript cookbook



image avatar

Charles Nadeau

Zendesk Documentation Team

Edited May 07, 2025


7

37

41 comments

How to access a agent email from script.js theme? I found the HelpCenter, but there is a deprecate/legacy notice, so there are no guarantees. Is there another way?

let agentEmail = HelpCenter.user.email;

1


Hi All, 

We are conducting research to improve our Help Center developer experience and would love to talk to any of you that have tried to edit Help Center theme code.

If you are interested please answer sign up here and answer the 3 survey questions. I will reach out to you to setup a 30 min Zoom call.

The interview will be a semi-structured interview where we would like to hear you take us through examples of what you have done or tried to do with customizations and your experience with the tools, documentation etc. you used.

Looking forward to talking to all of you.

Gorka Cardona-Lauridsen
Sr. Product Manager, Zendesk Guide 

0


I've found the solution (thanks to a genrous contirbutor) of my previous question and put it on a special article here

I have another question now 😂

Here :

You show how to prepopulate, can you show please show howto put text that fades when the user click on the field? (like a suggestion) here is an example : https://developer.mozilla.org/en-US/docs/Web/CSS/::placeholder

 

Many thanks 

0


Hi, Does anyone has the solution to put easily a field side by side to another one (to save and avoid scrolling) please

🥺🥺🥺

 Best regards!

0


Hi Nick, 
 
Ticket placeholders will not be rendered in a custom request form, it will be displayed as it is, Ticket placeholders are used in automations, macros, targets, triggers, and widgets as containers for dynamically generated ticket and user data.
 
I hope this helps, 
 
Best,

0


Hi team, does Zendesk support custom ticket placeholders in the subject field?

$('#request_subject').val("Credit Request - Agency name: {{ticket.ticket_field_ID}}, CID: {{ticket.ticket_field_ID}}");
$('.request_subject').hide();

The above code successfully hides the subject, but unfortunately the custom field data does not carry across to the subject, but rather it all appears as it does in the code. 

0


Is it possible to use dynamic content in the javascript file?  I'm trying to localize the Contact Us button text:

 $('.request-callout a').text('Contact Us ').attr('href','/hc/requests/new');

I have the dynamic content {{dc.kc-footer-contact-button}}.

I know how to add these to the .hbs files and use them in many places. However, I'm not sure how, or if, it can be used in the javascript.

0


Hi Shawn! My first thought would be that the last two options are drop-down or multi-select fields, which require that you pass in the tag for the value, as opposed to the field name. The syntax is slightly different with this being JSON as opposed to JQuery, but the general info can be pulled together from this article

If that doesn't resolve the issue for you, could you let us know if you're seeing any console errors that could shed some light on this?

0


I'm successfully able to autofill only one custom field in a ticket form using the script.js file.  My method is:
if(ticketForm == 7386956538260) {
$('.form-field.request_subject').hide(); // Hide subject
//Auto-fill fields//
$('#request_subject').val('Agency/Application SPOC change request');
$('#request_custom_fields_21608582').val('zendesk_assistance');
$('#request_custom_fields_21626618').val('User_Management_incl_Permissions_ID_Req_/_Passwd_Reset_etc');
$('#request_custom_fileds_21617267').val('Zendesk_Support_Portal');
}

My subject, a standard field, and field 21608582, a custom field, are auto-filling successfully.  The other two fields are not auto filling.  

Any insight?

Shawn A.

0


Hi T5 Admin,

Thanks for clarifying that for me!

Unfortunately, it's not possible to modify the behavior of the in-built custom field date picker. I can definitely see the use case for such a feature though, so I'd encourage you to create a post on the feature request community page. This will allow greater visibility to our product teams, as well as give others the opportunity to upvote and provide additional use cases for such a feature. You can find our guidelines around creating feature requests, here.

Have a great day!

Tipene

0


Sign in to leave a comment.