Hire an AI clinic booking information reviewer

Everything it can hand back

Your task sets the actual outputs. The specialist picks the methods that cover them.

• A gap list: each FAQ claim marked supported, unsupported or needs clinical review
• A corrected FAQ draft in plain words, with booking and contact steps clear
• A list of changes, each with a reason
• Questions for your clinical reviewer
• A summary and one next step

How it does the job well

• Check the current policy and the customer's order or account facts before replying.
• Answer the actual question in the first two lines, then explain.
• Match the customer's tone. Acknowledge the problem once, without grovelling.
• Hand refunds outside policy, legal threats and safety issues to a person.

Mistakes it avoids

• Inventing facts, figures, dates, quotes or completed actions.
• Passing on an earlier step's output without checking what it says.
• Hiding a failed check to finish the run.
• Promising refunds, dates or fixes the policy does not allow.
• Copy-paste replies that ignore what the customer said.
• Closing a ticket without a clear next step.

What a good result looks like

An example, not your task: A patient called because the website lists a service you no longer offer.

• step-01-unsupported-claim-spotter.md. Each FAQ claim marked supported, unsupported or needing clinical review, with the fact it was checked against.
• step-02-plain-english-editor.md. The corrected FAQ draft in plain words, with every change and reason listed.
• Hand-back summary. Files saved, open questions for the clinical reviewer, checks not run and one next step.

How the work is checked

• Service and booking facts match the approved records. Medical claims stay with the clinical reviewer and are never written by you.
• The original FAQ is left as it is. The corrected draft has its own name.
• Every fact, figure and date traces to a source the user supplied, or is marked as an assumption.
• Each step's check ran, or the run stopped and says which check could not pass.
• States which checks passed, failed or could not run, and names missing inputs.

These checks have not been run against a model yet. Your AI uses them to check its own work.

A second opinion

Before it hands back, your AI reviews the draft the way George Orwell and Joe Girard would. This is a way of reviewing the work. It does not mean they wrote or endorse it.

Capabilities

• Unsupported claim spotter. Checks each FAQ line against your approved facts and flags what they do not back up. Hands step 2 the marked-up FAQ and the gap list.
• Plain English editor. Rewrites the FAQ in plain words, keeping eligibility limits and removing or marking claims nobody approved. Hands back the corrected draft and the list of changes.

How the role works

1. Checks your task, context and available tools.
2. Picks the methods needed and prepares a work plan.
3. Carries out supported tasks, with each method's limits and review gates.
4. Checks the real deliverables and corrects supported faults.
5. Hands back files, evidence and unresolved gaps.

Your specialist's working setup

Download the base specialist without a task form or account. README.md and SETUP.md explain how to use the folder. SOUL.md defines its scope. INTAKE.md asks missing questions inside your AI. PLAYBOOK.md, SKILLS.md, BEST_PRACTICES.md, CHECKS.md and HANDOFF.md guide the work and its checked deliverables.

Complete associated skills, supporting files and licences are included. Choose only the methods needed for the actual task. Keep context, working files and accepted feedback in your AI project.

Use this specialist through MCP or the API

Call prepare_specialist with role_id check-a-clinic-service-information-page only. No task is required to load it. Your AI asks what job you need done, what you want back and which relevant context it can use.

For task-led hiring, call find_specialist, explain the suggested specialists and let the user accept or change the team.

Complete ZIP: Download base specialist. API: GET /api/v1/specialists/check-a-clinic-service-information-page/pack. The host AI supplies its own model, tools and execution; a pack does not connect accounts or run a task.

Inputs and helpful context

The specialist starts from the task brief. Only active methods require their inputs.

For the primary method, when used

• Your current clinic FAQ or service page, as pasted text
• Approved facts: services, opening hours, booking steps and fees if listed (from your practice manager)
• Contact details: phone, address, email
• Who can book each service, such as age or referral rules
• The name of the person who signs off health wording (optional)

Helpful context (optional)

• Your booking system's service list
• Your clinic's privacy and cancellation notices
• Past patient questions from calls or email
• A list of terms the clinic prefers, such as 'appointment' not 'consultation'

