How to STOP the follow up when someone buys

It just to make sure.

Guys, I didn't click record before, but if you're watching this on a replay, Martin's just talking about in our snapshots, there's a bit that is a manual entry step. I say, I can't tell you what the step is because I don't know what you're doing. The step is stop following people up if they bought from me because that's like a really bad look, isn't it? Like, hey, we've got this really cool offer. We've got this really cool offer. We've got this really cool offer. And the guy replies, I bought it yesterday. It's like, Sorry about that. So what we're talking about here is stopping that follow up sequence when there's a purchase. So what Martin just said before I hit record there was that he is using our white label suite licensing system. So we're selling the licensing program and GHL as a package. And now what we want to do is get that sale to stop the follow up and make sure that works. Go for it, Mon.

I've used this template. I've just customized it a little bit. The one that you gave us.

Awesome, bro. Looks amazing.

Then here, I'm literally just linked. When you click here, it goes to that payment link, your new stripe.

Fantastic. Awesome. The question then came around the automations where we have in the 20 leads system where we need to add this manual trigger.

Great. Now what we're looking at here is we need to stop the follow up. This is not cool. How do we do it? What do we do? Thank you so much for showing us how the Stripe payment link is on the page and everything. Let me show you exactly how to do it. There's a couple of steps. I'll show you the I'll show you the easiest way. I'll show you the slightly more complicated way, and then you can choose which way you go. Let me take the screen share back if I can.

Sorry, let me just hit this time.

Yeah, cool. Thank you. Quick share screen and a techy walkthrough of exactly what Martin just spoke about. First things first, how do we get there? How do we get to that point? Martin created a package for sale in our white label suite licensing dashboard. That's where we started from. Martin's coming here. That's Alex's account, so I don't really want to mess around with that. Martin's coming here. Let me get back to my own account. You guys can see my admin panel. Cool. Martin's coming here. He's got packages. He's created a package for sale just like I've done a few times here. Close, in fact, to this one, $9.97 a month and $1,000 set up fee. All of this is good. Martin's done the steps to create a package for sale. Martin's got a Buy link, a Stripe purchase link, and he showed that also on the page. When somebody clicks on that, they open up his own Leads Pro payment link, just like my company is called Gogeo. There it is, $9.97 a month, plus $500 set up fee, whatever that was, somebody pays, now what? So what we need to do is we need to electronically tell a completely separate system that a transaction has just happened over here.

The way that we do that is using what's called a web hook and an API key. So this is two programs talking to each other via what's called a web hook or API key. So what we're going to do is we're going to take the transaction from Stripe and we're going to push it down a web hook all the way to the other end to GHL, where at that end it's going to trigger something which will stop the rest of the followups from going through. So how do we make that happen? Inside of the dashboard here, if you come to account settings, you have this little bit here that says web hook. All right, web hook. And this is where you can load up as many as you like, web hooks, places. Tell all of these places about the transaction that just happened. This is where we load the web hooks. What web hook? Where do we get this web hook? What's going on? Let me show you. So we come to your GHL again. Forget about the branding. I'm going to do this in my demo account so I don't stuff things up. I'm going to come over here and I'm going to go to Automations.

This is step one, Martin. Step one, I'm going to tag that person as a buyer.

I've already done all of that, but I'm happy for you to show it. Everything is set up. Amazing. It was just adding that trigger because in the training you said, Hey, depending on how you set up, it could be done in many different ways. I just wanted to make sure I set it up correctly.

Cool. Let me give you a fast answer in case you need to go. How have you set up to tag the buyer at the moment? Is there a tag?

I followed whatever was in level two training when it was set up. When would I tag? When they... I said that's on... Which workflow would that one be?

The buyer's one after you set up the web hook. So you've already set the web hook to post back, create the account.

Web hook and everything is set up as per the training.

Perfect. Perfect. So the quick answer then is, in addition to creating the account with the web hook, you can also tag the person.

That's already set up.

