All decks
WhatsApp Clinic AgentPharoah Technology · deck · narration · production guide · generated 9 September 2026
02What it is

The facts, from the register.

ProductWhatsApp Clinic Agent
Register keywa-clinic
OwnerPharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50) · powered by app-builder
Live atclinic.pharoahtechnology.com · HTTP 200 on 9 September 2026
Price£49 a month · [object Object]
Built from6 register parts, 6 live, 1 probe-verified
Listed3 July 2026

What it does

Handles clinic bookings and reminders over WhatsApp. Patients book, reschedule and get reminders in the chat they already use, which cuts no-shows without a separate app or portal.

Runs on

First-party site analytics beacon
Expense Management
Meeting Note Taker — universal transcript→notes engine
WhatsApp/Meta inbound conversational rail
Source: estate register (products, product_parts, builder_blocks) · deploy probe 9 September 2026Evidence live
03The frameWhat this buyer's profession checks

We will measure it against the CQC key questions.

Three checks a buyer in this field applies, whether or not they name the standard. We use them as the frame for everything that follows.

Check 1

Safe

Check 2

Effective

Check 3

Well-led

Frame chosen by BRG as a summary of the CQC key questions. Verify the wording with the body before external use.No accreditation is claimed
04Why it's better · 1 of 6Check 2 · fit for purpose

The job as the register describes it.

Clinic no-shows cost the slot and the revenue, and reminder calls eat staff time.

Who carries it

Clinics and salons use this WhatsApp service to manage appointments and reminders.

Source: register pain_point · audienceThe problem, stated plainly
05Why it's better · 2 of 6Check 2 · fit for purpose

What it does instead.

A WhatsApp service for clinics and salons that books appointments, sends reminders and fills cancellations over WhatsApp — so your front desk isn

Handles clinic bookings and reminders over WhatsApp. Patients book, reschedule and get reminders in the chat they already use, which cuts no-shows without a separate app or portal.

The parts doing the work

First-party site analytics beacon verified

Public web-beacon edge fn (ofcjggvruhwhaqthdwxa/functions/v1/web-beacon, v3) + client tracker in Attoh _hubs/_shared/site-system.js initAnalytics() an

Expense Management

Universal expense capability: claim capture (portal/WhatsApp), multi-line receipts, approval workflow, and reimbursement intents on the forge.invoicin

Meeting Note Taker — universal transcript→notes engine

ONE reusable engine closing the largest gap cluster (53 products needed "meeting note taker"). Reuses rail.llm-gateway; per-product behaviour = a conf

WhatsApp/Meta inbound conversational rail

Meta WhatsApp Cloud API INBOUND rail: GET verify handshake + constant-time X-Hub-Signature-256 HMAC verify, parses webhook into {from,text,messageId},

Source: register purpose, public_blurb, product_parts joined to builder_blocks4 of 6 parts shown
06Why it's better · 3 of 6Check 1 · controls

Proof it exists, not a roadmap.

200

HTTP status of clinic.pharoahtechnology.com on 9 September 2026 · real-content-verified

1/6

register parts verified by probe

6

parts wired live

HTTP 200

functional surface probe

Open clinic.pharoahtechnology.com during the talk. Anything the deck claims should be visible there.

Source: register deploy_probe_code, deploy_probed_at, product_parts.verified_by_probeProbed, not promised
07Why it's better · 4 of 6Against the market, honestly

Where we lead, and where we don't.

AxisWhere we stand
WhatsApp messaging (inbound/outbound, reliability & compliance)level
Meeting transcription & AI summarisationwe lead
Expense capture, approval & reimbursementwe lead
First‑party site analytics & visitor trackingwe lead

Position

A reliable, scalable WhatsApp‑enabled workflow engine for clinics that combines messaging with AI‑driven meeting notes, expense tracking and analytics.

Evidence: respond.io · wati.io · twilio.com · aerochat.ai

Source: register vs_competition (9 September 2026)Named competitors are the register's, not the presenter's
08Why it's better · 5 of 6Check 2 · fit for purpose

Built for one kind of buyer.

Clinics and salons use this WhatsApp service to manage appointments and reminders.

Only we do

Verified BullMQ‑based async consumer job queue that decouples webhook handling from LLM inference for sub‑second responsiveness
Source: register audience, serves_niches, vs_competition ADJACENT (verified)One buyer, not everyone
09Why it's better · 6 of 6Price is part of the scope

What it costs, in one line.

£49 a month

Basis: [object Object]

Buying route

Payment on enquiry
software
Scope named on the next slides, so the price has a boundary
Source: register price_gbp, billing_interval, pricing_basis, payment_link_activeNo hidden rate card
10What's inside

The parts, with their verification state.

