Transcription
A common question we get is, "How can I use this for database reactivation?"
If Closebot isn't sending the first message, how is this possible? Well, it's actually easier than you think. All you have to do is have the first message send from your system. If you're using HighLevel or HubSpot, for example, you send the first message to the contact. Have an agent with your job flow connected to that source, and when they respond to that first message that you sent, boom, your agent is there to respond.
Now, keep in mind the message you sent is what they'll be responding to, so make your first objective line up with the first question you ask them to elicit a response. More likely than not, your first question to them is some version of, "Are you interested in our service anymore?" So it makes sense to have the first objective be interest. The short description for that would be, "Determine whether or not they are still interested in [blank] service." At that point, they are going to continue.
Now, something you can do here is you could do a branch to branch to different things if they're interested versus not interested, or you could have a custom scenario that's always listening for whether or not they're interested. That's helpful because if they get through here and maybe they initially say they're interested, but then later on while we're qualifying them they say, "You know what, never mind, not interested," a custom scenario is always listening. So in that case, it would jump down here: we have it tag them as not interested in our source, so in HighLevel or um in HubSpot, and then stop responding. And that's how you do things like database reactivation in Closebot, where you are sending the first message.