Daniel: Hey, Chris, so how’s it going, Chris?

Chris: Oh, I’m great, man. Excited to I always tell everybody InterFace and data help is our, central nervous system or spinal cord. But I don’t actually get to do a lot of webinars on, I talked a lot about FUB and other stuff, so FUB works through this, so yeah, I’m always excited to feel like it’s a niche product people don’t really know about, but they hear about.

Daniel: Yeah, exactly. Yeah. So now we’re trying to get the word out now that we have the 2.0 system up and running or letting everybody know about it.

Chris: Are we one of the earliest adopters that are customers still? I feel like we’ve been around a bit.

Daniel: Yeah. Yeah. I think.

Chris: Like you were still manually building Forms for us when we started.

Daniel:Yeah, exactly. Pulled out this appointment form. Shannon just rolled them out in two months apart. It was so new at the time. We didn’t even have all the Forms out.

Daniel: Yeah, exactly. We built we were building one form at a time into into Follow Up Boss

Chris: it’s been years. And then we connected OTC, that was a lift.

Daniel: Yeah, that definitely was a lift. Now we got, now we have to re lift that to get it into 2.0. Because they have a better way of sending data into Open to Close. And so the 2.0 Forms, we’re going to utilize that. So all the field mapping can be done in Open to Close.

Chris: Love that!

Daniel: Awesome. Alright so we’ll go ahead and get started. Can you guys see my screen? InterFace presents. Yes, sir. All right. Awesome. All right. Let’s get going. Okay. So how to optimize your Follow Up Boss Smart Lists. Build user type Smart Lists and Dynamic Smart Lists to maximize the results of your sales activity. Thank you from InterFace.

Here’s the team. We’ve been working a lot on this, so definitely very excited to have everyone here.

Chris: You guys have grown, man.

Daniel: Yeah, definitely. We have a lot of, a lot to build. We have primarily it’s developers. All right. So what you learn on this call. So the way we do regular you’ll learn Follow Up Boss, Smart Lists have limitations that cause leads slip through the cracks.

You’ll also learn how user type lists such as inside sales agents, outside sales agents and lender lists can allow your team to work together in Follow Up Boss harmoniously And you’ll learn how Dynamic Smart Lists provide a more optimal follow up cadence Before we start when we usually do webinars the information will help you, whether you become an InterFace customer or not.

The reason for that is because our there’s usually a do it yourself option to accomplish what our platform does. But our platform allows you to do it faster and Better, but that’s not the case here for dynamic, Smart Lists and user based lists, there’s no do it yourself option. And really we’re the only game in town.

I don’t know of any other way of accomplishing what we’re going to accomplish on this call today. So there’s not going to be as much teaching. We’re just going to go into how our platform does what it does. So how this will work, we’re going to run for about 30 to 60 minutes, depending on how many questions we get I’ll stick around after the presentation for as long as necessary to answer questions go ahead and type in your questions as you think of them.

If something comes up as we go through the presentation I’ll address it and this is being recorded. So I’ll tell you how to access the replay at the end. All right. So why am I here? Who am I? Who’s InterFace? So I started my career as a real estate agent doing multifamily properties in Inglewood, Hawthorne and Gardena area, right where the new Los Angeles stadium is now selling multifamily properties back in 2007. 

Absolute best possible time to get into real estate. So when the market collapsed actually played online poker professionally while living on the beach in Mexico, you could see my office here overlooking the Pacific. So online poker has a very requires a very similar skillset to data science and analytics.

So after my poker career, I taught myself how to code in a bunch of different programming languages got into data science and analytics, got hired as a database manager for the top selling real estate team in San Diego. At the time, Reef Point Realty got quickly promoted a Chief Data Officer and then started InterFace.

Originally as an automation and integration solution for Follow Up Boss. So what does InterFace do? So we’re an automation and integration as a service platform. We connect the best web apps in the real estate industry, such as Follow Up Boss and Open to Close. And we enhance their capabilities.

