- The Scorecard Rots First: Roleplays survive a pricing change, but scoring criteria written by hand go stale and mark correct answers wrong. Most teams keep a knowledge base and a drifting rubric copied from it.
- Link It, Get The Rest: Add a knowledge source from any LMS, Confluence or website. Outdoo builds AI Trainers, AI Roleplays and scoring criteria from the same articles, with nothing typed into a scorecard.
- Daily Re-Sync: Outdoo re-syncs the source daily, so Tuesday's pricing update shows up in practice on Wednesday. There is no manual sync button yet.
- Growth And Enterprise: Knowledge Sync is on the Growth and Enterprise plans. It trains and scores against whatever it finds, so contradictory or outdated pages need fixing first.
A product marketing manager ships a release with forty new capabilities, and every one of them is documented in Confluence. To train sales on it, enablement has to turn those pages into roleplays. Then comes the part nobody budgets for: writing the scorecard criteria. Did the rep explain the feature correctly? Did they mention the limit? Did they follow the positioning guideline?
That is hundreds of criteria, typed by hand. They are wrong the next time a page changes.
On Day 6 of 10 Days of Outdoo AI, we are launching Knowledge Sync. You add the link. Outdoo builds the rest.
Why the Scorecard Is the Part That Rots
When a team says its AI training went stale, people usually blame the roleplay. In our experience the roleplay is rarely the problem. The scoring criteria are.
A scenario can survive a pricing change, because the buyer's concern is still the buyer's concern. A criterion that says the rep must quote last quarter's packaging cannot. And the person who learns this first is a rep who gave the right answer and got marked wrong.
Most teams keep two copies of the truth: the knowledge base, and a rubric someone wrote from it once. Product owners edit the first. Whoever has time edits the second. They drift apart, and nobody notices until a rep complains.
Generic criteria are the other escape route. "Explained the product clearly" is easy to write and never goes out of date. It is also useless, because it cannot tell a correct explanation from a confident wrong one.
How Knowledge Sync Works
Go to Practice, then AI Trainers, then Create, then Add knowledge source, and paste the link. Outdoo works with any LMS, with Confluence and with websites.
From that content Outdoo builds AI Trainers and AI Roleplays. An AI Trainer teaches the material in a live voice conversation and checks understanding as it goes. A roleplay lets the rep use the material against a lifelike buyer or customer.
The scoring criteria come from the same articles. During a roleplay, and on real calls, Outdoo checks in the background whether the rep explained each feature correctly and followed each guideline. Nobody types those points into a scorecard.
Then it keeps going. Outdoo re-syncs the source daily. A pricing update in Confluence on Tuesday shows up in practice on Wednesday, and nobody rebuilds a roleplay.
Where It Gets Awkward
Knowledge Sync is available on the Growth and Enterprise plans. A few edges are worth knowing before you try it.
There is no manual sync button yet. A change you make this morning appears after the next daily sync, not in five minutes. Private Confluence spaces and websites behind a login are read through an integration. A public page needs only the link.
The bigger one is accuracy. Knowledge Sync is only as good as the source it reads. If two pages disagree, or a page still describes last year's packaging, Outdoo will train and score against what it finds.
We would go further and call that a feature in disguise. Most teams have never had a reason to find out how many of their own articles contradict each other. Once training and scoring read from the wiki, the contradictions show up as confused reps, and someone finally fixes the page. Treat the linked space as training content. Keep it current and delete what is retired.
What Changes on Monday
An enablement lead launching a new product links the release notes space on Monday and assigns the generated AI Trainer and roleplay to sales that afternoon. The two weeks she used to spend on criteria go to coaching.
A support operations manager links the help center. When an article about a billing change is updated, every agent's next practice call is checked against the new answer.
A compliance trainer links the policy pages in the LMS. Each roleplay checks that the required disclosures were made, using wording the policy team owns, not wording a trainer paraphrased from memory.
Why Scoring From the Same Source Matters
When the criteria come from the articles themselves, there is no second copy to keep in step. The knowledge base changes, and training and scoring change together. A real call is scored against today's answer, not the one from the last launch.
This is the Train stage of the loop we have been walking through since Day 1, and it feeds Practice and Perform too. A rep trained on the current pricing page is scored on the current pricing page, in the roleplay and on the call.
Training happens either way. Whether it shows up on the call depends on whether training, practice and scoring all read from the same place.
The people who write the knowledge should not have to write it again as training.
Ready to see it on your own knowledge base? Book a demo and we will link a source live.
Follow the series: See all 10 days
Day 6 of 10 | See all 10 days | Previous: Day 5 | Next: Day 7, Screen-Aware Roleplays
Outdoo builds AI Roleplays from your own calls and scores practice and real calls with one scorecard. Rated #1 for Best Results on G2.
Frequently Asked Questions
What does Knowledge Sync build from a linked source?
Link an LMS, a Confluence space or a website, and Outdoo builds AI Trainers and AI Roleplays from the content. The scoring criteria come from the same articles, so Outdoo checks whether the rep explained each feature correctly and followed each guideline, in roleplays and on real calls, without anyone typing criteria into a scorecard.
How often does Knowledge Sync update, and can I sync manually?
Outdoo re-syncs the source daily, so a change made in Confluence on Tuesday appears in practice on Wednesday. There is no manual sync button yet, so a change made this morning shows up after the next daily sync, not in five minutes.
Which plans include Knowledge Sync, and what does it need to work well?
Knowledge Sync is available on the Growth and Enterprise plans. Private Confluence spaces and sites behind a login are read through an integration, while a public page needs only the link. It is only as good as its source, so if two pages disagree, Outdoo trains and scores against what it finds.
.avif)
