LEAD GENERATION CHATBOT: WEBSITE TEST CHECKLIST By Roman Mohren | FullSession | 19 October 2026 Companion to "Lead generation chatbots: from a buying question to a demo request" Purpose: test the full buying journey on your own website before launch: buying question, useful answer, buyer-chosen next step, demo request with required confirmation, receipt, and the handoff your sales team receives. This is a blank test record, not a product test result. Every observation field is empty on purpose. Expected behavior is not an observation: fill a field only after you have seen the result, and record where the evidence is kept. Use test identities, a reserved test email domain (for example example.com) and a test destination for form submissions, so real sales queues are not polluted. Website/pages tested: ____________________ Chatbot/configuration: ____________ Tester and date: _________________________ Demo form used: ____________________ Approved sources connected: ________________________________________________ Hours and away message configured: _________________________________________ PART 1. YOUR QUALIFIED-REQUEST DEFINITION (fill in before launch) A qualified request is your team's decision, made in your own review process. Apply the same definition to chat-assisted and form-only requests. Fit (company type and size range you sell to): ______________________________ Need (use cases your product serves): _______________________________________ Role (who evaluates or influences the purchase): ____________________________ Contactability (what counts as a working business email): ___________________ Exclusions (existing customers with support issues, job seekers, vendors, competitors, spam, others): _________________________________________________ Who applies the definition: __________________ Within how long: ___________ Where the result is recorded: _______________________________________________ How chat-assisted requests are marked (hidden field, source value or other): ____________________________________________________________________________ Marker verified on a submitted test request? (date/evidence): _______________ Opportunity definition used by sales (existing stage rule): _________________ PART 2. PREPARE THE TEST SET [ ] Write three real buying questions from your pricing or plan pages. Q1: ______________________________________________________________________ Q2: ______________________________________________________________________ Q3: ______________________________________________________________________ [ ] For each, note the approved source passage that should decide the answer. [ ] Write one buying question your approved sources do NOT answer (for example an unpublished integration, a discount or contract term). [ ] List the next steps the chatbot should offer on each page (plan details, trial, demo request, a person). [ ] List the demo form's fields and which are required. [ ] Write your real follow-up commitment that the receipt should state. PART 3. TEST CASES For each case record: what the buyer saw, what was submitted (if anything), what sales received, the result state (not attempted / prepared / submitted and confirmed / failed / unknown), the evidence location and the issue owner. Case 1. Plan question answered from an approved source Expected: answer matches the source passage and states the deciding condition. Observed answer: __________________________________________________________ Source shown or traceable: _________________________________________________ Evidence location: ____________________ Issue owner: ______________________ Case 2. Question outside approved sources Expected: no invented answer; the question is flagged and carried forward or a person is offered. Observed answer: __________________________________________________________ Evidence location: ____________________ Issue owner: ______________________ Case 3. Buyer chooses a step other than a demo (plan details or trial) Expected: the chosen step is supported; no pressure toward a meeting. Observed behavior: _________________________________________________________ Evidence location: ____________________ Issue owner: ______________________ Case 4. Demo request prefilled from the conversation Expected: details already given are reused; only missing fields are asked. Fields prefilled: __________________________________________________________ Fields asked: ______________________________________________________________ Evidence location: ____________________ Issue owner: ______________________ Case 5. Buyer edits a field before confirming Expected: the summary shows the edited value; the submission carries it. Observed summary and submitted value: ______________________________________ Evidence location: ____________________ Issue owner: ______________________ Case 6. Buyer declines confirmation Expected: nothing is submitted. Form destination checked for a submission? (result): _______________________ Evidence location: ____________________ Issue owner: ______________________ Case 7. Buyer leaves halfway through the request Expected: nothing is submitted; a returning buyer can continue in the thread. Observed behavior: _________________________________________________________ Evidence location: ____________________ Issue owner: ______________________ Case 8. Confirmed request Expected: one submission; receipt appears only after success and states your real follow-up commitment. Receipt text the buyer saw: ________________________________________________ Form record matches the confirmed summary? (yes/no, differences): __________ Number of submissions created: ______________ Evidence location: ____________________ Issue owner: ______________________ Case 9. Failed or uncertain submission (use a deliberately failing test setup) Expected: buyer told the request is not confirmed; a person offered; no blind resubmission or duplicate. Observed message: __________________________________________________________ Submissions created: _______________________________________________________ Evidence location: ____________________ Issue owner: ______________________ Case 10. Buyer asks for a person mid-conversation Expected: a teammate can take over in the same thread with the conversation. What the teammate saw: _____________________________________________________ Evidence location: ____________________ Issue owner: ______________________ Case 11. Question left after hours Expected: away message shown; the question can be left; an owner is named for the next reply. Observed behavior: _________________________________________________________ Next-day owner and reply time: _____________________________________________ Evidence location: ____________________ Issue owner: ______________________ Case 12. Returning visitor Expected: the visitor picks up the same thread. Observed behavior: _________________________________________________________ Evidence location: ____________________ Issue owner: ______________________ Case 13. Sales handoff contents Expected: sales can see the question, the answer and its source, the next step chosen, the submitted request, its submission status, open questions and the assigned owner. Present: question [ ] answer/source [ ] choice [ ] request [ ] status [ ] open questions [ ] owner [ ] Missing items and fix owner: _______________________________________________ Evidence location: ____________________________________________________________ Case 14. Chat-assisted marker Expected: the submitted request carries your chat-assisted marker. Observed marker value: _____________________________________________________ Evidence location: ____________________ Issue owner: ______________________ PART 4. MEASUREMENT RECORD (one row per review period) Count each measure separately. Do not merge them into one "chatbot leads" figure. Period: ______________ Pages included: _____________________________________ 1. Buying conversations (AI-assisted, on buying pages): ______________________ 2. Answered buying questions (reviewer-confirmed correct and sourced): ________ Sample size reviewed: ______________ 3. Next-step choices (plan details / trial / demo / person): __ / __ / __ / __ 4. Completed demo requests (confirmed submissions): _________________________ 5. Qualified requests (Part 1 definition): __________________________________ 6. Opportunities (existing sales stage rule): _______________________________ Guardrail: answers marked wrong or unsupported: _____________________________ Guardrail: failed or duplicated requests: ___________________________________ Form-only qualified requests, same pages and period (for comparison): _______ Other changes in the period (campaigns, pricing, page edits, seasonality): ____________________________________________________________________________ Notes: a chat-assisted request was assisted by the chat, not necessarily caused by it. A before-and-after change is a signal to investigate, not proof of lift. PART 5. COST CHECK (Max AI) Max: $0.39 per AI-assisted conversation across support, sales and Customer Success, with a $99 monthly minimum credited toward usage (not added). No per-lead, seat or MAU fees. Desk app, shared inbox, human chat and supported integrations included. Optional Core CX / UX recording, third-party subscriptions and taxes are separate. Conversations this month: ______ x $0.39 = $______ ; bill = the higher of that amount and $99: $______ Verify current terms: https://www.fullsession.io/pricing?solution=desk NEXT STEP Bring one real buying question and your demo request to a Desk walkthrough: https://www.fullsession.io/book-a-demo?solution=support-desk