In short: Your AI agents read your knowledge base in small passages, not whole pages. Write every entry so it makes sense on its own: one topic, the subject named, exact numbers, and the answer in the first sentence. Write the way customers ask, and keep one version of every fact.
Why writing matters
When a customer asks a question, Voizee searches your knowledge base and gives the AI agent the few passages that match best. The AI agent does not see the rest of the page. So a passage that says “It costs $99, see above for conditions” leaves it guessing what “it” is and what the conditions are.
Most wrong answers come from content, not from the AI: the fact is missing, unclear, buried in another topic, or contradicted by an older source.
The rules
| Rule | Instead of | Write |
|---|---|---|
| Answer first | “Many customers ask about weekends. We understand how important…” | “Yes, we are open on Saturday from 9 AM to 2 PM. We are closed on Sunday.” |
| Name the subject | “It includes two visits a year.” | “The Comfort Plan includes two maintenance visits a year.” |
| One topic per entry | One FAQ about refunds, rescheduling and late fees | Three FAQs, one per topic |
| Exact facts | “Shortly”, “a small fee”, “nearby areas” | “Within 2 business days”, “$49”, “Within 25 miles of Austin” |
| Self-contained | “See the section above.” | Repeat the condition in the answer |
| Customers’ words | “Ingress service window” | “What time can you arrive?” |
| State limits and no’s | Say nothing about what you don’t do | “We don’t repair commercial units. We work on homes only.” |
| Who it’s for | “The discount is 10%.” | “New customers get 10% off their first service.” |
| Define terms | “Includes PDR.” | “Includes paintless dent repair (PDR).” |
| One version of each fact | Old price list on a file, new one on the website | Delete or replace the old source |
Structure longer content
- Use headings. In documents, start a new heading for every topic. Passages follow your headings, and each passage carries its heading with it.
- Use numbered steps for procedures, and say what the customer sees at the end.
- Put an intro sentence before a table, e.g. “Service call fees by area:”.
- Describe images in words. Pictures are not read.
- Keep long lists in tables. A table row with clear column names is easier to find than a long paragraph — see Add Price Lists and Catalogs as Tables.
Writing for phone calls
The AI Voice Assistant works as an AI receptionist for your phone line and speaks its answers from your knowledge base. What works on screen can sound awkward on a call.
- Keep answers short. Two or three sentences per answer. Put the key fact first.
- No links or “click here”. Write “We can text you our booking link” or “Our website has the full list” instead of a web address.
- Spell out what is hard to hear. “Monday to Friday” rather than “M–F”; “nine AM” reads better than “9a”.
- Avoid long lists. Give the top three options and offer to text the rest.
- Give a clear next step — “I can book you a call back” — so the caller knows what happens.
Check your writing
- Open the Test tab.
- Ask the question three different ways.
- Look at the top passage. Would it answer the question if it were the only thing you read? If not, rewrite it.
See Test What Your AI Agents Will Answer.
Templates you can copy
A good FAQ:
Question: Do you charge for estimates? Answer: No. Estimates are free for homes in our service area: Austin, Round Rock and Pflugerville. Outside this area, a $50 trip fee applies, and we take it off the price if you book the job.
A good document section:
Heading: Cancellations Text: You can cancel or reschedule an appointment free of charge up to 24 hours before the start time. Cancellations within 24 hours cost $40. To cancel, call or text us at the number on your confirmation.
Tips & best practices
- Write for the customer’s question, not your org chart. Customers don’t know your department names.
- Prefer FAQs for top questions. They are the most precise source.
- Delete before you add. When a policy changes, update or delete the old text first.
- Never put private customer data in a knowledge base. AI agents can repeat it.
FAQ
Does the AI understand synonyms? Yes. The search works by meaning, so “weekend hours” finds “open on Saturday”. Use customers’ words anyway — it makes the match stronger.
Should I write in a formal tone? Write the way you want your AI agents to sound. They use your facts and keep the tone of the conversation.
How long should an FAQ answer be? As short as possible while still complete — usually one to four sentences.
Related articles
- Add FAQs and Import Them from a CSV File
- Write Documents in the Knowledge Base
- Test What Your AI Agents Will Answer
- Keep Your Knowledge Base Current
Still feeling stuck? Please send us your questions using this form.