Which client questions belong in your answer library?

An answer library should contain questions that recur, have a verified answer and help clients make a practical decision. Start with service scope, duration, arrival details, booking rules and approved preparation instructions; keep individual exceptions outside the standard answer. The goal is not to store every conversation. It is to give yourself a small, dependable reference that answers the same question consistently, whether you reply personally or later configure a separately verified assistant.

Choose questions by the uncertainty they remove

Look through a representative selection of recent enquiries and write down the question behind each message. “Does removal come with this?” and “Should I add removal?” may express one uncertainty about what a service includes. Combine those variants instead of saving two competing answers. By contrast, a price question and a request for an earlier arrival time need different facts, even when they appear in the same message.

For the first selection, check four things:

• more than one client has needed this information;
• the answer affects a real choice or arrival;
• an approved source exists for the facts;
• the wording can be reused without knowing private details.

A useful entry might explain whether a listed service includes a particular step. Its source should be your current service description, not a promise made during an unusual previous visit. That distinction keeps your library grounded in the offer you actually intend to provide.

Cover the journey, not just the price

Price questions are visible, but a library built only around prices leaves other practical uncertainty untouched. Follow the client's journey from considering a service to arriving for it. Ask what information they need at each point, and include only categories that genuinely apply to your business.

A compact starting set can cover:

• what a named service includes and excludes;
• the published duration and what it describes;
• the address, entrance and useful arrival instructions;
• where to find the current booking or cancellation rules;
• preparation instructions you have explicitly approved.

Separate directions from availability: knowing where the studio is does not establish whether a particular time can be booked. Likewise, an approved preparation note is not permission to give individual health advice. If a question requires assessment, the entry should identify who must answer it. A short reference that marks its limits is more useful than a large catalogue that quietly turns exceptions into ordinary policy.

Give each answer a source and a boundary

Use one record for one question. Give it a plain-language title, a concise answer, a source and a condition that would make the answer unsuitable. Add the date of your last check so you can distinguish an actively reviewed entry from a forgotten draft. These are editorial fields in whatever document you use, not a claim about a particular application's features.

For example, an entry about the entrance could name the street-facing door and explain that the courtyard gate is not the client entrance. Its source might be your own checked arrival instructions. If access changes during building work, that entry needs review before reuse.

Keep internal explanations apart from the client-facing wording. A note about why you changed an answer can help you maintain it, but the customer generally needs the current instruction, not the history of every previous version. This separation also makes a short answer easier to find during a busy appointment day.

Keep personal decisions out of standard replies

Some questions recur because clients regularly need exceptions. “Can you fit me in after closing?” may arrive often, yet frequency does not turn it into a standing agreement. A library can record the normal rule and the next step for an exception without deciding that exception in advance.

Mark cases that require individual review:

• a request for work outside the published service scope;
• a proposed change to an existing agreement;
• a complaint about a particular completed visit;
• a request involving personal health circumstances.

Do not paste the original conversation into the general entry. Remove names, contact details and identifying circumstances, then retain only the reusable question. The answer should explain the boundary and how you will consider the case. This lets you recognise a familiar type of request without exposing another client's story or turning a one-time accommodation into a promise for everyone.

Test retrieval before expanding the collection

A library is useful when you can find the right answer, not when it contains the most entries. Try searching with the words a client actually uses rather than the terminology in your menu. If “take off the old colour” should lead to the removal entry, add that phrase as a search cue, not as a second independent answer.

Read the retrieved reply without its internal notes. Does it resolve the question? Does it rely on a condition the customer cannot see? Revise the entry if its meaning changes when taken out of the document.

When a source changes, update the authoritative answer and remove obsolete copies from saved messages. Compare service-related replies with your current KLIOSO service information and booking page. This is a manual consistency check; it does not imply automatic synchronisation with an assistant. Expand the collection only when a new question needs a genuinely different answer, rather than another wording of an existing one.

The key point

Build your answer library around recurring uncertainty, verified sources and clear limits. Cover the practical journey, give each entry one purpose and separate ordinary information from decisions about a particular client. Search tests reveal whether the collection works in daily use, while source changes tell you when a reply needs attention. KLIOSO service information and the public booking page can support that consistency check, but a document of answers is not itself an automated receptionist. Keep the collection small enough to review and specific enough to trust.