Start with one buying decision
A visitor who asks whether your product fits a particular workflow has a different need from someone browsing a general article. Choose one high-intent page and define the decision your sales employee should help that visitor make. For example: can our service support a five-person support team with an existing help centre?
This is a proposed workflow for a pilot, not a customer result or a promise of more revenue. Begin with questions your sales team already receives and compare the employee’s answers with an approved reference.
Prepare the facts before the pitch
Give the employee current product descriptions, supported use cases, limitations and the approved route to a human. Separate factual material from instructions about tone and qualification. A processed source does not establish that every answer is accurate.
In Aivah, review the employee’s Instructions, Knowledge and Tools. Follow the current Help Center for adding sources and saving changes. Ask about an unsupported capability to check that the employee acknowledges the gap rather than inventing a feature.
Read related guides
Ask for context in a natural sequence
Answer the visitor’s first question before asking for contact information. Then ask one relevant follow-up at a time. A short conversation that establishes a real need is more useful than a completed form full of guesses.
- Need: which business problem is the visitor trying to solve?
- Current process: what does the team use today, and where does it get stuck?
- Fit: which requirement matters most, and can the approved material support it?
- Next step: does the visitor want a human follow-up, and what contact details do they choose to share?
Separate fit, intent and spam signals
Do not label a person a scammer because they use a personal email address or leave a field blank. Distinguish a good-fit enquiry, an enquiry needing review, an out-of-scope request and likely spam. Treat repeated irrelevant messages and automated submissions as review signals, not proof about a person.
A suggested handoff is: “Small support team; needs help answering setup questions; asked about website deployment; would like a walkthrough.” Record the visitor’s own facts and the unanswered question. Do not fill in an invented budget, authority level or deadline.
Measure accepted leads, not just conversations
Define a sales-accepted lead before launch. Track eligible page visits, meaningful conversations, consented handoffs and leads accepted by a salesperson as separate stages. If a conversation never reaches the CRM, it is not a completed handoff.
Compare equivalent traffic sources and exclude internal testing. Inspect a sample of rejected leads each week to see whether the page attracts the wrong audience or the employee asks the wrong questions.