When you click Finalize in the contact card, ST300 sends the entire conversation to the AI evaluation engine. The engine reviews the exchange against the persona's defined end conditions and your organisation's configured metrics, then writes corrections for any messages where a different approach would have been more effective.
Evaluation takes 10–20 seconds. Once complete, the scenario appears as finalized in your list and is ready to review.
Open any finalized scenario to see the full conversation replay. Messages that received a correction are highlighted with a warning border and a “Correction” badge. Below each flagged message, a correction card shows:
Good question. Our partnerships workflow is the main bottleneck — we're managing eight markets manually. What does your solution actually do for APAC-scale operations?
We have a great platform that a lot of companies use. It's really flexible and I think you'll love it. We can set up a demo and go from there.
“Our platform is designed for exactly your situation — multi-market partnership pipelines in one place. Most APAC teams in financial services are live within two weeks. Can you tell me more about how you're currently managing onboarding across those eight markets?”
That's quite vague. What specifically makes this relevant to a multi-market APAC operation? I've heard similar things from other vendors.
Fair point. Let me be more specific — we handle multi-currency pipelines across up to 20 markets in a single workspace, with APAC-based support during business hours. What does your current onboarding process look like when you enter a new market?
Corrections are not about finding the single “correct” answer. Sales conversations do not have one right path. What the correction engine looks for is:
Read corrections in order from the top. The first flagged message often explains why later messages became harder — a weak opener reduces trust, which makes every subsequent objection harder to overcome.
The automatic evaluation covers the messages the engine flagged on its own pass. But you may have messages you want a second opinion on — moments where you felt uncertain about your phrasing or tried a new approach.
On any of your messages in a finalized scenario, a Request correction chip appears. Click it to submit that specific message for targeted AI evaluation.
3 / 10
corrections usedYour correction quota depends on your plan — some plans include a monthly allowance, others a fixed total. The indicator appears in the top-right of the simulation page. Need more corrections? Contact us at st300@octagrid.net to purchase additional credits.
Prioritise requesting corrections on messages just before the conversation turned — when the persona started pushing back, slowed down, or raised a new objection. These are usually the highest-leverage moments to understand.
Reading corrections is step one. Improvement comes from applying them. Here is a pattern that works well:
If you have the manager role, you can access your team's finalized scenarios from the Management → All Results page. Each scenario shows the rep's full conversation and any corrections applied.
Use the Request correction feature on specific messages to add targeted coaching notes — the same mechanism reps use on their own sessions. This lets you run asynchronous coaching without scheduling a separate debrief.
Ready to build more personas for your target markets? Read the persona creation guide →
Copyright © Sales Trainer 300 2026