One time actions

Effective communication is critical for a business, especially when it comes to delivering timely and urgent messages to customers. In exceptional circumstances, businesses may need to contact all, or a subset of their customers, outside of their regularly scheduled updates. For example, if U+ Bank temporarily closes one of its branches due to maintenance activity, it should send out an email communication to all customers, or those who are affected.

In such scenarios, you can send out the communications using one-time actions.

A one-time action is a batch communication that all or a subset of customers receive at a specific date and time, that is not coordinated with the always-on outbound schedules. These actions are created in a Business Operations environment to deliver one-time urgent or time-sensitive communications that do not repeat automatically.

When should you use One-time actions?

One-time actions are sent when the communication:

1. Must be sent to all or a group of customers.
2. Must be sent at once to all the customers and should not be repeated.
3. Communication is to be sent outside the regular outbound schedules.

To create a one-time action, you must choose the relevant tile while creating the change request.

 

Examples of one-time action change requests include:

• An emergency communication to all the customers from the CEO.
• Compliance notice notifying customers of changes in benefits and terms.
• Announcement of a branch closure.
• Communication of services outage due to maintenance activity in an area.

Unlike always-on actions, no engagement policies or constraints apply to one-time actions. One-time actions use a defined audience, and all the members of that audience receive the same message at the same time. These actions can be created and deployed to production through both standard release and fast-release revisions. However, as most one-time actions are used for immediate communication, it is recommended to use fast-release revision for deploying one-time actions.

The following figure shows which policies and constraints apply to different outbound interactions:

---

This Topic is available in the following Modules:

• Implementing outbound communication in BOE v1
• Implementing outbound communication in BOE v2
• Implementing outbound communication in BOE v3
• Implementing outbound communication in BOE v4