Spaces

Weekly chat review checklist for a publishing business

This checklist gives a publisher a short weekly routine for reading the chats an AI agent handled, from delivery complaints to software support, so mistakes are caught early and answers keep improving.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

An agent that is never reviewed slowly drifts. A new issue date changes, a price goes up, a software version is retired, and the agent keeps quoting the old fact. Publishing moves on a calendar, so facts go stale quickly. A short weekly look keeps the answers true.

Set aside twenty minutes at a regular time, such as Monday after the post is out. Read a handful of chats from each audience, tick the points below and write down one fix. Small weekly corrections beat a big clean-up after readers have complained.

Tick each one as you go. 0 of 10 done.

[ ] Read five chats from subscribers and note any answer that was wrong.
[ ] Read any chat from an author or contributor and check the tone.
[ ] Count the chats that were handed to a person and ask why.
[ ] Check that each hand-over note had enough detail to act on.
[ ] Look for software support chats missing a version or an error message.
[ ] Find questions asked more than twice and add a ready answer.
[ ] Check any chat that mentioned a correction, a rights request or money.
[ ] Review chats where the customer sounded annoyed.
[ ] Update dates, issue numbers, prices and version details that changed.
[ ] Write one change for next week and tell the team.

What to look for when you read

Do not try to read everything. Pick a few chats from each audience and read them as the customer would. Was the answer clear? Did it solve the problem or just sound polite? Would you be happy to get that reply from a magazine you pay for?

Pay special attention to the first line and the last line. The first shows whether the question was understood. The last shows whether the person knew what happens next.

Patterns worth acting on

When you see these, change something that week.

  • The same delivery area appearing in several missed-copy chats.
  • Authors asking where to find the guidelines, which means a link is missing.
  • Users hitting the same installation error after an update.
  • Advertisers asking for deadlines the agent could not state.

FAQ

How many chats should I read each week?

For a small publisher, ten to fifteen across all audiences is plenty. Read more in a week after a big issue, a price change or a software release.

Who should do the weekly review?

Ideally the person who knows your readers and products best, such as the audience manager, an editor or the support lead. Rotate the job if one person gets tired of it.

What do I do when I find a wrong answer?

Correct the fact in the notes your agent uses, then, if the customer was misled, write to them yourself. Do not just fix it quietly and hope they never noticed.

More free tools for publishers and software publishers

Read the guide: Answer reader, author and customer messages in publishing.