Our focus is on keeping agents in Follow Up Boss and building customizations that force them to do what they’re supposed to do and prevents them from messing everything up. Which I’m sure everyone on this call can appreciate. Recently we partnered with The Whissel Team to build analytics into the platform.

And we’ll be releasing that in Q4. So a couple other things I wanted to go over briefly. So we also have a Drag and Drop Web Form Builder. We’re not going to be going over that in this, webinar but we do have the capability of building out Web Forms that

Chris: what’s a Web Form?

Daniel: Like Google Forms or jot form.

So a digital form that you can collect data from your agents. Most teams are using Web Forms, but they’re outside of Follow Up Boss. Our Forms get embedded directly into each Follow Up Boss contact in an embedded app. Okay. So they’ll create an update deals and they can trigger automation virtually any automation you need to happen in Follow Up Boss at each stage of a transaction.

And so instead of teaching your agents how to do, five, six, seven different things at each stage where they’re going to forget to do it most of the time. We build out Forms, trigger all the automation from the Forms. And so all agents have to do is remember to fill out a form and then everything else in Follow Up Boss just gets done for them.

Chris: So it simplifies something that’s been under appreciated, on our own team with our agents, now that we’ve had custom Forms for so long, and I know you used to build them custom with, a bunch of tech to make other third party Forms, like job Forms, work, or woof, or any of those. But not having to put duplicate data or even the first time, not even duplicate, like putting someone’s name or email or phone or, if agents have to fill all that redundant data out and then you get to pending and you’ve got all this transaction data they’ve already told you.

Most teams probably have an adoption issue and their TCs probably are not able to scale with the company the way that team leader would want them to grow. It’s a big tech issue for a lot of teams of they can’t get their agents to follow process. This simplifies that a ton for us.

Daniel: Definitely simplifies a lot of things, streamlines everything, allows you to show what fields you need to, what data you need to collect from the agent.

In Follow Up Boss it’s just a big list of custom fields. So displaying only the fields that are necessary, requiring certain fields, and then triggering automation from it just streamlines everything. We’ll probably do a webinar specifically on this maybe next month but this isn’t the focus today.

So another product that we’re working on is our Business Intelligence and Analytics platform. We’ll be releasing this in Q4. So we’re going to have a customizable report engine. You’ll be able to do goals, challenges, leaderboards, ROI reports and we’re going to start launching it next month.

Conversion Ratios. Here’s what we’ve built so far. We have a Data Table. It’s very similar to the spreadsheet but not the focus today, but something to keep in mind. So if you’re ready to learn how to optimize your Follow Up Boss Smart List, go ahead and type ‘YES’ into the chat

There we are. Awesome. Okay.

So user type Smart Lists. So a lot of people don’t know this, but in Follow Up Boss, If you have multiple leads or multiple team members calling on the same lead, it drops that lead off of the other team member’s Smart List. Situation, let’s say an ISA, inside sales agent, Sets an appointment, agent goes on appointment doesn’t let the ISA know what happened on the appointment as often happens.

So the ISA reaches out to the client to find out what happened on the appointment. And now that client is going to drop off the assigned agent Smart List. If they’re supposed to call them or reach out to them, they’re not going to know. And that’s the lead slipping through the cracks. And it definitely happens often in Follow Up Boss.

So we’ve built one of the things we can do with our Smart Lists and this goes into, if an ISA calls, drops it off the OSA list also happens with lenders. If you have buyer agents and seller agents working the same lead, it’s the exact same scenario. And so what we can do is create a last call by assigned agent parameter or last communication by assigned agent or our next follow up date.

If you’re using our Dynamic Smart Lists, and then we could do that for assigned agents and ISAs or buyer agents and seller agents, and it allows us to create Smart Lists for specific user type groups, and they use their Smart Lists, and the other user types use theirs. And now you can have multiple agents on the same lead, working the same lead without them dropping the lead off of each other’s Smart Lists.

