Automated messages (Conditionals)

Conditionals are Inspector Studio's automation engine for customer communication. A Conditional is a rule that says "when X happens, send Y message." Once set up, Conditionals fire automatically without anyone on your team having to remember to send a follow-up.

What Conditionals can do

Conditionals send automated email or SMS messages to customers when booking events occur. Common uses include:

• Booking confirmation — send a confirmation email the moment a booking is created.

• Appointment reminder — send a reminder SMS 24 hours before the inspection.

• Report ready — notify the customer when their report is published.

• Signature request — prompt the customer to sign their agreement as soon as the booking is created.

• Reschedule notice — notify the customer when a booking's date or time changes.

• Follow-up — send a follow-up message a day after the report is delivered.

How Conditionals work

Each Conditional has three components:

1. Trigger — the event that causes the Conditional to fire. Examples: Booking Created, Booking Confirmed, Report Published, Inspector Assigned.

2. Timing — when to send the message relative to the trigger. You can send immediately, or set a delay (for example, 1 hour after the trigger, or 24 hours before the inspection date).

3. Message — the email or SMS to send. The message can include variables that are replaced with real data at send time, like the customer's name, inspection date, and address.

Creating a Conditional

1. Go to Settings → Conditionals (or Automations).

2. Click New Conditional.

3. Choose the Trigger event.

4. Set the Timing (immediately, or a delay).

5. Choose the Channel (email or SMS).

6. Write the Message. Use variables like {{customer_name}}, {{inspection_date}}, and {{property_address}} to personalize the message.

7. Click Save and toggle the Conditional On.

Variables

Variables are placeholders in the message body that get filled in with real data when the message is sent. Common variables include:

• {{customer_name}} — the primary contact's name.

• {{inspection_date}} — the scheduled inspection date.

• {{inspection_time}} — the scheduled start time.

• {{property_address}} — the inspection property address.

• {{report_link}} — a direct link to the published report (available after report is published).

• {{inspector_name}} — the assigned inspector's name.

The full list of available variables is shown in the message editor when you are writing a Conditional.

Turning Conditionals on and off

Each Conditional has an on/off toggle. Turning a Conditional off stops it from firing without deleting it. This is useful for pausing a message during a period when it does not apply without losing the configuration.

Testing a Conditional

Before relying on a Conditional in production, test it by creating a test booking and triggering the event. Verify that the message arrives with the correct content and variables filled in correctly.

Order of operations

If multiple Conditionals are triggered by the same event, they all fire. The order they fire in is the order they appear in the Conditionals list. You can drag to reorder if the sequence matters for your workflow.