Trust

How we keep your AI assistant under control.

An automated assistant can be useful, but only if it knows its limits. PracticalOps assistants are designed to answer from approved information, capture enquiries clearly, and hand over when a person should step in.

01

Approved information only

It answers from the business information you sign off: services, opening hours, common questions, approved price lines and agreed next steps. It is not left to improvise from the open internet or model memory.

02

Clear handover

When it does not know, it says so and moves the enquiry towards a human follow-up. Uncertainty, complaints and requests to speak to someone are treated as handover moments, not as prompts to guess.

03

No invented prices or promises

It never invents prices, availability, setup timelines or business promises. It also never says a booking exists unless the booking has actually been created through an approved route.

04

Always disclosed

The assistant tells people it is automated. It is there to help capture and qualify enquiries, not to pretend to be a member of staff.

05

Conversations are logged

When an assistant is in use, enquiries and conversation transcripts are logged for human review, so follow-up has context and there is a record of what happened. Nothing important is meant to disappear into a chat window.

06

Fallbacks keep capture working

If the assistant cannot respond, the route is designed to fall back to a message form, phone or email. The aim is simple: capture the lead and give the customer a clear next step, even when the clever bit is unavailable.

07

Knowledge can change

As your business changes, the approved answers can be updated. New services, changed opening hours and revised FAQs should be treated as managed business content, not hidden technical settings.

08

UK GDPR by design

Only relevant enquiry information is collected, for clear business follow-up and service delivery purposes. Retention, access and deletion processes are handled under UK GDPR; see the privacy page for the current public template.

Built this way

These are not aspirations. They are how the system is built.

The guardrails are practical controls: approved content, server-side keys, transcript logging, handover rules, forbidden-claim checks and message-form fallbacks.

That gives a local business owner something better than a shiny chat widget: a controlled route for enquiries, with a person still in charge of the business decisions.

Talk about a controlled assistant