faberiq

Trust

You set the rules.
You can see everything.

Handing your first conversation to software is a real decision. Here is exactly what constrains the front desk, how you check it before it goes live, and what happens to your data.

BOUNDARIES

The playbook is a form, not a prompt

You declare what the front desk collects, what it may quote, what it must never promise, and what it does when it doesn't know. Those are rules the agent runs inside, not suggestions in a paragraph of text.

BEFORE PUBLISH

Replay yesterday against tomorrow

Change the playbook and replay real past conversations against it. You see, side by side, what the front desk would have said differently. Nothing reaches a customer until you publish.

HANDOFF

It knows when to stop

Out of scope, out of price range, upset, or simply unknown: the front desk hands the thread to a person, tells the customer plainly, and stops answering. Refusing is behaviour we test for, not a failure.

AUDIT

Every action is on the record

Every message, booking, quote, payment and handoff is logged against the customer with a timestamp and the reason. If you ever have to explain what happened, the thread is the explanation.

Your data stays yours

  • We do not train models on your conversations or your customers' data.
  • Export customers, conversations, documents and invoices at any time, in a standard format.
  • Delete on request, and we mean the records, not a flag on a row.
  • Payments run on your own Square or Stripe account. We never hold your money.
  • Data is encrypted in transit and at rest. SOC 2 work is under way and we will say when it is done, not before.

Open on purpose

The front desk speaks MCP in both directions. It connects to new tools without waiting for us to build a connector, and your own Claude or ChatGPT can read and act on your front desk: ask it what got booked this week and it can answer.

Lock-in is a business model. We would rather you stayed because leaving is easy.

What it will not do

Said plainly, because you should know before you connect a channel.

  • It does not pretend to be a person. If a customer asks, it says it is the business's assistant.
  • It does not invent prices, availability or policies that are not in your knowledge base.
  • It does not discount, negotiate or make promises about timing unless you have said it may.
  • It does not give medical, legal or financial advice, whatever the customer asks.
  • It does not keep answering a thread it has handed to a person.

Watch it refuse something.

The demo we would rather show you is the one where the front desk says no and hands the thread to a person.