AI receptionist demo
Northgate Heating & Air is a fictional HVAC company in Portland, Oregon. This is the receptionist it would use. Ask it for a booking and see what happens.
This is the web-chat build. Phone builds run the same workflow behind a voice platform such as Vapi or Retell, so the part that answers, qualifies and files the lead does not change.
Starting the demo receptionist…
Demo only. Do not enter real personal, medical or payment information. A message you send here is processed by a language model to generate a reply.
What it is doing
Answers from a fixed knowledge base
Hours, services, the service area and the diagnostic fee come from one block of text. The assistant is instructed not to add facts, estimate prices, or invent availability.
Qualifies the job
It collects name, callback number, address, the problem in the customer’s words, and a preferred window, then reads the number back for confirmation.
Hands off correctly
Gas smell, a carbon-monoxide alarm, no heat in freezing weather, or an active leak route straight to the emergency line, and the lead is flagged urgent.
Files the lead
One structured record lands in a data table and one email arrives, so nothing depends on somebody reading a chat window later.
What is real, and what is not
A demo that pretends is worth nothing, so here is the split.
Real
- The assistant runs on a live n8n workflow with a real language model behind it.
- Answers are grounded in a fixed knowledge base for the fictional company, not free invention.
- A completed booking produces a structured lead and sends a real email notification.
- The page is protected by Cloudflare Turnstile, a rate limit, and a server-side proxy that hides the workflow endpoint.
Simulated
- Northgate Heating & Air does not exist. The phone number is a reserved fictional number.
- The three appointment windows are fixed strings, not live calendar availability.
- Leads are logged to a sandbox table. In a real build they go to FileMaker, a CRM, or your calendar.
- No payment is taken and no real appointment is created.
What it costs to have one
The package is deliberately small: one workflow, one knowledge base, one place for leads to land, and a handover so you can run it without me.
Build
$750 – $1,500
Scoped by channel and integrations. Includes the knowledge base, the qualification rules, the lead destination, and testing against real conversations.
Hosting and maintenance
$99 – $199 / month
Running, monitoring, prompt and knowledge-base updates, and a monthly review of what customers actually asked.
Where it writes is the part that matters. A receptionist that logs a lead into a chat window is a chatbot. One that writes into your FileMaker system, your CRM, or your calendar is a front desk. That integration is the work I do.
How it is built
The conversation runs as an n8n workflow on a self-hosted instance. This page talks to it through a Cloudflare Pages Function that verifies a Turnstile challenge, rate-limits abuse, and keeps the workflow endpoint out of the page source. Leads land in a data table and arrive by email.
If you want one for your business, or want to talk about wiring it into a system you already run,get in touch.