Meeting Coach

Sales Coach and Engineering Coach

There are two coaches, one for each side of the company, and each person sees only their own:

• Sales Coach, for sales and marketing (department, or the salesperson flag): sales calls, the six stages of the sale, objections and the rebuttal bank, competitor drills, and preparing for a real call.
• Engineering Coach, for everyone else on customer calls: software demos, tech support calls and customer training sessions.

A call, scorecard, recording, practice run, lesson or lesson video belongs to one side by its type. Someone from the other side can't list it, open it or start it, even with a direct link (it shows as not found), and the API and the Claude tools return only your side. The objection bank, the rebuttal bank, competitor drills and call preparation are sales only. Admins see both coaches and switch between them (Sales, Engineering or Both) at the top of each page.

Each coach has the same areas, in the sidebar under My Day:

1. Train: two-minute lessons for your side, quiz modules and your certifications.
2. Practice: role-plays with an AI customer, practice assigned to you and your practice scorecards.
3. Live meetings: coach a call live or in person, upload a transcript, your calls and their scorecards.
4. Team (managers and admins): how the team is doing, and assigning a role-play.

The old addresses (/sales/training and /coach/practice) still work.

SoftInWay basics (everyone)

One item belongs to both sides: SoftInWay basics, who SoftInWay is and what we do, so anyone can give a short, accurate pitch. It is a two-minute lesson, a short quiz, and a role-play, Give the 60-second pitch, scored on clarity, accuracy against the published facts, one relevant example, and ending with a question. It's in Train and Practice on both sides, and it's required for everyone on customer calls.

It starts as a draft that only admins see: the Train page lists every fact in it with its source on softinway.com. An admin checks them and presses Publish to everyone; Back to draft hides it again.

Team

Managers see their own reports on their own side; admins see everyone. For each person, across the three areas:

• Train: SoftInWay basics done, lessons passed, quiz modules certified.
• Practice: open, done and average score in the last 30 days, and the trend against the 30 days before.
• Live: calls in the last 30 and 90 days, the average score, the weakest skill, and how often a call ended with an agreed next step.

The team view adds the average for each scorecard item, the most common objections (sales), and everyone with no activity at all, so nobody drops off the list. Your own to-dos (practice waiting, SoftInWay basics not done, your last scorecard) show in a Coaching card on My Day.

Meeting Coach reads the transcript of a call and tells you how it went, scored for the kind of call it was:

Call type	Scored on
Sales call	Teach, Tailor, Take control, Discovery, Technical credibility (the Challenger method), with our Sales AI rules (BANT, first call-to-action, product names) as background
Engineer demo	Discovery before demoing, Relevance to their use case, Clarity and pace, Technical accuracy, Handling technical questions, Value link, Next step
Customer training	Structure, Clarity, Checking understanding, Hands-on practice, Technical accuracy, Handling questions, Next step
Tech support call	Diagnosis, Technical accuracy, Clear fix or workaround, Expectations and empathy, Ownership and follow-up, Knowledge capture, Account signals

Every scorecard has:

• Scores (0–5) for each item above, each backed by quotes from the call.
• Questions that were missed, with the moment in the call that opened the door.
• What the customer pushed back on (objections, concerns, where trainees struggled, or frustrations) and whether it was handled.
• Next steps that were actually agreed (or a flag that none were).
• Talk metrics: how much of the call SoftInWay talked (flagged when it's high for that kind of call), the longest monologue, and how many questions were asked.

It's built into Otium. No outside recording service is used.

Scoring a call

After every call or meeting, the scorecard page also lists the key information that was said (people and roles, needs, requirements and technical details, budget, timeline, how they decide, current tools, competitors, risks), each with a short quote, and the action items: who committed to what, and by when. Both go into the Salesforce Task too.

1. After a Teams meeting, open it in Teams → Recap → Transcript → Download (.vtt or .docx). Transcription must have been turned on during the meeting.
2. In Otium, go to Sales → Meeting Coach → + Score a call.
3. Pick the call type, give it a title, upload the file (or paste the text), and optionally add the Salesforce account id and attendee emails.
4. Scoring takes a minute or two. The scorecard appears on the call's page.

SoftInWay people in the transcript are recognised by name; everyone else counts as the customer.

Who sees what

You see your own calls. Managers also see their direct reports' calls on their own side (a sales manager never sees an engineer's demo, and the other way round); admins see everyone's. Only the rep (or an admin) can delete a call.

