Write one observable beginning
Replace “new lead” with a concrete event such as a specified form submitted or an inbound call classified as missed. Note which contact identity and business line are involved. A contact record being created is not automatically the same event as a fresh service request. Include exclusions, such as test submissions, wrong numbers or a second signal belonging to an inquiry already being handled.
Define the allowed response
Write the proposed message and its purpose. Is it acknowledging receipt, asking for missing context or handing the request to a person? State the channel and the permission conditions that must hold. A phone number on a record is not by itself permission for every kind of contact. This worksheet is not legal advice; obtain appropriate guidance for the market and message category before activating a real sending path.
Name completion and failure
Specify what evidence would count as success. A workflow action executing is weaker than delivery, and delivery is weaker than a useful human response. Decide where the operator will see an exception if a message fails or nobody takes ownership. A good requirement includes a stopping event and a backup action, not just the happy path.
Turn the requirement into tests
For a fictional inquiry, describe one normal case, one repeated signal and one response that should stop further automation. Record expected and observed results separately. Use authorized test contacts and do not import real customer details merely to populate a demo. Once the requirement is clear, compare implementations and their total costs. If the answer is still “it depends,” list the exact unanswered condition rather than purchasing on a broad promise.
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.
- HighLevel workflow trigger catalog — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27
- Form Submitted workflow trigger — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27
- HighLevel workflow settings — Merchant documentation · help.gohighlevel.com · Merchant-controlled · checked 2026-09-27