All articles

Content that helps

From repeated support question to useful website page

A walk through the Cura workflow, from the conversations themselves to an insight, a draft and a human review before anything is published.

The Cura team · · 3 min read

Every support team has a question it is tired of answering. The usual response is to answer it faster. The better one is to ask why it keeps arriving, and fix that.

This is how the work goes in Cura, step by step. The bakery in the example is invented. The steps are how the product works.

1. The conversations

A customer asks whether they can change a delivery date. Cura answers from the delivery information the business has published. If the answer is not there, or the customer still needs help, Cura collects a support request with the conversation attached, so the team can see what was asked and what the customer has already been told.

One such conversation is routine. The useful part comes when there are dozens.

2. The insight

Cura Insights looks at the last 30 days of answered conversations and groups them into two lists.

Not answered well covers topics where the answer was missing or unsure, was rated unhelpful, left the visitor needing help or led to a support request.

Asked for but not offered covers products, services or options that visitors wanted and the business does not appear to provide.

Each group shows how many conversations it contains, one practical suggestion and up to three real example questions. Each example opens the conversation it came from.

In our example, a group appears called “Changing a delivery date”, with a suggestion to say clearly how late a change can be made.

3. Reading the examples

Do not skip this step. The count tells you the topic matters. The examples tell you why.

Reading them, the bakery’s team finds that the information exists, in the fourth paragraph of the terms page. Nobody looks there. The problem is not a missing answer. It is an answer in the wrong place.

That distinction decides the fix: missing information needs writing, hidden information needs moving, and unclear information needs rewording.

4. The draft

From the insight, the team can choose what to do next:

  • Draft content for the website. Turn the repeated question into a brief or a first draft of an FAQ or guide.
  • Add knowledge. Write a knowledge note so the assistant answers the question properly from now on. It opens as an unpublished draft.
  • Add a rule. Set a next step for the topic, such as offering a “change my order” request.
  • Fix it in training. Correct the assistant’s answer in plain English and test the change.

The bakery does two of these: a short FAQ for the delivery page and a knowledge note for the assistant.

5. The human review

A draft is a starting point. Someone who knows the business checks every fact, in this case the cut-off for changes and what happens at weekends. Then the page is published through the website’s usual process. Cura does not publish to your website for you.

6. Afterwards

A month later the team looks at Insights again. If the group has shrunk or gone, the fix worked. If it has not, the examples will show what is still unclear.

One useful action

Find the question your team answers most often. Before writing anything, read ten real examples of it and decide which is true: the answer is missing, hidden or unclear. The fix follows from that.

See Cura for customer support

Start with the questions your customers already ask.

See what Cura can help you answer and improve.