Independent research · Source-linked guidance

Independent HighLevel affiliate publication. We may earn a commission if you buy through links on this page, at no extra cost to you.

Home / Respond / Choose the event that should start the response
Practical guide

Choose the event that should start the response

Last materially reviewed 2026-09-27

Quick answerSelect a trigger from an observed event and narrow its filters. A broad contact change is not automatically a new inquiry.
What to know

Translate the business sentence

“Reply when somebody asks for help” is not yet a technical trigger. Specify which form, business line, message channel or other documented event indicates that request. Write the details that distinguish it from newsletter activity, an internal correction or a message already being handled. This translation is the point where many apparently simple automations become ambiguous. Resolve it before composing the response.

What to know

Prefer a narrow beginning

Use only the event and filters needed by the requirement. Adding several broad triggers may appear to improve coverage while creating multiple enrollments for one inquiry. A changed contact field can be an update to old information rather than new intent. Keep a list of included and excluded events so another operator can review the choice without reverse-engineering the workflow.

What to know

Document what is not covered

A form trigger does not establish coverage of calls or new emails. A customer-reply trigger does not establish coverage of every incoming message type. These gaps are not necessarily defects: they can be deliberate scope limits. Show an operator how to handle excluded paths manually until they have their own verified requirement. Do not conceal an unknown channel behind a generic claim that all leads are automated.

What to know

Test one near miss

Alongside the intended event, test a similar event that should not start the workflow. For example, use the permitted test version of the inquiry form and a separate form that serves another purpose. Record both results. A correct positive test and an incorrect negative test mean the entry rule is still too broad. Stop there and repair the filter before adding more messages. Give the trigger a descriptive name tied to its event and exclusions, not merely “new lead automation.”

Continue when useful

Next: Map the inquiry before writing the response

Map the actual incoming event, not just a contact label. Then separate acknowledgement, assignment, response and evidence.

Open Map the inquiry before writing the response →
Keep exploring

Related guides

Map the inquiry before writing the responseMap the actual incoming event, not just a contact label. Then separate acknowledgement, assignment, response and evidence.Re-entry and repeated signals are not the same problemDecide whether another signal should restart, update or remain outside the workflow. Re-entry settings alone do not define a complete duplicate-response policy.New inbound email is not always a reply eventDistinguish a new email entering the business from a customer replying to an existing message. Choose the documented event that actually represents the request.

Sources used for this page

These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.

  1. HighLevel workflow trigger catalog — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27
  2. Form Submitted workflow trigger — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27
  3. Customer Replied trigger — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27