Beautiful. So then the trigger to stop the follow up is the tag. As soon as that tag has been applied to someone, don't follow up anymore. That's the quick answer. Now, let me rewind a step and show you. At the moment, what we've got is we've got a transaction happening in the database and we want to send our information down a web hook and something happens at the other end. I'll create this in my demo account. We go create a workflow. So step one, I want this system, my GLH account, to know that a transaction happened over there. So this is my... I'm just going to give it a name, web hook demo from. Right. So what is the trigger? The trigger is an inbound web hook. Ghl makes this available now, which is absolutely amazing. Okay. It's a web hook. They already have it in the system. So yeah, that's my trigger. Cool. As soon as you click on it, DHL gives you this big, long URL, and that's exactly the URL you need. So now I'm going to copy that URL. Come back to my dashboard here and paste that URL in here and click on Save.

And hey, Presto. Now, every time a transaction happens in my dashboard, it will send data to this big long URL that's over here. Now, back in my DHL system, I can't save this right now. There is no Save button. I can't save it. Okay, well, what do I do? I guess I have to test it. It's saying, Well, we haven't received any data yet, so I can't test something that I don't have. What do I do? You'll notice that as we created that web hook URL over here in the dashboard, we have a test button. Now I'm going to test. I'm going to send data down this URL web hook thing. It says this is the data I'm going to send. Now you can edit this. So I'm going to say my first name is Mon. My email is whatever and blah, blah, blah, and whatever I want to change. I can change here. But this is test data and I just hit send it. Now I have sent data to a completely another program and it's sitting there waiting for that data. Let's go and check it out. Back over in here in my automation, now when I click, look, there's a thing.

It came in, it's there. Click on it and I can see first name, Martin, last name, Johnson. It sent the data. When a transaction happened on my licensing dashboard, GHL caught that data, and now we can do something with it. What are we going to do? So this data is now here. I can save that. I won't let me save anything else until I do something with that data. It says, Okay, you got data. What are you going to do now? What I'm going to do is the only option it gives you is to create or update a contact. What am I going to do? I'm going to map the... Let's get this working. I'm going to map the first name to the first name. I'm going to map the last name to the last name, funnily enough. There we go. I'm going to map the email to the email. Let's go like that. So I'm literally just... You know those games when you used to be a kid and you had the left hand words and the right hand pictures and you had to match them up? That's what we're doing here. So we're literally just mapping the data that came in to the data that's in DHL.

So we're putting it in the right place. So now we've got all of that stuff. I'll just leave it at that for now. So we've got first name, last name, email, come from my transaction, shoot in, happy days, click Save, good start. When a transaction happens, DHL knows about it. Happiness.

That's not the end of this thing. Quick question, Walt? Yeah. In step four, in the workflows that you already provided, can I just add that web hook that we've just done? And then the sequence after that is removed from 14 days, removed from email sign up workflow, and removed from.

Mistakes through. Exactly. I would say it. Just like I'm.

Screen shot it.

Yeah, I would just say one extra step. So on the bottom of this, we just caught this web hook because that's the trigger. We just caught this coming in. On the bottom of this workflow, the thing that I would suggest is tag. So when that person comes in, add a contact tag and whatever the tag is, WLS buyer, add a tag. Boom, add WLS buyer tag. Happy days. So transaction happened. Ghl knows about it, creates an entry in my database and tags them as a buyer.

All good so far? Should I add then the create update contact as well?

I'll share screen in just a second. I'll finish this off and then I'll share screen and we'll work it through. We've got a transaction, GHL catches it, creates a contact, tags that contact. Now, the last and only step and coming back to your original question, how do I stop the followups? Now I have a tag that becomes the trigger for that follow up stopping system. So in the 23 Leads automations, the one we're talking about is that one. That's the bookings, it's here. This one, important, add manually on sale, add a removal step. Now the only thing we need to do is say, what's the thing that tells that there's a buyer and just stop following them up? We know now it's the tag.

Okay, so I couldn't add the web hook in there. I'd have to do that separately.

You could definitely add the web hook in there. That's absolutely fine. Yeah, definitely. Same thing. You could do it here. This could be the trigger. Web hook, you could do it here. Exactly the same. When that web hook is there...

That's what I've just done, but then it won't allow me to add the tag.

You will need to do the create and update contact step.

All right, that's why.

