The Pest control pack

Everything in the pack,
and everything it will not do.

The CRM fields and stages that follow every call, what it connects to, and what it never says. Why any of it matters is on the Pest control page.

Pest control — this pack was built for the calls that reach this kind of business. Illustrative photograph.

Fields that are filled when the call ends

This trade pack is built to order. Below is the design we switch on for you: the fields, stages and never-say list are drafted, so with your price list and hours it can be switched on within days.

Pest and where it was seenBuilding type and sizePets or infants in the homePreferred time and the time bookedSingle treatment or recurring planFollow-up visit date

The stages an inquiry moves through

How many inquiries sit at each stage, on one line — in the order work actually flows in a Pest control.

Inquiry→Treatment booked→Treatment→Follow-up visit→Recurring plan
PipelinePipelineInquiry4Treatment3Treatment2Follow-up1Recurring1

What it will not do

Not a setting you switch on and off. These are blocked when the Pest control answering is built; anything that touches them goes to a person instead of being answered.

  • It never names the species from a description.What is under the sink is identified on site, not from “small and brown” on the phone.
  • It never promises total eradication.It does not say “one visit and they’re gone”. It is not true, and it is where disputes start.
  • It never rules on product safety around a pet or a child.Which product, and where the cat should be during the visit, is the technician’s call. The AI books the pre-visit call and passes the question along.
  • It never describes what is inside a wall or a pipe.How far an infestation reaches behind the tiles is known only after it has been opened up.

This page is the list; the argument is on the other one. What kind of call comes in at night, what a missed one costs, and why a machine must not say certain things are written on the page this pack came from.