Export control

Never upload an ITAR or EAR call. Admins keep a blocklist of export-controlled Salesforce accounts and email domains under Meeting Coach → Policy; a call that matches is refused before anything is stored or sent to the AI.

Disagreeing with the coach

Every scorecard has a Disagree with this scorecard? box. Notes there are kept on the card and used to improve the rubric. They never change scores automatically. Re-score runs the call again.

Retention

Raw transcripts are deleted after the retention period set in the policy (180 days by default). Scorecards are kept.

Live coaching during a call

From the browser (no desktop client). On the Meeting Coach page press Coach a call (Chrome or Edge on a computer). It fills in the meeting from your calendar; pick the call type and confirm that everyone knows an AI note-taker is listening. Join the Teams call, then press Start listening, allow the microphone, and share the Entire screen (or the Teams browser tab) with Share system audio ticked: your microphone is you, the shared audio is them. Use headphones so the microphone doesn't hear the customer through your speakers. Keep the Otium tab open until the call ends. This needs cloud transcription (Deepgram) in the policy. With recording on, the shared screen and both voices are recorded in the browser and saved to your OneDrive when you end the call; if that fails, the page offers the file to download.

Tips on your phone or iPad. While you share your screen, open 📱 Tips on your phone or iPad on the live panel and scan the QR code. The phone shows the current tip in large type, the last few lines, and the Used it / Skip / Wrong buttons, and keeps its screen on. No login is needed: the link works for that one call and stops when it ends, so don't share it. A phone or iPad can't listen to the Teams app itself (Apple doesn't allow a web page to hear other apps), so the laptop does the listening.

In-person meetings (phone or iPad). On the Meeting Coach page press In person (or open Coach a call and pick In person). Put the phone face up on the table. Listening starts on its own when the page opens (allow the microphone; an iPhone may ask for one tap on Tap to start listening), and say hello first: the first voice to speak a full sentence is taken as yours, and the others are labelled Speaker 1, Speaker 2. If it gets that wrong, tap That last line was me. Tips appear on the same screen. Keep Otium open with the screen on (it asks the phone to stay awake): iPhones and iPads stop the microphone for a web page when the screen locks or you switch apps. Adding Otium to your Home Screen (Share → Add to Home Screen) makes it open full screen. The audio is recorded to your OneDrive when recording is on. This uses Deepgram's live service, which needs a Deepgram key with the Member role.

Just record, no tips. Untick Live tips when you start (calls or in person) to only record and transcribe. Nothing is shown during the meeting and no tips are worked out; you still get the transcript, notes and scorecard afterwards.

From the desktop client. Choose Coach this call… from the Otium tray menu, pick the call type, and confirm that everyone on the call knows an AI note-taker is listening. Nothing joins the meeting: the client listens to your microphone (you) and your speakers (them), transcribes on your own computer, and opens a live panel in Otium.

• Live transcript. Words appear greyed while someone is still talking, then turn into the final line.
• Nudges. One short tip at a time (12 words or fewer), usually a question you can say as-is. Mark it Used it, Ignored or Wrong so the coach improves.
• Sales calls are coached with our Champion Playbook: Challenger (teach, tailor, take control), BANT, discovery questions, objection and stall handling, and catching our own slips (talking price too early, offering brochures instead of a next step). A checklist on the panel lights up as you cover why they took the meeting, pain, impact, current tools, need, budget, decision process, timeline and the next step.
• Sales calls also get negotiation nudges from the playbook: "compared to what scope?" against a cheaper quote, trading instead of giving, checking whether a deadline is real, staying silent after a price, and Voss questions ("How would you take this to your team?").
• Engineer demos are coached with the demo playbook: discovery before demoing, showing their case instead of a tour, tying features to what they save, clarifying technical questions before answering, admitting what you don't know and following up in writing, and catching overclaims. The demo checklist covers their goal, machine and duty, current tools, success criteria, showing their case, checking understanding, who else decides and the next step.
• The coach never suggests prices, discounts, trials or commitments, and never claims what AxSTREAM can or cannot do.
• How fast. The coach looks at what the customer just said within about 2 seconds. While you are talking, it waits until the customer answers (or 8 seconds) and then looks at everything you said together, which keeps tips just as timely at about half the cost. Around 30 to 40 calls can be coached at the same time.

Who transcribes. An admin picks it under Meeting Coach → Policy → Live transcription: our own Whisper server on the office GPU box (laptops transcribe on their own when it can't be reached), or Deepgram, a cloud service, until the GPU box is ready. With Deepgram, the desktop client sends each spoken line to Otium, which passes it on and returns the text; the Deepgram key stays on the server, and the policy page shows the last 30 days' hours and estimated cost. Calls on the export-control blocklist are never recorded at all. Two lists on the same page improve accuracy with any transcriber: our words (products, competitor tools, customer names, jargon) are sent with every line, and spelling fixes ("axe stream => AxSTREAM") are applied to every transcript. Test checks the chosen service with a short sample.

The coach sees your screen on real calls

When you coach a Teams call from the browser (Coach a call), the coach can also see the screen you share, so its tips fit what the customer is looking at: if they asked about part-load behaviour and you are showing the design point, it nudges you to show part load; if a demo turns into a generic tour, it nudges you to tie it to their machine.

With Teams in front of Chrome, the coach still sees your screen: the picture comes from what you shared, not from the Otium tab. A slide that stays up is re-confirmed every 30 seconds, so the coach keeps seeing it.

• What is sent. While your share is live, the page looks at it every 5 seconds and sends a picture (at most 1280 pixels wide, JPEG) only when the screen changed, never more than one every 5 seconds. Nothing is sent while the Otium tab is hidden or after you stop sharing. The live coach looks at the newest picture when it is less than 90 seconds old. At the end the scorer looks at up to six of them, each with what was being said at that moment, and the scorecard mentions whether what you showed matched what the customer needed. Key facts and next steps still come only from what was said, never from what was on screen.
• Turning it off. On the Coach a call page, untick The coach sees my shared screen before you start. During the call, untick Coach sees your screen in the capture panel; nothing more is sent for that call. Do this for calls that show confidential customer content.
• The policy switch. An admin can turn it off for everyone under Meeting Coach → Policy → Shared screens → Screen-aware live coaching (on by default). Calls on the export-control blocklist never send a picture.
• Where the pictures go. Only to Anthropic's AI, for coaching and scoring this call. They are never sent to Salesforce and never shown on any page; Otium keeps up to 120 per call and deletes them with the call, or after the coach retention period, like the transcript.
• Cost. About 1 to 2 cents each time the coach looks at a picture. To keep that down it only looks again when the screen changed, or every third moment when it didn't.
• The desktop client doesn't send your screen (yet): this works only when you coach the call from the browser.

Recordings and Salesforce

When an admin ticks Record coached calls in Meeting Coach → Policy, the desktop client (v1.7 or later) also records while it coaches: the Teams meeting window (never the rest of your screen) and the call audio, in one small MP4 (about 200 MB an hour). When the call ends it uploads the file to your own OneDrive, folder "Otium Call Recordings"; Otium keeps only the link, shown on the call's scorecard. If Otium can't reach your OneDrive (Outlook not connected, or OneDrive access not granted yet), the file stays on your laptop and uploads after your next coached call; the scorecard says so.

Teams' own recordings of meetings you organised (saved by Teams in your OneDrive "Recordings" folder) are found after the call and linked on the scorecard too.

With Log each scored call in Salesforce ticked (the default), every scored call becomes a completed Task on the customer's Contact or Account, matched from the attendee emails: the summary, scores, next steps, and links to the scorecard, transcript and recordings. When a recording arrives later, the same Task is updated.

Practice with an AI buyer

Train and Practice (in your coach in the sidebar) are where you learn and practise before it counts. What you see depends on your side; only admins switch between the two.

Sales people practise the six stages of a SoftInWay sale, as the Sales Guide lays them out:

1. Prospecting: qualify before you call, and disqualify a lead that isn't a fit, politely.
2. Introduction: cold calls, the first 30 seconds, hostile openers.
3. Discovery: finding the real problem, happy-with-the-incumbent, stalls, reframing.
4. Demo (solution sale): evaluations on our terms (success criteria, paid test case), no free trials or unpaid studies, a champion who went quiet, doubts about a small vendor.
5. Proposal: "show us results first" turned into paid scoping, a proposal priced on value, and trading (not giving) when they want a bigger scope for the same price.
6. Closing: price is a message, trade never give (procurement wants 20% off), the cheaper competitor, and the objection gauntlet drill.

Engineers practise the calls they run:

• Software demos: discovery before the demo, showing their case, keeping a newcomer with you, the expert asking what you can't answer, ending with a next step instead of a trial. Two are written for sharing your screen: a customer who wants to see her own impeller, and an expert who asks you to show one specific result.
• Tech support calls: diagnosing before answering (an angry customer with a Friday deadline), calming a call when a whole team is blocked by licensing, and "your results are wrong". Two are written for sharing your screen: a customer who can't find where to change the inlet conditions, and a licence error on a new laptop you walk them through.
• Customer training sessions: checking understanding instead of asking "any questions?", the expert in the room who derails the session, and getting a trainee to do it instead of watching.

Each lesson is a two-minute read from the Champion Playbook (including Exact Words phrases and Voss), then a role-play: an AI buyer, customer or trainee with a real situation, hidden facts that good questions uncover, and objections at natural moments. Type or press the mic and talk (Chrome or Edge); tick Buyer speaks out loud to hear the answers in the most natural voice your browser has, or Hands-free to talk it through like a phone call: you speak, pause, the buyer answers out loud, and it listens again. Tick Camera feedback to see, at the end, how much of the time you were in frame and facing the camera, and how often you looked away (useful practice for Teams demos). That is measured inside your browser: no video or pictures leave the page, and nothing about expressions or feelings is measured. The live coach gives hints while you practise, as on a real call (untick Live coach hints to practise without them). In a demo, support or training role-play you can share your screen (below); otherwise describe what you would show.

A voice call, hands-free. When cloud transcription (Deepgram) is on, a role-play is a voice call that starts by itself when you open it: the buyer speaks out loud (including the opening line when they pick up a cold call), the microphone listens all the time, and when you pause, your words go to the buyer and they answer. Nothing is sent while the buyer is talking, so it never hears itself. If your phone asks for a tap first (iPhones sometimes do before the microphone or sound can start), a 📞 Tap to start the call button appears; tap the screen once more if it says so, to keep it awake. The call pauses by itself after 4 minutes of silence. If a reply is ever blocked, a Tap to hear the reply button appears. You can still type instead.

Natural voice and a face. The buyer speaks in a natural voice from Otium's own voice service (free, nothing leaves our server), or from Azure Speech if an admin saves a key. If neither is available, the browser's built-in voice is used. With a Simli key and faces saved as well, tick Show the buyer's face: the buyer appears as a talking face on video, speaking Claude's lines. Role-plays are fictional, so nothing real is sent.

Lesson videos. An admin can give any lesson a video: upload one (e.g. you reading the lesson on camera), or Record it with the avatar: the coach face reads the lesson while your browser records it, and the result is saved as the lesson video for everyone.

End and score it scores the role-play like a real call. A lesson's role-play with an average of 3.5 / 5 or better appears in My certifications for a year.

Practice from your own calls. When a real sales call or demo scores 3 or lower on something, Otium assigns you a replay of that call aimed at that point ("Replay: Priya intro (Take control)"); the scorecard links to it. Admins can turn this off in the policy. Managers can assign any role-play to their reports and see who practised, their practice scores and their real-call scores side by side.

Demo and support practice with your screen

How. In a demo, tech support or training role-play on a computer (Chrome or Edge), press 🖥 Share my screen next to the call controls and pick the window you'd show the customer (AxSTREAM, a results file, a slide). It works with the voice call and when you type. The button doesn't appear on phones and tablets, or in browsers that can't share a screen. Press ⏹ Stop sharing (or the browser's own Stop button) to go back to describing.

What the customer sees. About every 4 seconds, and right before each thing you say goes to the customer, the page takes a picture of the shared window (at most 1280 pixels wide); it skips pictures where nothing changed. Each turn sends the newest picture once, so the customer reacts to what is actually on your screen: in a demo they ask about what they see and say so when it isn't their case, they're lost, or it's too generic; on a support call they say whether they can follow the steps you show and whether they fix their problem. Pictures go only to Anthropic's AI (the customer and, at the end, the scorer), never anywhere else. Otium keeps up to 40 of them with the practice for the scorecard and deletes them when the practice's call is deleted or after the coach retention period. Share a window with practice material, not customer data.

Scoring. The scorer looks at up to six of the pictures, each with what you said while it was on screen, and judges whether the screens matched what you said and the customer's case: a demo of their machine, or a generic tour; on a support call, steps that match the fix you described. It uses the usual scorecard dimensions and mentions the screens in the evidence and the summary.

Recording. Record this session is ticked when you start sharing (untick it to skip). The recording holds the shared window, your microphone and the customer's voice (when it's Otium's natural voice; the browser's built-in voice can't be recorded), as a WebM video of about 7 MB a minute. When you press End and score it, it is saved to your own OneDrive, folder "Otium Call Recordings", before the scoring starts (keep the tab open while it uploads), and the practice page links it. If Otium can't reach your OneDrive (Outlook not connected, or OneDrive access not granted yet), the page offers the file to download instead, then Continue to the scorecard. Practice recordings are yours: they are never logged to Salesforce.

Prepare for a real call

Before a real call, give Otium the person's email and the stage of the call (the six stages above: prospecting, introduction, discovery, demo, proposal, closing). You get a briefing and can rehearse the call with an AI playing that person. There are two ways to do it.

The Prepare button. Prepare for a real call in Training, or Prepare for a call on the Meeting Coach page (/coach/prepare). Type the email (or pick someone from an upcoming meeting in your calendar), pick the stage and press Prepare the briefing. Otium researches in the background, usually within two minutes; the page updates by itself. It reads:

• Salesforce, with your own Salesforce login (you see what Salesforce lets you see): the contact or lead with that email, their account and its owner, open and closed deals, and the dates and subjects of the last activities (not the notes), plus any warnings such as an opt-out or an old "don't call us".
• Your own mailbox: threads with that address (subject, date and a short snippet).
• Apollo (sales team only): free people search first; a paid lookup only when Salesforce doesn't know the person or their company, counted against the same monthly caps as the rest of the Sales AI.
• Recent news about their company from a web search. Only news whose link the search really returned is kept.

One AI pass then writes the briefing: who they are, what we know (each fact with its source and link), what they build and whether it honestly fits AxSTREAM, likely needs and objections (marked as guesses), the tools they use today (with the Sales Guide's approved answers when a competitor is named), the goal for this stage, a suggested opening, five questions to ask, risks (for example another rep owns the account) and unknowns. A fact the sources don't support is never shown as known: it goes to unknowns. You can prepare up to 10 calls a day.

Rehearse this call starts a voice role-play (the same practice page as Training). The AI plays the real person by first name, role and company, from the briefing: what is known it keeps to, what isn't it improvises plausibly. The scorecard judges the rehearsal against your plan: the stage goal and which of the planned questions you didn't ask.

From your own Claude. If your Claude is connected to Otium (the OtiumWork connector), ask it, for example, "prepare me for my discovery call with ana@acme.com". Your Claude reads what Otium knows (coach_prepare_sources: Salesforce and your mail snippets, no Apollo credits), does the web research itself, and hands Otium the briefing (coach_prepare_practice). Otium checks it (news and web facts need their link, everything else unsourced goes to unknowns), stores it without spending Otium's own AI on research, and gives you the link to the briefing with the Rehearse this call button.

Private. Only you can open your briefings and rehearse them (Otium admins can read them). The rehearsal is a simulation: nothing is sent to the person and nothing is written to Salesforce, and like all practice it never feeds the objection library or the competitor board. Like your other practice runs, it appears in your practice history, where your manager sees its title and score. Companies and accounts on the export-control blocklist can't be prepared: Otium refuses before reading anything, and if Salesforce shows the account is blocked, nothing that was found is kept.

Objections and competitors from real calls

Every scored sales call (uploaded, coached live or in person) also saves, for training. Demos, support and training sessions keep their concerns on their own scorecards and don't feed the objection bank:

• Each objection the customer raised, sorted into a category (price and budget; timing; happy with what they have; someone else decides; no need; trust in us; technical doubts; other), with the customer's own words, how we answered and whether it was handled, partly handled or missed. The scorecard shows the category and the quote too.
• Each tool the customer said they use, are evaluating or considering, or dropped (CFturbo, Ansys CFX, an in-house code, Excel, AxSTREAM itself), with what they said about it: features they like or miss, price, support. Names are matched to the company's competitor list (CFX and Fluent count as Ansys; something ambiguous like "Vista" on its own is left unmatched).

Practice role-plays and calls on the export-control blocklist never feed any of this. That includes a call whose account or domain is added to the blocklist after it was scored: saving the policy removes what it saved (its objections, its tools and its FIELD notes), it can no longer be re-scored, and the backfill skips it before anything is sent to the AI. Re-score replaces the call's saved objections and tools instead of adding to them; deleting a call deletes them.

Customer names. When a call is saved, Otium also writes a copy of each objection and tool detail with the customer's names taken out: the Salesforce account's name (without Inc, AG, Company..., with its abbreviations such as MHI or GE), every customer attendee's email domain (an EPC and the end user on the same call), and the names of the customer's people on the call. When the AI is available, one quick AI pass then takes out names Otium could not know (a company or person only mentioned, the customer side of a live call). Everyone who doesn't see customer names reads this copy, so it stays clean after the transcript is deleted. If Otium could not tell who the customer was and the AI pass did not run, that call's objections are shown only to sales people, managers and admins, can't be practised, and never reach the gauntlet or the competitor board.

In Training → From real calls:

• Objections we hear: the last 12 months of objections by category, with counts, the customer's words, our answer and the verdict (answers that worked are listed first). Filter by category, and by sales calls or engineer calls (demos, support, training). Everyone sees the whole company's objections; customer names are shown only to sales people, managers and admins, and everyone else reads "a customer" and [customer] / [name] in the quotes. Practise this starts a role-play where a fictional buyer (made-up person and company, never the real customer) raises that objection; managers can assign it to someone on their team instead. The buyer is made once per objection (the first click takes a few seconds) and reused for everyone after that; clicking again within a few minutes opens the practice you already have. Managers pick who to assign it to once, at the top of the page.
• Who uses what (sales people, managers and admins only): by competitor, how many accounts and calls named it, stance and sentiment, and the latest details with a link to the call; and by account, which tools each customer uses or weighs.

The objection gauntlet drill uses the team's five most frequent real sales objections (customer names removed) once at least three have been recorded; until then it uses the playbook's list.

Competitor board. When a call names a competitor with a concrete detail (a feature they like or miss, price, support), a FIELD note is added to Market intel → Feature board ("Field: …", filter From calls), linked to the call, once per competitor per call. Notes on other tags are never changed. The live coach still never criticises a competitor.

Calls scored before this existed can be filled in once by an admin with scripts/backfill_coach_intel.py --company <id> (--dry-run first shows what it would save, without writing or calling the AI). For those older calls the tools come from the scorecard's key information; a plain "they use X" is saved as a tool but only something they said about it (liked, missing, price, speed, support) becomes a FIELD note. --force redoes calls that already have intel, but always keeps the tools the scorer itself found on a call.

The Sales Guide in the coach

The coach reads the company's own Sales Guide from Sales AI → documents (the sales-process overview, the objection-handling scripts and the competitive positioning). Nothing from the guide is built into Otium: replace a document and the coach uses the new one within minutes.

Rebuttal bank (Training → Rebuttal bank, or /coach/rebuttals; managers and admins). Ready answers to objections and competitors: what the prospect says, a short line of at most 12 words for a live tip, and the guide's full answer. Seed from Sales Guide (admins) proposes answers from the objection scripts and the competitive positioning; every answer must be the guide's own words (anything the AI rewrote or invented is dropped), and triggers already in the bank are skipped, so it is safe to run again. It runs in the background and takes a minute or two. Seeded answers start as proposed: review them, edit the short line if needed, and Approve the ones the coach may use; Retire removes one from live use. You can also add your own, or click Add rebuttal next to an objection in Objections we hear or a competitor in Who uses what to start one prefilled. A short line that sounds like a price, discount, trial or promise is flagged: the live coach would hold it back.

Live tips quote approved rebuttals word for word. On sales calls and demos, when a competitor from the guide is named in the last three minutes (Ansys, CFX, Agile...), the coach reads that competitor's guide section as background for a good discovery question. When the customer raises an objection or names a competitor that has approved rebuttals, the coach may pick one: the tip is then its short line exactly as approved (the guide's full answer is under it), never words the AI made up. Without an approved rebuttal the usual rules stay: no AxSTREAM capability claims, no prices.

Phrases we never say. When one of our people says a phrase from the guide's "dangerous phrases" list, the live panel shows Avoid saying "…" (once per phrase per call), and the scorecard lists every such phrase our side said, with the line, under the summary. This is a word match on the transcript, not an AI judgement; the customer saying the same words never counts.

Competitor drills. Training → Competitor drills has a Practise vs … button for each competitor in the guide (the ones customers named on our calls first; the rest under more). The AI buyer is a fictional person and company who uses that competitor and raises its typical objections, built from the guide's section on it, its honest loss patterns and its discovery questions. The buyer is made once per competitor and reused for a week, so later clicks start at once. The scorecard judges your answers against the approved rebuttals for that competitor.

Coming next

Automatic transcripts from Teams (no download needed).