IFFIELDServiceVALUEWind MitigationRULEis included in inspection
ANDFIELDService LocationVALUEOrlando OfficeRULEis
ANDFIELDContact TagVALUEInsurance ClientRULEis assigned to contact
We use cookies to ensure you get the best experience on our website. By continuing to use our site, you accept our use of cookies, privacy policy and terms of service.
Inspector Studio watches the moments that move your business. Each rule decides what to send, who should receive it, and exactly when it should go.
Illustrative editor based on the implemented trigger, condition, and multi-communication workflow.
Automations react to real changes across the platform. A booking moves, a report publishes, a payment fails, a lead leaves the request form, or a helpdesk thread escalates. That event becomes the beginning of the rule.
A published report does not have to produce the same message for every job. Add rules for the service, contact tags, inspection status, service location, or helpdesk context. The automation sends only when every condition matches.
Illustrative conditions based on the implemented rule and tag-inhibition controls.
Add up to ten communications to one automation. Each communication gets its own channel, recipients, timing, business-hours behavior, and message.
+ Seller Agent+ Insurance Agent+ Lead Inspector+ Custom email
Email the customer, text the customer, notify the agent, and alert the assigned inspector without maintaining four separate triggers.
Use minutes, hours, days, weeks, or months. Time-relative inspection triggers also support communication before the appointment.
Customers, co-customers, buyer and seller agents, insurance agents, lenders, inspectors, requesters, staff, thread participants, and selected system recipients.
Insert names, property data, services, fees, inspection times, balances, report links, portal links, booking details, airspace context, and company information.
Illustrative communication editor based on the implemented channel, timing, recipient, message, and variable controls.
A new organization begins with an automation library covering the everyday customer journey and the product workflows that depend on reliable communication. Edit the language, change the recipients, adjust the timing, or build your own.
Illustrative library using names and triggers from the implemented starter automation set.
The sending engine checks the recipient, consent, inspection settings, conditions, and timing before a message leaves. When it decides not to send, that decision is recorded.
Suppress automated notifications for a specific inspection without dismantling the company-wide rules.
SMS opt-outs and do-not-contact records remain hard stops, including when a team member manually sends an automation.
Keep an SMS from landing overnight. The message waits for the next eligible sending window.
Stop outreach for a contact or an agent’s agency without affecting unrelated automations.
Sign-in codes, invoice links, insurance access, and other required templates cannot be accidentally disabled.
The first-text opt-out notice is readable in the library but locked against edits or deactivation.
Illustrative inspection message history based on implemented automation states and delivery records.
The global automation log and each inspection’s Messages tab show the rule, recipient, channel, timing, content, and current delivery state. Suppressed and failed sends keep their reason.
Start with the complete library, shape it around the company, and keep every customer, agent, inspector, and office workflow moving from the same event system.
Get Early Access