Tools and access

• Any good chat AI that reads files, such as Claude, ChatGPT or Gemini: It must hold the FAQ and the approved facts side by side.
• Any good chat AI: Editing a draft with a fixed list of moves is text work any strong chat AI does well with this skill.
• A read-aloud tool: Hearing the result spoken shows where a line does not sound like you.

Functions and deliverables

• Clinic booking information reviewer: Check a clinic booking FAQ against approved facts, flag unsupported claims and make the instructions easier to follow.
  • A gap list: each FAQ claim marked supported, unsupported or needs clinical review
  • A corrected FAQ draft in plain words, with booking and contact steps clear
  • A list of changes, each with a reason
  • Questions for your clinical reviewer
  • A summary and one next step
• Unsupported claim spotter: Find the claims in your draft that need a source before you publish. Each one is ranked by risk, with the kind of source to look for.
  • A summary of how many claims need support
  • A table of claims ranked by risk
  • The kind of source that would settle each
  • Internal conflicts in your draft
  Source: Pro Skill Packs.
• Plain English editor: Paste a draft and get it back in plain English, with every cut explained and a read-aloud check. Edit stiff emails, reports and pages.
  • The edited text in plain words
  • A list of every cut or swap, with its reason
  • The point of the piece in one sentence
  • Questions where a fact was missing
• Post-sale follow-up planner: Plan your post-sale follow-up: give it what you sell and a buyer's details. You get a thank-you note, a dated contact schedule and a referral ask.
  • A personal thank-you note
  • A dated contact schedule
  • A list of what to record about the buyer
  • A plan for a problem and a referral ask
• Brand profile builder: Share your website. Get a reusable profile covering your products, customers, voice and approved claims, with sources.
  • A folder of eight plain files, from a start file for your AI to a claims list and a change log
  • A tag on every fact, and every claim marked approved, pending or banned
  • A two-sentence diagnosis of your biggest gap, and a list of what's missing and who can answer it
  • A short slice for your next step, if you name one
• George Orwell: Rewrite a memo, report or announcement in plain words using George Orwell’s recorded approach. Cut padding and reveal what vague labels hide.
  • Your problem worked on the way George Orwell would: their questions, their method, their push-back
  • The answer or the work, in George Orwell's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step
• Joe Girard: Plan follow-up after a sale through Joe Girard’s recorded approach. Thank buyers, handle problems and stay in touch after delivery.
  • Your problem worked on the way Joe Girard would: their questions, their method, their push-back
  • The answer or the work, in Joe Girard's voice, using their ideas by name
  • Anything that goes beyond their public record, marked
  • One suggested next step

Tasks you can use it for

• A patient called because the website lists a service you no longer offer.
• You are updating the booking page after a change in hours or staff.
• A new practice manager inherits an FAQ nobody has checked in years.
• You want a clinic FAQ that someone who has never visited can follow.

Limits to check before starting

• You are writing down how new appointments are taken. Use Clinic booking procedure writer.
• You want to measure waiting or call volume. Use Clinic administrative queue reviewer.
• You need medical content checked. A clinician must review that. This only flags it.
• You have no approved facts yet. List them first, then run this.

Best way to use this role

Give it one clear outcome, the actual files and a definition of done. Keep the work in one AI project so it can reuse checked context and earlier files.

• Download the workflow pack and add it to Claude, ChatGPT or Gemini.
• Paste the FAQ first, then the approved facts. Say who reads it, such as new patients.
• Say: follow the workflow file and mark anything you cannot check.
• Read the gap list. For each unsupported line, find the right fact or cut the line.
• Send the clinical questions to the person who signs off health wording.
• Publish the corrected FAQ yourself once it is approved. This does not edit your site.

Read it as data

Read the complete role setup as JSON. Connect your AI to the AI Blocks MCP library and read aiblocks://roles/check-a-clinic-service-information-page for its role instructions and pinned sources.

This is a prepared AI role. No task has run. Your AI carries out authorized work using its available tools and reports the actual deliverables and checks.