Tradesly · Guide
Versions: any change can be taken back
Use version history to return to an earlier setup when a recent coaching change does not work as intended.
If a recent coaching change does not work the way you expected, you do not have to rebuild the earlier wording from memory. The Versions tab gives you a visible history and a Restore action for returning to an earlier setup.
Use Restore when going back is faster and safer than coaching another correction. For a small wording issue, coaching forward may be easier. For a change that affects an important customer interaction, an earlier known setup can be the clearer starting point.
1 Read the history before you act
The page is headed Version history. The setup in use now is marked “· current,” so you can distinguish it from earlier choices. Review the order carefully and choose the point that best matches the behavior you want back.
Before you restore, note any newer coaching you still need. Returning to an earlier point can replace changes made after that point. Save the wording of an instruction you may want to add again later.
2 The steps
Open Versions in the test account.
From Your AI Team, press Coach on a teammate, then open Versions. Confirm the account name first.
Find the earlier setup.
Use the “· current” marker and the order of the history to identify the point you want to return to.
Press Restore in the sandbox.
Review the restored test setup before anything is copied to live.
Review the restored behavior.
Use the test experience available for that teammate and check the situation that caused you to restore.
Record what your team approved.
Note the restored point and the customer-facing behavior you checked. Contact Tradesly before relying on it in the live account.
3 What to test after restoring
Start with the exact situation that made you step back. If a price answer became too aggressive, ask the same price question. If a greeting changed unexpectedly, listen to the first line before testing anything else.
Then check the next action. A familiar answer is not enough if the teammate no longer offers the right booking or follow-up. Keep the call short and focused so you can tell whether the chosen version solved the problem.
A test call is real. Use your own contact details, and remove any unwanted booking or text it creates.
4 Restore only when it matches your intent
Use Restore only when the earlier point matches the setup you actually want back. If you are uncertain, stop before restoring and ask another admin or Tradesly to review the choice with you. The history is there to support a deliberate recovery, not to encourage experimentation with a live customer experience.
After restoring, keep your notes with the reason for the change and the result you reviewed. That gives the next admin enough context to understand why the earlier point was chosen without exposing or reconstructing how the underlying behavior is produced.