Chris: Daniel, you just covered a nuance that I just. I don’t want to dumb it down for, those that watch this they’re watching it live, you might not, we’re all busy in our business. You might even not realize the impact. Of this, if you’re not seeing it, like we’ve, one of the benefits of having a hundred plus agents is you see a lot of micro trends really largely in your face and they look really bad when you catch these things happening, when we were a smaller company, I think a lot of things went under my radar personally, because it’s.

It’s such a small percent of 15 agents, 12 agents, you just don’t see it. So we used to have lenders in our account. We don’t anymore because of the issue you just described. Now that we have InterFace, one of our next builds we’ll prioritize is bringing in lenders back into FUB because it won’t cause issues.

But historically, if the lender, let’s say called a hot lead. through FUB the way the team leader wanted. And let’s say the agent was relying on their Smart List like they should be for hot follow up and said, you know what? I don’t need to set a task for Mr. and Mrs. Smith. I’m going to call them through my Smart List weekly because they’re hot.

They’re their active client. And then the lender goes for a prequal follow up, that they said they’d return the call. Now they just went, two weeks without talking to that person. They committed to talking to a week from now all because the lender accidentally cleared their Smart List.

And that’s just for that type. We’ll talk about some others such as. CC’ing on YLOPO property alerts. If an agent, which we’ve found in our company, they CC so they can see all the property alerts that go out. So they CC themselves. That updates the last communication field for inbound email on the client profile for every daily alert.

So now we’ve seen leads that go three weeks, five weeks, For months without a single outreach because they’ve not shown up on a single Smart List, all because we used to use the last communication field for our outreach list for hot, warm, cold, all of them, which was massively broken. I think we had a 65%, I want to say, reduction in Smart Lists previously, all because of erroneous last communication or lender called or ISA versus agent called which caused a lot of follow up issues for us.

Daniel: Yeah, and so we heard a lot of feedback on this and went ahead and developed a solution. This is one of the things we can do with our Automation Platform. And now the other is Dynamic Smart Lists.

So what are Dynamic Smart Lists? So in Follow Up Boss, the way Smart Lists work, if you’re on a weekly list, for example, it’s a one size fits all approach.

So call, text, email, it’s going to drop. The lead off for seven days, seven days later, it’ll show back up. But that’s not ideally how you would want a list to work, because if you’re supposed to speak to the person every seven days and you call and have a five minute conversation with them, then it makes sense to follow up in a week.

But if you call and get voicemail and it’s a 32nd call, it doesn’t make sense to follow up in a week, because if that happens two, three times in a row, now it’s been a month. And you haven’t spoken to somebody who you’re supposed to be speaking to.

Chris: It does, Daniel. I’ll just interrupt that. It does. It, I don’t know, anyone on this call could, refute that statement.

Our hottest leads are active shopping buyers, our sellers. They don’t answer the phone every time we call. And they don’t respond to everything. Probably a majority of times.

Daniel: Majority don’t.

Chris: Majority of times it takes us, I want to say 23 outreach attempts. to connect with someone we’ve never connected with or non connected lead.

And it’s taking us an average of four to five times to connect with someone we have had a meaningful deep, conversation to qualify with. It still takes four to five attempts. And that’s with call trust, branded calling. That’s with a strong robo dialer we use outside of FaultBuzz. Like it is a very hard feat to get ahold of people.

And the problem that you’re describing is just some hot Daniel with seven days. That’s like best case scenario. That was the least abandoned for us because it’s the most frequent. So you can always get right again in seven days. But when you talk about follow ups, the warms, the colds, that’s where this like repeat gets really bad because they don’t answer on one call.

Let’s use the cold as the extreme use case. 65. Our rule is 65 days or on a sphere call, let’s say, 90 days. I think you know, the average coach is recommending if they don’t answer or have two-way communication. Did you actually create a meaningful touch point for follow-up just because you attempted a call?

We all know the answer’s, No. That means nothing. Your caller ID on their missed call list gets swiped and they move on with their day and they don’t call you back. You lose. And now you wait 65 days to call back and you’re like, Oh, my agent suck at follow up, but really our system just made 125 days, 130 days between first attempt and second attempt.

