Start here

Training your AI

Prybar only knows what you tell it. That is deliberate — it is what stops it inventing a price or promising an appointment you cannot keep. This page is how you give it what it needs.

Why this matters more than anything else

A generic AI, asked about your prices, will produce a plausible number. A plausible number is worse than no number: it is a promise you did not make and will have to break, or honor at a loss.

Prybar is built the other way around. It answers from what you have given it, and when it does not have an answer it says “let me check with the team” and flags the conversation for you. The direct consequence is that answer quality is a function of what you teach it. An hour spent here is worth more than any setting.

Where you teach it

Open Settings → Prybar Assistant → Training & Knowledge. There are two ways to add information:

Import from your website

Give Prybar your website address and it reads your pages to draft your services, hours, and description. Fast, and a good starting point — but always review it. Your website says what you want customers to think, which is not always what you need the assistant to know.

Add facts directly

Type the things only you know: your actual price for a common job, your minimum call-out, how far you travel, what you charge for after-hours, what you will not do. These are read on every conversation.

What to add, in priority order

  1. Prices for your most common jobs. If a customer asks “how much for a water heater?” you want a real answer, not a deferral. Even a range is far better than nothing.
  2. Your service area. Which cities, towns, or radius you cover — and, just as importantly, what you do not cover. This stops the AI booking a job three counties away.
  3. Your hours and after-hours policy. When you work, and what changes about pricing or response time outside those hours.
  4. What you do and do not do. Trades overlap, and customers assume. If you do not do gas work, or do not service a brand, say so.
  5. Your policies that come up often. Deposit requirements, cancellation windows, warranty terms, whether estimates are free.
  6. Answers to your five most-asked questions. If you find yourself typing the same reply every week, it belongs here instead.

Rules worth setting explicitly

These come up often enough to be worth writing down as facts:

  • “Never quote a price for a job that requires an on-site look.”
  • “Always confirm the customer’s address before booking.”
  • “For gas smells, tell the customer to leave the building and call 911.”
  • “Never promise a same-day arrival after 3 PM.”

The assistant treats these as hard constraints, not preferences. Anything safety-related should be written down here rather than left to judgement.

Tone and autonomy

Two adjacent settings change how it behaves rather than what it knows:

  • Replies & Tone — how the assistant sounds. Brief and direct, or warmer and more conversational. Set it to how you actually text your customers.
  • Autonomy — what the assistant may do without asking you first. Booking an appointment is different from sending an invoice; you decide which it handles alone and which it queues for your approval.

How to check your training worked

Test like a customer, not like an owner. Open the test drive, or text your own number, and ask:

  • A price question you have answered in your facts — does it get it right?
  • A price question you have not answered — does it defer, or invent?
  • An area question for somewhere you do not cover — does it say no?
  • A question about a service you do not offer — does it deflect politely?

Heads up

If it invents an answer to something you never told it, that is the defect to chase. Add the missing fact and retest. Do not leave it — an invented price reaches a customer as a commitment.

Next