What to include when you contact support

Four details that let us solve it in one reply instead of three.

We'd rather fix your problem in one reply than spend two days asking what it is. This is the short list of what makes that possible.

If you're in a hurry, the single most useful thing you can send is the form link plus one sentence about what you expected to happen.

Include these four things

  1. The form link, or the form name and the subaccount name. Most accounts have many forms, and almost every answer depends on which one.

  2. What you expected, and what actually happened. One sentence each is plenty. "I expected the lead in GoHighLevel and it isn't there" is enough to start.

  3. When it last worked, if it ever did. A setting that never worked and a setting that broke on Tuesday have completely different causes.

  4. A screenshot or a short Loom. If a specific lead is missing, include that one lead's email address — we don't need the rest of your list.

Check the log first

Open the form's Integration logs tab, or go to Connect → Integrations → Logs. Every delivery to GoHighLevel, Meta, or a webhook is listed there with the response we got back.

If a row failed, paste that row into your message. It's often the whole answer, and it's usually the difference between a five-minute reply and a day of guessing. See How to Use Integration Logs.

Try the chat first — really

The help center and the chat assistant between them cover most of what comes in, including every topic in this collection. Ask the question in full and you'll usually have an answer before a person would have read it.

info icon
Tip: Ask the thing you actually want to know. "Quick question" or "can I talk to
support" on its own just gets handed to a human who then has to ask what the question is,
which costs you the time you were trying to save.

When it's definitely not a setup question

Some things need an engineer and no article will fix them. Send the four items above and say plainly that you've already checked the setup, if any of these apply:

  • An integration disconnects repeatedly, not just once

  • A setting saves correctly and has no effect on the published form

  • Submissions appear in ROASForm and the delivery log shows no attempt at all

  • Something that worked for months stopped with no change on your side

Related articles

Did this answer your question?
😞
😐
😁