And then the third attempt, fourth attempt, fifth attempt. And the mastermind, I just did, Daniel, I just said, like we had on average, we’d have people who’s yeah, we’re moving in the spring. Okay, cool. We’ll follow up with you. We put them in the Smart List. Agent trusts our system to work. They attempt every, two and a half months to call.

No answer. They finally answered. It’s July spring past. I already moved. Agents pissed. You didn’t answer the phone. We had to introduce redial rules. That’s what we’re calling him, Daniel. Ultimately, this allows you to have redial rules. Redial meaning we’re going to dial again if we don’t get the result that we were seeking.

Daniel: Yep

Chris: And the cool thing that Daniel and I will show you in a second is you can train, like you don’t have to have my aggressiveness. You can go more passive. Maybe you don’t want to, redial after three days on a cold. You want to read it, wait 10 and I’ll show you ours. And you’ll ultimately be able to set a cadence for how often do we want to try again?

If we didn’t get an optimal result, that’s the concept I need you guys to get from that is you’re seeking for an outcome, not checking a box that you did the activity, go you, but you didn’t get any results. So you’re not getting sales. No one wants that. Effort metrics are okay, but they don’t really matter.

Daniel: And so what we can do is build out dynamics, marvelous or follow up rules. This is an example that we have The Whissel Team just uses calls. This is if you want to use calls, texts, and emails, but essentially if it’s a call with a duration, greater than two minutes, on a weekly list, we’re going to schedule the next follow up for seven days, if it’s called duration, less than two minutes, maybe we’ll do three days or maybe even one these durations can be whatever you want them to be now an inbound text.

You wouldn’t even want that to drop it off the list. What you’d want an inbound text to do is to add the person onto a list. Because you got to reply to this text. So now we schedule the next follow up for immediately, so they appear on the list. Outbound text, not as valuable as actually speaking to them, so maybe we do a follow up in five days.

Same thing with inbound text or and actually this is supposed to say email. Inbound email, outbound email, we pretty much do the same as text. You have a lot more control of when the next follow up is going to be scheduled based on the activity that was just logged. So does that make sense to everybody?

Does anybody have any questions on how this works? Because now we’ll go into an actual demo of the platform.

Chris: The configuration is you set it and forget it on a lot of this. You set it out, you build it and then your tweaking will come, it’s Hey, agents are overwhelmed.

There’s too many calls. That’s happened to us. Like quite literally we had so much more follow up that we had to slow roll it out and change our timeframes. Cause I just wait, there was that much stuff miss. They, I think it was on colds, Daniel. I wish I had the stats, but I want to say 71 percent increase in cold leads needed to fight like overnight we had a 71 percent increase across our whole database on warms, which were 29 day repeat traditionally, we want 29 days two way communication.

Those increase, I want to say, by about 40 percent and then our HOTs increase by 20-25%. Obviously those cold leads are going to have the biggest increase because the redog rules have the longest amount of time in between.

Daniel: Exactly. Alright, so who’s excited to see a demo? If you want to check out a demo on how this works, go ahead and type ‘YES’ into the chat.

I want to make sure Everyone’s still here and alive. Awesome. All right, so let me go here.

Chris: Oh, yeah, if you’re, you have two agents on the same lead. Yeah, and then the way you would do that, and the cool part is what we’re showing you, Ashley, is, this is our configuration in the back end, you can do any configuration you want.

So let’s say the collaborator, is going to be someone in the agent is going to be the primary, Daniel, the cool part is we can update any custom fields so you could set some rules and custom fields, but you could absolutely create a redial rule and Communication reengagement rule for the buy side and the sell side through the Dynamic Custom Fields and the Dynamic Rules in the automations.

Daniel: Yeah, exactly. And if you want to have different rules for different user types, we could do that as well. Like your ISA, you could have different cadences. Because they’re hammering the phones and then if you want to back it off a little bit for your agents, we can do that as well. All right.

