A GoHighLevel workflow sends a follow-up message when a phone call starts. The call then fails before the caller explains their request, but the message claims the office has received all the details.
Choose the trigger from the outcome you actually need, not simply the earliest available call event.
Define what completed means for the action
A finished phone connection, completed intake, saved booking, and accepted transfer are different milestones. Decide which one authorises each follow-up.
| Follow-up purpose | Required evidence |
|---|---|
| Acknowledge saved request | Verified intake record |
| Confirm appointment | Confirmed scheduling outcome |
| Ask staff to call back | Owned callback request |
| General missed-call response | Approved rule for an unanswered interaction |
Review the client's supported triggers and actions in HighLevel's documentation and actual account configuration. Do not assume similarly named events carry the same payload or timing.
Separate call lifecycle from business completion
An external CRM or calendar write may finish after the phone session ends. A post-call trigger can therefore fire before the relevant result exists.
Use an explicit operation state or controlled delivery event when the follow-up depends on that write. If the result remains pending, the message should preserve that uncertainty rather than present an optimistic outcome.
The post-call reconciliation article covers the underlying lifecycle distinction.
Deduplicate and recheck before delivery
A repeated event should not send duplicate texts. Give the intended message a stable operation reference and retain its delivery state.
If a caller changes or withdraws the request before a queued message is sent, determine whether the message is still appropriate. A delayed worker should not describe an obsolete booking as active.
Do not solve this by adding an arbitrary wait and assuming everything finishes during that interval. A delay may reduce a race without establishing the required state.
Test timing, not only message wording
Use fictional calls that complete normally, disconnect early, leave a pending write, change the request, and arrive twice through event delivery. Simulate a notification provider timeout.
Check recipient, content, delivery count, and the state that authorised the message. A friendly text is still wrong when it describes work that never happened.
For a limited first release, staff-reviewed follow-up may be appropriate where the platform cannot expose the necessary verified outcome. Document that boundary instead of hiding it in a timing workaround.
Follow-up trigger questions
Does a call ending prove intake was saved?
No. Verify the business operation separately.
Can a fixed delay replace outcome checks?
It cannot guarantee completion or correct ordering.
What should an agency review?
Review trigger semantics, deduplication, and late corrections in the workflow acceptance tests.