Intern
What you actually do
Day one: the form converts, the CRM never sees the answers — map every field on a sheet. Run a test submit. Do not restyle the form. Mapping is the work. Hidden UTMs are fields, not folklore.
A pretty form sits on a page. Answers live in the form tool. The contact in GHL is a name and an email, or it does not exist. Sales asks 'what did they say?' and someone forwards a CSV.
Read it once, then stop negotiating with it. Forms that write in for agencies and services is a wiring job: map → hidden → test → dedupe. Objects, then edges, then one test conversion. You do not need a new tool to start. You need the first writer to land on one contact this week.
Agencies and services do not have a Forms that write in problem because they lack GoHighLevel. They have it because the form converts. The CRM never sees the answers.
Wire these objects first: Form fields, named GHL custom fields, hidden UTM fields, thank-you, contact identity (email), opportunity stage, test-submit ritual.
Then these edges, in order: Each visible question → one named custom field; no 'create new' duplicates · Hidden UTMs → source/medium/campaign on the contact after thank-you redirect · Submit → create or update one contact (email key); not two · Stage → right pipeline stage for that form's job
Done looks like a test you can repeat: Submit the live form with UTMs in the URL. Confirm one contact, fields filled, UTMs survived the thank-you, stage correct. Submit again with the same email; confirm update, not a duplicate. If answers are only in a notification email, fail.
Start here: Every field maps to a named CRM field
Agencies and services already have GoHighLevel. The leak is not a missing feature. The form converts. The CRM never sees the answers. Software did not cause it. A missing write-in did: the person exists in one tool and not in the pipeline.
Here is how you actually wire it. Name the objects: Form fields, named GHL custom fields, hidden UTM fields, thank-you, contact identity (email), opportunity stage, test-submit ritual. Then connect these edges, in order: Each visible question → one named custom field; no 'create new' duplicates · Hidden UTMs → source/medium/campaign on the contact after thank-you redirect · Submit → create or update one contact (email key); not two · Stage → right pipeline stage for that form's job. If you skip an edge, the next one is decoration. If you add a GoHighLevel feature first, you usually skip an edge without noticing.
Prove it with a test, not a screenshot. Submit the live form with UTMs in the URL. Confirm one contact, fields filled, UTMs survived the thank-you, stage correct. Submit again with the same email; confirm update, not a duplicate. If answers are only in a notification email, fail. How you know it worked on the board: Write-in is 100% (test submits land on a contact). If that number is a vibe, do not add traffic.
What to do this week, and only this week: Every field maps to a named CRM field An intern can run the objects page and one test conversion. A CEO should protect that from a second priority.
Intern
Day one: the form converts, the CRM never sees the answers — map every field on a sheet. Run a test submit. Do not restyle the form. Mapping is the work. Hidden UTMs are fields, not folklore.
Operator
You already feel the form converts. the crm never sees the answers. The form converts. The CRM never sees the answers. Protect one sequence for 90 days. The four moves are map → hidden → test → dedupe. The edges are Each visible question → one named custom field; no 'create new' duplicates then Hidden UTMs → source/medium/campaign on the contact after thank-you redirect. Every field on the form is a named field on the contact. Hidden UTMs survive. A test submit creates one contact on the right stage. If two submits create two contacts, you do not have write-in — you have a leak with a thank-you page.
CEO
This is a money leak, not a preference about tools. A pretty form sits on a page. Until write-in is a number you will defend, buying more traffic or more seats makes the leak more expensive. Refuse a second database: Each visible question → one named custom field; no 'create new' duplicates.
Before
Tuesday. Someone among agencies and services. The form converts. The CRM never sees the answers. GoHighLevel is open. A colleague asks where a person sits. The answer is a screenshot, a Slack thread, or “I think they’re interested.” The writer (form, calendar, shop, or phone) and the pipeline are two databases.
After
Same Tuesday, after write-in exists. Every field on the form is a named field on the contact. Hidden UTMs survive. A test submit creates one contact on the right stage. If two submits create two contacts, you do not have write-in — you have a leak with a thank-you page. Each visible question → one named custom field; no 'create new' duplicates The next move is written. That is the difference between a login and a system.
Keep it this plain. A person in agencies and services already paid for GoHighLevel. The form converts. The CRM never sees the answers. They add a page, a form, a calendar. None of it writes into a spec. By Friday the calendar has ghosts and the pipeline still looks like the snapshot.
The fix is not a better template. Every field on the form is a named field on the contact. Prove write-in: Submit the live form with UTMs in the URL. Confirm one contact, fields filled, UTMs survived the thank-you, stage correct. Submit again with the same email; confirm update, not a duplicate. If answers are only in a notification email, fail. This week is one move: Every field maps to a named CRM field If that feels too small, that is the point. Operators fail by starting at move four.
The leak
A pretty form sits on a page. Answers live in the form tool. The contact in GHL is a name and an email, or it does not exist. Sales asks 'what did they say?' and someone forwards a CSV.
The system
Every field on the form is a named field on the contact. Hidden UTMs survive. A test submit creates one contact on the right stage. If two submits create two contacts, you do not have write-in — you have a leak with a thank-you page.
Open the form and list every question. Next to each, write the GHL field it maps to. If a question has no field, either add the field or delete the question. Notes are not a mapping.
Submit as a stranger. Watch the contact. Stage, source, offer, and the answers must be visible without opening the form tool. Then submit again with the same email — one contact, updated. Two contacts is the failure.
Every field on the form is a named field on the contact. Hidden UTMs survive. A test submit creates one contact on the right stage. If two submits create two contacts, you do not have write-in — you have a leak with a thank-you page.
The form converts; the CRM never sees the answers when fields are unmapped, dumped into notes, or lost on a thank-you redirect. Every field maps to a named CRM field. A test submit creates or updates one contact. Hidden UTMs survive, and the contact lands on the right stage. That is the whole job — pretty forms with dead mapping are a lead leak with a designer.
Wire identity: email required unless you have a serious phone-only motion. Third-party forms (Typeform, native GHL, ScoreApp) all must hit the same fields. If you use a redirect, pass UTMs or write them before redirect. Workflows that fire on submit should not create a second contact. Notification emails to the owner are fine; they are not the database.
Two databases: form tool responses tab and GHL. The intern submits weekly after any form edit. They do not 'fix copy' until write-in is green. If GHL native forms and embedded HTML forms both exist for the same job, pick one. Two forms is two mappings, which is how one of them silently dies.
Form fields, named GHL custom fields, hidden UTM fields, thank-you, contact identity (email), opportunity stage, test-submit ritual.
Each visible question → one named custom field; no 'create new' duplicates
Hidden UTMs → source/medium/campaign on the contact after thank-you redirect
Submit → create or update one contact (email key); not two
Stage → right pipeline stage for that form's job
Submit the live form with UTMs in the URL. Confirm one contact, fields filled, UTMs survived the thank-you, stage correct. Submit again with the same email; confirm update, not a duplicate. If answers are only in a notification email, fail.
Day one: the form converts, the CRM never sees the answers — map every field on a sheet. Run a test submit. Do not restyle the form. Mapping is the work. Hidden UTMs are fields, not folklore.
Each form question → one named CRM field. Written on one page.
UTM source, medium, campaign, and page path as hidden fields.
Stranger submit creates one contact on the right stage.
Second submit updates the same contact. Never a twin.
On one line, for agencies and services: The form converts. The CRM never sees the answers. Add who gets hurt (calendar, cash, inbox, or reputation). If two people write different sentences, you do not agree yet — stop and agree.
Why: Teams skip this and jump into settings. Then every person is fixing a different problem with the same login.
Done when: One sentence. Shared. No adjectives required.
Form fields, named GHL custom fields, hidden UTM fields, thank-you, contact identity (email), opportunity stage, test-submit ritual.
Why: If objects aren't named, software invents a second database.
Done when: A stranger can list them.
Each form question → one named CRM field. Written on one page. Then wire: Each visible question → one named custom field; no 'create new' duplicates
Why: Agencies and services cannot skip this edge. The form converts; the CRM never sees the answers when fields are unmapped, dumped into notes, or lost on a thank-you redirect. If it is not true, GoHighLevel is already a second database.
Done when: Each visible question → one named custom field; no 'create new' duplicates is true on a test.
UTM source, medium, campaign, and page path as hidden fields. Then wire: Hidden UTMs → source/medium/campaign on the contact after thank-you redirect
Why: Agencies and services skip this and the leak returns as a private language. Wire identity: email required unless you have a serious phone-only motion. Spec tags, fields, and states have to be the same objects the next workflow will read.
Done when: Hidden UTMs → source/medium/campaign on the contact after thank-you redirect is true on a test.
Stranger submit creates one contact on the right stage. Then wire: Submit → create or update one contact (email key); not two
Why: Agencies and services feel this as the form converts. The CRM never sees the answers. Two databases: form tool responses tab and GHL.
Done when: Submit → create or update one contact (email key); not two is true on a test.
Submit the live form with UTMs in the URL. Confirm one contact, fields filled, UTMs survived the thank-you, stage correct. Submit again with the same email; confirm update, not a duplicate. If answers are only in a notification email, fail.
Why: Calendar full + pipeline empty means two databases.
Done when: One test conversion, one contact, right stage/state.
Every Monday, look at Write-in (Test submits land on a contact), then twin contacts (Same email, one record). Write one action or write “hold.” A dashboard with no action is theatre.
Why: What gets reviewed gets run. What only lives in a tool gets ignored the week someone is busy.
Done when: Three numbers. One owner. Fifteen minutes. Actions attach.
Every field maps to a named CRM field
Why: Operators fail by starting at move four. Interns fail by making a 40-item checklist. CEOs fail by adding a second priority. One proven write-in beats an elegant plan.
Done when: The move is true, or you can name the blocker in one sentence.
Form fields, named GHL custom fields, hidden UTM fields, thank-you, contact identity (email), opportunity stage, test-submit ritual.
If objects aren't named, software invents a second database.
The form converts. The CRM never sees the answers.
Each form question → one named CRM field. Written on one page. Then wire: Each visible question → one named custom field; no 'create new' duplicates
Agencies and services cannot skip this edge. The form converts; the CRM never sees the answers when fields are unmapped, dumped into notes, or lost on a thank-you redirect. If it is not true, GoHighLevel is already a second database.
On GoHighLevel, this means the data model matches how agencies and services actually work — not the snapshot demo. Edge: Hidden UTMs → source/medium/campaign on the contact after thank-you redirect
UTM source, medium, campaign, and page path as hidden fields. Then wire: Hidden UTMs → source/medium/campaign on the contact after thank-you redirect
Agencies and services skip this and the leak returns as a private language. Wire identity: email required unless you have a serious phone-only motion. Spec tags, fields, and states have to be the same objects the next workflow will read.
Every field on the form is a named field on the contact. Hidden UTMs survive. A test submit creates one contact on the right stage. If two submits create two contacts, you do not have write-in — you have a leak with a thank-you page.
Stranger submit creates one contact on the right stage. Then wire: Submit → create or update one contact (email key); not two
Agencies and services feel this as the form converts. The CRM never sees the answers. Two databases: form tool responses tab and GHL.
Every field maps to a named CRM field
Because the login already exists. A pretty form sits on a page. Answers live in the form tool. A new feature on a missing spec is a second database. Finish this edge first: Each visible question → one named custom field; no 'create new' duplicates.
Day one: the form converts, the CRM never sees the answers — map every field on a sheet. Run a test submit. Do not restyle the form. Mapping is the work. Hidden UTMs are fields, not folklore. Workflows on unnamed objects fire on folklore. Name contact (or profile), stage or state, and the writer (form, calendar, metric) before any on-switch.
A test conversion creates or updates one person, on the right stage or state, with the fields the next sequence will read. Submit the live form with UTMs in the URL. Confirm one contact, fields filled, UTMs survived the thank-you, stage correct. Submit again with the same email; confirm update, not a duplicate. If answers are only in a notification email, fail. If you merge after the test, identity is wrong — fix that, do not add a dedupe automation.
If it is only in someone's head, a new hire needs a story, reporting cannot be defended, and automations fire on folklore. Writing is how two people mean the same object on Monday.
Because setup was a project, not a review. UTMs (Or reporting is a campfire story) is how you stop the leak returning dressed as a new feature. If two CTAs compete, neither is a system. If the thank-you page does not change the contact, you paid for traffic that your ops cannot see. Build the spine first: capture, route, remind, recover no-shows. Then argue about copy.
More leads into a leak is a more expensive leak. Every field on the form is a named field on the contact. Hidden UTMs survive. A test submit creates one contact on the right stage. If two submits create two contacts, you do not have write-in — you have a leak with a thank-you page. Watch write-in before you buy traffic. If that number is folklore, acquisition is a vanity spend.
Then you only have time for the objects page and one test conversion. Every field maps to a named CRM field That is the intern version of strategy. Protect it from a second priority for seven days.
Skip this
Leaving objects unnamed because GoHighLevel is “set up”.
Do this
Form fields, named GHL custom fields, hidden UTM fields, thank-you, contact identity (email), opportunity stage, test-submit ritual.
Skip this
Building a workflow or flow before a writer lands on one contact.
Do this
Each visible question → one named custom field; no 'create new' duplicates
Skip this
Calling it done because a screenshot looks busy.
Do this
Submit the live form with UTMs in the URL. Confirm one contact, fields filled, UTMs survived the thank-you, stage correct. Submit again with the same email; confirm update, not a duplicate. If answers are only in a notification email, fail.
Skip this
Leaving “Dedupe” to chance.
Do this
Second submit updates the same contact. Never a twin.
The usual miss
Calling GoHighLevel “set up” because someone logged in and imported a snapshot.
Do this instead
Each form question → one named CRM field. Written on one page. Then prove write-in: Submit the live form with UTMs in the URL.
The usual miss
Building the workflow or flow before the writer (form, calendar, shop event) lands on one contact.
Do this instead
Connect Each visible question → one named custom field; no 'create new' duplicates first. Automations on a missing writer invent a second database.
The usual miss
Adding a page, form, flow, or campaign every time last week hurt.
Do this instead
Name which edge is missing. Fix that edge. Hurt is usually a skipped write-in, not a missing asset.
The usual miss
Reporting that nobody will defend in a meeting — screenshots, vanity opens, 'interested' counts.
Do this instead
Write-in: 100%. Test submits land on a contact. If you cannot say it out loud, it is not a scoreboard.
The usual miss
Hiring or retaining an agency to invent the spec while also running the calendar.
Do this instead
Hands on a known sequence are useful. Hands inside a missing spec pick the louder job (the calendar) and the leak stays.
Write-in
100%
Test submits land on a contact
Twin contacts
Zero
Same email, one record
UTMs
On contact
Or reporting is a campfire story
This week
Every field maps to a named CRM field
Every field maps to a named CRM field
A test submit creates or updates one contact
Hidden UTMs survive the thank-you
The contact lands on the right stage
Want the longer lesson, not the page for this niche? Write the tag spec on one page ↗
Working notes
The minimum CRM, pipeline, and nurture spec before you add more pages. Request the file. It arrives by email — not a public dump, not a drip of slogans.
Forms that write in does not split by niche and city. The wiring is the same: objects, edges, one test conversion. Read a connect map if two tools are already in the stack, or a vertical essay if the language needs to change.
A full calendar and an empty pipeline is two databases.
Read ↗A high score in a CSV is not a qualified opportunity.
Read ↗If the thank-you does not change the contact, the page was a brochure.
Read ↗One 'we miss you' postcard is not a system. Holes in the book you cannot name are the leak.
Read ↗A morning-after callback is a eulogy. Membership vs demand vs install are different jobs.
Read ↗Instagram is not a CRM. Mixing first-visit and lapse in one blast cheapens both.
Read ↗Email and WhatsApp stay open. A call is for installing the system.