So this is InterFace. So like I mentioned earlier, we have a few different platforms. Automation is what we’re going over today. We also have our Form Builder and then Analytics are coming soon. So we’re going to jump right into the automation platform. So I’m sure everyone or most of the people on this call are familiar with Zapier.

So this is a similar. Set up as Zapier where we can build out workflows but it’s specific to Follow Up Boss and it has a lot of capabilities that aren’t in Zapier or in Follow Up Boss automation. So I do a test here.

So here are the different triggers that we built so far. And as you’ll see, a lot of these aren’t anywhere else. So person created person updated. This is very unique. So this will trigger automation in Follow Up Boss when a specific field on a.. 

Chris: I have to interrupt that I am in Automations 2.0. I think it’s in beta Dan and team did a phenomenal job on Automations 2.0. And it solves some things for a lot of users. They are not looking to compete with this. This does not exist. Also the Zapier, you call it what you want. That’s also managed. I don’t know if a lot of people know this, Daniel make any of these automation platforms for Follow Up Boss or for Google Sheets.

And the integration for Zapier is managed by the company of the integration. So Zapier does not also does not have these endpoints available. The only way you’re accessing the ability to use these as triggers is if you have a developer, someone that’s writing custom APIs for you, then they’re listening for these types of events.

So I think it’s a very big clarity point for everybody is and then you can connect these things to native because of the tag system or through Zapier, if there’s limitations but this is the only system that exists. Besides writing custom code that allows you to trigger, let’s say, when a collaborator is added, I know that’s a big one people want, or when a collaborator is removed, and then you can filter by which collaborator was added or removed.

That’s just, if you go to the person updated field drop down there, Daniel.

Daniel: Yeah, when a lead reassigned, that’s a big one. Lead reassignment as a trigger. the pond.

Chris: So there’s lots of different. These people in points are very valuable, for, the smart techie people that are writing code.

This gives it to every team leader right in your toolbox to be able to create custom automations natively in FUB, with this or directly in InterFace. It’s dynamic. Daniel really in team thought about that is, hey, we’re not going to be able to build everything all at once.

We’re going to have priorities, but let’s make this work really nicely with your current workflows that you already have and just bolster them. Even if that’s all you need to better filtering things like that.

Daniel: So also a person deleted tags, created person stage updated. So if a note is created or updated this, it.

create some really interesting possibilities because you can trigger automation if there’s like coded notes or if notes are coming.

Chris: I’ll give an example.

Can I give a use case there Daniel? Like a coded note would be for YLOPO users. This person re engaged with your remarketing or they’ve been off site for 90 days or you might have a task you’re looking for.

I know you guys are working on the task. I don’t think that one’s available yet, right?

Daniel: No tasks we’ll probably, we’ll be adding soon.

Chris: So even if not, if you guys don’t know, like a lot of the companies like YLOPO or RealSky, any of them, they do a redundant approach of tags, tasks, and notes. So the way you would use this note create is look for a normalized note, not like an agent note that they’re going to write, whatever, but.

Any company that’s posting notes to your system. You can scrape that note for specific messaging, exact quote, and then you can use that to create a trigger downstream of a workflow automation, email action plan campaign, and just deepen the already existing integrations you have. So that’d be a notes use case.

And then Will Ward asked, it can create custom filters. So let’s create a trigger, Daniel, if you don’t mind. And we’ll show that like I’d say reassignment trigger, if you want to show that one.

Daniel: Yeah let’s go through the rest of the triggers first, and then we can go back in and filters will be the next step though, Will.

Chris: You’ll able to slice and dice a filter for, Or not pass through literally based on any criteria within FUB.

Daniel: Yeah. Email created, appointment created or updated. So this could be used for appointment outcomes. This is the one thing that has an overlap with. The Follow Up Boss 2.0. I think that’s the one trigger they’re adding.

So text message created, call created, and then deals created or updated. And this is the same as the lead record. If a specific field on the deal is updated, we can trigger automation from that.

