Mark Rickard

Why would my content block styles look different from native content?

In this example, both headers are H1. I am using the Picto template and it is up-to-date.

This has stopped working for me and I can't tell if changes to Zendesk have broken it. I'm using the Diziana Makem theme, Theme version 3.1.2, Templating API v1. I've added jQuery 3.6.1 to the script.js file, made sure the form IDs below are correct, and added the following code to my document_head file:

//Hide forms from anonymous users
jQuery( document ).ready(function()  {
if (HelpCenter.user.role=="anonymous"){
var tagsToRemove = ['1260815258330', '1900004317724', '13506320793243', '1260815256470', '1900004317704', '13528765623707', '5308706681371', '5073802798235', '1260815252470', '1900004315784', '17932684959515', '17932846343067', '17932966253339', '18224882477211', '17932893585691'];  
function removeTagsWeDontWant() {
$('.nesty-panel').on('DOMNodeInserted', function(e){
for(var i in tagsToRemove) {
$('li#' + tagsToRemove[i]).remove();
}
});
};
removeTagsWeDontWant();
}
}
);

I know. I did, at the time I commented here.

I also know you have no intention of updating the widget and prefer we use the API.

I think the article labels are in line with what Zendesk recommends. What I'm worried about is that AnswerBot is serving up articles for QUALITATIVE reporting and not QUANTITATIVE reporting, as if it's parsing similar words and not the actual labels.

As a customer, I believe that it would be beneficial for Zendesk to add functionality allowing customers to export Guide articles in PDF format. This feature would greatly improve the user experience by providing customers with an easy way to save and share important information from their interactions with Zendesk. Additionally, this feature will help product managers and engineers better understand how users are interacting with their products and services since they can track which articles were exported as PDFs. 

From a technical standpoint, adding this functionality is relatively simple compared to other features that have been implemented in the past. It requires minimal coding resources while still offering significant value for both customers and support teams alike. Furthermore, it could easily be integrated into existing systems without disrupting current processes or requiring major changes or updates from engineering teams or product managers - making implementation quick and cost-effective overall.  

Adding this functionality has numerous benefits for both users of your service as well as your own internal team members who need access to customer data quickly and efficiently; therefore I strongly urge you consider implementing such a feature in order increase engagement levels among existing clients while also attracting new ones due its ease of use when compared against traditional methods of exporting article content manually via copy/paste operations etc.. Thank you once again considering this proposal!

Dear Zendesk Team,

I hope this message finds you well. I am writing to express my strong support for the feature request to add a CC field to the Web Widget, as outlined in this feature request.

As a long-standing user of Zendesk Guides, I've come to appreciate the convenience and efficiency they bring to our customer support processes. The ability for end users to include CC recipients when submitting support requests via web forms is a critical aspect of modern communication. It not only ensures transparent and collaborative interactions but also helps streamline communication channels.

It's been noted that this feature request was created back in 2020 and has garnered significant attention from the Zendesk community. However, the absence of this functionality in the Web Widget has been a limitation, preventing us from achieving the same level of flexibility that the Help Centers offer.

By incorporating the CC field into the Web Widget, you would bridge an important gap and provide a more consistent experience across your platform. This enhancement would undoubtedly improve the user experience, encourage better communication practices, and align the Web Widget with the evolving needs of businesses and customers alike.

I urge Zendesk to give due consideration to this request and prioritize its implementation. Adding the CC field to the Web Widget would not only demonstrate your commitment to enhancing customer experience but also showcase your responsiveness to user feedback.

Thank you for your attention to this matter. I look forward to witnessing Zendesk's continued dedication to innovation and customer-centric solutions.

Best regards,

Mark Rickard
Technical Writer

I'm adding forms to the classic web widget. In Help Center, there is an optional CC field available but it's not in the web widget.

How can we add the optional CC (carbon copy) field into the web widget?

My contextual help doesn't seem to be working as expected.

The app URL is /mod/reporting/quantreport but the classic widget contextual help articles that are served up are not the top three articles where "mod reporting quantreport" is the help center search term.

Never mind! I forgot to add the jquery script to the document_head file.

https://support.zendesk.com/hc/en-us/articles/4408829274906-Importing-or-upgrading-jQuery

Would the jquery referenced above go in the script.js file or on the new request page? I added the script to the script.js file, adjusted for multiple forms to block from anonymous sight, and published it, and I don't see that it's working.