Services

The inspection services you offer, the scope statement for each, and how they route reports, agreements, and claims.

Every inspection company offers a different mix of services — home inspection, sewer scope, radon, mold, pool, commercial. Each one has its own report, often its own agreement, and its own answer to “what could the inspector see?” Settings > Services is where you tell Callback HQ which services you offer and how each one’s scope should be described.

Why it matters

A property visit usually produces several reports at once. When a complaint concerns the sewer line, the AI needs to judge it against the sewer scope report and the sewer scope agreement — not the home inspection — and defend it on what a sewer camera can and cannot see. Your service list is what makes that routing possible.

Reports synced from Google Drive are labeled with a service from their filename, and every report from the same visit is linked to the claim.
Agreements and Standards of Practice can be tagged with a service on Settings > Documents, so the right one is cited.
The intake form lets the homeowner say which inspection their complaint is about, using the services you have switched on.
The reply draft defends each issue on the scope of the service it concerns.

Built-in services

Callback HQ ships with these services, each with a default scope statement:

Home Inspection
Sewer Scope
Pool / Spa Inspection
Mold Inspection
Termite / WDO Inspection
Radon Test
Fire Hardening / Defensible Space
Chimney Inspection
Septic Inspection
Well & Water Quality
Indoor Air Quality
Asbestos / Lead Sampling
Stucco / EIFS
New Construction / Phase
Builder’s Warranty (11-Month)
Commercial Inspection
Property Condition Assessment
Physical Needs Assessment

Only Home Inspection is on for a new company. Switch on each service you offer using the checkbox at the left of its card. A service that is off still exists — it just doesn’t appear in the intake form or the document-tagging dropdown.

Editing a service

Click Edit on a card to change:

Name— how the service is labeled in the intake form, the claim page, and the documents dropdown.
Scope statement — one or two sentences on what this inspection can and cannot report, written in the company’s favor. The AI paraphrases it when a complaint falls outside the service’s scope. It is never quoted to the homeowner verbatim.
Report filename keywords — extra words that mark a report PDF in your Drive folder as this service, on top of the built-in detection. Comma-separated.

A built-in service you have reworded shows an Edited badge and a Reset to the platform default link.

The scope statement is the defense the AI leans on. “A sewer scope camera cannot see past a blockage, through standing water, or beyond its reach” is the sentence that turns a sewer backup claim from a concession into a scope answer. Make each one specific to how you actually perform the service.

Adding a service we don’t list

Click + Add a service we don’t list at the bottom of the page and fill in:

Name— for example “Thermal Imaging”.
Scope statement — required, since it is the only scope language the AI will have for this service.
Report filename keywords — without these, reports for the service are filed as “Other” and never linked as that service.

Custom services carry a Custom badge and can be deleted. Built-in services can be switched off but not deleted. Deleting a custom service untags any agreements or Standards of Practice that used it, so they apply to every service again.

How reports get labeled

The Drive sync reads each report’s filename. Spectora and similar platforms put the service in the name (8761_Robles_Dr___Sewer_Scope_.pdf), so built-in detection covers the common cases. Your own keywords are checked first, so a company that names its radon reports “RT” can add that. Reports already filed as “Other” are relabeled on the next sync pass once a keyword matches.

What the AI does with an unrecognized report

A report labeled “Other” is still linked to the claim and still read. It just carries a generic scope statement instead of a specific one, so tagging it correctly gives you a better defense.