PartCategoryStateVerified
First-party site analytics beaconintegrationlive_wired
Expense Managementfull-stacklive
Meeting Note Taker — universal transcript→notes enginebackendlive
WhatsApp/Meta inbound conversational railintegrationlive_wired
BullMQ async consumer job runtimebackendlive_wired
WhatsApp CTA recipient + honest copy (7 wa-* products)backendlive_wired
Source: product_parts joined to builder_blocks · 6 of 6 shown probe-verified   not yet
12Why packaging matters

Five things a package does that a price cannot.

1
Scope becomes visible. The parts are named, so nothing is assumed.
2
Boundaries are explicit. What is outside is written down before the first invoice.
3
It is auditable. A package is a documented process, which is what the CQC key questions looks for.
4
Buyers compare like for like. A referral needs a defined thing to refer.
5
Switching fear drops. The move is inside the package, not a project bolted on the front.
Source: BRG packaging doctrine; frame from slide 3Packaging = a compliance instrument
13This packageCut by what each part does

WhatsApp Clinic Agent, as a package.

integration

First-party site analytics beacon

Public web-beacon edge fn (ofcjggvruhwhaqthdwxa/functions/v1/web-beacon, v3) + client tracker in Attoh _hubs/_

verified

WhatsApp/Meta inbound conversational rail

Meta WhatsApp Cloud API INBOUND rail: GET verify handshake + constant-time X-Hub-Signature-256 HMAC verify, pa

live_wired
full-stack

Expense Management

Universal expense capability: claim capture (portal/WhatsApp), multi-line receipts, approval workflow, and rei

live
backend

Meeting Note Taker — universal transcript→notes engine

ONE reusable engine closing the largest gap cluster (53 products needed "meeting note taker"). Reuses rail.llm

live

BullMQ async consumer job runtime

Redis-backed BullMQ job queue + worker decoupling webhook handlers (<1s) from LLM inference (10-30s). Job type

live_wired

WhatsApp CTA recipient + honest copy (7 wa-* products)

Repointed 21 CTAs across all 7 wa-* products from https://wa.me/?text= (NO recipient — opened a contact picker

live_wired
Source: product_parts grouped by builder_blocks.category3 groups
14Anatomy of the packageOn one page · 8 items of work left, filed

A package reads like a control document.

Inside the scope

  • First-party site analytics beacon

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 1 parts probe-verified
  • Functional surface: HTTP 200
  • Register row updated with every probe

Outside the scope today · work left

  • Human WhatsApp service round trip and ownership or continuity of +34670631458 are not proved; page is explicit
  • Verified two‑way WhatsApp conversation analytics (response time, CSAT, message throughput) to exceed competito
  • Verified high‑quality WhatsApp outbound campaign manager (template approvals, media support, delivery analytic
  • 5 parts still to verify by probe

Who signs, and where the work sits

  • Pharoah Technology Ltd owns the product and the data layer
  • 3 build packets proposed · 5 management items pending
  • Change log kept in the register
Source: product_parts (inside), deploy and part probes (evidenced), v_deck_work_left (work left; filed to manager_work and build_packets by deck_work_left_sync)One page
15Across the family

Where it hands over.

Anaïs AIgateway.pharoahtechnology.com
Anaïs AI (LLM router / reseller)anaisai.co.uk
Anaïs AI (working app)anaisai.co.uk
Pharoah TechnologyWhatsApp Clinic Agentclinic.pharoahtechnology.com
ATS Résumé Scanner (free)ats.pharoahtechnology.com
Aurora AIauroraai.pharoahtechnology.com
Aurora Guardauroraguard.co.uk
Source: register rows sharing client_key pharoahOne house, many doors
1 / 16
Arrow keys or space · N narration · P print
Slide 1Narration Words Running total

Production guide

How to turn these sixteen slides into a presentation video. Same structure as every deck in the family, so a crew that has made one can make them all.

1 · Deliverable

ItemSpec
Format16:9, 1920×1080, 25 fps, H.264 MP4 plus WebM. Burned captions and a sidecar SRT.
RuntimeNarration below plus screen captures of the live product; typically 8 to 12 minutes.
Framethe CQC key questions. Verify the wording of the three checks with the body before external use.
BrandPharoah Technology family palette as rendered here. Green only for verified and live states; red only for exclusions.
VoiceCalm, exact, never theatrical. Read figures and dates in full. Numbers are the register's, and the register is cited on every slide.

2 · Runtime plan

#SlideNarrationWordsStarts

3 · Screen captures

4 · Full narration

5 · What this deck must not say

  • No numbers that are not on a slide with a register source.
  • No accreditation by the CQC key questions; the frame is a lens, not a badge.
  • No named competitor read aloud unless the audience asks; the register's names are on slide 7 for the presenter.
  • No client names, volumes or tenure unless the register carries them.

6 · Regenerate

This deck is generated from the estate register. Update the product row, re-run the deck build, redeploy. Do not hand-edit this file.