And so the calls, texts, and emails is what we’re utilizing for our Dynamic Smart Lists. So we’re going to go ahead and click on call and we’re going to go through a, so we’re going to build out a workflow for if a call happens, that’s greater than two minutes. So we’re going to test our trigger here.

So now it pulls in. So one of the things we do a little differently than Zapier is we go and pull extra data in so you don’t have to do that little get step. So in Zapier, if a trigger happens and you want related data, you have to add like a step. We go in and pull all the data related to the call. And we also go in and pull all the data related to the person.

And so you have all that to work with in the next steps.

Chris: That’s a little deep, Daniel. Just even for me, I’d say, you’re brilliant developer. So just if you’ve built Zaps or you haven’t, for example, I’ll use the people in the deals, objects and Follow Up Boss, let’s say you created a trigger, what was the trigger call, but you want to know, do they have any appointments set or appointments met in the deal section?

In FUB, when you do a trigger for, which calls created trigger doesn’t actually exist in Zapier, but roll with me on the example, they go ahead and they create and you would say I only actually want to look at this if they’ve had a met appointment with our agent in the deal section then you, to Daniel’s point, you’d have to do a lookup step, look up any active deals against the user ID for that contact that had the call created, and then that will pull in deal data.

And then you do a filter. So you got like a five step process that we’ve completely eliminated here into a single step filter. Now you just do what you want. Okay.

Daniel: Yep. And so now we have filters. So we have some pre-created filters. We want to make it as easy as possible. A lot of real estate teams aren’t as super tech savvy.

And so we want to make things simple but we need duration on this filter. So we have to go into advanced filters and now it’s just like Zapier and so I can come in here and search for duration. And now I have call duration. And then we want to do greater than or equal to, and then this is in seconds.

So we’re going to do 120 seconds. And so now if a call is logged, that the duration is 120 seconds or more, this automation is going to run. And so the next step is we have this utility. It’s a date calculator and this. Example, we’re doing for a weekly list. So we’re going to take today’s date and we’re going to add seven days.

And so now we have a date seven days from now, and then our actions that we have available are we can apply a tag, we can trigger an action plan, or we can update the lead record. And so for Dynamic Smart Lists, we create a custom field. So a hot active next follow up date field. And then we populate the calculated date to that field.

And so now the way we can figure the Smart List is when this date arrives seven days from now, this lead is going to show up on the Smart List for them to be called. And then we set up. A workflow for all the different activities you want to allow to reset the Smart List. The Whissel Team is just called greater than two minutes, call less than two minutes.

Other teams, they want to include texts and emails. However you want to configure it, we can configure it.

Chris: We know that the average voicemail takes a minute and I think five seconds to get to. I think we did 90 seconds and we said, yeah, if you get rushed off the phone in that first 25, 30 seconds, you should call back.

You had nothing meaningful happen there at the grocery store. The kids were yelling in the back of the car. Something was happening. Yeah. So that, and the cool part is I’m actually noticing instead. This is really fun. I don’t know if you did this on purpose or this just happened to happen. We’ve actually built our Dynamic Smart List to do the same thing, but we built them completely differently.

Daniel is looking to post when to call. Mine is looking when the last one happened, and I’m using FUB. I think that’s just a cool thing to just say out loud, is we’ve built the same thing, we built it together, and then Daniel naturally overhauls, and engineers seem to be more efficient, but yeah, we’re doing inverse ways of doing the same thing, which, to me I think just speaks to how capable the system is and how dynamic it can be, is that we can literally build inverse of the process, one on lagging date, one on the next call date, and both can accomplish the same thing in fun.

Daniel: Exactly. What do you mean by multiple criteria in the trigger?Ashley? let’s see call direction and tech.

Chris: Yeah. So you’d set up different automations, Ashley, and they’re going to stack and work within rules together.

Daniel: Exactly. And so what we’re doing is we’re populating the same field in all the different workflows. So this would be the field for your weekly list. And so we would set up maybe five or six different things.

