Fictional manual rehearsal · 16 October 2026
Is that feature on your roadmap?
Your meeting on your laptop. Your answer cues on your phone.
A customer meeting happens on your laptop. With EvidCue, company answer cues appear on a separate phone at the same time. You review the cue and decide what to say. Then the customer asks about something the product does not do yet. The phone may show an internal plan, but a plan is not a promise you are allowed to make.
EvidCue is an interactive closed beta preview, not a connected answering service. All questions, plans and cues below are fictional. This manual exercise does not demonstrate automatic listening, question detection, roadmap access controls or meeting integration. Use assistance only where permitted and disclose it where required.
Three cues, three kinds of authority
Laptop · customer meeting
"Can we export every report in bulk? If not, is that on your roadmap, and when?"
Separate phone · fictional approved card
"Reports export one at a time today. We do not commit to future release dates on sales calls. I can share your request with our product team."
Approved card: roadmap questions
In this scenario the approved card answers both halves of the question. It states the current capability, and it gives approved wording for the future part without a date. The rep can say that much without improvising.
Separate phone · illustrative source passage
Internal source: product planning notes.
"Bulk export: under consideration. Not scheduled."
Evidence to inspect, not approved wording
Separate phone · AI draft requires human review
"Bulk export is coming soon and should be available next quarter."
Draft. Do not read aloud without review.
The source passage tells the rep something internal: the idea exists and has no schedule. That does not make it customer-facing. The AI draft is worse. It turns "under consideration" into "next quarter", a date that appears nowhere in the fictional sources. A human reviewer should reject it.
Answer today, park tomorrow
A fictional response could be: "Today, reports export one at a time. I cannot give you a date for bulk export, but I will pass the request to our product team with your use case." The rep answers the supported part and does not hint at timing.
Watch for softer versions of the same promise. "Soon", "it is in the works" and "most likely this year" can all sound like commitments to a buyer comparing vendors. If the approved wording does not include them, leave them out.
- If an approved card covers the roadmap question, use its wording and stay inside its scope.
- If only an internal planning note exists, treat it as background. Say what the product does today and route the request through your normal company process.
- If no cue exists, say you will check. A pause is better than a date you cannot support.
A manual handoff might read: "The customer asked for bulk report export and wanted a date. I confirmed single-report export today and gave no timing. Please log the request; their use case is monthly board reporting." Record the actual question and what you said; leave out unrelated customer details.
Why this question deserves its own card
Roadmap questions come up in many evaluations, and the honest answer usually has two parts that carry different authority. The current capability can often be stated plainly. The future part depends on who in the company may speak about plans, and what they have agreed to say. Writing that boundary into a reviewed card before calls is easier than deciding it live.
These are suggested review distinctions, not controls EvidCue claims to enforce today. Do not upload company roadmaps or customer information to the preview to try this exercise.
Rehearse the request without real company material
- Write a fictional approved roadmap card and a separate fictional planning note on paper. Mark the note "internal; not customer wording".
- Have one colleague ask the laptop question while another checks the separate-phone cue. Keep the conversation going.
- Add a fictional AI draft that includes a date or "soon". Check whether the rep spots the invented timing before speaking.
- Review the exact response and handoff. Did anyone describe an internal plan as a commitment?
This exercise has not been tested with participants. Human comprehension remains untested, and no improvement in call speed, follow-up volume or sales-cycle length is claimed.
Explore the simultaneous laptop-meeting and separate-phone illustration. Related guides cover reviewing an AI draft before speaking and keeping an estimate distinct from a promise.