1. Issue: Difficulty in identifying the cause of unsubscriptions

An agricultural company operates an online mail-order business that delivers vegetables from local farms nationwide. The mail-order team regularly sends out email newsletters to repeat customers introducing seasonal vegetables and recipes.

The newsletter was generally well-received, and the person in charge had put a lot of effort into creating the content. However, there were still requests to stop receiving the newsletter without the reason being known. The team wanted to understand which emails were causing people to stop subscribing in order to improve the newsletter content.

However, because the sending and stopping processes were performed in separate processes, it was not possible to identify the email that caused the problem without comparing the records of both. This meant that analysis took a long time, delaying improvements to the content of the email newsletter and reviewing measures.

2. Solution: Coordinate delivery and suspension between parent and child processes

The process owner has now linked the distribution and unsubscribe processes, which were previously performed separately, as parent-child processes.

Specifically, they incorporated a Service Task into the parent process that delivers emails, which calls a child process that executes the unsubscribe process. This automatically links the parent and child process IDs, allowing them to correlate and check the delivery and stop history of each process.

As a result, mail order team members were able to accurately identify who had been sent the email and which email had triggered the suspension.

Accurately identify the specific emails that triggered unsubscribes to refine your strategy.

3. Customers Case Study

4. Other Business Applications

We will enable AI-based reviews for the following tasks:

5. Related Posts