Transcription
Welcome. By the end of the video, you are going to configure a conversational AI text bot for real estate investor clients, because this is my own qualification bot that I use in my real estate investment company.
Now, the reason I'm making this video is because, at the time of recording, Closebot is mid-transition from version one, aka Classic, to version two, aka purely Closebot. Now, this entire transition is monumental; it's basically a new product, but we'll get into that in a second.
If you're new to the channel, welcome. My name is Justin, and I like to create videos just like this, showing you how I solve problems in my business, in businesses of my clients, and those in my community.
Now, if you're new here, I run a free community called Automation Station. Everything I cover in this video will be given away here in the Automation Station community. As you can see, there's over 1.9K members at the time of this recording. How you can find the resources for this video: for example, I'm going to give away this bot template. So, you can just click the link and import it. You come over here to video announcements, and then you just search for the title of this video or potentially the upload date. You can come over here, pop it open, and if there are any resources, they will be provided to you either in links or in a file.
So, enough of that. Let's go ahead and move on. I want to cover a few key things. I'm going to do a few of these videos, but I'm going to cover this on this first video just to highlight some changes inside of Closebot, but also to give you some background on what I use Closebot for.
So, first and foremost, if you don't know what Closebot is, Closebot is—let's see if we can go to the homepage here—uh, closebot.ai. Closebot is a conversational text-based provider. They don't do voice at the moment, but they can qualify and book leads, as you can see here on their website. They're very good. They actually came out before GoHighLevel had their conversational AI. If you're choosing between GoHighLevel and Closebot, I really have no preference for you. I think you should just test both. They have a free tier, a pretty generous free tier. And Closebot also has, I think, their summer of AI going on right now. So try both and see what you like. I really like the drag-and-drop builder. And then I've also just built a business around Closebot. So I continue to use it. I have to migrate bots from V1 to V2 because I don't want to pay for two accounts.
So enough of that. Now let's co—let's cover some important notes here. So this is a complete overhaul. As I mentioned, it's basically a brand new product. Bryce and Laura, the team over at Closebot, the founders, they have completely developed a new product. You know, Closebot V1 was a little bit buggy. The interface was just kind of put together by Bryce and maybe a few other people. But now they've completely overhauled it and changed it to sort of a canvas style of drag-and-drop builder, similar to that of N8N, which we all know and love, or make.com, which we all know and love, and even GoHighLevel workflows. It has some similarities as well.
Now, as I mentioned, I have to migrate my clients over to V2 with as little interruption as possible. I'm starting with me as a client; this is my company that I'm migrating over. And I say little interruptions as possible—it's kind of false because what I'm actually doing is deleting everything. So, Closebot actually migrated me from V1 to V2, and all the bots migrated over. So, I could just click publish, but I don't like that because if anything goes wrong, I won't understand what's actually happening and the nuance in between these new bot builds. And so, I want to build it from scratch. So, there will be a little bit of downtime, especially as I record this. Some I just won't record because there's like personal information that I don't want to give out, but ones I can, I'll release here on this channel.
Now, rebuilding from scratch is counterintuitive. Yep. I'm doing it so I can learn. I want to learn the ins and outs of the system so that I can be more efficient in my builds and so I can teach you how to be more efficient as well.
Let's see. Bot exports, already mentioned, will be shared in the Automation Station community. So version one versus version two. This is by no means an exhaustive list of changes, but these are just changes that I find most notable in my business operations. And one is the drag-and-drop builder that I mentioned earlier, the canvas style drag-and-drop builder, which is awesome. Also has autosave functionality, which is pretty cool. We have expanded functionalities. We're going to go over some custom actions that are in there that weren't available inside of version one. And that's going to enable us to do more things inside of Closebot instead of relying on GoHighLevel workflows and just sort of hacking things together to make them work.
We also have the addition of webhooks. I'm excited for webhooks. We're not going to use webhooks in this video just yet, although we probably can because they have some real estate specific functionality, but I'm not going to change the game here. But webhooks are awesome, you know, for checking service areas, pulling information from external databases, or connecting to other CRMs. Pretty awesome stuff.
Uh, they also added support for HubSpot. So that I didn't write that down here, but that's a big deal as well. They have switch nodes. Switch nodes are essentially—uh, you can kind of change—before we would change bots, right? So we would have maybe two, three different bots. We would ask a question; depending on how they answered that question, we would use a workflow inside of GoHighLevel to switch the bot ID and change bots. It was just a big pain. Sometimes it worked, sometimes it didn't. But now they released what are called switch nodes. So now we can—we can define certain cases where they would go down a different route in the canvas, and we'll—we'll maybe see a little bit of that here. And then we can ask different questions, have a different set of objectives depending on how they answer. And the best part about it is is we can use AI to evaluate their responses and then determine their intent, which is powerful.
Then we have branching. We can like if statements, kind of like inside of GoHighLevel workflows, all available inside of the V2 builder, which is great. And then we have more custom scenarios. For—we were limited to one custom scenario. And what's a custom scenario? Let's say here's an example for a home service company. I have home service companies who we generate leads for. We qualify leads. We book leads. But every once in a while, we have people who reach out and say they're looking for employment. Well, if they're looking for employment, we have no interest in trying to qualify them as a lead. So that's a custom scenario that we built out. And so if the AI detects that they're looking for employment, then we will just turn the AI off. So that's a custom scenario. In version one classic, we were only limited to one of those. Now we can add multiple custom scenarios, which is very powerful as well.
And then there is a conversation node, and we're not going to use that in this video, but that is a powerful scenario or a powerful node for people who—let's say like a med spa that has a lot of returning clientele. We can now have an initial qualification bot, and then we can leave the bot on. Before we would turn the bot off, or I would turn the bot off so the bot wouldn't respond. But now we can like leave the bot on and just have general conversations to answer general questions, and we can pair that up with a new custom scenario saying if they want to reschedule, you know, a visit, then go down this route and schedule them. So really powerful stuff. That's just conceptual right now. I'm not going to cover that in this video. We're going to focus on my real estate qualification bot.
So current struggles I'm having with Closebot V2, and hopefully the team watches this. This is not a knock on them; this is a brand new product—product. It's actually pre-release. So, some of these struggles are going to get solved by the time June 9th, I think, is the official release date. But, I'm going to cover them. I'm going to tell you what my—my—my issues are. And right now, my current struggles is understanding the relationship between personas, job flows, providers, and sources. So, that's a lot. We're going to go over that, and I'm going to show you what they are. But, in the past, we had a pretty simple drag-and-drop builder. It was just like a bot. Let's see if I can pull one up here. We just had a bot. It had objectives. It had a main prompt and maybe some, you know, knowledge base. And that was it. But now there's sort of more components that we have to account for. And so I'm still trying to wrap my head around the relationship between them all and then also which settings are available inside of which menus. And I also think that Closebot has some room for improvement there. Uh, and I'll highlight some of those in this video. But just the amount of clicks and places you got to go to make a bot actually do what it needs to do, I think it'll get better over time.
Now, another struggle I'm having is migrating legacy workflow automations to version two native functionality. And what do I mean by that? As I mentioned earlier, we had to rely on GoHighLevel workflows in the past. We were like evaluating custom fields in order to do stuff like if somebody was interested, they selected yes, then we would continue. If not, we would turn off the bot. We needed like a GoHighLevel workflow to help us with that. We no longer need that. So in my current accounts and my current builds, I have a lot of workflow-dependent actions that happen. Well, now some of that stuff can just be migrated into Closebot, and we no longer need those workflows. So I have to identify those workflows; is I have to turn off those workflows or modify those workflows maybe and build that functionality into my Closebot. So, we're going to go over some of that today that I think there are some opportunities to see that here in—in this build.
Now, build efficiency. I am inefficient right now. I am still, like I said, I'm understanding the relationship between personas, job flows, providers, and sources. And so, I'm going to hop around a bit. I'm trying to get better. The reason why I'm doing this and getting the reps in and choosing to build from scratch is because I want to get better at building this and get more efficient and then share that framework and process with you.
What else? I'm struggling with where GoHighLevel variables can be used and where they cannot be used. So in the past I relied heavily on custom values inside of a sub account, and I would use those custom values inside of Closebot in order to fill in information. It made it easy for me to make changes because I just go into sub account, change the custom value, and it automatically updated the prompt. But now it seems that those custom values are not available. I'm not really sure. And so I think they've been replaced with what they call source values or source variables. Closebot calls it that. And so I'm still getting used to that. Uh, and—and again, I think all this will get better and more clear with time. And then, yeah, I just don't know if custom values are gone.
So, without further ado, we're going to go ahead and hop into the tutorial.
All right, so I'm here inside of my sub account. This is an active sub account. So, uh, let's see if I can pull—Yeah, here's the website. So, this is a landing page I have for flipping, wholesaling. I was generating leads, driving a ton of traffic to—to this website to try to find off-market properties, like a lot of real estate investors do. So, if you're a real estate investor or maybe if you work with real estate investors, this is going to be relevant to you.
Now, I no longer drive traffic to this site. I've been focused on building my agency, building my YouTube channel, building my community, but I leave this site up and I leave this—the bot attached because every once in a while, I have this brand and another brand that's very similar. I get a lead that just comes in organically and I'm not paying attention to it. So, uh, last month at like 11:53 p.m., a new lead came in. The bot was attached to it. It qualified the lead. It booked them on my calendar for a cash offer call. And then two weeks later, the same thing happened in the middle of the day. And both of those leads are actually—we have offers out on both of those leads. We haven't gotten any under contract yet, but there's huge potential on that stuff. So, I'm not going to turn it off. And I want to keep the bot active on those. So, this is the landing page that's out there. This is a form that somebody would fill out. And after this, we need to ask some qualifying questions, like I think it's like motivation, selling timeline, and then try to book them on the appointment. I think also people find me on this profile on Google. They might call, they might text, they might find the page on Facebook. And so I want to make sure all—all of that works. So let's go over, and I'm going to look at some of the legacy stuff.
So I'm here in automations inside of the sub account. This is a really old bot. This is the old way that Closebot used to do business with all these workflows. They've since consolidated it in Classic to one workflow, and now in version two, you don't need any workflows to make it happen. Now that's not necessarily going to be the case for us. I'm going to have some workflows that add functionality to my bot, but all of these need to be drafted because this is all version one stuff. So, I'm just going to come in here and draft all of these workflows. And I'm going to go ahead and annotate some that I might be interested in continuing. And so, let's see here. Let's draft all these.
All right. At this point, every workflow for Closebot version one classic's core functionality should be disabled. This bot should be neutered. If I put in a new—a new lead here, it—I should—if I submit a new lead, it shouldn't respond and—or it'll get the initial—initial message, but the bot shouldn't engage. Okay, I'm confident in that. I'm not going to test it and waste time.
Now, there's another thing that happens here. So, I have another tool here where I do goal setting. And so, I'm going to draft this for now because this goal setting workflow relied on me evaluating custom fields in order to, you know, list something as—as—as qualified or not. So, if I come in here, you see that this is triggered by motivation and timeline. If the goals accomplish that, which is a custom field inside of the contact, contain motivation and timeline, we'd go down—make sure we have both motivation and timeline, and then we have different states that we were evaluating and then we determine if they were qualified or not and send it a notification to the team. This was before they booked. So remember, you can have a qualified lead that didn't book. Uh, and so that's what this was for. And I think we're going to simplify and modify this uh so that we can take some of this and actually move it to Closebot. So, this is one that I'm going to target. Let me make sure there's no other ones. So, I think we have some follow-up stuff here. No answer. Follow-up. So, yeah, this one we might actually be able to—Let's see. What is this triggered by? Contact tag. No answer. Okay, I'm actually going to add—So, this is if somebody doesn't answer, we have a follow-up sequence. And what I'm going to do is actually I need to add functionality to remove a contact from this workflow if they respond. And so I'm going to try to build that into the Closebot V2 workflow. And what else? What else? That's it. That's it for now. I'm just going to draft this so I know what I'm working with. Okay.
All right. So, let's go ahead and move on. So, now we are in version one. Let me review the functionality of this before. So, we have a main prompt here. A lot of this stuff is just going to transfer over minus our custom values. Let's see if I could zoom in here a little bit so you can see. Remember, our custom values are not necessarily—they're not working the way I—I thought they would. Um, and then also it looks like, yeah, some custom values don't work. So, we're going to have to modify some of this. Uh, objectives, probably the most important part here. We're going to have to build this out inside of our canvas. We have address, email, phone number, timeline, motivation, and attempts. Okay, cool.
If I come here to integrations, you see that we're currently integrated inside of uh GoHighLevel. So, what I'm going to do here is I'm going to remove this integration, but instead of doing it from here, I'm going to see if I can actually come into Closebot because I migrated, and Closebot moved everything over. These integrations are now known as sources. So, if I come in here into sources and I search for flipping home buyers, you see we have a source and with a job flow connected, I'm just going to uninstall this source, and it should pop open a—pop me into the app marketplace. So, let me just go ahead and log in here.
All right. Took a second to log into GoHighLevel. Uh, so now it should just pop into the sub accounts app marketplace so I can delete the—the sources.
All right. So here is the Closebot app. So it shows that it's not installed, which is interesting. Uh, let me come over here and just make sure there's no installed apps. And there is an installed app. Okay, so this is an issue that I've had. So right now you see that this distribution—distribution type is agency and sub account. If I click uninstall here, I actually can't uninstall it because it says that it's managed at the agency level. And if I go to my agency level, this bot—this—this app is not installed. So I've reached out to Closebot about this. I've also reached out to GoHighLevel. If you reach out to GoHighLevel support, they will be able to manually remove this. However, I've talked to Bryce and the team, and they said that this no longer plays a part. Uh, so they've—they've handled it on their end. Before, the symptoms I was getting is if I had—because we're about to install another app—and so if I had this app installed and the new GoHigh—and the new Closebot app installed, the bot would respond twice. It would wig out or do all—a bunch of weird stuff. Well, I think Closebot has since handled that on their end. And so we're going to test that here. But what I am going to do is come in to my classic account, and I'm just going to remove that uh integration there. That shouldn't delete the app. I don't think it's going to delete the app, but I am going to remove that integration so that this V1 bot is no longer active. I'm going to give that a second to stop spinning. And there you go.
Now, I'm going to come in here, and first thing I'm going to do is go to agents, and I'm going to create a persona. A persona is sort of the bot personality, as I understand it. One of the frustrations I have with personas is I typically have very standard personas that just have different names. And so I wish I could use a variable here in the persona name. And maybe I can. I'm not sure yet. Um, but I—I—it doesn't look like it's, you know, it's going to fill. So I'm going to just go ahead and create the persona. And I'm going to create a persona for each bot right now. Uh, and hopefully Closebot sees this feedback and either just tells me I'm wrong and I can fix it or maybe they make an update. So if I come here to the main prompt, the—the persona is probably—is—is pretty much just this—how to respond section and the name and a few other pieces of information. So you see here we have the name of Alex. So if I come to persona name, I'm going to say Alex. And then in the description, this is just internal. I'm going to say
Flipping home buyer bot. I can upload an avatar if I wanted to, but I'm going to skip that for now. I don't have any response delays, frequency, AI typos, and breaking up larger messages. I don't have any of that configured, but I do have how to respond instructions. So, if I come back here to my main prompt and I copy this, all this is going to be provided in the link. So, whenever you import this into your Closebot V2, um, it should just show up.
So, let me see if I can extend this a little bit. So, again, I don't know if these variables even work in here. Closebot, please let me know if they do. It's kind of hard to tell. So, instead of contact name, I'm going to use the @ lead name decorator or variable. Uh, I think this works inside of closebot. So again, new to this. So let's see. Don't tell @ lead name that you are a bot. If contact name asks you, right, let's change that to lead name. These are just guidelines for how the bot should respond. Maybe guardrail some people would call them. All right. You should sound, you should not sound like an assistant. This means not using contact name in all your responses. All right, we gave an example here. This is an old bot, so I have some legacy stuff that I wouldn't necessarily do here, but that's fine. We're going to keep it as it is. We're going to try to transition as as uh one to one as possible.
So, you see here for bot, we have friendly and confident. So, I'm just going to go ahead and type in friendly and confident and then click next. And then our provider. So, providers are our API key. So, one of the nice things about Closebot V2 is you can now rebuild your clients for AI usage. And so, before you might have asked your client to get an AI key uh from OpenAI, from from Enthropic, or maybe you added your own and then you rebuild them manually somehow, or you didn't rebuild them at all. Now, we can actually just have, I have two main keys. I used to have hundreds of keys. Now, I have two main keys. So, I'm just going to go ahead and select my API key for closebot and my API, I'm sorry for OpenAI, and my API key for uh anthropic. If you needed a new provider, you can come over here, drop down. You see they support Gemini, Deepseek, and Grock. Uh, you just need to get your API key from there. I'm not going to cover that in this video. There's tons of resources out there showing you how you can get your API key.
Now, this is the priority and which API provider that they use. I think this one we have set to Closebot. Yep. So, we, I'm sorry, I keep saying closebot. We use OpenAI first and then Enthropic. Next, you can make that change if you want to or modify this. Anthropic tends to be more conversational, so people doing stuff over like Messenger or WhatsApp might want to use Anthropic, but I've just used Open OpenAI. It seems to get straight to the point and do its thing. This bot actually, this bot and another bot that I have for another brand that I'm not mentioning here is really good at booking appointments and it's really good at at asking the qualifying question. So, it's had a lot of success. I want to change it. So, we're going to go next and it we can go ahead and create this persona.
So now that this persona is created, it's not assigned to anything just yet, but next thing we need to do is create a job flow. And a job flow is sort of this whole like objective map, a combination of this main prompt and this objective map. And a job flow plus a persona equals a bot from what I understand. Correct me if I'm wrong, Close bot. But right now, we have a persona that's not a bot. We need a job flow to connect to it. So what I'm going to do here is I'm going to add a new job flow. And I'm going to say flipping home buyers feed 2. And then there's groups. Okay, so these are like folders. I I I don't have any groups right now. So I'm going to keep this just like it is. And then it asks us what what kind of source this is. And so you see we have highlevel sub account, lead connector sub account, which is just the gray label for high level. We have HubSpot and web web hook. I'm going to go ahead and select high level. I'm going to just search for flipping home buyers. Okay. And then filter by tags. Okay. So, we have that connected. I I feel like this is going to cause issues, but we're we're going to do it live because I wanted to remove that source and then read that source because I don't really even think that the app is installed correctly, but we'll see.
Uh, so here we have filter by tags. Um, okay. So, we have an AI off tag here. Now, something interesting that I've realized inside of my transitions is that like the AI off tag sometimes comes in with no space in between AI and off, and that's just a major difference. And so, sometimes the bot doesn't actually turn off. So, I'm just going to go ahead and let's see if I can, can I add a tag here? I can't. Okay. All right. I'm going to leave this here for now. And hopefully it works as we expect. But if not, we might have to go ahead and add a tag inside of our sub account. That's AI off with no spaces. and then add that to the list of tags to pay attention to. And if those tags are added, do not respond. Channels here, we're going to respond to all channels, but if I wanted to limit channels, like a lot of times I don't respond to IG messages because a lot of people are sending reactions and doing personal things on IG. And so just know if if no channel is selected, all channels are selected. Kind of counterintuitive, but if you actually start selecting things like SMS, you can actually be particular and deliberate about which channels they respond on. And so I can technically do this. Yep. We don't want IG WhatsApp. We don't really use WhatsApp, but I can technically do this. Um, but what I'm going to do is just exit all that and respond on all channels because I don't even have an IG. Uh, I think I don't, I actually I do have an IG for this and I don't do any personal stuff on that IG. So if somebody messages me on that IG, I want the bot to respond. So we'll just do that. Click next and then we're going to start from scratch. They have templates from a prompt from marketplace. So, it looks like these two aren't quite working yet, but I'm just going to go ahead and start from scratch and deploy.
All right, first things first. We're going to come over here and we're going to start building out our objectives. Actually, we're not. We're going to build out our main prompt first. So, I'm coming over here to the main prompt. If I come here to settings, you see we need to select a persona. So, I'm going to go ahead and select my Alex persona. And then I'm going to go over here to job information. You see why this conversation is happening. I'm just going to come over here, copy this, and make some modifications. Now, you notice here if I use a variable in here, I just put this open squiggly bracket and it popped up this little menu. If I wanted to do it manually, I can click this plus icon. And if I select a variable here, it it it shows up like this, tells me it's working, right? That's my indicator that it's working. Could be wrong. I'm not sure. Look at the documentation. Ask the support team. But on this side, there is no like easy fill indicator. And I have no clue if these custom values are actually working. And so I'm just going to remove these custom values because I'm having to create a job flow and a persona for each one of my bots. I can just say who this person is here instead of using a custom value. I'll solve that problem later on. If I wanted to create a bot that worked with multiple people, um I I'll try to solve that. But for now, we're going to keep this here. So you're confident investor named Alex at location name. So in I've tested this. If I just do location name and I ask the bot where do you work? It doesn't know. It's kind of frustrating. Uh but if I put the actual name here, it does work. So uh something something that I've learned. Maybe it'll change before June 9th. Who knows? Which is uh the best uh best cash buying company? This company is well trusted in the community. So at lead name doesn't have to worry about a thing. The lead filled out a form either on our website. So I'm just going to put our website. Uh we don't even need to put the website in there. That's that's just fluff. Okay, cool. So, this is by no means the most optimal prompt that's out there. Okay, this is just what I had. This is just what was working. And I'm pasting it in here because I just need to get it to work.
All right. Now, I'm going to come over here to important business information. It's pretty brief and I think less is more here whenever we're dealing with uh whenever we're dealing with with with bots and AI. So, this company buys houses and can close on rapid timelines when needed and buy as is. We you remodel homes. Okay, this is used telling the bot. your model homes after purchase. So, contact name doesn't have to make any repairs. Let's see if I can uh get that to actually fill in. Uh so, if I go here, contact full name, I guess. Sure. Doesn't have to make any repairs. And so, location name, like it's not autofilling in here, but I know location name is a thing. So, if I come over here to location name, there you go. Location name is a local company that was built by location owner first and last. I'm just going to go ahead and put my name in there, Justin Melendez, because I don't see a Oh, I guess here. Location first name and last name. That might work. I don't know. Yeah, I'm not sure. I'm just going to put my first name and last name in there. Conversational rescheduling. We don't want to handle that. So, we're just going to move on. And if I had any variables here, so like I guess I can replace my custom values with this. Like if I had like business information here, I can go ahead and add a property and then later on I'd be able to fill that in. I'm going to leave that in here just for now so I could show you where that would be filled in because I can essentially take this business information. Let me go ahead and save and close this. Pop this open and then maybe inside of here. You see now we have source variables and that business information is in there and that's filled out in a in another location. I I'm still not really clear where I would use this versus custom values, but I'm sure it'll come in handy and become more clear as time goes on. But I'm just going to go ahead and save and close this.
Now, we need to start building out our objectives. And so, let's come over here and click on our objectives. You see, we're starting here. We're asking for the address, email, and phone number. Now, the reason I had these stacked up all in one is because we already had their address, email, and phone number. So, if it was already filled out, I didn't need it. But now, I'm going to do things a little bit differently because Closebot now has these sort of objective stacking and subobjective mechanisms. So, the first thing I'm going to do is drag and drop an objective here. And I'm going to go ahead and ask for the user's full name. Full name. And let's see. I just like using this as a template and copying it. So, I actually didn't even ask for the name here, which is crazy. But this thing's working. So, I'm just going to copy this and paste this. And let's make sure skip if not blank. Perfect. So, we want their name. Let's go ahead and add, I just clicked the plus icon here and it added a a subobjective. I'm gonna say email. Uh, email. I wish these were standard fields like they had in classic where they would just fill out the information for like standard contact fields, but it doesn't seem like it automatically does that for us. And so, I'm just using my version one or classic to copy over my descriptions here. So, here's my short description. And in the advanced settings, it looks like by standard there's an extra prompt, which I don't typically include, but I'm just going to try to keep it exactly as it is inside of version one. I'll add one more subobjective and we're going to call that phone number. So remember, if we already have this information, the bot's not going to ask it. But if it doesn't have it, it'll ask it. And when you stack them up like this, the bot will sort of ask it either simultaneously give it all give it all to me at once or it will step through those objectives as it sees fit. So we'll name this phone. And again, we'll come back here and look at the description for phone. We'll copy this. It says get at lead names phone number and says looking for a valid phone number. Cool. I'm just I didn't make those up. That came from Closebot. So now you see we have an objective filled out with two subobjectives. We have full name, email, and phone number. Uh these will get skipped again if they do not need to be asked. So I'm just going to go ahead and connect these two.
Now the next thing I'm going to ask, I'm going to create another objective and I'm going to name that address and I'm going to leave that all on its own uh because I want to do something different. So, if I come in here and I just search for address, you see we have full address, street address, city, and county. Um, I noticed if I ask for full address, the prompt is so strict that it wants them to provide like their street address, their uh their city, their state, and their zip code, and their and like if it doesn't have it all, it's going to keep asking, which is pretty annoying. And so, I'm going to break this down a little bit. I really just care for their street address. Uh, and state. I'm just gonna say street address and state because if I had that information, I feel like it'd be fine. Yeah, I feel like it'd be fine. All right, let's see what we have here. So, address, get lead names, address, and and I wonder if I could just add an extra prompt here because I like really the the city and state are not super important to me. So, if I add that in the extra prompt, I wonder if it would ask for the city and state. And if they don't provide it, it won't give them too much grief. That's kind of the effect I want. Street address is enough for me. Uh, especially because I know I'm only, you know, running this in Georgia and in North Carolina. So, I'm going to leave it at that right now as I I don't really want much more.
So, next thing I'm going to do is ask for motivation. And so, if I come over here, motivation, that's a tough one. So, we're going to add some limitations here because that's a sensitive topic sometimes for people if you ask like why are you selling your car or why are you selling your house? Some people don't like that. So, uh let's go ahead and fill out motivation. Now, motivation is a custom field that I created inside of the sub account. So, if I come over here to settings and then come down to custom fields, you'll see that in here. Oh, well, if I come to fields and search for motivation, I created this a long time ago and it's just a contact field, single line text that is motivation. Okay, so if you're doing this from scratch, you won't actually have this motivation custom field. You'll just have to come here, create it, add a single line. Next, and then type in motivation, and then go ahead and save it. Now, I already have it in there, so I'm not going to create that. So, here we have motivation. Let's go ahead and title this motivation. Close bot. You can autofill that, please. That would that would be awesome. I know you guys have a ton of stuff to uh to work on. So, on one of um Bryce's videos, he mentioned saying the word get a lot, like tell the AI exactly what you want. So, I'm just going to add get the reason for at lead name wanting to sell the property. And then in the additional prompt, we have you're interested in uncovering specific reasons why they're looking to get rid of their house. Not being too pushy, but genuinely curious about their situation. Cool. I made that up. I'm proud of that. All right. So, paste that. And then max attempts here. I'm just going to put the max attempts here to two. Remember, this is a sensitive topic. If we already have it, we're not going to ask it, but we're going to try twice. If it moves on, then cool. We're good to go.
All right. Now, um, let's see. I just thought about something. All right. Cool. We're going to go ahead and move on to booking. So, once we have their booking Oh, no. Timeline. We skipped timeline. Why don't you tell me that approximate timeline for sale? So, let's go ahead and remove this. So, if I click on this line and delete it because timeline came first, it's less of of a personal question. Uh, we're going to go ahead and insert timeline here. So, if I search here for timeline or I think it's selling timeline, what did I name it? Selling timeline. The title is selling timeline. If I come in here and copy my short description and paste it, approximate timeline for sale. get at lead names approximate timeline for sale and then I'm just going to copy this. Accept any timeline as being satisfactory. If lead name doesn't have a strong motivation, uh anticipate that they likely won't be interested in selling quick. Uh don't use the word timeline every time. Sure, whatever. This was working. So sometimes I don't know why I come up with certain things. Uh sensitivity was 50 and I didn't have any max attempts. Cool. Now we are save. We have some auto save happening right here. Um, and you see right here, you see this check mark means it's saved. So, we're good to go. I don't have to keep clicking save. But I do have to click save on the objectives in order for the objectives to complete. All right. So, now we have contact information, street address, selling, timeline, and motivation. Okay. I'm going to get fancy here. I'm going to get fancy here. I think I'm going to get fancy here. Yeah. Let's see. I'm going to see if I can use a branch. And I'm going to use a branch to evaluate true or false. Okay. And so I'm going to come over here and say qualified lead. I'm gonna say use AI at lead name provided a timeline and a motivation to sell their property. H do I want to do that? I actually only really care if they provided a timeline. I don't really care if they provided a motivation just yet. We're going to leave it like this. Okay. So what when we click use AI to respond, what should happen is that this node should determine if the lead using AI if the lead provided a valid timeline and a motivation to sell their property. Now notice I didn't fill in anything like I can not use AI to respond and then I can sort of compare values like I can actually come in here and look at the node and look at let's say like motivation result and then evaluate that like hey it contains this it equals this or whatever and determine like pretty definitively whether they gave like say it was like a number or an age if they're over 18 or whatever like you can do that but I'm just going to use AI to power this response because I'm I'm going to have AI and test if AI I can actually look at what happened in the conversation, determine if they provided a timeline and a motivation for selling the property. Now, I didn't really have this in this workflow or or in this bot before, but I did evaluate this in a sense using my goaling workflow that I mentioned earlier, right? Because we looked if they provided motivation in timeline. It's pretty static evaluation, but now we're going to use AI to do that. Okay? So, let's go ahead and save that. We'll see how that works.
And then, if they did, then what I'm going to do is I'm going to add a tag named qualified. And that tag is going to be used as a trigger inside of GoHigh Level to send a notification out. And so, let's go ahead and do this.
And the reason I'm doing this is because I want to notify a customer, which is me in this case. Hey, you had a new lead. They provided this information. They're engaging with the bot, and they're actually qualified. So I'm going to notify you of a new qualified lead. And then I'm going to notify you again after you book the appointment. But right now, I just want to notify you that you have a qualified lead.
So, if I scroll down here, there's an action called modify tags, which is new. I'm going to name this qualified, and the tag to be added is qualified. Now, I notice GoHigh Level doesn't like auto-populate your tags here. But what's cool is also if the tag doesn't exist, it'll automatically create it. So, I'm just going to go ahead and click save. And we're going to add the qualified tag.
And then what I'm going to do, I'm going to continue to build this out a little bit more because I'm still going to move to the booking objective regardless because maybe they don't want to provide me with the selling timeline and they don't want to provide me with the motivation, but I still want them to book on the calendar. Maybe they want to talk to a human or they want to talk to somebody on the phone to tell them that stuff. Um, or maybe they don't want to tell it at all and they still want to sell their house. So, we're still going to book them.
So, next thing I'm going to do over here is come over here and add the GHL booking objective, and we'll call this cash offer call. Let's come over here, see what descriptions I did. Book a 15-minute call with a qualified offer specialist for lead name. So, that's my short description. And my calendar name. Let's come over here to my calendars. And my calendar name is offer call. This is my first first time doing this. Excuse me. Uh, so hopefully I'm doing it all right. And then the calendar ID is this right here. So, I'm going to copy this. All right. Advanced settings. Anything else? Let me make sure. See if I have an extra prompt in here. Attempt booking for earliest available date and time. Sweet. I don't even think that's necessary, but we'll do that. Max attempts. Nothing. No. All right, we're good to go. So, I'm going to go ahead and save this.
And what's cool, and the reason I think they let you actually name these these calendars is because you can add multiple of these calendars. So if you have like, let's say like a med spa who has multiple services, you can now use a combination of like switch nodes or branch nodes and a bunch of different calendars to book on different uh service calendars, which is really nice, and before you would have to like use a custom field, fill out the calendar ID, make sure you get it right, and then it was just a mess, right? So this makes it a whole lot easier. So now we have uh our workflow here. So if somebody is qualified, we're going to add a tag, and we're going to do something with that tag here in a second, and then we're going to try to book them on the call. And let's say once they're booked on the call, we're just going to stop responding.
Now, I think GoHighLevel automatically adds an AI appointment booked uh tag. So, I don't need to manually do that. And this stop responding node actually adds the AI off tag automatically. So, I don't need to add the AI off tag. I don't think so. We're going to see here in a second. Now, let's see what happens if they're not qualified. All we're really going to do if they're not qualified is we're just not going to add the tag. But we are still going to try to book them on the call, and then we will stop responding. Awesome. I think that's all we need.
Now, I mentioned earlier that there were some like real estate specific There's an error saving my bot. I'm not sure why. We'll see here in a second, but um there are some real estate specific uh nodes here like verify address and get property details. This can probably be implemented into this bot to improve it, but again, I'm just going to keep it simple. This bot was working. I'm going to leave it as it is. So, I'm going to go ahead and click save. See if there's an error saving the bot this time. Okay, it doesn't look like there's an error. And then I'm going to click publish. Let me make sure. We have our prompt. We have our job flow. Sweet. Let's go ahead and publish it. I don't know if that's going to work. You need to unlock your iPhone first. Siri's going crazy. Sorry about that.
All right. So, here we go. And let's go ahead and what I want to do now is go to sources. And let's come over here and search for the sub account flipping home buyers. And you see we have two job flows. And the reason we have two job flows, I didn't mention this earlier, but in my migration, we actually had a bot that you see here, it's like published and drafted. Well, no, actually that's that's that's the one I just created. It's unpublished draft. This is the one that actually got migrated over. Uh, and I actually didn't even look at it. Let's pop into it real quick. I'm about to delete it. But if I pop into it, let's see what happened. Ooh, cool. So, we missed some stuff. We had aggression detected. But you see here, it was actually quite simple. It was more simple. We didn't have the evaluation on whether it was qualified or not. Uh, and it went straight to booking, which would have worked as well. But let's go ahead and add this aggression detected. Uh, just in case somebody gets aggressive with us, we can go ahead and delete that.
So, let's come over here back to agents. First thing I'm going to do is I So, I'm not tempted to use the old one. I'm just going to delete the old one. How about that? Uh, let's go ahead and delete this job flow. Let's come back in here and then let's add our aggression detected. So if I scroll down here to scenarios, we have aggression detected. Standard scenario. We that one autofilled, which is super nice. Uh, we'll leave that alone. And then I will add a contact tag. Modify tags. And we will say AI off. Add tag. AI off. So, if the person gets aggressive at any point in the conversation, that will happen. So, we're going to go ahead and save that and publish. I'm curious to see if I'm going to wait for all this to happen. I feel like this is a little excessive. Like, there's just like a lot going on here. Not really sure. Like, it's still saving bots. I'm not really sure what's happening here. Um, okay. Let's go back to agents. Let's make sure we're like all greened up here. home buyers. See, we have an unpublished draft. Not sure why that happens. Publish. Okay, now it says it's been published. Let's see. Let's see if that's actually true. There you go. Published. It's green. All right. Probably would have been fine. It was an unpublished draft. There's probably really no changes, but the autosaving function is kind of wonky right now.
Um, if I come over here to sources now and I look for the sub account, you see now we have only one job flow connected. Now, what I want to do is over here for flipping home buyers, I'm just going to edit this source. And this is important to do. So, before like this stuff, whenever you add a new source, this stuff isn't automatically um enabled. And so, because this was a uh a migrated one, it is, but uh I'm just going to go ahead and enable these. Graceful goodbye when goodbye is detected. Shut off on manual message. So if I manually respond to the lead or your client manually responds to the lead, then it will shut it off. It'll add the AI off tag. Then we have connected bots. It looks like uh flipping home buyers v2 is connected. Um, we have some tags here. We saw this earlier whenever we were modifying the sources. And then you have variables. So remember we added that source variable called business information. Well, you would actually have to go in here and add the information here in order for that information to be populated in the prompt if you use that anywhere inside the prompt or anywhere inside the objectives. Now, I'm going to leave this empty here, but I showed you inside of the job flows where you create these variables and then you fill out the variables inside of the sources. It's kind of confusing. You kind of have to like hop around. I'm sure there's a reason why they did that. Um, but I'm I'm just not used to it yet, but I'm going to leave that empty. I just wanted to put that in there as an example.
Then you have this neat thing called follow-up. So, we can actually automatically follow up and follow up on a schedule. And so here what I'll do is I'll follow up anytime Monday through Friday. And I wish I could copy these timestamps for every single one, but we can't. Yeah, actually do Monday through Saturday. And we'll follow up, let's say, 9 to 7. So follow-ups will not be sent outside this window. But let's say somebody stops responding to an objective. The bot's going to automatically follow up on the schedule that we're about to set in this time, like like in this time span. Now, it's not really clear. I bet it's using the contact time zone if I had to guess, but it doesn't really show it here. It's probably in the docs, but I'm not going to go over that right now. Let's go ahead and add a follow-up. So, we're going to follow up. I'm going to be pretty aggressive here in this follow-up because these are high value leads. So, first follow-up after 30 minutes. Then, we're going to follow up after, let's say, 3 hours. And then we're going to follow up after one day. And then we're going to add another follow-up after 1 day. And then we're going to add another follow-up after 3 days. And then we'll call it quits. But don't sleep on these follow-ups. These follow-ups are actually very powerful. Uh, especially in real estate, you make all your money in a follow-up, right? So, cool. We got that working.
And at this point, I think we have everything connected. We have a persona. We have our persona connected to our job flow. We have our source attached. So, we should have an active bot. And I'm going to test here in a second if that's actually the case. We can actually use the testing module here. Uh, see, it's showing we have unsaved changes, which is crazy. We don't have unsaved changes. But again, uh let's see if I go ahead and click test and start a new session. You see we're connected. So if I just say hello, we should get some interaction here. All right. Hey there. Thanks for reaching out. Could I get the best email address? I can send you some information about our process. Interesting. It asked for the email first. Don't know if I love that. Uh, so if this happens, I probably break up these objectives. You remember how I stacked name, phone number, and email into one objective? Uh, I'd probably break that up if I want to know their name first. But, uh, let's just play the game right now. Uh, just because I want to make sure it it I'm going to see how it reacts here just a little bit. And then I'm actually going to like submit a live lead so that we can actually see it work via SMS. Thanks. To keep things smoothly, can you please share your phone number? Sure. Uh, 900. All right, let me go ahead and send that. What's cool about this new testing engine though is that it shows you exactly what's going on, which is kind of nice. What's your last name? This is weird. I don't like the way this works right here with last name. So, I'm going to make a change really fast. Um, because like why is it asking for my last name first? It's just odd feedback for closebot here. V1 worked really well. Uh, I think they still have some things to work out here on V2. Great. Thanks. Like it only asked for my last name. It didn't ask for my first name at all. I wonder why. Maybe it's a nuance with the testing here. Like maybe it attaches like a guest first name or something. I'm not sure. Okay, I'm going to just go go ahead and go back here. I'm going to make some modifications to this agent because I don't like the way that that's behaving. And then we're just going to test it live. A lot of building bots is testing is is is doing it and then making sure it has the the uh the the behavior that you you like.
All right. So, first thing we're going to do here is ask for the full name. Let me just go ahead and copy from here. Get contacts full name. All right. And I'm going to delete this line. Actually, let me save this objective first. Delete this line. Drag that over here. Drag that over here. And then I'm actually going to come in here and remove full name. And then we just have email and phone number there. Sweet. Looks like it's saved. We're going to go ahead and publish that. And I'm curious. I'm actually just going to go to the test session one more time and see how it asks for that name before I submit a new lead because if I submit a new lead, I'm going to provide it with a full name. So, let's see. Hey there. Just so I can address you properly, can you please show your last name? This is very weird. It's only asking. Oh, contact has already filled filled first name. That's weird. Very strange. Okay, possible. Did it strange. I'm so curious why that's happening. I think that's why. So, it adds the guest name. So, I I think that's what's happening. So, the first name technically can't be tested, which is feedback. I I think I think this testing engine should ignore the guest first name. So, I'm going to leave it at that uh for for the testing engine. But, let's actually go ahead and submit a new lead. Um I'm going to come over here and let me I'm going to pause the video and just delete some information uh just in case I have a lead in here. I wanted to be able to interact. So, let's go ahead and pause this.
All right. So, I went ahead and I just had a contact that was already in there that I wanted to delete. And so, I'm just going to go ahead and submit a new lead here. Uh, I have a test account here that actually has an active phone number that can test. So, I'm just going to copy this because that's what I'm going to use to submit the new lead. So, we'll call this John Doe at 123 Main Street, Pineville, North Carolina. Fine. Uh, phone number is going to be that phone number that I pasted and email is going to be. And let's just go ahead and submit this lead. Awesome. So, that lead has now been submitted. My funnel has a calendar here in case they book. Good to go. We never need to talk to them. But let's see if we actually get a text message from lead intake. That should work because we didn't modify any any lead intake workflows. Let's see if uh automation bot not bot lead intake. Did that work? Why didn't that work? Let me make sure this is the right funnel page. All right. Right. So, one of the reasons it didn't work is because we had this main funnel form that actually was using this bot override message which relied on old uh it relied on old workflows to actually make that bot override message go out. And so now we just need to replace this with an SMS. And so I'm just going to come back over here to my bot override message inside of custom values. Again, if you didn't use a older version of bot uh close bot, then this doesn't apply to you. Uh, I'm going to go ahead and copy that and come back into my workflow. Not that one. This one. Mainfunnel form. And let's go here. So, let's just replace this with an SMS. I like to send a first initial SMS to introduce myself. Hey, this [Music] is Alex from Flipping Home Buyers. Okay. exclamation exclamation point can be a little intimidating. So, we'll click save. And then we add a wait step here. I'm going to add like 0.1 seconds 0.1 minutes, which is I don't know how many seconds. And then we're going to send uh our initial message, which is our um I guess this would be our initial. The other one would be our intro. Why did I paste that way? I just need to get a few piece pieces of information so that our team can reach out regarding your offer. Is that okay? Okay. So, this is going to be intro. We don't need the SMS word here. We'll click save. Awesome. And now we can delete this bot override message. And now when I fill out a main funnel form, we should be good to go. I forgot actually this this brand, Flipping Home Buyers, I was running pure ads to Flipping Fatville is the other brand that actually had the form on a WordPress site that triggered it. So, uh, I just enabled this workflow and then now we should be working. Form submitted is mainfunnel form. Perfect. Awesome. All right, let's go ahead and resubmit that and let's see if it works. So, I'm just going to refresh. Not now. John Doe 23 Main Street, Pineville. Let's go ahead and copy and paste our phone number that we had here. All right. And email will be IO. All right. Let's go ahead and submit that and see what happens. We should receive a text message here in a second. There you go. Hey, this is Alex from Flipping Home Buyers. Now, this isn't the bot yet. This is just a GoHighLevel automation. I just need to get a few pieces of information. Is that okay? So, if I respond yes, the bot should actually respond. Interesting. So, it looks like something else is I have a tattoo bot attached. This is weird. That's a weird That's weird behavior. Oh, it's because I have a bot attached to this as well to my to my vet. I have I have a tattoo bot attached to this vets washouses here. So, let me make sure that I actually delete this because that's going to go inside of an infinite loop. Oh boy. Let's delete this live. The joys of live testing. So, I'm going to draft this workflow really fast. Make sure I have nothing else in here. spot interactions turned off. Cool. Should be good. Shouldn't respond anymore. And just for good measure, what I'm going to do is add the AI off tag to this person. Yeah, you guys are you guys are seeing it all. So, I'm going to actually restart that conversation because I think that this is probably going to muddy up some of how it responds because I had the bot responded to it. So, let's go ahead and come into our contacts. I'm just going to go ahead and delete this contact. Awesome. Let me give that a second to delete. Just do the same on this side in the vets watch houses account, the test account we have here. I'm just going to delete that contact just so that we start from scratch. I guess the AI off tag is not going to matter here, but the AI should AI shouldn't respond anymore because we don't have it connected. And just to be sure, let's see if I can delete any of these marketplace apps in this sub account. I might be stuck in the same situation as I was before. And I am okay. It still should be good. So, let's go back here to conversations. Make sure. Awesome. That's gone. All right. Let's come back over here. Let's copy this phone number and go back. Refresh this screen. John Doe. Let's go ahead and submit this lead testing. The joys of testing and development. Um, you're going to have to go through the same exact thing. I leave this stuff in here for a reason because it it it it'll be you going through it and it's pretty it's it's pretty frustrating and so you have to try to track things down. So I'm going to go ahead and add the AI off tag here just in case there's anything connected. I don't want it to respond. All right. So just need to get a few pieces of information. Is that okay? I'm going to give it a second just to see if anything responds here because we had a bot attached to this account. Okay, cool. It's not responding. So, I'm going to just say yes. So, now we should only have the flipping home buyers.
Buyers bot in play. So, the bot already has our name, our email address, and our phone number. So, it should go and it has our street address. So, it should go to like motivation or timeline. Hey, thanks. If you were to move forward with selling, do you have a preferred time of the year? We open it whenever the right offer comes along. I am looking to sell ASAP.
Now, before I answer the next question, I am going to modify my goaling workflow because the goaling workflow is actually what determines if we have a qualified lead, and I want that to be triggered by the qualified tag because we made those modifications inside of our job flow and closebot. Um, and we haven't yet published that workflow again. So, before I answer this nice question, thanks for sharing, just so I understand the situation better: Is there anything particular motivating you to sell the property quickly? Cool. That's awesome. That's what I wanted it to ask.
So, if I come in here into automations, before I answer that next question, I'm going to come into goal checking and I'm going to add a trigger, which is tag added. Name it qualified. Tag added. Qualified. That's what's going to trigger this bot. And I'm going to delete this trigger here. And what I'm going to do is I'm actually going to move everything from down here to up here. And then I'm going to delete this action to clean it up a little bit. So, we have state splits here because I was evaluating states here. I was running Facebook ads to this, and I one of the questions I had was the state. So, I was able to like cleanly do state splits. I think I'm going to remove that just for just for this example. So, I'm going to move everything from here. And the reason I had state splits is I had two different partners. I had a North Carolina partner and a Georgia partner. And I would send notifications to certain people based on that. So, I'm just going to move that up here. I'm going to delete this action. Cool.
So, now we don't need to add the tag qualified because we're doing that inside of the workflow. We're going to update the opportunity to qualified lead. And then the internal notification is just going to go to me, and it's going to provide all this information. Awesome. Sweet. Publish this and save. So, now this should work. Thanks. Anything in particular? Yeah, we are being foreclosed on. Home is going to auction next week.
So, at this point, the bot should be in its evaluation stage, determining if the lead gave us the motivation and gave us their timeline, and it should tag it as qualified. So, we're going to see if that actually happens. I'm going to wait for it to respond really fast, and then I'm going to go and check the contact and see if it marked it as a qualified lead. So, if you come over here, let's go back. Let's go to contacts. Let's pop into our John Doe contact. See if it has a qualified tag. It does. It has a qualified tag. So, that worked. Check my phone. Make sure I got a notification. And I did get a notification. So, pretty cool. All right. So, we got that notification. Now, it's trying to book an appointment. Thank you for letting me know the timing is crucial. Do you have a 15-minute call? As early as 2 p.m.? Yeah, that works. Just giving it no friction right now. I want to make sure that it actually can book. So, if I come in here, it looks like the opportunity was updated. Yeah, that works. We should get a booked appointment here in a second. New appointment created 2 p.m. Thanks. You're scheduled for your offer call. Awesome. Sent out the email. Everything worked. Okay, cool.
That was a little bit painful. Um, this is the first one that I do live. This is the first one that I do with a little bit of advanced functionality, but I think it is important. Now, there's one thing that we didn't cover and that I said I would, and that is inside of automations. We were going to make it so that the follow-up somebody gets removed from this follow-up sequence every time the AI answers. And so, what I'm going to do here is if I'm going to turn that back on. So, we have our follow-up sequences working as we expect. And if I come in here into contacts, go into John Doe, it looks like, let's see what Okay, so tags aren't automatically added. So, in previous versions in classic, when the AI responded, the AI responded tag would be added. And so, I think I'm going to have to modify my bot to automatically do that. So, let's see. AI responded. So, I'm going to come back into our job flow because what I want to do is when the AI responded tag is added, I want to remove them from the follow-up workflow because closebot's now handling the follow-ups and I don't need them in that follow-up workflow or else they'll get dual messages. So, let's go ahead and make that change really fast. Uh, let's go to agents and pull up our agent. I'm going to test this off camera cuz it's already an hour in.
All right. So, uh, buyers. So, as soon as the bot initially responds, cuz right here, we can actually add it right here because if if the bot Yeah, we can add it before the full name objective because if the bot is actually activated and like moving on to the objective, then that means that the person responded. Uh, so we're going to come over here and we're going to say AI responded. Let's just copy that. Save. And we're actually going to fit that in right here. Close. It'd be awesome if you guys had like a cleanup feature where you can just clean up the canvas and it automatically organizes everything. Probably super low on your priority list, but I think it would be a nice feature add to the UI. Okay, bots's been published. We're good to go. That should work. So, now, if I come into my workflow, what I'm actually going to do is I'm going to add a new workflow from scratch. And I'm going to say stop followup. And it's going to be triggered by a tag. Contact tag added. AI responded. Filter tag added. AI responded. So, that's going to trigger the workflow, and all we're going to do is remove a contact from a workflow. And that workflow is going to be another workflow which is is it followup? Yeah, no answer follow-up. That tool follow-up one day is disabled, so it no longer works. Save. And let's name that. Cool. Save that. Publish. Save. All right. Good deal. I think that's all we need. I'm not going to test that. I'm pretty sure that's going to work. But that is the end here. I'm going to go ahead and I'm going to do this again with another real estate investment account. Flipping home buyers. That's actually where the new leads come in on is is uh not flipping home buyers, flipping Fayetteville. Uh, and so that's actually a WordPress site. So, the trigger is going to be a little bit different. Uh, but it really doesn't matter to you. The bot's going to respond the same. But in the next video, I'm going to go over that one. So, you're going to get two real estate examples, two brands do the same thing. Flipping home buyers, flipping Fayetteville. One we drove traffic to. One has a WordPress website that's out there and gets organic leads. And we also used to drive traffic to that one as well. But I hopefully that helps. I'm going to export this bot. As a matter of fact, I'll do it right now. Um, before I forget, let's see if I can figure out share agent. I'm going to copy this agent. I will put this inside of the school community post for this video so that you guys can watch this. Uh, hopefully you find this helpful. In the future, we'll do that other real estate one. And then I'm also going to do some home service ones for some clients that we have. And if you're new to the channel, please like, comment, subscribe if you found this valuable. If you found it frustrating cuz I was hopping all around, hey, you can comment on that, too. I get it. I'm learning just like you are. Have a good one. Paste.