claude skills / Customer service pack / faq-du-site / en français

Website FAQ.

The questions your customers really ask, with answers Google and AI can read.

See what it produces
  • WordPress
  • Wix
  • Shopify
  • Webflow
  • Google Search Console
  • Zendesk
8 to 15questions on the FAQ page, the others on their service page
2 to 4sentences per answer, the first one answers on its own
1single version of the truth, aligned with the response library

orders of magnitude, depending on your volume

the problem

What gets in the way today.

  • 01The current FAQ was written to place keywords, not to answer.
  • 02The same questions arrive by email even though the answer exists, hidden at the bottom of a page.
  • 03The FAQ says 5 days, customer service says 10: the customer no longer knows who to believe.

input, output

You give this. You get this.

The questions received and your documents

Atelier Ressac, wetsuit repairs, drop-off in store and postal service.
Questions from August to October: price of a repair (64), lead time (51), sending by post (30), all brands? (22), paid return shipping? (18), warranty (9).
Documents: Prices page as of 1 November 2026, 6-month warranty, postal form.
Website on WordPress, JSON-LD can be added.

$ claude "Build our FAQ with these questions, the markup and the source table."

FAQ ready to publishexample

FAQ: Atelier Ressac | Updated on 12 November 2026

Before you drop off

How long does a repair take?

Allow 5 to 10 working days after we receive it, depending on the season. The exact lead time is shown on your drop-off slip or in the confirmation email.

Do you repair all brands?

Yes, we repair all brands of neoprene wetsuits. For drysuits, we reply case by case after seeing photos.

Sending by post

Do I pay for return shipping?

Yes, return shipping is charged by weight, at the rate shown in the postal form. Drop-off and pick-up in store are free.

After the repair

Is the repair guaranteed?

Yes, our seams and glued repairs are guaranteed for 6 months, except for normal wear or a new tear. Keep your invoice, it serves as proof.

JSON-LD markup

FAQPage block with the 6 questions and answers, word for word, dateModified 2026-11-12.

Question sources

Price of a repair: emails and calls, 64, FAQ and Prices page

Lead time: emails, 51, FAQ

Warranty: customer reviews, 9, FAQ

Questions left out

"What is the best neoprene?": a topic for an article, not for customer service.

Next review: February 2027, store manager

the method

What Claude does, in order.

  1. step 1Collect the real questions

    Tickets, calls, reviews, Search Console, questions tested in an AI assistant, each with its source and frequency.

  2. step 2Group and place

    8 to 15 general questions on the FAQ page, service-specific questions on that service's page.

  3. step 3Write

    The question in the customer's words, a first sentence that answers on its own, one fact per sentence, one useful link.

  4. step 4Mark up and connect

    FAQPage JSON-LD word for word, visible update date, link to the customer service response library.

demo in French / click, try it

Your turn.

An interactive demo of the skill. It is in French, the pack works in any language: ask Claude to answer in English.

64 demandes

the film / 44 seconds, with sound

The pack film.

the pack film

In 8 seconds.

the guardrails

What the skill never does.

  • Only real questions, each with its source.
  • Lead times, prices and terms taken from a company document, and dated when they change.
  • The markup matches the visible text word for word, with no hidden questions.
  • No promise of rich results or of being cited by an AI.

Questions

Will FAQ markup change how I appear in Google?

The skill does not promise it: Google stopped showing FAQ rich results in search in 2026. The markup remains a clean structure that machines can read.

Can I add questions for my SEO?

Not questions made up to place a keyword. The skill starts from questions people really ask, including question-style queries seen in Search Console.

How many questions should go on the page?

8 to 15 on the general FAQ page. Service-specific questions go on that service's page, 3 to 6 per page, rather than in a catch-all FAQ.

How do I stop the FAQ from contradicting customer service?

Each published question links to its entry in the Response Library. If the two differ, you fix the source, then both texts.

the pack

In the pack: Customer service pack.