How to use the Discovery Question Generator.
Discovery questions should uncover the current process, cost of the problem and decision constraints. Avoid asking a prospect to confirm your preferred solution.
Make the workflow fit your task.
Ask about the current process before proposing improvements. Explore where time or errors arise, who reviews the work and what a successful alternative would need to preserve, using neutral follow-ups for specifics.
- What you provide
- Account context and solution scope.
- What you get
- Questions to establish problem, impact and buying process.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
A catalog team says imports take too long. Generate five neutral discovery questions covering process, errors, review ownership and success criteria.
Completed example
1. Can you walk me through your most recent catalog import? 2. Which step took the most time, and why? 3. How did the team discover and resolve errors? 4. Who reviewed changes before they went live? 5. What would an acceptable review process need to preserve or improve?
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
How can discovery questions avoid leading the prospect?
Ask how the work happens and what is difficult rather than asking them to agree that your preferred feature is necessary.
Why are answers too vague to guide the next step?
Request a recent example, its sequence and the people involved. Concrete cases reveal constraints that broad opinions can miss.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