AI Writing, Templates (MS Office), User Guides
Using Google Gemini to Refine the FAQ Writing Process
Jul
Using Google Gemini to Refine the FAQ Writing Process
FAQ pages are not trendy but, if you run a technical-orientated website, or a site that has software products, you’ll notice that FAQ pages get a lot of traffic. In many cases, if your site focuses on a single product it might be the one of the most visited pages. With that in mind, knowing how to write, review, and update FAQs makes a ton of sense. This is where prospective customers hang out. They’re looking for specific answers to specific questions.
According to ZenDesk, “While an FAQ is traditionally thought of as a basic list of questions and answers, it can also be part of a company’s larger help center—a comprehensive knowledge base that empowers customers to find solutions independently.”
Why?
Because when people have a problem, they want a fast, straightforward answer. They don’t want to file a support ticket or wait for a callback. They want a solution, now.
This puts a lot of pressure on you to get your FAQs right. They need to be accurate, easy to find, and genuinely helpful. This used to mean days spent wading through support tickets and arguing with engineers over terminology.
Today, you have a new tool in your kit: AI.
Let’s get one thing straight. An AI tool like Google Gemini will never replace a sharp technical writer or an experienced customer support agent. It lacks the human touch, the ability to read between the lines of a frustrated customer’s email. But to think you can ignore it is a mistake.
Think of Gemini as a deluxe co-writer. It lets you focus on the human things, such as planning and empathy, while it handles the heavy lifting, such as research or summarizing.
Definition: What is an FAQ, Really?
In our world, an FAQ (Frequently Asked Questions) document isn’t just a list of questions.
- For Customer Support: It’s a first line of defense. A tool for ticket deflection that empowers users to solve their own problems, freeing up human agents for complex issues.
- For Software Development & Testing: It’s a living document. It clarifies functionality, explains edge cases, and sets expectations about how a feature is supposed to work before it ever ships.
- For Users: A quick and accessible source of truth that builds confidence in the product.
Who Reads and Writes FAQs?
The Readers: Your readers are often frustrated, confused, or just curious. They scan for keywords, look for clear headings, and want an answer in 30 seconds or less. They have zero patience for long, meandering paragraphs.
The Writers: This is a collaborative role.
- Technical Writers shape the structure and voice.
- Customer Support provides the raw, real-world questions.
- Software Engineers verify the technical accuracy.
- Marketing makes sure the tone aligns with the brand.
The 7-Step Process for Writing FAQs with Gemini
Here is the framework for integrating Gemini into your workflow, from a blank page to a published resource. This isn’t a shortcut to avoid work; it’s a roadmap to do better more effectively. See if this helps.
1. Prepare
Before you write a single word, scope out a plan. The most-read FAQs are built on a solid foundation of strategy, not guesswork. Rushing this stage is like showing up for a triathlon without knowing the course.
- Define Your Goal and Audience: First, decide what this FAQ is for. Is it to reduce support tickets for existing users? Or to answer pre-sales questions for potential customers? The audience dictates the tone and depth.
- Identify Core Topics: Break your product or service down into its main functional areas. For a software company, this might be ‘Account & Billing,’ ‘Project Setup,’ and ‘Reporting.’ This creates your initial structure.
- Gather Your Source Material: Collect all existing documentation. This includes marketing pages, user manuals, white papers, and technical specifications. This is the raw knowledge you’ll be working with.
How tools like Google Gemini can help:
Feed it your list of core topics and a link to your product’s homepage. Ask it:
“Based on these product categories, generate a list of potential user questions for an FAQ page. Structure them as a new user would ask them.”
This gives you an instant, intelligent outline to refine.
2. Research
This is where the FAQs development process starts. You must dig into what people are really asking, not what you think they’re asking. Your goal is to become an expert on your users’ confusion.
- Mine Your Support Data: Systematically review support tickets, live chat transcripts, and call logs. Look for patterns, repetition, and the exact phrasing users employ.
- Scour Public Channels: Go where your users talk. Read app store reviews, search Reddit and Twitter for your product’s name, and check community forums. These are unfiltered sources of user frustration and curiosity.
- Interview Internal Teams: Talk to your colleagues. The sales team knows what questions block a sale. The social media manager knows what questions pop up on Facebook. The support team lives and breathes user problems.
How AI can help:
Instead of you manually reading 500 support tickets, you can (with proper privacy controls) feed it anonymized data.
Prompt it: “Analyze these support transcripts and identify the top 5 most frequent problem areas. List the three most common questions for each area.” It synthesizes vast amounts of data into a clear, prioritized list.
3. Write
With your questions and research in hand, it’s time to draft the answers. The guiding principles are clarity, simplicity, and directness. Get to the point, fast.
- Frame the Question Like a User: Always phrase the question from the user’s point of view. Use “How do I…” or “Why can’t I…” instead of corporate-speak like “The functionality of Feature X.”
- Start with the Answer: Give the direct solution in the first sentence. Then, if necessary, add context or explain the ‘why’ in the following sentences.
- Draft in Simple Formats: Use numbered lists for steps, bullet points for options, and bold text for emphasis. Break down complex solutions into small, manageable chunks.
How AI can help:
Take one specific question and your research notes.
Prompt Google Gemini:
“Using these key points, answer the question: ‘How do I add a new team member?’ Write the answer as a simple, numbered list. The tone should be helpful and direct.”
It will produce a clean first draft in seconds, freeing you up to focus on the next question.
4. Edit
A raw AI draft is never customer-ready. It can be generic, slightly off-tone, or just plain wrong. This is where your professional judgment transforms a good draft into a great resource.
- Fact-Check Everything: This is the most important step. Verify every link, every step in a process, and every policy detail with the appropriate Subject Matter Expert (SME). The AI can be confidently wrong. Your credibility is on the line.
- Inject Your Brand Voice: Rewrite the AI’s generic text to sound like your company. Are you witty and informal? Or straightforward and professional? This human layer builds trust.
- Simplify, Then Simplify Again: Your users are in a hurry. Remove any jargon, unnecessary words, or complex sentences.
How AI can help:
Use it for refinement. Highlight a clunky paragraph and prompt it:
“Rewrite this to be simpler and more direct.” or “Can you explain this concept using an analogy?”
It can provide alternative phrasings you might not have considered.
5. Collaborate
An FAQ page is a team sport. It needs buy-in from support, engineering, and marketing to be truly effective. Think of your team like a Formula 1 pit crew—everyone has a critical role, and perfect coordination is vital for success.
- Establish a Clear Review Workflow: Use a shared document (like Google Docs) where stakeholders can easily leave comments and suggestions.
- Assign Specific Reviewers: Don’t just send a mass email. Tag the lead engineer for the technical review of a feature. Tag the support lead to confirm the answer solves the real-world problem. Tag marketing to check for brand voice.
- Set Firm Deadlines: A review cycle without a deadline is a project that never finishes. Give people a clear timeline for their feedback.
How Gemini Doesn’t Help:
This step is for you: the ‘human in the loop’. Gemini can’t sit in a meeting and mediate a disagreement between a developer and a support agent. This requires your skills in diplomacy and project management.
6. Update
An FAQ page is a garden, not a monument. It requires constant care. Products evolve, new issues arise, and user questions change. Embrace the Japanese concept of Kaizen, or continuous improvement.
- Schedule Regular Audits: Set a recurring calendar event—monthly or quarterly—to review the entire FAQ page for accuracy.
- Create a Feedback Loop: Make it easy for your customer-facing teams to flag an FAQ that is outdated, unclear, or missing. A dedicated Slack channel or simple form works well.
- Monitor Analytics: Look at the data. Which FAQ articles are viewed the most? Which have a high bounce rate? This tells you what’s helpful and what needs improvement.
Use AI, such as Claude, to stay ahead of the curve. Every quarter, feed it your latest batch of support tickets and ask:
“Compared to our last dataset, what new user problems are emerging?”
It can help you spot trends before they become major issues.
7. Publish
Once your content is polished, reviewed, and ready, you need to get it in front of the right people at the right time.
- Choose the Right Home: Decide where the FAQ will live. Is it a single page on your website, or will it be part of a larger, more robust knowledge base platform like Intercom or Zendesk?
- Optimize for Findability: Make the page easy to use. A prominent search bar is essential. Clear, logical categories are a must.
- Promote It Actively: Don’t just publish and pray. Link to relevant FAQs from within your app, in support email signatures, and on related marketing pages. Guide users to the answers.
Give Gemini a finished Q&A and prompt it:
“Write an SEO-friendly title tag under 60 characters and a meta description under 155 characters for this FAQ.”
This helps your answers get discovered on search engines.
Mistakes to Avoid
- Blind Trust: Never copy and paste directly from Gemini without a rigorous fact-check. AI models can “hallucinate” and invent answers with absolute confidence. You are the expert; the AI is the intern.
- Losing Your Voice: Don’t let the AI’s generic tone strip the humanity from your content. Edit heavily to inject your brand’s personality and a sense of empathy for the user.
- Answering a Question No One Is Asking: Your FAQ page should be driven by data, not assumptions. If you aren’t using real customer feedback (emails, tickets, reviews), you’re just guessing.
Glossary of Terms
- Ticket Deflection: The process of providing customers with self-service options (like an FAQ) to solve their own issues, reducing the number of new support tickets created.
- Subject Matter Expert (SME): The person on your team with the deepest and most authoritative knowledge on a specific topic, often an engineer or a senior support agent.
- Knowledge Base: The central library for all help-related content, including FAQs, how-to guides, and in-depth articles.
- Search Intent: The underlying goal or reason behind a user’s search query. Understanding this helps you write answers that truly solve the problem.
Reference: Great FAQ Examples
- Notion: Clean, searchable, and beautifully integrated with the rest of their help content.
- Dropbox: A classic example of a massive knowledge base broken down into user-friendly FAQ sections.
- Nintendo Support: Excellent use of visuals and simple language to solve problems for a very broad audience.
Next Steps
In this primer, we looked at how to develop FAQs that are concise, contextual, and in sync with changes in the product development. More important than ever in an Agile development environment.
And, we also looked at when/how/why you should remove stale and redundant FAQs. Removing outdated content will ensure your customers find the info they need super fast.
In the following articles, I’ll show you how to use AI tools, such as ChatGPT, Google Gemini or Claude, and tools such as Retrieval Augmented Generated aka RAG (not as spooky as it sounds) to laser-focus your FAQs and identify gaps in your document set. If you’re not using AI, these non-technical articles will be a great starting point. No technical skills will be required. Btw – sign up for the newsletter, that way you’ll know when they come online.
Template Downloads:
Connect with us
