Get the pack · ₹699

← Faqtory

4 min read

How to build a client knowledge base from your WhatsApp chats

A five-step way to turn the answers you have already typed into one approved table your whole team can use.

Most service businesses already have a knowledge base. It is scattered across WhatsApp threads, old proposals and the memory of one senior person. The job is not to write something new. It is to collect what you have already said, settle the contradictions and put it where the team can reach it.

1. Export three chats, not one

Pick an easy client, a demanding client and a recent one. WhatsApp lets you export a chat without media from the chat's menu. Before you paste anything into an AI tool, delete phone numbers, bank details and personal matters. You need the questions, not the client's identity.

2. Extract the questions and the real answers

Ask ChatGPT, Claude or Gemini to list every question the client asked, including the ones hidden inside complaints. 'Still waiting for the report' is the question 'when will I get the report?'. Ask for the answer you actually gave, not an improved one. At this stage you want the truth, including the times you dodged.

3. Put the contradictions on top

Merge the three lists and group questions that mean the same thing. You will find that you have given two or three different answers to the same question. That is normal. It is also the single most useful thing this exercise will show you, because every contradiction is a policy nobody has decided.

4. Decide, then write

Sit down for one hour and decide each one. A good decision is more than picking the best old answer. For revisions, for example, it defines how many rounds, what a round is, and what counts as new work. Then write each answer in the client's words, with the direct answer in the first sentence, short enough to read on a phone.

5. Give every answer an owner and a date

Use a simple table with these columns:

  • An ID that never changes
  • The question as a client asks it
  • The approved answer
  • When to hand over to a person
  • The owner, by role
  • The date it was last reviewed

An answer without an owner goes stale quietly. Prices move, tools change, people leave. If you cannot say who would know first that an answer has changed, it is not really approved.

What to expect

The first pass usually produces thirty to forty questions, and most are about process, not expertise: what happens next, who to send things to, when something is due. That is good news. Process questions are the easiest to answer once and reuse in quick replies, a welcome pack and your onboarding messages.

The Faqtory vault has ten prompts written for exactly these five steps, and its workbook has the table ready with thirty example entries to edit.

Keep reading