Campaigns

Campaigns are like automessages, but allowing more advanced workflows with multiple messages and logic flow. You can use them for things like drip emails, educating customers after onboarding, and qualifying leads.

You can access campaigns from [MDX CODE].

Default Campaign

By default, every team starts with a campaign to collect the name and email of any anonymous users when they start a chat. If you don't like this behavior, or you want to change the wording of the message or the fields you collect, you can edit the campaign by going to [MDX CODE] and selecting the campaign titled Email and name form.

Creating a campaign

  1. Go to [MDX CODE] and click Create new campaign.
  2. Select your audience for the campaign. See filters for more info.
  3. On the left side of the campaign page, you'll find various campaign components on the left side of the page.

Components

  1. Filter can apply conditions to users who have engaged with the preceding components.
  2. Schedule / wait time: adds a delay before running subsequent components. It can be either some amount of time or a fixed date.
  3. Inbound message triggers the next component in response to a user sending a message.
  4. Send message / email sends a message or email. Composing the message will take you to the automessage editor. If you toggle New conversation, then the message will start a new conversation. Otherwise, it will be a follow-up to the closest upstream conversation.
  5. Assign to assigns the closest upstream conversation to an inbox on your team.
  6. End workflow will force the user out of the campaign immediately. They will not receive any future messages, even if they match the conditions.

Dependencies

Components can be linked by drawing a line from the first component to the second, creating dependencies that dictate the sequence of steps within the campaign. To delete a dependency, hover over the line and click the scissor icon.

Global exits

Global exits ensure that users who no longer fit the campaign's criteria are excluded before it proceeds. They are similar to the End workflow component, except that they apply at all times during a campaign. As soon as a user meets the global exit criteria, they are removed from the campaign. A practical example lies in the default campaign: if a user becomes a signup at any point, we no longer need to request their name and email, so they are exited from the campaign.

Statistics

Pavior shows you rich statistics for your campaigns. Each campaign component will show an icon with the number of people that the component acted on. You can click the icon to drill down and see the individual users that interacted with the component. But Pavior lets you go even further! You can rewind time on any conversation or form submission to understand exactly how users are interacting with your campaign

Feedback or clarification