Yeah. So you absolutely need to tell the system that when the web hook comes in, it relates to a specific contact. Create or update that contact. If the contact already exists, name, email, all that stuff, then it'll say, Cool, update done. Don't need to do anything. And it'll just move to the next step, which will be tag. Then it'll move to the next step, which is remove from this, remove from that, remove from that. So that was a really long answer to a really short question in the end. So your short question was, what steps should be my trigger? My shorter answer should have been web hook. When the web hook fires, stop the follow up. But I just wanted to show what's the web hook, how does it work, where does it get the data from, what do I do with it? And that's what stops that follow up flow. Got it. How do you feel? You paused before you said got it, which makes me go, what other questions have I missed?

No, my only question is when I try to add the contact, it only allows me to create an opportunity. But I'm just thinking the opportunity would have already been created somewhere else when they signed up.

When they opted in. Yeah, absolutely. Do you want to share your screen and just show me?

Yeah, if you don't mind. Just want to make sure I've set it up correctly because there was just one of those that were a bit grey in the training.

Of course. Hey, Mike and Terry and Juanita and Anna. Guys, it's so happy to see you. I just hadn't said hi. I just wanted to say hi. Nice to see you. All right, cool. What do we got? So we've got our web hook. Just click on that one for me. Click on Save. All right. Now it should have actually given you... See that error? Can you remove that trigger for me, Martin? Can you actually just delete it? Get rid of it for now? We're going to reedit, so I'm sorry, but we're going to reedit. New workflow trigger, inbound web hook. Let's do our steps. We want to get that URL. We want to put it into your dashboard. We want to send the test data.

Do you want to delete this.

One and read? Yeah. We're not using it anymore. It was a one off. We can create another one. Chuck it in there. Perfect. Click Save. Perfect. Click Test. Perfect. Done. Now we can go back. Click Test. Click that. Top one. No, just the top one that's there. Yes. That's it. Click Save and pause. Boom. Straight away, that's what I was looking for. It wasn't there before. Got it. Now, we need to do the create up. C ontext. Add field, first name, first name, last name, last name. You can search if you want to or you can scroll.
 
First name. Here you go.
 
First name, select first name. Last name, select last name. Got it. Email, select email. One more. You need email. You need either email or phone number in GLL, otherwise, it won't identify a contact. Got it. So I.
 
Can save that. Email is email. Save that.
 
Boom. And then I can add the tag.
 
Add the tag.
 
Here? Yeah.
 
Yeah, exactly where you are now. Automations happen in sequence. What I got caught when I was first starting with GLL is I did a thing where it's like, remove from all workflows and then tag them. I was like, Dude, I just removed it from the workflow. How do you want me to tag? It's no longer in the workflow. Everything happens in sequence. So yeah, add the tag next and you're good to go.
 
So my question follows up with this, only because I saw your Facebook post on you figuring this out today or yesterday. Do we.
 
Need Zappier? Yeah. No, but yes. No, but yes. I had Zappier for 10 years. I ended up at a point where I was spending like 500 bucks a month because I had so many Zaps running for so many different things and it was freaking amazing. But it was costing me a bomb. And then I saw Pably and I was like, Sweet, 497, lifetime. Yes, sign me up, baby. And I moved everything over to Pably, which is where we've been running everything, all of our training in the last year has been Pably, Pably, Pably, Pably, Pably. 23 leads, Pably it into GHL, Pably this, Pably that, and Pably an invoice off to zero and QuickBooks and it's amazing. And now, GHL just released their own web hooks and I'm going, still need it. So the best and most honest answer, dude, is do I still need Zappier? Don't know. Depends what you want to do. There are things that you cannot do with the web hooks inside of GHL. You cannot... Let me think.
 
You cannot... It's just a post in just simplistic one, right?
 
It's a very simplistic. It's like, if all I want to work with is in the GHL framework, I don't need P ably or Zappier. I'm good. I can use what they've got. It's cool. If all I want to use is Google Docs, Slack, and Stripe transactions, and that stuff, and I'm doing everything I do in my life in GL, you don't need it. If you're getting outside of that world, if you're getting into multi threaded automations that do 25 different things and post on Facebook when this guy does that and this guy does it, yeah, you still need Zappier or Pebble or something. So if you're just doing transactional stuff and it's just contact database updating, don't need it. If you're getting wild and wacky with integrating all kinds of other automation stuff, yeah, you probably still do.
 
