Prep material

Prep is what makes the answers yours. Every question the app hears is searched against this material, and the matching passages go to the answer engines along with the question. Without it the answers are generic, and they will invent details you then have to defend out loud.

The row of pills at the top of the page is the short version: what this kind of meeting wants, and what you have loaded.

Adding something

Pick the type first, give it a title if you want one, then use whichever of the three routes suits what you have:

• Drop a file, or click the box to choose one. PDFs, .docx Word documents and plain text formats are accepted. A PDF that is a scan has no text to extract and will be rejected — paste the text instead.
• Paste a link and press Fetch page. The app fetches it, keeps the text and throws the markup away.
• Paste the text straight into the box.

The meeting's own details

At the top of this page, Meeting details holds the name, the company, the role, which round it is, when it is and your notes. It is the same form as Edit on the meeting's card, with room to read it — so a meeting is one page rather than a form in one place and its documents in another.

Two scopes, and the difference matters

Material either belongs to you or to one meeting, and the app is strict about which:

• Your profile — follows you from one meeting to the next, and is never cleared by creating a new one.
  • Interview: your CV, your STAR stories, past questions and answers.
  • Sales: what you sell — the product, the pricing, the case studies.
• This meeting — belongs to one conversation and stops grounding answers when you select another.
  • Interview: the job advert, and the research done for this company.
  • Sales: the prospect, who is on the call, notes from last time.

Selecting a different meeting swaps the second section and leaves the first alone. Nothing is deleted by that swap — the previous meeting's material stays attached to it, and comes back when you select it again.

A CV written for one job

Tick "Written for this meeting" when you add something from the first list and it is kept to the meeting you have selected, instead of following you.

That is what a tailored CV is for: the version rewritten for this advert should ground this interview and no other, while the general one carries on to the next. It is still filed as a CV, so it still ticks the checklist and still reaches every prompt that mentions your CV — you do not have to file it as "other" and lose both, which was the only way to do this before.

Add both if you have both. They are separate documents and neither replaces the other.

From a terminal it is --tailored:

whispr prep add ./cv-northwind.md --kind cv --tailored

and a Claude session preparing with you can pass scope: "meeting" to add_prep_material. All three say which owner the document ended up with, so you never have to guess.

The box only appears where the choice is real. A job advert is always kept to its meeting and cannot be made to follow you, because an advert that grounded every later interview would be describing a job you are no longer applying for.

Anything you added before meetings existed sits under your profile. That is honest rather than tidy: guessing which meeting an old file belonged to, and hiding it from every other one, would be worse than showing it everywhere.

Reading the list

Each row says what type it is, its title, how many searchable chunks it produced and a preview of the text.

Pasting a link works anywhere. If the only thing in the box is a URL, Whispr fetches that page and reads it rather than storing the address — the same thing the link field does. A document that merely mentions a link is still stored as a document.

not searchable in red means too little text came out of the document to index — a couple of words, a stray caption. It is stored but it will never match a question, which is worth fixing before the call rather than discovering during it. A document with no extractable text at all does not get this far: it is refused when you add it, with the reason.

Superseded material

A job advert is the one thing you can only have one of per meeting — there is one role being interviewed for, and two adverts grounding one conversation is two different jobs in the same prompt. Adding a second retires the first.

A retired row is greyed, marked superseded, and names the document that replaced it. It is out of search and out of the prompt, but nothing was deleted: Restore puts it back and retires the other one in its place.

Everything else accumulates. Three pieces of company research are three useful documents about one company, and notes from three previous calls are the best thing in a sales prep.

Drafting the likely questions

Draft likely Q&A predicts the ten questions this advert is most likely to produce and writes a considered first-person answer to each, from your own material. It lands in prep as ordinary material.

That last part is the point. The drafted answers are indexed like anything else, so during the call retrieval grounds the live engines in them — a considered answer written in advance, reached instantly, instead of the engines rebuilding one from your CV under time pressure.

It is one model call on your own account, roughly the cost of two answers, and it happens only when you press the button. Whispr never predicts questions during a meeting: that would be a paid call per guess for answers mostly unread.

Re-drafting replaces the previous draft rather than adding a second — two drafts would both be retrieved and would ground the same question twice.

It needs the advert and your CV (or, on a sales call, the offering and your prospect notes). Without them the questions would be generic and the answers would be about nobody, so it says which one is missing instead of guessing.

Drafting the likely objections

Beside the Q&A draft is a second button, and it is deliberately not a variant of the first. Nobody asks "why are you more expensive than the incumbent" — they say it, and the two need different answers.

Draft likely objections predicts the eight pushbacks this call is most likely to produce, in the words somebody would really use, with how to answer each. Like the Q&A draft it is one model call on your own account, it happens only when you press the button, and it lands in prep — so when the objection actually arrives, the answer is already retrievable at the moment there is no time to compose one.

Every response is written to acknowledge the objection before answering it. That is the whole reason it is a separate draft: an objection answered by denying it comes back at the end of the call, larger than it was. Where the objection is fair, the draft says so and says what you do about it — and it will not invent a capability, a customer or a price to defeat one, because a claim made on a call is a commitment somebody has to honour.

Re-drafting replaces the previous one. It needs the same two documents the Q&A draft does.

Generated reviews

Two things the app can write for you, both from material you have already loaded. Neither happens on its own, because each one is a call on your own account: they are buttons.

How you match this role sits at the top of the meeting's section — how what you have done lines up with what they asked for. It is the thing to read the night before. On a sales meeting it becomes how what you sell fits this prospect.

A review sits under a job advert, company research or prospect notes: the document boiled down to what matters. A company page you added by pasting a link is reviewed automatically. Your CV, your stories and your price list are deliberately not reviewable — they are already your own words, and a paraphrase would compete with the original for room.

Both are labelled as generated, and both say when they have gone out of date because the material underneath them changed. They are not regenerated quietly, for the same reason they are not generated unasked.