Know what actually arrived.

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

Use the specific form as the entry condition and review the submitted fields before deciding what the response may say.

Do not assume an external website form triggers HighLevel’s native form event. Verify the integration event, field mapping and duplicate handling.

The built-in missed-call text-back feature can respond to every missed call. Decide whether that simple behavior fits before adding a more controlled workflow.

Choose a clear repeat-call policy and one response path. Do not rely on the built-in text-back feature to supply an undocumented cooldown.

A matching phone number is a routing clue, not proof of a person’s identity. Keep automatic replies free of sensitive request details.

Separate an immediate receipt message from the next staffed response. State real operating hours and a truthful next step.

Distinguish a new email entering the business from a customer replying to an existing message. Choose the documented event that actually represents the request.

Plan phone and message handling separately. HighLevel’s call forwarding does not by itself move incoming SMS to the person answering the phone.