Survey Creates Opportunity: From Answer to Pipeline Record

A survey that only creates a contact has captured a person; one that creates an opportunity has captured a piece of work.

Survey creates opportunity: turning an answer into a pipeline record

A survey that only creates a contact has captured a person. A survey that creates an opportunity has captured a piece of work with a value, a stage and an owner — something that appears in a forecast and gets chased when it goes quiet. The difference is a few settings, and it decides whether the answers a visitor gave become part of how the business is run or a row in a list nobody opens.

The catch is that this is easy to overdo. Creating an opportunity for every submission fills the pipeline with records that were never going to become work, and a pipeline nobody trusts is worse than one that is merely incomplete.

Contact, opportunity, and why both exist

A returning customer enquiring about a second job is one contact and two opportunities. Collapsing that into a single record loses the ability to say anything useful about either, which is the practical argument for creating opportunities at all rather than working from a contact list.

Decide which submissions deserve one

The rule that holds up in practice: create an opportunity when the answers describe a specific thing the business could be paid for. A quote request, a service enquiry with a location and a timeframe, an application for a programme. Not a newsletter signup, not a content download, and not a general enquiry with no subject.

Where a survey serves both purposes, the honest mechanism is a branch rather than a filter after the fact. skip logic and branching paths lets the survey ask the qualifying question early and route accordingly, and disqualifying a lead in the survey handles the case where the answer means no work exists. Both are better than creating everything and tidying up later, because the tidying never happens.

What to write into the record at creation

An opportunity created with a name and nothing else is a task for whoever picks it up. Map the survey answers into the fields the team will actually use, and decide each one deliberately:

• Pipeline and stage. A new submission usually enters at the first stage. If your survey qualifies hard enough that it can enter later, say so explicitly — pipeline stages and exit criteria is where that decision belongs.
• Value. Where the answers imply a range, write the midpoint rather than nothing, and mark it as an estimate. An empty value makes the whole forecast useless; an honest estimate makes it approximate, which is different.
• Owner. Assign at creation if the routing is knowable from the answers. An unassigned record waits for someone to notice it.
• Source. Which survey, which campaign, which step. This is what makes how to measure pipeline conversion answerable later.
• The answers themselves. Keep them on the record, not only in the submission log, so the person calling can see what was said.

Naming the opportunity so a list is readable

A pipeline where every record is called by the contact’s name tells you nothing at a glance. Build the name from the answers — the service requested and the location, say, or the plan and the seat count. Whoever opens the pipeline on a Monday morning should be able to read the list and know what each row is without opening any of them.

Scoring, and when it earns its complexity

Where a survey has several qualifying answers, a score can be more useful than a branch, because it combines signals rather than testing them one at a time. arithmetic on a lead score is the mechanism, and scoring and branching in a quiz funnel is the same idea applied to a whole funnel. Two cautions are worth stating.

First, a score is only as good as the weights, and the weights are usually guesses at the start. Treat the first version as a hypothesis and check it against outcomes after a month rather than trusting it immediately. Second, a score is a sorting aid, not a verdict — classifying leads by evidence is about classifying by evidence, and a number derived from self-reported answers is weaker evidence than a booked call.

What has to happen next, or the record rots

Creating the opportunity is the start of an obligation. A record that sits at the first stage for three weeks is worse than no record, because it looks like coverage while nothing is happening. a conversation sla sets the expectation for the first response, and a stale opportunity trigger catches the ones that quietly stop moving.

Make the immediate acknowledgement part of the same automation. The visitor who just answered eleven questions should see the thank-you step confirming what happens next, and the follow-up should reference something they actually said. The routing and suppression rules in routing and suppression matter here too — an opportunity created for someone already in an active sequence should not start a second one.

Where the mapping usually breaks

1. A dropdown’s stored value differs from its label, so the mapped field receives a code rather than the readable answer. dropdown options, values and routing is where this is decided.
2. A conditional question that was skipped maps as empty and overwrites a field that already had something in it. conditional fields that behave is the same behaviour seen from the form side.
3. Two surveys write to one custom field with different vocabularies, so the pipeline filters stop matching.
4. A duplicate submission creates a second opportunity for the same job, usually because someone refreshed the confirmation page.
5. The value field is left blank because the answers did not include a budget question, and the forecast silently undercounts.

Test by submitting the survey yourself along each branch, then opening the opportunity rather than the contact. Most of these are visible in ten seconds from the record and invisible from the submission log.

Frequently Asked Questions

What is the difference between a contact and an opportunity?

A contact is a person and there is one per person. An opportunity is a specific potential piece of work with a value, a stage and an owner, and one person can have several over time. A returning customer enquiring about a second job is one contact and two opportunities.

Should every survey submission create an opportunity?

No. Create one when the answers describe something the business could be paid for — a quote request, a service enquiry with a timeframe, an application. A newsletter signup or a content download should create a contact only, or the pipeline fills with records that were never work.

What should go into the opportunity when it is created?

Pipeline and stage, an owner if the routing is knowable, a value even if it is an honest estimate, the source so conversion can be measured later, and the answers themselves so whoever calls can see what was said without opening the submission log.

How should I name opportunities created from a survey?

From the answers rather than from the contact. The service requested plus the location, or the plan plus the seat count, makes a pipeline list readable at a glance. A list where every row is a person’s name requires opening each record to know what it is.

Is lead scoring worth adding to a survey?

It is when several answers each carry some signal and no single one decides. Treat the first set of weights as a hypothesis and check it against real outcomes after a month, and remember a score built from self-reported answers is weaker evidence than a booked call.

Why is my mapped field showing a code instead of the answer?

Because the dropdown’s stored value differs from the label shown to the visitor, and the mapping carries the value. Either set the stored values to readable text or map deliberately, and check by submitting the survey yourself and opening the record afterwards.

How do I stop duplicate opportunities from one enquiry?

Most duplicates come from a resubmitted form, often a refreshed confirmation page. Add a check for an open opportunity on the same contact within a short window before creating a new one, and make the confirmation step a distinct page so refreshing does not resend.

We build your GoHighLevel account for you

CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.

• Setup (one-time)$850
• Ongoing (per month)$38.80

Get my free setup quote

No obligation quote · reply within 1 business day

This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.