Purpose
This article provides best practices for our feature, Partner Journey Automation (PJA) to Allbound Administrator users.
Introduction
Partner Journey Automation (PJA) is a reactive automation engine that smoothly onboards and educates new partners into the Allbound platform. Simple-to-use and powered by Triggers and Actions, PJA makes collaboration... Allbound easy. A PJA workflow consists of one trigger and can have multiple actions.
Best Practices
-
To fully harness the power of our PJA tool, follow these best practices for optimal usage:
- Based on your company's current marketing processes, strategically choose the most appropriate PJA Action for you and your partner users
-
-
- Our PJA Actions include: "Send Email," "Send to Zapier," and "Advanced Webhook"
- Most of our customers choose "Send Email" unless their technology/marketing team(s) are experienced with Zapier and/or Advanced Webhooks
-
-
To cultivate a portal "journey" for your partner users with a PJA workflow's Action's messaging, follow these best practices:
- Use our PJA merge tags function in an Action's subject title and message body for a personal touch (see below screenshot)
- View the below screenshot series as an example of a message "journey" your partners can take. *Note: each "journey" needs to be a separate PJA workflow! For the below example, you need your new partner users to:
1. Register for your Allbound portal
2. Watch the "Welcome" video
3. Complete the "Getting Started" Learning Track
4. Receive the "Getting Started" Certification from the completed Learning Track
5. Register their first new deal in the Allbound portal
First PJA Workflow: Trigger: User Has > Registered. Action: Send Email to Action User
Second PJA Workflow: Trigger: User Has > Viewed Content (Welcome Video.) Action: Send Email to Action User
Third PJA Workflow: Trigger: User Has > Completed a learning track (Getting Started.) Action: Send Email to Action User
Fourth PJA Workflow: User Has > Completed a certification (Getting Started Certification.) Action: Send Email to Action User
-
In order to better segment your PJA workflows to the appropriate partner users, follow these best practices:
- View our Help Center article for PJA filters to learn how to successfully segment your notifications to specific partners
- If you need to send a notification to a specific Dynamic Group in your portal, you may do so by specifying that information in the Trigger box with filters. See below image for example to create a PJA workflow for a specific Dynamic Group:
-
- If you need to send a notification to a specific Partner Type/Tier in your portal, you may do so by specifying that information in the Trigger box with filters. See below image for an example workflow to be sent to Referral and Reseller partners:
-
- You can create separate Actions for different recipients. For example, if you want to send one email to an Action User and then a second email to your Allbound Administrator users to alert them of the user's registration. See below images for an example workflow
If you still have questions, please reach out to your Customer Success Manager or Open a Support Ticket.
Also, please refer to this article to further learn about Partner Journey Automation:
- A Guide to PJA Merge Tags (& Glossary)
- How to Create Partner Journey Automation Workflows
- How to Create Partner Journey Automation Workflow Actions
- How to Create Partner Journey Automation Workflow Triggers
- How to Manage Partner Journey Automation Workflows
- Glossary for PJA Triggers, Events, and Filters
- How to Create Webhooks for PJA
- How to Create Automated Slack Notifications with Zapier