Keep every account current
Outcomes
Every update is a version
A setup keeps improving after you roll it out. You sharpen the AI Receptionist's instructions, add a follow-up, or adjust a form. Make the change on the model account, then update the Blueprint: the update captures the model account again and creates a new numbered version.
One version is always current, and every new apply uses it. Accounts that already received the Blueprint stay on their version until you move them.
Labpublish a new version
Make one change on your model account, such as a line in the AI Receptionist's instructions. Then go to Partner Center → Accounts → Blueprints → My blueprints, and open your Blueprint.
Set the current version
On any version that is not current, Make v{N} current points every future apply at that version. It changes no account and deploys nothing.
Use it to stage a rollout: test a new version on a few accounts, then make it current once it proves itself. Use it to pause one, too: when a new version has a problem, make the previous version current so the problem reaches no more accounts while you fix it.
See who is out of sync
The Applied accounts tab lists every account the Blueprint reached, with the version it runs. Summary cards across the top count each status and filter the list when you select one:
| Status | What it means |
|---|---|
Up to date | The account runs the current version |
Out of sync | The account runs an older version, and the row shows the version available |
Failed | The last apply did not finish, and the error details say which components failed |
Applying | An apply is running now |
To move one account forward:
- Select the
Out of synccard. - Open the
⋮menu on the account's row. - Select
Apply latest version (v{N}). The label shows the version the account moves to.
To move many accounts at once, select their checkboxes and open Actions:
Re-apply to latest versionmoves them all forward.Roll back...moves them to the version you pick.
A selection holds up to 100 accounts.
What a roll back leaves in place
Rolling back applies an earlier version, and an apply only adds and updates. The earlier version's components return, and components that a later version added stay on the account until you remove them by hand.
Plan around campaigns
Campaigns are created on an account the first time a Blueprint reaches it, and a later apply never updates them. Every upgrade, roll back, or re-apply to that account reports the campaign as failed, even when every other component landed.
Keep campaigns in a Blueprint of their own. The Blueprint you version often then upgrades cleanly. To change a campaign on an account that already has it, edit the campaign on that account.
Knowledge Check
Three quick questions on versions, out-of-sync accounts, and what a roll back leaves behind.