Conditions and stop on reply
Every If / Else condition and its negative, what record each one needs, the Has tag? block, the stages a Status changed trigger can fire on, and how Stop if they reply works.
An If / Else block splits a chain in two. Pick a condition under Check, give it a value under Is when it needs one, and connect the True and False exits to whatever should happen next. Every condition is listed twice in the dropdown, once plain and once as its negative, so you never need a separate "is not" operator.
Each condition reads a particular record. The editor shows which one under the picker ("needs a booking", "needs a proposal"). A lead that has no booking yet cannot answer a booking question, so that condition goes down the False path.
If / Else conditions
| Condition | Negative | Value under Is | Needs |
|---|---|---|---|
| Deal stage | Deal stage is not | A stage (see the list below) | a project |
| Production state | Production state is not | Not started, Running or Delivered | a project |
| Lead or client status | Lead or client status is not | Lead, Booked, Editing, Delivered or Archived | a lead or client |
| Booking total is over | Booking total is under | A dollar amount | a booking |
| They replied | They have not replied | None | a lead or client |
| Proposal was sent | Proposal was never sent | None | a proposal |
| Proposal was opened | Proposal was never opened | None | a proposal |
| Proposal was accepted | Proposal was not accepted | None | a proposal |
| Contract is signed | Contract is not signed | None | a booking |
| Deposit has landed | Deposit has not landed | None | a booking |
| Paid in full | Not paid in full | None | a booking |
| Balance still owed | Nothing left owing | None | a booking |
| Invoice is overdue | No invoice overdue | None | an invoice |
They replied
They replied counts replies since this automation last wrote to them. It looks for an incoming email from the couple that arrived after the automation's most recent email to them. It needs reply capture to be set up; without it Hailo never sees replies, and this condition is always false.
Deal stages
| Stage |
|---|
| Inquiry |
| Consult booked |
| Proposal sent |
| Contract signed |
| Deposit paid |
| Booked |
| In production |
| Delivered |
| Complete |
| Lost |
Has tag?
Has tag? is a shortcut for one common branch. Pick a Tag from the dropdown (it lists tags already on your leads) and connect the True and False exits. Tags live on leads only, so this block only means something before a lead converts to a client. See Automation gotchas.
Stages that fire a Status changed trigger
A Status changed trigger offers only the stages that Hailo actually moves a record into:
| Stage | What moves a record here |
|---|---|
| Proposal sent | Sending a proposal |
| Contract signed | The couple signing |
| Deposit paid | The deposit landing |
| Booked | The lead converting to a booking |
| In production | Editing starting |
| Delivered | The film being delivered |
| Lost | Marking the lead lost |
Inquiry, Consult booked and Complete are on the stage list for conditions, but nothing fires them, so they are not offered as triggers.
Stop if they reply
This switch belongs to the whole automation, not to one block. Open the ⋯ menu at the top right of the editor and turn on Stop if they reply. The note under it reads "Drops what is still scheduled."
With it on: when a couple replies to your email, every step of this automation that is still waiting for them (a follow-up after a Wait, for example) is dropped. Steps that already ran stay in the record. The reply has to reach Hailo, which means reply capture must be set up.
With it off: the chain keeps going even after they answer.
Turn Stop if they reply on for any follow-up sequence such as Proposal follow-ups. A couple who has already written back should not get a "checking in" nudge.
If it didn't work
- They replied is always false. Reply capture is not set up, or the couple wrote from an address that is not on their record. Both partners' addresses are matched. See Replies inside Hailo.
- A booking condition always goes False on new leads. The lead has no booking yet, so there is nothing to read. Use a lead condition (status, tag, replied) early in the journey and booking conditions after Booked.
- Stop if they reply did not stop the chain. The reply arrived before the automation had written to them, or it came from an unmatched address. Only replies after this automation's own email count.