Post Campaign Trigger

Post-Campaign Trigger, as the name suggests, is an event that triggers based on user response to the campaign template, whether button-based or general text response. These triggers help keep customer data current and relevant based on the selected campaign status (filter) and the action concerned.

Note:

Post Campaign Trigger is not a campaign. It's an event that triggers after a campaign is launched based on user response.

Different Events In Post Campaign Trigger

The Post-Campaign Trigger is initiated based on specific conditions/filters. In this case, two primary conditions are considered:

Notification Send

This condition triggers actions based on the status of the sent notifications. The primary options in this are:

  1. Sent: The event triggers when the notification is successfully sent to the user.

  2. Delivered: The event triggers when the sent notification reaches the user's device.

  3. Read: The event triggers when the user opens and reads the sent notification.

  4. Failed: The event triggers when the notification fails to deliver.

You get two conditional logic to opt from, specifying what event condition should be, to start post campaign trigger.

Conditional Logic In Notification Send
  1. Is (True, False)

    • If you choose "Is True," it means that the event will occur only if the specified condition is true.

    • If you choose "Is False," it means that the event condition will be satisfied if the specified condition is false.

    Example:

    • If you set a condition like "Notification Sent Is True," the event will be triggered only if the notification sent is true, i.e., notification is sent to the user.

  2. Is not (True, False)

    • If you choose "Is not True," it means that the event will occur only if the specified condition is false.

    • If you choose "Is not False," it means that the event will occur only if the specified condition is false.

    Example:

    • If you set a condition like "Notification delivered and then logic as Is not- False, the event will be triggered only if notification is delivered to the user.

Notification Replied

  1. Button Reply: The event triggers when the user responds to the notification using predefined buttons in the template.

  2. Text Reply: The event triggers when the user responds to the notification with a general text reply.

You get many conditional logic to opt from, specifying what event condition should be, to start post campaign trigger.

Conditional Logic In Notification Replied
  1. Is

    • Condition is met if the user response, whether a button or text reply, is exactly equal to the entered value.

  2. Is not

    • Condition is met if the user response, whether a button or text reply, is not equal to the entered value.

  3. Contains

    • Condition is met if the user response, whether a button or text reply, includes the entered value.

  4. Not contains

    • Condition is met if the user response, whether a button or text reply, does not include the entered value.

  5. Starts with

    • Condition is met if the user response, whether a button or text reply, begins with the entered value.

  6. Ends with

    • Condition is met if the user response, whether a button or text reply, concludes with the entered value.

  7. Has any value

    • Condition is met if the user response, whether a button or text reply, has any value, not empty or null.

  8. Has not any value

    • Condition is met if the user response, whether a button or text reply, does not have any value, empty or null.

You can select a maximum of two event conditions, one from notification sent and other from notification replied, to start the post-campaign trigger.

Selecting the above filters as an event condition, Chatman allows you to perform several actions to keep customer data updated and relevant that initiates the post-campaign trigger.

Below are all the actions with explanations and purpose:

Create/Update Attribute
  • Definition: Adding or modifying user attributes based on their notification interactions.

  • Purpose: Ensures that user profiles are dynamically updated with relevant information.

Assign Conversational Label
  • Definition: Labeling the conversation for organized reference.

  • Purpose: Facilitates easy categorization and retrieval of conversations.

Assign Tag
  • Definition: Associating a tag with the user based on their notification interactions.

  • Purpose: Streamlines user categorization for targeted communication.

Subscribe/Unsubscribe
  • Definition: Including or excluding the user from further communications.

  • Purpose: Respects user preferences based on their response to the campaign.

Assign to an Agent/Group
  • Definition: Assigns the user to a designated agent or user group for personalized follow-up.

  • Purpose: Improves efficiency in handling user queries and providing tailored support to queries/issues faced during completing the campaign and etc..

Create Post Trigger Campaign

Suppose you want to run a campaign for a segment of people with user tag as 'sale enthusiast.' But people might have changed their mind so you want to omit all those people from the segment who select not interested in the template.

Further, you also want to exclude all those people from the segment whom notification fail to deliver.

How do you that?

  1. Define Event Conditions

  • Choose an event condition based on notification send or reply.

Set Different Events

Sent: This means that your message has been successfully sent to the cusotmer server. You can use this status to track the delivery rate of your campaign, or to send a follow-up message after a certain period of time.

Delivered: This means that your message has reached the recipient’s inbox. You can use this status to measure the success of your campaign.

Read: This means that the recipient has opened your message and viewed its content. You can use this status to gauge the interest and engagement of your audience, or to trigger a survey or a coupon when someone reads your message.

Failed: This means that your message could not be delivered to the recipient for some reason, such as a bounce, a spam filter, or a block. You can use this status to identify and fix any issues with your message deliverability, or to resend the message to a different address or at a different time.

Replied (text reply, button reply): This means that the recipient has responded to your message, either by typing a text message or by clicking a button. You can use this status to collect feedback, confirm appointments, or segment your audience based on their responses.

As per the scenario, the first condition is that the user replies as 'not interested' to the template. Therefore we select button reply, set conditional logic 'Is' and enter the value as Not interested.

insert

  1. Choosing 'AND' 'OR.'

  • Select AND if you want the post-campaign trigger to run when both filters are applicable to a user.

  • Select OR if you want the post campaign trigger to run when any one of the filter applies to the customer.

For our scenario we select OR as we want to exclude people who select not interested and also to whom notification fails to deliver.

insert

  1. Choose second event condition

  • Opt for second event condition, only if required.

For the scenario above, we need to add a second condition for excluding people to whom notification fail to deliver. For this we select Notification Send>Failed, set conditional logic 'Is' and opt for true.

insert

  1. Actions

As per the above scenario we need to do unsubscribe people from the segment 'sale enthusiast.'

So we select Subscribe / Unsubscribe and opt for Unsubscribe and from select segment, choose Sale enthusiast.

insert

When the campaign is launched all those people who tap 'Not Interested' in the template and to whom notification fail to deliver are unsubscribed from the segment 'Sale enthusiast.'

You can set post campaign trigger for any of the campaign: one time, triggered, recurring or the drip campaign.

Last updated