Intern
What you actually do
One complete, one partial, UTM, identity. Watch where humans work the lead. GHL must win.
Library / Wire / Typeform is allowed only if it writes the spec
Typeform wins on UX. It loses when answers land in a Typeform inbox and GHL gets an email notification. If you keep Typeform, every question that sales needs is a GHL field the same hour, identity is email, and you have a reason native GHL forms could not do the job. Otherwise use GHL forms and stop paying for a vault.
Typeform wins on UX. It loses when answers land in a Typeform inbox and GHL gets an email notification. If you keep Typeform, every question that sales needs is a GHL field the same hour, identity is email, and you have a reason native GHL forms could not do the job. Otherwise use GHL forms and stop paying for a vault.
Ask why Typeform exists. Logic jumps and better UX can be a real gap. 'We like the look' is not a gap if GHL forms can write the spec.
Webhooks must map answers to named fields. A Zap that dumps the whole JSON into a note is the notes leak again.
Hidden fields in Typeform need the same JS or native hidden UTM pattern as any form. Pretty forms drop UTMs just as well as ugly ones.
Partials: Typeform will tempt you to capture abandoners. If you create contacts on question two, you need a different spine and consent story. If you do not, do not pretend you have those leads.
Turn off 'new response' emails as the operating process. They train a shadow inbox.
Intern
One complete, one partial, UTM, identity. Watch where humans work the lead. GHL must win.
Operator
Typeform is packaging. GHL is the spec. If the gap vanishes, migrate. Do not collect two quiz tools.
CEO
A premium form that does not change CRM state is branding. Write-in is the gate. Extra questions are not insight until they are fields.
Typeform form, hidden UTMs, answers, GHL contact, custom fields, webhook/native, Typeform email notifications (usually kill), opportunity rules, duplicate identity.
Typeform complete → GHL contact + fields mapped; Typeform is not the lead list
Hidden UTMs in Typeform → GHL source fields
Partial Typeform (if used) → either a contact with incomplete flag or no contact — write the rule
Notification email to a human is a copy, not write-in
Gap: logic, embedding, research length. If the sentence is taste, migrate to GHL forms.
Why: Every extra form tool is a writer to keep honest.
Done when: Keep or kill decided. If kill, a migration date. If keep, the gap is on the spec.
Question → GHL field. Disqualifiers as fields. Score or branch result as a field if logic is the point.
Why: Otherwise sales opens Typeform to prep, and GHL is a notification.
Done when: Test complete: answers on the GHL contact, not in a note.
Hidden fields, email match, update vs create rule. Same as GHL forms.
Why: Typeform does not get a pass on source truth.
Done when: Test URL with UTMs writes GHL source.
If partials create contacts: incomplete tag, different spine, consent. If not: no contact until complete.
Why: Silent partial contacts are how you spam people who bounced on question one.
Done when: A partial test behaves as written. No surprise contacts.
GHL is the list. Typeform responses are a log. Kill team notification emails or send them to a dead archive.
Why: Humans will work the email, not the CRM.
Done when: A week with no one 'working Typeform'. All follow-up from GHL.
Complete the Typeform with UTMs. Confirm GHL fields. Confirm no duplicate if the email already existed. Partial test per the rule. Ask the team where they worked leads last week — if Typeform email, that inbox is the leak.
Typeform Plus, a second Typeform, or a researcher building more questions until write-in is true. Longer forms into a vault make sales blinder.
Typeform notifications to sales@ . GHL integration was 'on' but mapped three fields. UTMs missing. Partials creating ghosts. Team lives in Typeform results. That is a survey product, not a CRM writer.
Complete + UTM + field map + identity update. Partial behavior matches spec. Follow-up happens in GHL for a week. Gap sentence still true or migrate.
Not if write-in is worse. Premium is a contact sales can run. A pretty dead-end is still a dead-end.
Yes if complete apps write GHL with disqualifiers and route fast. Application is a job. Typeform is optional packaging.
Two quiz tools is how you split brains. Pick one door per job.
This week
This week: keep/kill, field map, UTM test, partial rule, notification emails demoted. No new Typeform.
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 ↗If paid lives in Stripe and the opportunity is still open, reporting is theatre.
Read ↗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.
Email and WhatsApp stay open. A call is for installing the system — not for a tour of tools.