Chris: How the two would. Like a real world use case. You’d call it didn’t answer. So you would set the next date for, let’s say in our rules, three days from now, because they didn’t answer the call was less than two minutes. So now that custom field in FUB called hot active follow up date is September 3rd, but then they text me back and say, hey, I just got your call.

Everything’s good right now. Doesn’t really matter what they say, but they sent a text back. Now we have another rule that we haven’t built yet. That says if text is happens and it’s inbound text, go ahead and change this date to seven days from now. Pardon my math, but let’s say it’s the 7th of September instead of the 3rd.

So now the text automation, which is a separate automation from this, different completely, updated the same field value. So now in FUB, when you say, call if the date is within this date to this date as your Smart List rule for that custom field, that field is updating whether it’s email, text, or phone, and you’re just relying on that next call date as your Smart List, which Daniel will show you in a second.

Daniel: Exactly.

Chris: We’ll ask I guess we have a Q & A section and a chat. That’s fun. How many leads on average are agents carrying when using these Dynamic Lists and how many leads normally appear within the lists for them to manage daily? Yeah, I think that’s a, I’ll give you a direct answer, but it doesn’t really matter only because it’s up to the agents lead generation, ultimately is going to define quantity and how many leads are we delivering to them from, channel partners that we work as a team. So ultimately lead intake volume is going to be, determine ultimately how many leads they’re carrying in these lists.

So, I don’t think that’s super relevant. I have agents that have four or five per list and I have agents that have 85 to 90 in some of their cold lists for follow up because they in early in the career they’ve done so much lead generation for follow up and I have some people with high lists that staged improperly. They have a bunch of leads.

They’ve never connected with they sit at an open house they’re like, ooh, they’re looking at a million and a half open house hot, warm, and then there’s I’m hopeful that I’ll follow up and rather than following a lead qualification process. So it’s a mixed bag. Will ultimately I’d go on the percentages, whatever leads you have in your current hot follow up, warm follow up, cold follow up, whatever your stages are, you should have marginal increases of 25, 40, and 65%, respectively, depending on your redial rules and aggressiveness to calling.

Daniel: All right. So is there anything else we want to go over on the platform? Any, anything else? Oh, quickly some other stuff we’re going to be adding in. So right now we can send webhooks to Zapier, so you can use this to trigger Zaps as well. So now all of our triggers that we’ve created can be used to chain into Zapier and build automation off of that.

Chris: And then can you give an example of what we’d do that from our account? Like another, basically you’re connecting FUB data you can’t extract to other systems that you’d normally do in Zapier. That’s why you would do that.

Daniel: Yeah, exactly. So there’s just there, what there’s five triggers in Zapier, maybe this just makes it so all of our triggers can be used to trigger automation in Zapier.

So we’re gonna be adding in Twilio notifications, email notifications, Slack notifications soon. So then when something happens in Follow Up Boss, you can send out notifications. And then you’ll also be able to feed all of your Follow Up Boss data into an analytics database that you can build out reports in.

And we’re actually pretty excited about this. I’m gonna, I’m gonna show you what we’ve done so far very quickly. So right now we have the initial table set up. So when this is related to deals in Follow Up Boss and this operates like a spreadsheet. So if I want to see how many pending transactions I have, I can see my pending transactions.

It has group by functionality so if I want to group by agent, I can group by the agent and see how many transactions my agents have and then I can even build out reports like chart, like a Chart Builder. So if I right click. I can do like a bar chart.

So this is for opportunities very soon. This will be for all your different data. So if you want to see your, a table of your calls, texts, emails, notes, anything that’s in Follow Up Boss, you’ll be able to play around with your data. Okay. So back to the presentation.

Chris: Ashley, I don’t know what you mean is that available outside of InterFace.

Can you export it or?

 Daniel: Yeah, you can export that data as well. Yeah. You take pictures of explore. I don’t know what outside of it means. If there’s a export to CSV. So if you want to pull it into a actual Spread Sheet. You can do that.

Thanks everyone for joining us and we’re going to wrap this up.

Chris: Thanks guys!

Daniel: Bye everyone! Thanks!