Voiceflow Starter Chatbot Template

What this template covers

• This is a structural template, not a visual design. It maps every flow you need to build in Voiceflow.
• Copy the structure. Fill in your specific content. The conversation logic stays the same across most service businesses.
• Build each section as a separate Voiceflow flow, then connect them.
• Estimated build time with this template: 2 to 3 hours for a first-time Voiceflow user. Under 1 hour if you have built before.

FAQ Block: 10 question slots to fill

Create one intent per question. Add 3 to 5 phrasings per intent to handle the way real people type.

1. 1What services do you offer? -- Answer: [YOUR SERVICES IN 2 TO 3 SENTENCES]
2. 2What are your prices? -- Answer: [YOUR PRICING OR "Starting from X" OR "Depends on scope, book a call"]
3. 3How do I book / get started? -- Answer: [YOUR BOOKING PROCESS + CALENDLY LINK]
4. 4Where are you based / do you work online? -- Answer: [LOCATION + REMOTE AVAILABILITY]
5. 5How long does [your main service] take? -- Answer: [HONEST TIMELINE]
6. 6Do you offer a free consultation / trial / quote? -- Answer: [YES/NO + HOW TO GET IT]
7. 7What happens after I book / sign up? -- Answer: [YOUR ONBOARDING STEPS IN ORDER]
8. 8How do I cancel or reschedule? -- Answer: [YOUR CANCELLATION POLICY]
9. 9Do you work with [specific client type]? -- Answer: [WHO YOU WORK WITH BEST]
10. 10How do I contact someone directly? -- Answer: [EMAIL + CALENDLY LINK]

Lead Capture Flow

Wire these steps in order. Save each response to a named variable. Send all variables to your CRM or email via webhook at the end.

1. 1Opening message: "Hi there -- what brings you here today?" Use entity extraction to capture their name if they include it.
2. 2If name not captured: "Just so I can address you properly -- what is your name?"
3. 3"And what is the best email to reach you on?" -- save to variable: email
4. 4"What is the main thing you are trying to sort out?" -- save to variable: intent
5. 5"What is your business called?" -- save to variable: business_name
6. 6"Great. To summarise: [name], I will have someone follow up at [email] about [intent] for [business_name] within a few hours."
7. 7Confirmation + webhook: send name, email, intent, business_name to your CRM, Airtable, or email notification
8. 8Closing: "Is there anything else I can help with while you wait?"

Human Handoff Conditions

Build these as intent triggers that override normal flow and escalate immediately.

• User says any of: "speak to a human", "talk to someone", "call me", "real person", "agent"
• User expresses frustration: "this is useless", "not helpful", "forget it", "never mind"
• Fallback trigger fires 3 times in a row without a match
• User provides contact details and specifically asks for a callback
• User asks about pricing above a threshold you set (e.g. contracts over a certain value)

Handoff Message

When handoff triggers, show the user this message:

"I am flagging this for [Your Name] who will reach out at [email the user provided] within [X hours / your response time]. You will not need to explain the situation again -- I am passing the full conversation across.

Is there anything else you want me to include in the note?"

Then send an internal notification to yourself with: the full chat transcript, the user's contact details, and the reason for escalation.

Fallback Handling (the most important flow in the bot)

1. 1First unrecognised input: "I did not quite get that -- could you put it another way?"
2. 2Second unrecognised input: "I am not sure I have the right answer for that. Want me to flag this for [Name] directly?"
3. 3Third unrecognised input: Automatically trigger human handoff. Do not show a third "I do not understand" message.
4. 4Rule: every path in the bot ends with either an answer, a captured lead, or a human escalation. Dead ends destroy trust.