Talk about your next project
Zendesk case study

The lesson

Lead with the operational change and the customer’s own support metrics before telling the implementation story.

The move

The page opens with the title “DuPage County modernizes employee support and CX with Zendesk AI,” a short summary, a customer photo and a “Watch the video” prompt. It then places two named quotes above a facts-and-results block: county population, employees, agencies on Zendesk, support agents, plus resolution time, email volume, first-reply time and CSAT. The body moves through the county context, “A CIO on a mission,” the tool selection in “A powerful platform at one-third the price,” then sections on AI, reporting and intranet modernization.

Why it works

  • Our readThe opening summary says what changed, who changed it and what Zendesk product is involved before the reader reaches the story.
  • Our readNamed quotes from the CIO and Web Services Manager make the public-sector value and time savings feel attributable, not vendor claimed.
  • Our readThe metrics block lets a reader scan for scale and outcomes before deciding whether to read the implementation detail.

What not to copy

Don't copy DuPage County's government setting, AI roadmap or taxpayer-value language. Keep the structure of title, short summary, named quotes, customer facts, outcome metrics and a chronological story of the change.

More from Zendesk

More case studies

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.