Create the lead record
Save the submitted answers and source context together in Spacebrain’s built-in CRM.
Lead generation use case01 02 03 04 01 02 03 01 02 03 01 02 03
Turn form submissions into useful conversations.
Spacebrain carries form answers and source context into qualification, follow-up, routing, and booking—so the next response starts with what the lead already told you.
The problem
The click was expensive. The handoff should carry its context.
When a form lands in an inbox or moves between tools, the person replying has to reconstruct what the lead wanted. Spacebrain keeps the campaign, answers, qualification signals, and next action on one lead record.
Continue from the form
Use approved questions to clarify fit, timing, and what should happen next.
Qualify and route
Send the lead to the right person or workflow based on the answers already collected.
Offer the next step
Continue the conversation or offer a booking path with the full lead context attached.
What this use case connects
- Forms
- Qualification
- Follow-up
- Built-in CRM
- Routing
- Booking
Make the first reply feel connected to the form that started it.
Start with one form and one follow-up path, then refine the questions, routing, and booking logic as your process becomes clearer.
Start for free →FORM FOLLOW-UP
Use it where form leads go quiet after submit.
This workflow fits teams that collect useful information in a form but lose context or momentum when the response moves into an inbox, spreadsheet, or separate tool.
Campaign and source matter
The person replying needs to know which form, offer, or campaign created the lead.
The form already answered key questions
A generic first reply wastes the information the lead just provided.
Different answers need different paths
Fit, timing, location, request type, or application answers can change who should respond next.
WORKFLOW
Continue the conversation from the form.
The first response should use what the lead already told you, ask only the next useful question, and preserve the full handoff in one record.
- 01
Create the lead record
Save the submitted answers, source, campaign context, and contact details together.
- 02
Acknowledge the request
Respond from the form context instead of restarting with a generic introduction.
- 03
Ask the next question
Clarify the approved detail that determines fit, timing, urgency, or ownership.
- 04
Route or offer booking
Use the answers to select the right person, workflow, or calendar.
- 05
Keep follow-up attached
Record the conversation, status, owner, and booking state in Spacebrain’s built-in CRM.
BEFORE YOU LAUNCH
Define what happens after submit.
A form workflow stays useful when every important answer has an obvious operational meaning. Decide how those answers should change the next step.
What Spacebrain needs to know
- Form and campaign source
- Fields that determine fit or priority
- Questions that still need an answer
- Owners, teams, and calendars
- When a person should review the lead
- Follow-up channels and stop conditions
Example handoff map
The lead meets the basic criteria
Continue qualification or offer the approved booking path.
The answer points to a specialist
Route the lead and full form context to the correct owner.
A key answer is unclear
Ask the next approved question before sending the lead elsewhere.
The lead does not respond immediately
Continue the approved follow-up from the original form context.
THE HANDOFF
Let the next person see the whole conversation.
The handoff should explain where the lead came from, what they asked for, and what the workflow has already done.
Source and answers
The form, campaign, submitted fields, and any clarification collected afterward.
Fit and ownership
The current qualification state, assigned person or team, and why that route was chosen.
Conversation and next step
Messages already sent, replies received, booking state, and the action that remains.
Start small. Start with one high-intent form. Map each important field to a question, route, or booking decision before adding more sources.
FIELD GUIDE
A form is the beginning of a conversation, not a finished handoff.
A submitted form may contain the most useful context a lead gives you: the offer that brought them in, the problem they named, the service they selected, and the constraints that shape the next step. Treating it as a notification wastes that context. Treating it as a working brief makes the reply more relevant from the first line.
Source changes the meaning of an answer.
A contact who reached a pricing form, a consultation form, a campaign-specific application, or a referral page may use the same words for different reasons. Keep the page, campaign, offer, and form name connected to the lead record. The person responding should know what the lead was responding to before they choose a question, owner, or booking path.
Every field should earn an operational role.
For each form field, be able to say what a given answer changes. It may determine fit, priority, specialization, location, ownership, or a follow-up question. If an answer does not change the next decision, reconsider whether it belongs on the form. A shorter, purposeful intake is usually more useful than a form that collects information no one acts on.
Do not make the lead repeat the first conversation.
The fastest way to make a response feel generic is to ignore what the person just submitted. The reply does not need to paraphrase every answer. It should carry forward the important parts, acknowledge the purpose of the inquiry, and ask only for the detail that determines what happens next.
DECISION DESIGN
Map answers to decisions before you automate the reply.
The form, the follow-up, and the handoff should behave like one sequence. Begin with the operational decisions the team needs to make; then decide which fields, questions, messages, and owners support those decisions.
- 01
Identify the entry point precisely.
Record the form itself, the page where it appeared, the campaign or referral source when available, and the offer or call to action that prompted it. These details give the team a starting hypothesis about intent. They are not a substitute for qualification, but they prevent a responder from treating every submission as if it came from the same conversation.
- 02
Mark the answers that change the route.
Choose the fields that decide whether a lead should continue, be reviewed, be assigned to a specialist, be offered a booking path, or be handled outside the normal process. This might include service type, company size, location, timing, requested scope, or an application answer. Keep the rule visible enough that a human can understand why a particular route was selected.
- 03
Ask for the next useful piece of context.
A strong follow-up does not restart discovery. It asks the one approved question that resolves the next decision. When the submitted information is already enough, move to the relevant handoff or booking option. When it is not enough, ask clearly and explain the purpose of the question in plain language.
- 04
Assign a person or queue before momentum disappears.
Every path needs a visible owner. The owner might be a team, a specialist, a review queue, or the next available person under the business’s rules. What matters is that the assignment is explicit on the record and that there is a fallback when the first owner is unavailable. A response sequence without ownership is simply an inbox with more steps.
- 05
Stop the sequence when a person or decision takes over.
Define the events that should end or change automated follow-up: an accepted booking, a completed handoff, an explicit decline, a review status, an out-of-scope request, or a request to stop communication. The goal is not to keep sending messages. The goal is to make the next responsible action visible and appropriate.
THE WORKING BRIEF
A lead record should preserve why this person submitted this form.
When someone opens a record, they should be able to see the origin, the submitted context, the qualification state, the conversation so far, and the pending decision. That is what turns form capture into a connected lead-management process.
What to retain with the submission
- Form name, page or offer context, and the campaign or referring source when it is available.
- The submitted answers as the lead gave them, including any answer that affects qualification or routing.
- The current interpretation of fit or priority, with a clear status rather than a vague label.
- The owner or queue responsible for the next decision and the reason for that handoff.
- Messages, replies, booked events, and notes that allow the next person to continue the thread.
Decisions to define with the team
Which fields are informational and which are decisive?
Separate context that helps a conversation from answers that determine a route. This distinction prevents the workflow from pretending that every field is a scoring signal.
What should happen when a key field is empty?
Decide whether the workflow asks a follow-up question, sends the lead to review, or allows a normal route. Empty information is a state to design for, not an edge case to discover after launch.
Who may override the route?
Give the team a clear way to correct a misrouted lead without losing the original context. A sensible exception path is more valuable than an inflexible rule.
When should the customer be offered a calendar?
Make booking conditional on the information the business actually needs. Some submissions are ready for a calendar; others need clarification or a specialist’s review first.
THE FIRST RESPONSE
The acknowledgment should continue the conversation, not flatten it.
The best follow-up language is usually specific, short, and honest about the next step. It recognizes the person’s stated need and makes the transition to the appropriate owner, question, or calendar easy to understand.
Use the submitted context sparingly and well.
Refer to the request, service, goal, or timing detail that tells the lead you understood why they reached out. Do not mirror every field back to them or create the impression that a form was read by a script. The purpose is continuity: the reply should feel like the next part of the same conversation.
Ask one question with a visible purpose.
If a response requires more information, ask for the detail that changes the next route. Explain it simply: the question is needed to connect the person with the correct team, understand the request, or choose the appropriate next step. Open-ended questions can be useful, but they should not replace a decision the business already knows it must make.
Describe the path, not an invented outcome.
Say whether the request is being reviewed, assigned, continued, or offered a relevant booking option. Avoid exact time, availability, price, or service commitments unless they are defined and approved by the business. Clear process language gives the customer a useful expectation without promising a result the workflow cannot verify.
Practical starting point. Start with one form where the team already knows what a good handoff looks like. Map the meaningful fields to a decision, test submissions with complete and incomplete answers, and review the record with the person who receives the lead. The goal is not a clever sequence. It is a response path the team can explain and improve.
OPERATING REVIEW
Inspect where form context disappears before you add more automation.
A form workflow often fails quietly. The lead record exists, a reply may be sent, and a task may be created—yet the person taking over cannot tell what was offered, what was answered, or why the route was chosen. Review the actual sequence rather than assuming the configuration tells the whole story.
Read a sample submission end to end
- Can a teammate identify the form, offer, and source without hunting through another system?
- Can they see which answers mattered to the qualification or routing decision?
- Does the first response acknowledge the submitted context rather than restart the exchange?
- Is the next owner explicit, with a visible status and an action that can be completed?
- Can the final state distinguish a booking, review, disqualification, handoff, or closed conversation?
Use the review to improve the intake
Remove fields that never affect a decision.
More form data is not automatically better. A field that nobody uses can add effort for the lead and clutter for the person who follows up.
Make repeated human corrections explicit.
If a teammate repeatedly changes an owner, asks the same question, or corrects the same status, that is evidence that a rule needs refinement.
Check the stop conditions.
Ensure that a booking, review, resolved request, or explicit opt-out changes the sequence as intended. The right message at the wrong state is still a poor customer experience.
Keep language aligned with the offer.
Review replies alongside the page, campaign, or sales process that created the form. The next message should not contradict the expectation set before submit.
COMMON QUESTIONS
Questions teams should answer before they connect another form.
Should every form lead be asked to book immediately?
No. Offer a booking path when the form supplies the information the business needs and the lead is on the right route. When a key detail is missing or a specialist must review the request, make that next step clear instead. A calendar is a tool in the workflow, not a substitute for qualification.
How much should the form ask before submit?
Ask enough to make the next decision, then let the follow-up continue the conversation. The right amount depends on the offer and the business. A useful test is simple: for each question, can the team point to the route, owner, priority, or next question it changes?
What makes an internal handoff trustworthy?
The receiving person can see the source, the submitted context, the messages already exchanged, the current status, and the expected next action. They should not need to ask the lead to repeat their goal or guess why the record reached their queue.
INTAKE DISCIPLINE
The standard is simple: every answer should have somewhere useful to go.
When form fields, follow-up questions, routing rules, and record ownership are designed as one system, the business can make better use of the context it already collects. That is a stronger foundation than adding more tools around a weak handoff.
Capture the context.
Keep the source, form, offer, contact information, and meaningful answers together. The record should preserve what the person told the business at the moment they chose to submit.
Turn it into an owned decision.
Use approved rules to choose a question, owner, review path, or booking option. A clear next action is more useful than a generic “new lead” label.
Keep the thread connected.
Store the reply, follow-up, handoff, and outcome on the same lead record. The next person should inherit the conversation, not just a contact record.
SEE THE PLANS
Choose the plan behind your first workflow.
Compare plan options, included capabilities, and usage before you build.
See pricingONE CONNECTED WORKFLOW
- Capture
- Qualify
- Follow up
- Book
- Built-in CRM
Start with calls, forms, or a client workflow. Keep the next step connected.
