Every call answered. Then the result is checked against the real record.
When Hailey books a job, cancels one, changes an address or takes a message, FlintCrew looks in the real system itself instead of taking the AI’s word for it, and seals every check in a tamper-proof record you can verify yourself. Customer details are swapped for placeholders before the AI that runs the call reads them. Don’t run an AI receptionist on trust.
No contracts · No setup fee · Live before your next busy weekend
An AI receptionist that sounds right is not the same as one that did the job. These are the failures we built FlintCrew to catch.
You should not run an AI receptionist without this.
What FlintCrew checks today: bookings, cancellations, address changes and messages. It does not yet check emergency texts, customer confirmation texts or text-message consent; we will add each one here when it does. Detection of customer details is best-effort: a detail we do not recognise is not replaced. A sealed chain cannot by itself show entries cut off the end; keep a seal you saw earlier and the checker catches that too.
No scripts to write. No training. Hailey knows HVAC, plumbing and electrical out of the box — hours, services, and what counts as an emergency. More trades are rolling out; tell us yours and we’ll set you up by hand meanwhile.
Hailey picks up in under 3 seconds, 24/7. No busy signals, no voicemail. Your customer always reaches a live voice.
What broke, where, how urgent. She works out whether this is a real emergency or a Tuesday appointment.
If your on-call tech isn’t answering, a real FlintCrew person is paged the moment the ladder stalls. Nothing sits in a queue waiting to be noticed. Hailey does not transfer live calls.
Your on-call tech gets a text with the address, the issue and the callback number. No reply? We escalate, then call them. The customer gets a confirmation either way, and the whole chain is written down.
A homeowner's AC goes down at 11pm in July. Here's what happens.
11:02pm — Customer calls. Voicemail. They hang up.
11:04pm — They call your competitor. Reach a live voice.
11:05pm — Job booked. Deposit taken.
7:00am — You wake up. Missed call. No message. No job.
11:02pm — Hailey answers in 3 seconds. Calm, professional.
11:03pm — Name, address and phone swapped for placeholders before the AI that runs the call reads them.
11:04pm — Emergency confirmed. Tech texted. Customer told help is on the way.
7:00am — You wake up. Job's done. Invoice pending.
What missed calls cost you. What you're paying now to handle them badly.
| Feature | FlintCrew | Ask any other service |
|---|---|---|
| Checks your calendar after it says “you’re booked” | ✓ | Ask |
| Checks a cancellation, an address change and a message were actually saved | ✓ | Ask |
| Sealed, tamper-proof record you can verify yourself | ✓ | Ask |
| Customer details replaced with placeholders before the AI reads them | ✓ | Ask |
| Caller’s words screened for manipulation before a booking or message | ✓ | Ask |
| Fixed, written lines: no invented prices or promises | ✓ | Ask |
| Every action checked against a fixed list of what Hailey may do | ✓ | Ask |
| Weekly proof report | ✓ | Ask |
| Your data kept to your business alone | ✓ | Ask |
| Google Calendar built in | ✓ | Ask |
Protection is included in every plan — never an add-on. FlintCrew governance is included with both plans at no extra charge for now.
You are choosing between us and a person. That is the honest comparison, because a person is what we replace: we answer, book and get the tech chased down, and page one of our people if the ladder stalls.
$3,750–$4,600/mo
Salary, payroll tax and benefits, all-in. Answers during business hours. Takes holidays. Does not chase an on-call tech at 2am.
$179–$649/mo
Takes a message and passes it on. No booking into your calendar, no escalation ladder, and no record of what was decided.
$49.99–$199.99/mo
Answers, qualifies, books (on the $199.99 plan), dispatches, escalates when nobody replies, and pages a real person if the ladder stalls. Every call written down.
FlintCrew is our AI governance gateway. When Hailey books a job, cancels one, changes an address or takes a message, the request goes through FlintCrew. It comes with both plans.
Names, phone numbers and addresses are swapped for placeholders before the AI that runs the call reads them. The real details are put back only where they are needed, such as the booking itself.
Bookings and messages are screened for manipulation before they run, and every action is checked against the list of actions Hailey is allowed to take. If it fails, it is refused.
After a booking, a cancellation, an address change or a message, FlintCrew looks in the real record itself. A check that fails comes back ✗, not ✓.
What was asked, what was protected and what was refused are recorded for each action, and every check’s result is sealed into a tamper-proof record, so there is something to show when someone asks what your AI did.
Today FlintCrew governs Hailey. It does not yet cover other AI tools in your business, such as ChatGPT or Copilot.
Plain English, no jargon. How many calls were handled, how many got a tech dispatched, and what was escalated and why. It arrives whether the week was good or bad — a report you only get when things go well is not a record, it is marketing.
Every call Hailey answered, what she did with it, and which ones needed a human.
Who was texted, who answered, who did not, and what happened when they did not.
Redactions and blocked requests. Caller names, addresses and phone numbers are replaced before a model reads them, but the report carries no figure for that, because we do not publish a number we have not measured.
Show it to your insurer. Show it to a customer who asks. It is your documentation, not ours.
FlintCrew takes its name from where we come from — Flint, Michigan, and the people there: the kind of place where showing up and doing the work isn’t a virtue, it’s just what you do.
We’re based in North Carolina and we’re small on purpose. Every FlintCrew customer gets a direct line to the people running the system. No support tickets. No call centre. We own the process and we own the outcome.
“Show up. Do the work. Help people.”
That’s not a slogan. It’s the standard we hold ourselves to when a call goes wrong at 2am.
Tell us about your shop and we'll set up a live demo — you'll see the real product, not a slide deck.
We'll reach out within one business day to schedule your live demo. In the meantime, call +1 (984) 238-4018 to hear Hailey right now.
FlintCrew replaces names, addresses and phone numbers with placeholders before the AI that runs the conversation reads them — and gives you a plain-English weekly report of what happened on your calls. The report does not yet count what was redacted or blocked.
Built by engineers who've seen what happens when AI goes wrong.
Before the AI that runs the conversation reads anything, the transcript runs through Microsoft Presidio — an industry-standard NER (name recognition) engine. Names, addresses and phone numbers it finds are replaced with placeholders, so that AI works from "{{PERSON}} at {{ADDRESS}}", not the real details. If that step can't run, Hailey skips the AI for that turn rather than send it anything. Detection is best-effort: a detail the engine does not recognise is not replaced. The real details are kept on our side so Hailey can read them back and book the job, and they are stored securely. When a booking or message is screened for manipulation (L3 and L4), the screening models read the request with the names and addresses we detected replaced by placeholder words. Anything we did not detect is read as given. An appointment lookup or an address change does not go through this route yet. Where those requests are screened, the screening model reads the request as the caller gave it. A lookup by phone number alone is not screened for manipulation.
When Hailey is about to act on something a caller said — a booking, a non-emergency message — those words are compared against a live database of known AI attack patterns — sourced from OWASP, Lakera, and Anthropic security research and checked for new entries by a scheduled daily job. If the input matches a known prompt injection technique or jailbreak attempt, the action is refused before it runs. Emergency dispatches are never held up by this check. The database covers known attack vectors, not new ones nobody has published.
When Hailey is about to act on something a caller said — booking an appointment, taking a message — the caller's words are screened by an AI safety model for prompt injection, jailbreak, and data-exfiltration attempts before the action runs. A flagged request is refused and recorded instead of carried out. If the screen itself can't run, the request is rejected rather than waved through.
A second AI model scores the same request on a 0–1 scale for manipulation intent — separate from the injection screen. Where that screen asks "is this an attack on the AI?" this layer asks "is this caller trying to manipulate the AI?" A score of 0.7 or higher blocks the action.
Every action Hailey takes — booking an appointment, dispatching a tech, taking a message — is checked against the fixed list of actions she is allowed to perform before it runs. An action outside that list is refused and recorded. This check does not compare the action with what the caller asked for.
Hailey's lines are fixed wording filled in with the caller's own details, not text an AI writes freely. The last step before a line is spoken checks it for a leftover placeholder: if one is there, the line is not spoken and Hailey asks the caller to repeat instead, so nobody hears a code word. This guard checks for placeholders only. It does not review a line for other content.
Each call is recorded turn by turn as it happens: what the caller said, what Hailey said, and the actions she took, with names, addresses and phone numbers replaced by placeholders. Actions that go through FlintCrew get a second record there, including the ones it refused. The recording runs in the background so it can never slow a caller down, which also means a turn can be missed if the recorder fails. It is a working record, not a guarantee of every line. Every Monday you get a proof report by email: what Hailey did that week, in plain numbers. It does not count redactions or blocked requests. No jargon. No tech degree required. If you ever need to show a customer, insurer, attorney, or regulator what happened on a call, this record is what we pull.
Your proof report tells you what Hailey did with the week's calls. It arrives by email every Monday. The figures below are an example, not a customer's.
A line with nothing to report is left out, and a week with no calls gets one sentence, not a grid of zeros. If we could not produce a figure, the report says so instead of showing a zero. It is a short email with no attachment, and it does not report on redaction or blocked requests.
So we are precise about who sees it. The AI that runs the conversation works from placeholders — the names, addresses and phone numbers Hailey detects are replaced before it reads a word, and if that step can’t run, Hailey skips it for that turn rather than send it anything. We do see it, and so does your tech: that is how somebody gets to the door. The difference is that every time it happens it is written down and scoped to your business alone.
Your calls, your bookings, and the people waiting on you — from your phone, whenever you want it.
Your calls, newest first, with the time, the caller's number, what the call was about and how it ended. Open one to read the transcript, with names, addresses and phone numbers shown as placeholders.
Today's booked jobs on your home screen, and a count of the calls on your call log that left a booking.
Emergencies Hailey sent out, people waiting on a call back, and calls that got nowhere — at the top of your home screen, so you can respond fast when it matters.
A proof report by email every Monday: what Hailey did that week, in plain numbers.
We'll show you the real product on a live demo — your questions, your shop, no slides.
Two plans. No contracts. No setup fee. Protection built into both.
No contracts. Cancel anytime. Setup is free — most shops are live before their next busy weekend.
Hailey answers calls from day one. Text messages start once the phone carriers approve your number, which usually takes 10 to 15 days.