Create, share, and reuse playbook instances
To use a playbook, navigate to Use Case Playbooks > Playbooks. Browse and use the various searching and filtering options on the page to select and get started with a specific playbook.
Create a playbook instance create-playbook-instance
Before creating a playbook instance, explore the available playbooks to discover the right playbook for you. When you are ready to proceed with a playbook and create an instance, select Create Instance to proceed with the playbook and generate technical assets.
This action generates several assets for you to use to achieve the use case described by the playbook.
Use the configuration controls to edit instance names and descriptions edit-instance-metadata
After creating an instance based on a playbook, you can personalize it to distinguish it from other instances created from the same playbook. Select the configuration control as shown below. Edit the name, description, and notes and select Save when you are done.
Understand the generated assets understand-assets
It is important to understand that the generated assets differ based on the use case you are enabling:
- Different assets are generated for different types of playbooks. These assets are created specifically for the use case achieved through the playbook. For example, a playbook generates a schema, an audience, a journey, and messages. Another playbook generates a schema, an audience, and a destination to activate data to.
- The assets themselves differ between playbooks. For example, for the Send A Birthday Message To Guests playbook, the audience that is created has the rule
birthday=today AND year=any.
To illustrate an example, for the Abandoned Cart: Merchandise playbook, you can see that a specific journey is created that includes the messages created for this use case.
Use and edit the generated assets use-and-edit-assets
As you explore the assets that get generated after you create an instance of a playbook, you can edit any of the assets created.
If either you or someone on your team create another instance of the playbook, the edited assets are kept and new assets are created for the new instance of the playbook.
The behavior described above is true for all assets that get created, except for schemas. In the case of schemas, new schemas are not created when a new instance of a playbook is created, so you will be using the edited schema from another instance of the playbook in the newly created instance.
Reuse playbooks reuse-playbooks
By creating multiple instances of the same playbook, you can implement the same use case later, without modifying the details of your previous implementation of the use case.
Share the playbook and the generated assets with other team members share-playbook
You can share the generated instance and assets with other team members. To do this, copy the URL link from the browser and share it with your team to give them an overview of the generated assets.
Video walkthrough of the end-to-end playbook process
Watch this video to learn how to discover, create, publish, and troubleshoot instances of a Use Case Playbook from end-to-end, as well as how to copy the assets generated by the playbook into other sandboxes set up in your organization.
Next steps next-steps
By reading this guide and the one about discovering the right playbook for you, you now know how to interpret the various sections of a playbook and how to use the assets that get generated after you create an instance of a playbook.
Next, you can browse the playbooks catalog to find the right playbook for your use case and read the troubleshooting guide if you encounter any issues.