A call-preparation workflow your team can evaluate

A call brief should help a salesperson understand what is known, what remains uncertain, and what the meeting needs to resolve. It should also be short enough to use. This workflow is a proposed starting point for a team to evaluate, rather than a claim that every engagement begins the same way.

Use approved account notes and current sources. Do not assume a model can discover or verify recent information from a company name alone.

Prepare the source pack

Include the meeting purpose, participants where known, relevant prior notes, and approved product information. Label the date and origin of each source. Remove material the team is not permitted to process.

If sources conflict, keep both and flag the conflict. Silent cleanup can erase the uncertainty the meeting should resolve.

Ask for a brief with visible boundaries

Use this instruction:

Create an internal call brief using only these sources. Summarize the known context with source references. List unresolved questions. Suggest a meeting objective and possible questions, clearly labeled as recommendations. Do not infer budget, authority, intent, or a commitment from a job title or friendly reply.

Ask for a concise output. The length should follow what the meeting needs, not a requirement to fill every section.

Check an illustrative result

Suppose the notes say, “Operations wants a demonstration; finance has not reviewed it.” A supported brief can say that operations requested a demonstration. It cannot say that finance is blocking the purchase or that budget is approved.

A useful suggested question might be: “Who else needs to assess the proposal before you can decide?” That is a recommendation to the salesperson, not a statement about the buyer.

Review each factual point against the source. Then decide whether the proposed objective makes sense given the relationship and stage. The salesperson owns that decision.

Test the workflow on comparable calls

Record the time needed to prepare inputs, generate the brief, verify it, and make corrections. Compare that with the previous preparation method. Collect omissions and unsupported statements so the instructions can be improved.

If the brief takes more effort than it saves, inspect source quality and scope before adding more tools. Do not mistake a polished page for useful preparation.

The five sales prompts cover adjacent tasks. The sales Sprint is a specific published package within AI Training; tailored training for other teams is scoped separately.