Typical FAQ sections feature speculated questions and answers. These questions provide filler content to answer the types of questions the marketing team hopes the customers have. These questions are usually ignored by the customers as they search for the contact form.
An effective FAQ section should be literally transcribed. This means the questions received in the inbox should be transcribed, word for word, and the difficult answers should be provided. People ultimately check the FAQ section to find the difficult answers.
This will include at least three difficult questions your sales page would choose to ignore. These questions include the edge cases on pricing, what the product or service explicitly does not do, and what happens in the case the customer wishes to exit. Answers will be provided in such a way that the answer to the question will be the first sentence.
A machine cannot generate answers without first producing the questions. Because of this, the FAQ written by a model will accurately answer every question, unlike a human-written FAQ. Customers can have questions that marketing copy doesn’t address, and the answer to those questions is usually a no. Generated FAQs will never say no.
The author reads and sorts real customer interactions (tickets, chat transcripts, pre-sale emails) by what the customer was worried about rather than by topic. Fifteen differently worded concerns usually collapse into four questions. Getting four questions gets you four well-written answers; getting fifteen questions gets you fifteen poorly written answers.
The set comes with an instruction document and prepared questions in a list that you can paste directly into a CMS field or an FAQ schema block. Questions are numbered and categorized into groups with a note indicating which questions can be posted on the product page versus the FAQ page because there are always a few questions that should be posted in the FAQ page.
One rate, whatever the format: $10 per 100 words. You are paying for the writer’s time and judgement, so the price scales with the words rather than with a package tier.
| Typical FAQ | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Five-question block | 350 | $35 | $0.35 | $35.35 |
| Standard FAQ page, 12 questions | 900 | $90 | $0.90 | $90.90 |
| Help-center FAQ library, 30 questions | 2,400 | $240 | $2.40 | $242.40 |
The writer receives 100% of the writing price. Our 1% fee is added on top of it, and 0.5% is donated to tree planting. Full pricing breakdown.
Every draft goes through an editor, then through several AI detectors and a plagiarism check. Anything that does not come back clean is revised or reassigned. You get the reports with the delivery email.
What the piece is for, who reads it, roughly how long it should be, and anything it must include or avoid. Links to your existing material help. If you are unsure, send what you have and the writer will come back with questions.
Yes. The absence of a queue puts the writer at a disadvantage as they work from your product, competitor support pages, and questions that come up during your sales calls. These drafts are a first step, so don’t be surprised to find they have more questions than clear answers.
Generally speaking, both types of question belong where people can look for them, with a clear intent separation. You may place buying questions next to the purchase, with account and billing questions elsewhere. The delivered set identifies the responses and intended locations. You may disregard the placement entirely.
Completely. Copyright transfers to you on delivery, with no attribution requirement and no licence back to us. Nothing written for you is resold, repurposed or republished.
Reviews from completed, paid orders in this category.
Thirty articles with the same structure and with the same voice are difficult to develop for a knowledge base. Screenshot placeholders were described with prose instead of with tags. Unfortunately, our designer had to try to find them with some difficulty. This is a small thing, but I plan to put it in the brief next time.
Twenty-two articles on our top ticket drivers. The writer requested redacted transcripts, and then described the problems in the way customers used the language – thermostat will not hold temperature, instead of thermostat calibration. Help center search finally started working.
Eleven articles covering our top ticket drivers. They requested the original ticket text first, not the internal descriptions, and the difference is significant. The articles use the terms customers input into the search box. There’s been a downward shift of about a fifth in the volume of contacts on those topics.
We do not ask you to take the no-AI promise on trust. Each draft is run through these platforms and the reports are attached to your delivery email.
Originality.aiAI detection + plagiarism
GPTZeroAI detection
TurnitinAI detection + similarity
CopyleaksAI detection + plagiarism
Winston AIAI detection
ZeroGPTAI detection
SaplingAI detection
Content at ScaleAI detection
Send the brief, get a human draft back within 3 days. No account, no subscription, no AI.
$10 per 100 words · all of it to the writer · 0.5% to trees