Live system demo
Try the front desk we build.
The demo below is the same front desk layer we deploy for clients. It answers the question, qualifies the enquiry, takes contact details, books the appointment, produces a structured CRM record, and hands over to a person the moment judgement is needed. The panels beside it show what the system is doing at each step.
This public sandbox demonstrates the workflow, orchestration and system behaviour. It runs in your browser with simulated integrations. The decision layer is rule-based — there is no language model behind it. Nothing you type leaves this page: no email, SMS or calendar action is performed, and nothing is written to a CRM. Voice mode is the one exception — there, audio is sent to an external speech provider to be transcribed and spoken. The business details are a sample configuration belonging to two fictional businesses.
Demo
Start the conversation.
Type, or pick one of the suggested replies. Switch the business and the same engine answers as a different company — because the business knowledge is data, not code.
Currently configured for: Harbour & ValeSampleSample configuration — professional services firm
Welcome to Harbour & Vale. I can arrange a consultation, tell you what we work on, and explain how we charge. How can I help?
System events
- Conversation startedSample configuration — professional services firm
These are real events emitted by the demo system. They describe system behaviour, not business results.
CRM record
- source
- Website chat
- business
- Harbour & Vale
- status
- New enquiry
- transcript_turns
- 0
In a deployment this object is written to your CRM. In the demo it is only displayed here and sent nowhere.
Business knowledge base
- Commercial contracts
- Employment advice
- Corporate and shareholder matters
- Disputes and litigation
- Hours
- Subjects it won't answer
The agent's answers come only from this data. It does not invent what isn't here — it states the limit, or hands over.
Architecture
What's in the demo, and what happens in a deployment.
The difference between the demo and a live deployment is the connections, not the engine. The conversation logic, the qualification rules and the record structure stay the same; the channels and the destination systems are replaced with real ones.
01
Entry channel
In a deployment
- A real phone number (SIP / telephony provider)
- Website chat component
- WhatsApp Business API
02
Decision layer
In a deployment
- Intent classification and entity extraction
- Business knowledge base and answer rules
- Qualification and prioritisation logic
- Handoff thresholds
- Optionally a model provider, bound to the same knowledge base
03
Actions
In a deployment
- Calendar availability and appointment writes
- CRM record creation and updates
- Email / SMS / WhatsApp follow-up
- Human handoff with a handover note
In this demo — In the demo the decision layer runs in your browser, rule-based; the entry channel is this page and the actions are only displayed on screen. In a deployment the same decision layer runs on a server, optionally backed by a model provider, and the actions are written to real systems. Because the engine and the business configuration are separate, that move is a connection rather than a rewrite.
Deployment
Configuring this for your business.
The demo uses the same structure as a deployment. The work done for you is extracting the business knowledge and connecting it to real systems.
Extracting the knowledge base
Services, hours, price bands, frequent questions and handoff rules are written down. The agent speaks only inside that.
Connecting the channels
A number for inbound calls, a chat component for the website, WhatsApp where it's needed. Same agent, same rules.
Writing to your systems
Calendar and CRM are connected. Every conversation leaves a structured record, an appointment and a follow-up trigger.
Handoff and measurement
Which subjects go to a person is defined up front. Every conversation keeps its transcript and event log, so what the system did can be audited afterwards.
Getting started
Discuss a deployment
Tell us about the enquiry that goes unanswered, the follow-up done by hand, or the work that scatters between systems. In the first call we'll establish what can be systematised and where to start.
After you send the form
- A reply within two working daysWe read your message and suggest a time that suits you.
- A 30–45 minute discovery callA working session that maps the process, not a sales pitch. If it isn't a fit, we'll say so plainly.
- A written summaryAfterwards we put in writing what could be built, in what order, and within what scope.