
Auto-branching by contract length skips unnecessary emails, reducing workload and errors.
1. Issue: Burden of reviewing the renewal confirmation email list
A company currently, approximately 30 client companies have outsourcing contracts related to DX promotion support. Contract periods range from one month to about one year, and around 80% of clients renew their contracts. The sales department’s contract management staff send renewal confirmation emails to clients 60 days and 30 days before the contract end date, based on customer information registered in the system.
These sending schedules are automatically set in advance based on the contract end date. Staff members check the delivery list ყოველდღ and send emails to the relevant clients after confirming there are no errors. However, for contracts with short durations, there is a possibility that renewal confirmation emails may be sent shortly after the contract begins, which is not appropriate.
Therefore, staff needed to check not only the number of days remaining until the contract end date but also the contract duration each time to determine whether the email should be sent. Since this verification task occurs daily, it created a significant workload and introduced risks of judgment errors and oversight.
2. Solution: Automatic branching based on contract duration
The process owner incorporated a branching event before the renewal confirmation email sending step, where a decision is made based on the contract duration.
Specifically, if the contract period is less than two months, the workflow branches to a route that skips the 60-day prior email sending step. If the contract period is less than one month, it is configured to skip the 30-day prior email sending step as well.
Automation reduces manual checks and improves contract management efficiency.
Before




View details of the workflow diagram
Customer Registration
The sales representative registers the customer information.
x1.Scheduled Sending Date and Time
The scheduled date and time for sending contract renewal confirmation emails are automatically set based on the registered customer information.
2.Sending Approval (60 days prior)
The contract manager reviews the email content and scheduled sending date 60 days before the contract end, and approves the email for sending after confirming there are no errors.
Pending (60 days prior)
The process waits until 60 days before the contract end date.
Send 60-day prior notification email
Send an email to the customer.
3.Sending Approval (30 days prior)
The contract manager reviews the email content and scheduled sending date 30 days before the contract end, and approves the email for sending after confirming there are no errors.
Pending (30 days prior)
The process waits until 30 days before the contract end date.
Send 30-day prior notification email
Send an email to the customer.
After




View details of the workflow diagram
Customer Registration
The sales representative registers the customer information.
x1.Scheduled Sending Date and Time
The scheduled date and time for sending contract renewal confirmation emails are automatically set based on the registered customer information.
Branching
If the contract period is two months or longer, the process proceeds to the “2. Sending Approval (60 days prior)” route. If it is less than two months, the process moves to the next branching point.
2.Sending Approval (60 days prior)
The contract manager reviews the email content and scheduled sending date 60 days before the contract end, and approves the email for sending after confirming there are no errors.
Pending (60 days prior)
The process waits until 60 days before the contract end date.
Send 60-day prior notification email
Send an email to the customer.
Branching
If the contract period is one month or longer, the process proceeds to the “3. Sending Approval (30 days prior)” route. If it is less than one month, the process proceeds to the end.
3.Sending Approval (30 days prior)
The contract manager reviews the email content and scheduled sending date 30 days before the contract end, and approves the email for sending after confirming there are no errors.
Pending (30 days prior)
The process waits until 30 days before the contract end date.
Send 30-day prior notification email
Send an email to the customer.


3. Customers Case Study
Honda Motor Co., Ltd.
Used for Company-wide Approval Flows such as general affairs applications, training recepti…
View MoreToho Gas Network Co., Ltd. (Negotiation and Design Section)
500 Applications Per Month Completely Digitized! Reduced Labour and Eliminated Printing and…
View MoreNippon Light Metal Co., Ltd.
Enhanced Quality Assurance through Visible Progress: A Continuous Improvement Cycle
View More4. Other Business Applications
We will enable AI-based reviews for the following tasks:
Subscription contract renewal management
Customer follow-up timing management
Customer Master Synchronisation Process, Google Sheet Integration
5. Related Posts
-

Contract Renewal Email Process Automation
View More: Contract Renewal Email Process AutomationAuto-branching by contract length skips unnecessary emails, reducing workload and errors.
-

Documents Ready! Automated Sharing Before Sales Meetings
View More: Documents Ready! Automated Sharing Before Sales MeetingsTo prevent lost files and incomplete minutes, URLs will be auto-posted to chat.
-

Automating the Often Forgotten Task of Meeting Minutes Creation
View More: Automating the Often Forgotten Task of Meeting Minutes CreationDefining roles and automating shares ensures every meeting is documented without fail.
