BRD-004 Mandatory Lead Form Blocking
BRD – Mandatory Lead Form Blocking During Chat Flow¶
Product: MachineAvatars
Feature: Chat Input Blocking Until Lead Form Submission
1. Background & Problem Statement¶
- MachineAvatars allows chatbot creators to configure lead forms that appear during free-flow AI conversations.
- Currently, when a form is presented, the chat input (text and voice) remains active.
- This allows users to bypass the form, resulting in missed lead capture and broken conversation logic.
2. Objective¶
Ensure that when a lead form is presented within the chatbot, all chat inputs are paused until the form is submitted.
3. Scope¶
In-Scope
- Block text input when a lead form is displayed.
- Block voice input when a lead form is displayed.
- Resume chat interaction only after successful form submission.
- Apply this behavior to all forms configured via the chatbot “Form Setup”.
Out-of-Scope
- Optional or dismissible forms.
- Editing form structure during an active session.
- Backend lead validation workflows beyond submission.
4. User Personas¶
- End User: Required to complete the form to continue the conversation.
- Chatbot Creator / Admin: Configures mandatory lead forms in the chatbot setup.
¶
5. High-Level User Flow¶
- User engages in a chatbot conversation.
- Chatbot triggers a configured lead form.
- Chat text input and voice input are disabled.
- User fills and submits the form.
- Chat inputs are re-enabled.
- Conversation continues from the next logical step.
6. Functional Requirements¶
- FR-1: System shall disable chat text input when a lead form is displayed.
- FR-2: System shall disable chat voice input when a lead form is displayed.
- FR-3: Chat input shall remain disabled until the form is successfully submitted.
- FR-4: After submission, chat shall resume without resetting the session or context.
- FR-5: Form submission status shall be explicitly acknowledged by the system.
7. Constraints & Non-Functional Requirements¶
- Input blocking must be immediate and visually clear to the user.
- Form submission must not cause chat session reset.
- Blocking logic must work consistently across devices and browsers.
8. Acceptance Criteria¶
- Given a lead form is presented, when the user attempts to type, then the chat input is blocked.
- Given a lead form is presented, when the user attempts voice input, then voice input is blocked.
- Given the form is incomplete, when the user tries to continue chatting, then the system prevents it.
- Given the form is submitted successfully, when the user resumes interaction, then the chat continues normally.