PYROX AIHome services / Project notes
A website-to-CRM inquiry workflow for home services
A submitted form is only the beginning. The business also needs a usable contact record and a clear way to handle the inquiry.
Website inquiry
CRM contact
Receipt & follow-up
The operational problem
Home-service inquiries need context: who contacted the business, how to reach them and what work they need. Leaving that information only in a notification makes follow-up harder to manage.
The verified project scope
The project documentation records a website form connected to a CRM and a receipt flow. The form-to-CRM path and booking emails were tested in September 2026. The business is based in Illinois. This is an inquiry-handling project, not a claim that software has already acquired new customers.
Why a contact record is not a qualified buyer
An imported contact, an inquiry and a confirmed customer describe different stages. The workflow must preserve that distinction. A successful technical test proves that data moved; it does not prove purchase intent or a completed sale.
Separate the integrations
Forms, calendars, email and phone messaging have different dependencies. A working form does not prove that every calendar slot is correct or that SMS is approved. Each channel needs its own configuration and delivery checks.
Reporting the boundary honestly
The published case covers the verified inquiry workflow. It does not claim a specific number of customers acquired, guaranteed booking availability or measured hours saved. The older URL is retained so existing links continue to work.