In this video, I explain the possible reasons why a bot may not respond to a message. I discuss two main factors: credits on the Offerbolt account and the assignment of a user. I also show examples of different types of messages and how the system responds to them. Finally, I explain the concept of a Do Not Contact (DNC) pipeline and how to manually contact a contact in that pipeline. Watch this video to understand why your bot may not be responding and how to handle different scenarios.
Objective is to troubleshoot and identify reasons why the bot may not be responding to messages effectively.
Understanding Why the Bot is Not Responding
Initial Message Not Responded to
Lack of credits on Offerbolt account
No user assigned to the message
Contact may have indicated wrong number, do not contact, or no longer own the property
Actions Taken Based on Contact Response
Contact marked as Do Not Disturb (DND) if they indicate any of the above
Contact placed in a pipeline
Bot turned off for further communication with the contact
Re-Engaging with Contacts
Manually contacting contacts in the DND list if needed
Ensuring DND settings are unchecked to resume contact
Bot will only respond to a DNC contact if the automation fails to pick up a phrase
Bot Response to Lack of Interest
Bot may ask for a better time to contact or similar message
No further messages until a three-month follow-up
Manual follow-up if necessary, as the bot is meant to shut off to avoid unnecessary back and forth after determined lack of interest of contact
Summary of Circumstances Where Bot May Not Respond
Lack of credits, no user assigned, contact indicating specific responses, contact marked as DND, lack of interest, and three-month follow-up protocol