Flow Preview
Lead IntakeLead Company FitLead Decision ContextSales HandoffLead Nurture
Overview
Capture a sales inquiry, collect practical qualification data, route sales-ready leads to a human, and give early-stage leads a useful nurture path.
Who It's For
The user wants an inbound sales or demo-request bot that qualifies prospects before sales handoff.
Setup Requirements
- What ICP or segment should count as sales-ready?
- Should sales-ready leads start a human conversation, be tagged, or be sent to a CRM?
- Which resource should early-stage leads receive?
- To alert your sales team about qualified leads, tag each sales rep’s contact with the sales tag (open Contacts, pick the contact, add the sales tag). The Notify sales team action then messages every contact carrying that tag. Remove it if you rely only on the live sales handoff.
Node Breakdown
- Start or main menu
- Ask whether the prospect wants sales, demo, or pricing help
- Capture name with reply validation
- Capture email with EMAIL reply validation
- Capture company name with reply validation
- Ask company size using buttons
- Ask whether the user is a decision maker, evaluator, or researcher using buttons
- Capture the main business problem or use case
- Ask buying timeline using buttons
- Branch sales-ready leads to tag and human handoff
- Branch early-stage leads to resources and a later follow-up path
Details
Good to know
- Use reply capture for user-entered name, email, company, and use case so the generated flow creates real triggers where input is expected.
- Use button choices for company size, role, and timeline because leads are more likely to answer sensitive or business context questions when ranges are offered.
- Use ADD_TAG for simple in-platform segmentation when an existing or new contact tag is enough.
- Use START_CONVERSATION for sales handoff when the workspace has human sales support.
- Use HTTP_REQUEST only if the user explicitly approves a CRM/API integration. Otherwise, keep the handoff complete with tags and SET_VARIABLE placeholders.
Keep in mind
- Do not ask for highly sensitive details like exact revenue or budget unless the user explicitly requests it; use ranges or softer intent signals.
- Do not create CRM-specific actions unless a module exists or HTTP fallback is approved.
- Do not leave free-form questions without messageReplyConfig and expectedMessageType.
- Do not dead-end early-stage leads; give them a resource or a way to contact sales later.