Does that include other softwares as well, Walt? So if we want to integrate with Sim Pro and stuff like that, we still need to have their SAPA, right?
 
Well, good question. So what's Sim Pro for a start?
 
It's just a tradey job management software.
 
So can you just type in Google search for me? Can you just open up a new tab and just type in the word Sim Pro API? Cool. Sim Pro API, Sim Pro software. Simpo, that's a developer. Yes, that one there right there. Sim Pro software API. Cool. Click on that for me. To answer that very specific question, can we synchronize GHL with Sim Pro using the stuff that we've already got? The answer looks like yes. So scroll down just a little bit for me.
 
That's where you're saying if it has its own API, you can't?
 
Yeah, exactly. So we do not recommend using a browser to interact with the API user. Yeah, exactly. Cool. So they will give you... Can you click on the next topic down? What is the Sim Pro API? It's going to give you, probably at some point a URL. That URL is going to be the Sim Pro API key. Again, let's answer the question specifically. Sim Pro has an API, which means it's opened up a little portal to other applications. And so long as you've got an API key, you can unlock the door. So API is, yes, you're allowed to communicate with me. So go back to your GHL, and I'll show you how you would do that. Maybe open up a new automation just as a draft. And instead of a trigger being an incoming web hook, what we're going to do is have an action as an outgoing web hook. So let's say we tag someone in the database and we want to send that person to Sim Pro. So just click on.
 
The database. Basically, the way we would use it would be at a point where they become a job, that's when we want to send all the information into the job management software. So they don't need to enter it all from scratch.
 
Awesome. Exactly right. So click on add your first action there. No, not a trigger, just the action. And use custom web hook. There it is. This is where you're going to put the API URL that Sim Pro give you. They'll have like, blah, blah, blah, SimPro. Api. Blabla. Com forward slash equals api key equals. You'll need to put your API key into the actual URL, and then you can send across any data. When a contact turns into a job, send their name, the email, the address, the phone, you can map out the same data here in the same way you did on the last step. You can say what I'm going to send.
 
As long as the software has the API and we can get the API, we just use the web hook and the API URL, and then that creates the trigger, basically.
 
Exactly right.
 
Okay, that's perfect. Can I just add the last thing and I'll let everyone else get on? Just one quick one. So the last thing that I did, you guys had that splash page. So what I did, I just went in and created like this. Perfect. If people are inside the software and they just by coincidence click here, then you want to sell it to them. Then we just go in and just like this, the video that you've done, but I've just put a new thumbnail on it. Awesome. People can.
 
Log.
 
In, but then also they can also just sign up. So if they click here, it just leads them straight back to this page.
 
Brother, if.
 
I.
 
Was next to you, I'd be taking a little gold star off my sheet right now and I'd be pushing it firmly onto your chest. That is perfectly done.
 
Okay, cool.
 
Good job. It would be weird science. Not worthy.
 
We're not worthy. But that's exactly what we wanted you guys to do. Because if you've got sub accounts of people coming into DHL, even on free trials and that stuff, they're going to see a little thing on your menu that says lead generation. And the natural inclination is click. They watch your video, they can buy it direct from there. Zero sales interaction required. Perfectly done. Gold star.
 
Correct. To be honest, you can tell if anyone that likes it and that sees this, it's actually it's all done off the training that you have in there in level two. I think it is one of them. So it's pretty straightforward to set up.
 
I said on a sales call this morning, we had 26 people on the call. And I said, we have an evil plan, all of us here at White L evel Suite. Our evil plan is that we want to get really rich. Sorry, but we do. The only way we can do that is to help you guys get really rich. And if we help make life easy for you, that's going to help you make sales. Every time you make sales, our company grows. So we will absolutely give every training we can, every template we can, every system we can, because we want you guys to make a lot of money. We want you guys to make it.
 
Yeah, it's perfect. Thanks so much. I'm happy with the set up now. Thanks, Walt.
 
Amazing, dude. Thank you. So great to have you on the.