The same question from the same client
The site launched with a training call. The client's marketing assistant took notes. Three weeks later she emails: how do I add a new case study? The developer replies with steps. A month later her colleague asks the same thing. Two months later she asks how to change the homepage banner, which was covered in the training call, but the notes are lost.
Across all clients, the developers answer dozens of these small questions. Each takes a few minutes, but they interrupt real work, and they count against maintenance hours or are not counted at all.
Why clients keep asking
- Training happens once, at launch, when clients are overwhelmed.
- Every custom site uses different custom fields, blocks and templates, so generic CMS guides do not match.
- Staff at the client change, and new people were never trained.
- The client edits rarely, so they forget between updates.
- Emailing the developer is easier than searching for notes.
The client is not being lazy. They simply have nowhere better to look than your inbox.
What repeated questions cost
Developer time is spent on the same answers repeatedly. Interruptions break concentration on project work. If the questions count against maintenance hours, clients feel their plan is being used up on basics. If they do not, the studio gives the time away. Clients who cannot easily update their sites stop updating them, and then wonder why the site feels stale.
The help library we build
- For each site, the common editing tasks are listed during the build: add a post, add a team member, change the banner, update a service, edit the footer.
- The developer records a short screen video for each task on that specific site, and writes brief steps. Tasks that are the same across sites reuse a shared template with site-specific screenshots.
- The library sits inside the client's WordPress dashboard as a help panel, or on a private page, so help is where they are working.
- A simple assistant answers questions by searching that site's library, using a language model such as OpenAI or Anthropic Claude restricted to your content, and links to the right video.
- If the library has no answer, the assistant offers to raise a support ticket, which goes to your desk with the question attached.
- Questions that come up often without an answer are listed for the studio, so the library grows where clients need it.
| Client question | Where the answer comes from |
|---|---|
| How do I add a blog post? | Short video and steps for their site |
| How do I change the homepage banner? | Video showing their custom block |
| Can I add a new page template? | No library answer, raised as a support ticket |
| Why is my image blurry? | Guide on image sizes for their theme |
The assistant only answers from your library. It does not guess, and it hands anything uncertain to a person.
After launch with a help library
At launch, the client gets a short training call and is shown the help panel. When a new colleague needs to add a case study, she opens the panel, asks the question, and watches a video made on her own site. The developer's inbox gets the questions that actually need a developer.
Are you answering the same questions?
- Clients regularly email how-to questions after launch.
- Training is a single call at launch.
- New staff at clients were never trained on the site.
- Generic CMS guides do not match your custom builds.
- How-to questions use up maintenance hours or go uncounted.