Intern
What you actually do
Persona tests are the job. High and low. Screenshot both contacts. If sales still needs ScoreApp to prep, the fields are wrong.
Library / Wire / ScoreApp is a door. GoHighLevel is the follow-up.
ScoreApp without write-in is a quiz you cannot sell from. Outcomes, answers, and score band must land on the GHL contact the same day, and high vs low band must not share a book-now email. This is the object map, not a click tour of ScoreApp themes.
ScoreApp without write-in is a quiz you cannot sell from. Outcomes, answers, and score band must land on the GHL contact the same day, and high vs low band must not share a book-now email. This is the object map, not a click tour of ScoreApp themes.
Map bands to jobs before you connect a webhook. A 90 who is a student and a 90 who is a buyer are not the same contact. Capture the disqualifier in the quiz — budget, role, timeline — and write those onto fields.
GHL is the system of record for the person. ScoreApp keeps the quiz design. If both keep a lead list, you will export weekly and call it ops.
High band creates an opportunity you can audit. Low band is not trash; it is a slower spine. If both bands share one workflow, the quiz is a vanity metric.
Identity is email. Test twice in one hour: high persona and low persona. If you merge contacts after, the match key is wrong.
Sales must see answers on the contact. Opening ScoreApp to 'prep the call' is how the CRM never becomes the prep.
Intern
Persona tests are the job. High and low. Screenshot both contacts. If sales still needs ScoreApp to prep, the fields are wrong.
Operator
The quiz is not the product. The split path is. Protect the high-band booking spine. Do not 'simplify' by merging workflows when volume is low.
CEO
A lead magnet that does not change CRM state is content. Until high-band write-in and a different low path exist, buying traffic to the quiz rents curiosity.
ScoreApp quiz, outcome/band, question answers, GHL contact, custom fields for score and disqualifiers, opportunity stage, tag offer/outcome, two workflows (high path vs slow proof).
Quiz complete → GHL contact created/updated; score + answers on named custom fields, not a note blob
High band → opportunity on Qualified quiz + workflow whose only job is a booked call
Low band → contact still written; Slow proof workflow; no calendar CTA in email one
Owner opens the contact → quiz context visible without ScoreApp or a CSV
List score ranges or outcomes. Each maps to a stage or to nurture-only (no opportunity). Name disqualifier questions. No book-now until low scores have a different path.
Why: Connecting first and sorting later is how everyone gets the same booking email.
Done when: A printed band → path table. Synonyms banned.
Every question that sales needs is a field: score, band, budget, role, timeline. Refuse a single 'quiz dump' note.
Why: You cannot filter or report on a paragraph. Discovery calls then start from zero.
Done when: High-score test contact shows answers on the record.
High: short sequence, calendar is the conversion. Low: proof, no fake urgency, sunset. Triggers listen to band field or outcome tag, not to 'quiz completed'.
Why: One trigger on complete is how you burn the low-intent list and cheapen the high-intent path.
Done when: Low-score test does not receive the high-score booking email.
High band: opportunity on Qualified quiz. Low band: contact + tag, no deal card unless you have a real slow pipeline with exit rules.
Why: A board full of students is how close rate looks broken and sales stops trusting GHL.
Done when: Pipeline count matches high-band completes, not total quiz takes.
After native or webhook write-in works, disable weekly spreadsheet imports. One writer.
Why: CSV is a second database with a delay. Duplicates and stale scores follow.
Done when: No import in the operating cadence. Completes appear in GHL the same day.
Take the quiz as a high-score buyer and as a low-score student. Both must create contacts. Open each record: score, band, and at least the disqualifier answers are fields. High score has an opportunity. Low score does not get the book-now email. If either fail, do not add questions to the quiz. Fix the map.
A prettier ScoreApp theme, more traffic to the quiz, or a second quiz until high vs low is a different journey in GHL. More completes into one workflow is a more expensive vanity metric.
Webhook creates a contact with email and a score in notes. One workflow on 'quiz completed' sends a Calendly link to everyone. Sales exports ScoreApp on Fridays. Duplicate contacts from email case. Qualified quiz is empty. That is a door with no room behind it.
Two completes in one hour, two personas. High: opportunity + book workflow. Low: contact + slow spine, no calendar in email one. Owner can prep the high call from GHL alone. If you merged contacts, fix identity before you launch ads to the quiz.
You paid for a filter, then threw it away. High-consideration buyers also notice when the next step ignores their answers. Sales will ghost the board.
Then GHL cannot route, suppress, or report. The quiz becomes a lead magnet your ops cannot run.
That is incomplete write-in. Add fields via webhook or Zap mapped to named custom fields. A number without answers is a fake discovery.
This week
This week: band table, field map, two test completes, CSV import turned off. No new quiz questions until write-in is true.
A full calendar and an empty pipeline is two databases.
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 ↗A lead sitting in Ads Manager is already someone else's booking.
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.