Zendesk trigger add CC end user and Freshservice service catalog audit log: three help-desk gaps we are testing

Two jobs are awkward in Zendesk and Freshservice today. In Zendesk, a trigger can copy support staff on a ticket, and the request for a native way to copy the customer in has been open since 2009. In Freshservice, the audit log article says every action across the service desk is recorded, but its examples do not name Service Catalog items. Zendesk’s Follow article says followers are not told when an article changes. This page sets out the requests, what people do today, and four tools that do not exist yet, including one for letting people who follow a help-centre article know when it changes. Each has its own no-payment interest button, counted separately.

Covers: requests described on Zendesk’s and Freshworks’ own idea sites, the workarounds used today, and an interest test for four proposed tools that do not exist. Doesn’t cover: Zendesk or Freshworks plans, terms or marketplace rules beyond the links shown, or any promise that a tool will be built. Guidance only, not a recommendation of any product. Independent page. Not affiliated with or endorsed by Zendesk or Freshworks. Zendesk and Freshservice are trademarks of their owners. Read the idea pages, the help articles, the Follow article and the third-party guide (3 November 2026) and check the counts yourself.

Zendesk automatically CC the customer: the trigger gap

In Zendesk Support, a trigger can copy a ticket to support staff. Zendesk’s own help article says:

Zendesk’s help article, Can I use triggers to automatically CC end users?, read 3 November 2026:

Triggers can only be used to automatically copy agents on a ticket.

Source: Zendesk help: Can I use triggers to automatically CC end users?. Read 3 November 2026.

The article does not mention followers.

On Zendesk’s community idea site the request is for a trigger action that adds the requester or chosen addresses as CC on a new ticket. On 3 November 2026 the idea showed 487 votes. It was opened on 22 October 2009, and its status was Parked.

Source: Zendesk community ideas: add an end user as CC via trigger or automation. Read 3 November 2026.

Today a technical admin can connect a webhook to Zendesk’s own Tickets API and set email_ccs on the ticket. It is a third-party guide from June 2025; we have not tested it. The guide is over a year old, and it describes using an admin token and a way to avoid loops.

Source: Classmethod, 3 June 2025: add a CC with a webhook and the Tickets API. Read 3 November 2026. Paraphrased, not quoted.

Track changes to Freshservice service items: the Service Catalog change log (secondary)

This is the secondary part of the page, and the less certain of the two. Freshservice’s audit log article says:

Freshservice’s audit log article, view and export audit logs in Freshservice, read 3 November 2026:

The Audit Log records every action and modification across your entire service desk

Source: Freshservice support: view and export audit logs in Freshservice. Read 3 November 2026.

Its examples do not name Service Catalog items, and we have not confirmed whether changes to them are recorded.

On the Freshworks community idea site the request is for an audit log of Service Catalog items. On 3 November 2026 the idea showed 106 votes. It was opened on 1 December 2022, and its status was Under Review.

Source: Freshworks community ideas: audit log for Service Catalog items. Read 3 November 2026.

Zendesk: notify followers when an article is updated

Zendesk’s Follow help article explains how followers are told about a help-centre article. In Zendesk’s own words:

Zendesk’s Follow help article, What does Follow mean in the knowledge base or the community?, read 3 November 2026:

won't receive notifications when someone updates the article or post

add a comment to the article to inform followers about new content

Source: Zendesk help: What does Follow mean in the knowledge base or the community?. Read 3 November 2026.

On Zendesk’s community idea site the request is for an add-on that notifies followers when a help-centre article is updated. On 3 November 2026 the idea showed 186 votes. It was opened on 22 October 2014, and its status was Accepted.

Source: Zendesk community ideas: follow article feature to notify users of article content updates. Read 3 November 2026.

Zendesk’s own workaround is a comment on the article, and the proposed tool would add that comment automatically when an article is edited. It works only where article comments are on, and whether such a comment shows publicly is not established.

The four tools we are testing

The four tools are separate offers at separate prices. Each button is counted on its own, so a press on one says nothing about the others. The page’s view count is one number shared by all four; a button’s rate is its presses divided by the page’s views.

This page is a test of interest, not a shop. There is no payment form and no email field anywhere on it. Each button allows one press per page load. Pressing records one anonymous count for the day, and a short tag if the link you followed carried one. Nothing is stored in your browser.

Not on sale yet. These tools do not exist yet and may never be built. No payment is taken. Pressing only counts your interest.

Secondary offer, and not confirmed. Its examples do not name Service Catalog items, and we have not confirmed whether changes to them are recorded.

How this page is checked

Every quotation above is a line of the page’s one data file, and a test fails the build if a served line is not in that file. A second test fails the build if a banned word appears. The counts are kept per button and per tag, with no cookie and no address. No web source was re-fetched for this build: the sources were read on 3 November 2026 and every quotation is copied exactly from the records. This is a test of interest with a fixed end: the page is taken down at the latest 56 days after it goes live, or sooner if its stop rule is met. If a source changes or we find an error, we correct this page and record it here. Read 3 November 2026.

No corrections yet (the idea pages, the help articles and the third-party guide read 3 November 2026).