Respond to every callback in minutes with AI-powered accuracy.
Callback HQ matches each guarantee-claim email to the right inspection report, evaluates it against your agreement and Standards of Practice, and drafts a reply you can approve in one click. Your inspectors stay on the road. Your office stops re-reading reports.
Card required to start. Cancel before day 14 and you owe nothing — we ask up-front to keep spam accounts out.
Frivolous callbacks are a huge waste of time. Fast replies are good customer service — and save you money.
Homeowner emails you a complaint. You dig up the right report. You re-read the agreement to remember what's covered. You check the Standards of Practice. You draft a measured reply that doesn't expose you. You send it. By the time you're done it's the afternoon — and there are three more in the queue.
From claim to signed release in four steps you control.
Homeowner submits a callback
Embed the intake form on your website or send the link. The homeowner types their issue, picks the inspection date, optionally uploads photos.
Claude analyzes against the report
We pull the right inspection PDF from your Drive, run a three-question analysis (was it flagged? did the SoP require it? does the agreement cover it?), and draft a cited reply in your voice.
You approve and send
Review the verdict, scan the cited quotes, nudge the tone if you want. Hit Approve and we email it under your domain. Confident drafts auto-send after 5 minutes — undo any time.
If you pay, the release signs itself
Offer money and your own release goes out with it, ready to sign electronically. Everyone on title signs, you get a payment notice and an audit certificate, and the claim only closes when it is actually executed.
When you do pay, paper it properly. Automatically, and with a signature you can prove.
Money going out without a signed release is money you can be asked for twice. Callback HQ issues the release the moment you offer a settlement, collects the signatures electronically, and refuses to call the claim closed until it’s executed.
Your release, not ours
You upload your own settlement release — the one your attorney wrote. Callback HQ never drafts legal language and never edits yours. We generate the cover page with the particulars filled in and attach your document behind it.
Everyone on title signs
A release signed by one of two owners releases one of two owners. We capture the owner list when the claim comes in, send each person their own signing link, and the agreement is only executed when the last one signs.
Evidence, not a screenshot
We keep the exact bytes the claimant received, hashed. The signed copy carries an audit certificate with timestamps, IP address and signature method — and a one-click integrity check that proves the document hasn't changed since signing.
Somebody gets told to pay
The moment it's fully executed, your payments contact gets a notice with the client, property, amount and reason, and the signed PDF attached. Nothing sits waiting for someone to notice.
Callback HQ is not a law firm and provides no legal advice. We don’t write, review, or check your release against any state or federal law — that’s your counsel’s job.
Find out what your callbacks are actually about.
Every callback is categorised by the nature of the underlying issue — plumbing, roof, HVAC, electrical, mold, and so on. Read it company-wide to see where claims cluster. Then filter to one inspector.
That second view is the useful one. If a roofer’s worth of roof callbacks sits against a single name while nobody else has them, that’s not a mystery to solve — it’s a training conversation to schedule, and now you can have it with numbers in front of you instead of a hunch.
Filterable by date range and by inspector, alongside response time, denial rate, and where your settlement money is sitting.
Illustrative figures.
Nothing is automated until you say it is — and only as far as you say.
Out of the box, Callback HQ drafts and waits. Every reply sits for a human until you decide otherwise. When you’re ready to let some of it run, you loosen it one setting at a time — and four independent limits still apply.
Set the posture, per workspace or per claim
One slider moves the whole letter from goodwill-first to firm and contract-first. Same facts, same citations, different stance. Set a default and override it on any individual claim.
Decide what may send itself
Every analysis carries a confidence score. Hold everything for review, auto-send only at or above a confidence level you set, or go fully automatic. Anything queued waits 5 minutes first, and you can undo it. On a multi-issue claim the score used is the lowest of them — one uncertain item holds the whole letter.
Cap the money, independently of confidence
Confidence answers “is the analysis sound?”. It says nothing about how much money is leaving. Set a goodwill cap and a refund cap and any offer above them waits for a person no matter how confident the analysis is — per issue and in total, so several small offers can’t add up past your limit.
Some claims never automate at all
A minor, a claimant with a lawyer, or a filed lawsuit halts the workflow outright. Those aren’t warnings you can dismiss — they’re cases where this shouldn’t be the tool, and the claim tells you what to do instead.
A confident analysis recommending a large payment is exactly the case you want a person to see. Confidence and money are separate questions, so they get separate limits.
Generic AI won't cite your agreement. Callback HQ will.
Cited, not hallucinated
Every claim, verdict, and dollar figure traces to a specific paragraph in the inspection report, agreement, or SoP. The reviewer sees the source before approving.
Trained on your documents
Upload your inspection agreement and pick your SoP (InterNACHI, TREC, ASHI, CAHPI — we'll fetch the official text). All analysis stays scoped to what you actually use.
Pulls reports straight from Drive
Connect your Google Drive once, point us at your inspections folder. We catalog the full tree and lazy-load the right report when a callback arrives — no migration or re-upload.
Proof it actually arrived
Every release email is tracked per signer — delivered, opened, bounced. A bounced agreement is the one failure that looks exactly like an ignored one, so we surface it loudly instead of letting a reminder chase a dead address.
Per inspector. One plan, every feature. Annual saves ~17%.
Simple seat-based pricing with a volume tier that kicks in automatically as you grow. 14-day trial on every account, no setup fees, no per-claim metering.
Questions we get most often.
Do I need to upload all my inspection reports?
No. Callback HQ catalogs your Google Drive once (we read the file list, not the contents), then pulls the specific report we need when a callback arrives. A 5,000-report Drive is fine.
What email address does the reply send from?
Your domain. You verify the sending domain in Resend during onboarding (we'll walk you through the DNS records). Replies arrive in your homeowner's inbox from claims@yourcompany.com, not from us.
Will it auto-send a wrong reply?
Only if you tell it to. Every workspace has a confidence threshold (default 0.85). Below that, the draft holds for human review. Above it, the draft queues with a 5-minute undo window before it actually sends.
Which Standards of Practice are supported?
InterNACHI, TREC, ASHI, and CAHPI out of the box — pick one in onboarding and we'll fetch the official text. You can also upload your own SoP PDF if you follow a state-specific one.
What happens to the homeowner's reply if they write back?
It threads onto the original claim. You'll see a Replies tab in the claim review, the status flips to 'replied', and the original outbound and the homeowner's response sit side-by-side.
Do you write the settlement release?
No, and we won't. You upload your own release — the one your attorney wrote or approved. We generate a cover page with the particulars filled in (client, property, amount, date) and attach your document behind it, unchanged. Callback HQ is not a law firm, doesn't review your release for compliance with anything, and gives no legal advice.
How does the e-signature work, and does it hold up?
The claimant gets a link unique to them, reads the agreement, types or draws their signature, and consents electronically under ESIGN/UETA. We record the exact document they saw — hashed, so it can be proven unchanged — plus timestamps, their IP address and the signature method, and bind it all into an audit certificate on the signed PDF. One click re-verifies the hash any time.
What if the property has two owners?
Both sign, separately. A release executed by one of two owners releases one of two owners' claims and leaves the other live — so we ask who's on title when the claim comes in, send each owner their own link, and the agreement isn't executed until the last one signs. If nobody recorded the owners, we won't issue a settlement until you do.
Can I stop it from offering large amounts on its own?
Yes, and this is deliberately separate from the confidence setting. You set a goodwill cap and a refund cap; any offer above them holds for a person regardless of how confident the analysis is. It's checked per issue and in total, so five individually-permitted offers can't add up past your limit. Set a cap to zero and no money ever leaves without you.
How do I know it isn't quietly sending things?
The default is that nothing sends itself — every draft waits. If you switch on auto-send above a confidence threshold, queued replies still sit for 5 minutes with an undo button, and the claim states the score and the threshold it passed. Anything held tells you why: low confidence, over a money cap, or no matching report.
How does the per-inspector tracking work?
Each callback is categorised by the nature of the underlying issue, then rolled up two ways: company-wide, and per inspector. Filter to one person and you see where their claims cluster. It's meant for coaching — the point is spotting that one inspector's callbacks concentrate somewhere the others' don't, early enough to do something about it.
Are there claims it refuses to handle?
Three, and they stop the workflow rather than warn you: a claimant who is a minor, a claimant represented by an attorney, and a matter with a lawsuit already filed. Each is a case where a pre-suit property release is the wrong instrument, so the claim tells you what to do instead of quietly doing the wrong thing.
What happens if the release email bounces?
You see it. Delivery is tracked per signer — delivered, opened, bounced — and a bounce outranks everything else on the claim. It matters because a bounced agreement is indistinguishable from an ignored one otherwise: the claimant never saw it, nobody knows, and the reminders keep chasing an address that can't receive mail.
Does an unsigned offer stay open forever?
No. Offers expire 30 days after they're sent, the date is stated on the agreement and in the email the claimant receives, and an expired link stops working — a new agreement has to be issued. Until one is signed, that money shows as awaiting signature, never as settled.
Stop hand-writing the same five emails.
Spin up your workspace in under five minutes. Connect Drive, upload your agreement, embed the form. Your next callback gets drafted for you.