What it does
Displays a contact form UI to collect visitor information through a structured form interface.
When to use it
ONLY when explicitly needed. For most conversational lead capture, prefer using
@ask_question steps.Configuration
Available in tool settings:
Fields to Collect
- Name (combined or split into first/last)
- Email address
- Phone number
- Consent checkbox
- Custom question (text input or dropdown)
Email Validation
- Option to require work email (blocks free providers like Gmail, Yahoo)
Form Behavior
- Mandatory vs optional: Force form before continuing or make it optional
- Display timing: Show after X messages or every Y messages
Title
- Dynamic: AI-generated based on context (recommended)
- Static: Custom text you provide
Syntax
@show_contact_form
Example
Basic usage:
1. @recommend relevant information about our services 2. @show_contact_form 3. @mention_specifically: "Thank you! Someone from our team will reach out shortly." 4. @stop_playbook
Tips
- Prefer conversational
@ask_questionsteps for better user experience
- Use forms when you need to collect multiple fields simultaneously
- Configure required fields to match your lead qualification needs
- Always follow up with a confirmation message
- Test form completion rates and adjust fields if needed
Configuration Best Practices
For Lead Capture:
- Enable: name, email
- Optional: phone, company
- Consider: work email validation to reduce spam
For Support:
- Enable: name, email, issue description (custom question)
- Consider: mandatory form to ensure contact info
For Enterprise:
- Enable: name, email, phone, company
- Add custom question: "Number of employees" or "Annual revenue"
- Require work email
Learn More
- Getting Started with Playbooks - Overview and all tools
- Core Concepts & Structure - Understanding playbook structure
- Complete Playbook Examples - See forms in action
- Best Practices & Tips - When to use forms vs questions