Offerbolt

In this video, I explain how notifications for unassigned users work in our workflow system. I detail where these notifications trigger from, how they are related to initial SMS, and the process of fixing them. I show how contacts move through the system, the importance of assigning users, and how the workflow recycles contacts. Viewers are instructed on prioritizing and fixing unassigned user notifications promptly.

The objective of this video is to show users how to identify and resolve notifications for contacts that have not been assigned to a user in the initial SMS workflow.

Understanding Notifications for User Not Assigned

- Notifications for user not assigned are triggered from the workflow, specifically from the initial SMS.

- Contacts are added and move through the workflow.
- Contacts split based on the time of day (9-12, 12-4, 4-8).

- If contacts fall into for example the 12-4 time frame and no users are assigned, a notification for user not assigned is triggered.

- Contacts without user assigned to them get filtered out and tagged as user not assigned.
  
   
- They are temporarily placed in a pipeline for user not assigned while being recycled back to the top of the workflow.

- Receive internal notifications for user not assigned.
- Prioritize assigning users during the relevant time frame (e.g., 9-12,12-4, 4-8).
- Add users to the appropriate sections to prevent further notifications.

- Notifications occur when contacts enter the workflow without user assignments.
- Quick fix involves adding users to the assigned section to auto-correct the issue.

- If users were not created for the workflow, draft and save the workflow to pause it.
- Create users, assign them to appropriate sections, and publish the workflow to resume functionality.

- Handling notifications for user not assigned is crucial for workflow efficiency.
- Promptly addressing user assignments ensures smooth workflow operation without losing contacts.

1. Trigger Point:
 - Notifications for user not assigned are triggered from the workflow, specifically from the initial SMS.
2. Workflow Overview:
 - Contacts are added and move through the workflow.
 - Contacts split based on the time of day (9-12, 12-4, 4-8).
3. User Assignment Section:
 - If contacts fall into for example the 12-4 time frame and no users are assigned, a notification for user not assigned is triggered.
4. Filtering Process:
 - Contacts without user assigned to them get filtered out and tagged as user not assigned.
 
 
 - They are temporarily placed in a pipeline for user not assigned while being recycled back to the top of the workflow.
5. Handling Notifications:
 - Receive internal notifications for user not assigned.
 - Prioritize assigning users during the relevant time frame (e.g., 9-12,12-4, 4-8).
 - Add users to the appropriate sections to prevent further notifications.
6. Root Cause and Quick Fix:
 - Notifications occur when contacts enter the workflow without user assignments.
 - Quick fix involves adding users to the assigned section to auto-correct the issue.
7. Workflow Adjustment:
 - If users were not created for the workflow, draft and save the workflow to pause it.
 - Create users, assign them to appropriate sections, and publish the workflow to resume functionality.
8. Conclusion:
 - Handling notifications for user not assigned is crucial for workflow efficiency.
 - Promptly addressing user assignments ensures smooth workflow operation without losing contacts.

Learn why a user would receive a user not assigned notification from the Initial SMS Workflow