Practical guide
Create a change log for product knowledge updates
Create a change log for product knowledge updates: a practical process, a clearly illustrated example and checks to use before the next live session.
A practical process
- Record the changed field, old value, new value and reason for the update
- Name the reviewer and the sessions or scripts affected
- Re-test the related question after the approved change is applied.
Worked example
For example, a package-content change should show when one accessory was removed and which answers were updated. This lets the next operator understand the current package without searching through old messages or guessing which note is newest.
Before the next session
Use the current Aseacast product overview to check which parts of this workflow fit your setup.