Customer story · Support

Copperleaf keeps its help center current after every release and gets 38% fewer repeat tickets.

Healthcare380 peopleAustin, Texas

fewer repeat tickets
38%
help articles kept current
400
from release to updated help center
3 hrs

Copperleaf makes patient scheduling software for clinics and outpatient practices. More than 3,000 clinics use it to book appointments, send reminders and manage waiting lists. Its support team of 40 answers questions from front-desk staff, practice managers and IT administrators.

The challenge

Front-desk staff at a busy clinic don’t have time to wait for an answer. When they get stuck, they search the help center first, and if the article they find is wrong, they write in. Often they write in again when the first reply points them back to the same outdated article.

Copperleaf ships updates every two weeks, and its help center has about 400 articles. Keeping the two in step was nobody’s full-time job. Support agents updated articles when they had time, usually after the tickets had already arrived.

“We’d see the same question twenty times in the week after a release,” says Imani Clarke, Head of Support. “Each time we knew the article was wrong, and each time there was no time to fix it because we were answering the tickets.”

Repeat tickets, where the same customer writes in again about the same problem, were the clearest sign. They made up almost a third of the team’s volume.

How they use Pilot

Copperleaf connected Zendesk, its Jira release tickets and the help center to Library. Pilot can read every help article, every resolved ticket and every release ticket, and each agent sees only what they already have access to in those tools.

The core of the setup is an Autopilot agent that runs on release day. It reads the release tickets, compares them with every help article and produces a short report in Slack:

  • Which articles mention a feature that changed, with the outdated sentences highlighted.
  • Suggested rewrites for each, drafted in Write in Copperleaf’s help center style.
  • New questions likely to come up, based on similar past releases.

A support lead reviews the report, accepts or edits each suggestion as a tracked change, and publishes the updates. Most releases need between five and fifteen article changes.

A second agent runs every Friday. It reads the week’s tickets and looks for questions that the help center doesn’t answer well, then drafts a new article or a section for an existing one. Support agents can also ask Library during a ticket how a similar issue was solved before, and get the answer with a link to the resolved ticket.

Because Copperleaf works with clinics, it was careful about patient information. Pilot is set to skip ticket attachments, and it never trains on customer data, which made the review with Copperleaf’s compliance team straightforward.

“The release report is the first thing I read on release day. It’s a to-do list I don’t have to write.”

The results

The help center is now updated within about three hours of each release, down from one to two weeks. All 400 articles are reviewed against every release, which no one on the team had time to do before.

Repeat tickets have fallen by 38%. Customers find the right answer the first time, and when they do write in, agents can link to an article that is correct.

The Friday agent has added 32 new articles in six months, each based on questions customers were actually asking. Several now rank among the most viewed in the help center.

The team’s morale has improved as well. Agents spend less time answering the same question and more time on the complex cases that need a person, such as a clinic migrating from another system.

“We used to measure how fast we closed tickets,” Clarke says. “Now we measure how many we never get. That’s the number that matters to a clinic with a queue at the front desk.”

“Our help articles used to fall behind the product within a week of every release. Now Pilot tells us what's out of date and drafts the fix, so customers find the right answer before they write to us.”
Imani ClarkeHead of Support, Copperleaf
Imani Clarke, Head of Support at Copperleaf
All customer stories

Your next draft is already started

Join 14,000 teams that research, write and ship with Pilot.