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

The facts, from the register.

ProductWhatsApp AI Assistant
Register keywa-assistant
OwnerPharoah Technology Ltd (Craig Attoh and Phil Pereira, 50/50) · powered by app-builder
Live atassistant.pharoahtechnology.com · HTTP 200 on 9 September 2026
Price£29 a month · [object Object]
Built from8 register parts, 8 live, 6 probe-verified
Listed3 July 2026

What it does

WhatsApp support for your business in the app your customers already use. AI drafts replies in your brand voice and, during early access, every reply is checked by a person before it is sent; no unreviewed bot ever talks to your customers. No app to install.

Runs on

Cloudflare Hosting — operator alias over deploy rail and site deploy engine
Stripe payments
WhatsApp delivery rail
First-party site analytics beacon
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 buyer's own change-control.

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

A control between the work and the submission

Check 2

A process fit for this buyer, not a generic one

Check 3

Readiness for the next rule change

Frame chosen by BRG as a summary of the buyer's own change-control. 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.

Customer messages land on WhatsApp out of hours and sit unanswered until someone is free.

Who carries it

Businesses seeking WhatsApp customer support with human‑checked AI‑drafted replies.

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

What it does instead.

WhatsApp support for your business — reach the Pharoah team on WhatsApp — every reply is human-checked before it

WhatsApp support for your business in the app your customers already use. AI drafts replies in your brand voice and, during early access, every reply is checked by a person before it is sent; no unreviewed bot ever talks to your customers. No app to install.

The parts doing the work

Cloudflare Hosting — operator alias over deploy rail and site deploy engine verified

Operator-language register alias for Cloudflare Pages hosting/deploy readiness, composed from the existing live deploy rail and white-label site deplo

Stripe payments verified

WhatsApp delivery rail verified

WhatsApp group delivery + MAYA routing rail. Twilio inbound webhook -> wa_group_messages (idempotent ingest) -> dedupe gate -> MAYA intent route -> in

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

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

Proof it exists, not a roadmap.

200

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

6/8

register parts verified by probe

8

parts wired live

HTTP 200

functional surface probe

Open assistant.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 automation & AI chatlevel
Meeting transcription & summarizationwe lead
Expense managementwe lead
Payments processingwe lead
Analytics & reportingwe lead
Reliability/hosting & infrastructurelevel

Position

Reposition as an all‑in‑one SMB operations platform that combines WhatsApp AI with finance, analytics and meeting automation.

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

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.

Businesses seeking WhatsApp customer support with human‑checked AI‑drafted replies.

Only we do

Universal meeting note taker
Expense management
Stripe payments
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.

£29 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
Cloudflare Hosting — operator alias over deploy rail and site deploy engineintegrationlive_wired
Stripe paymentsbackendlive_wired
WhatsApp delivery railintegrationlive_wired
First-party site analytics beaconintegrationlive_wired
Expense Managementfull-stacklive
WhatsApp CTA recipient + honest copy (7 wa-* products)backendlive_wired
Meeting Note Taker — universal transcript→notes enginebackendlive
AI model router (LiteLLM ai-proxy-gateway)integrationlive_wired
Source: product_parts joined to builder_blocks · 8 of 8 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 buyer's own change-control 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 AI Assistant, as a package.

integration

Cloudflare Hosting — operator alias over deploy rail and site deploy engine

Operator-language register alias for Cloudflare Pages hosting/deploy readiness, composed from the existing liv

verified

WhatsApp delivery rail

WhatsApp group delivery + MAYA routing rail. Twilio inbound webhook -> wa_group_messages (idempotent ingest) -

verified

First-party site analytics beacon

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

verified

AI model router (LiteLLM ai-proxy-gateway)

LiteLLM AI model router with pinned free/core aliases, cost-aware fallback routing, live health/model inventor

verified
backend

Stripe payments

verified

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

verified

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
full-stack

Expense Management

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

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

A package reads like a control document.

Inside the scope

  • Cloudflare Hosting — operator alias over deploy rail and site deploy engine
  • Stripe payments
  • WhatsApp delivery rail
  • First-party site analytics beacon
  • WhatsApp CTA recipient + honest copy (7 wa-* products)

Evidenced, and how

  • Live URL probed: HTTP 200 on 9 September 2026
  • 6 parts probe-verified, latest 5 July 2026
  • 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
  • Obtain verified SLA/uptime guarantees for enterprise‑grade reliability
  • Confirm omnichannel extension (e.g., Instagram, SMS) beyond WhatsApp
  • Validate advanced AI response quality/tuning for higher‑value conversations
  • 2 parts still to verify by probe

Who signs, and where the work sits

  • Pharoah Technology Ltd owns the product and the data layer
  • 5 build packets proposed · 2 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 AI Assistantassistant.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 buyer's own change-control. 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 buyer's own change-control; 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.