Community Event: Chemical Applications Features!

And we're live. Welcome everybody to a community event.

It seems like we're far away, but we are literally within arm's reach.

There you are. So we're going to go ahead and get started. I'll kind of outline the objective of today's call and it could be a quick one, it could literally be 10 and 15 minutes.

Or it can be longer if needs be. I feel like it's this one's going to be a little shorter and then we'll probably have another one in early February that'll be much more detailed once we actually have functionality built and then there's feedback on that which will probably be more extensive. So George is alongside me because he's actually taking notes, he's had a product and we'll be making sure that as we get ready for January and February that we have a clear roadmap and we will this actually be now we have an application designer joining the team. This is probably going to be our best, well thought out feature and so that's why we want to do a little bit of preamble and get some of your feedback. We do have a few different other softwares that we know are very comparable and we would like to kind of mimic some of their features and those being Service Autopilot and Real Green. We want to choose the best from both of those worlds and then simplify it dramatically as you've kind of seen with Sequence Automations or sorry I should say price matrices and job costing. It being an optional toggle on as an advanced feature. This will be similar because a lot of people don't need to have things like waiting lists, they don't need to have multi step programs, et cetera and we don't want them to be bogged down with that when they are trying to get started. However, it'll be something you can toggle on and see the advanced functionality. So really the goal of today is to get some of the most important things to you when it comes to chemical treatments and applications. And the thing that is risky in having a meeting like this is everyone's like, well it's not in there. We won't be able to accommodate everybody. But we want to get a general gist and direction of where people are coming from. So that way when we do develop during January and February and do our best by March 1st to have the bulk of the functionality there and then we can refine that in the future. And we just want to make sure we prioritize what is most important to the community. Community in part due to the fact that I don't have thousands of chemical treatment applicating.

Clients. Most of my, most of my locations have a couple hundred max. We don't specialize in it. It's not something that we do. And so there are literally specific softwares like Real Green that specialize in just this one thing. And so I'll, I will first off say if you have thousands of chemical treatment applications, you have very, very detailed treatment treatment packages, you might want to wait on us until after this spring rush, like wait until next spring rush. That might not be a bad idea. Now, do I believe that 90% of people that do chemical treatments applications and that do have a lot of customers will be able to be using COPA by March 1st? I do believe that, but I would not put all the eggs in the basket if I was a business owner that my applications that are happening on March, the first week of March are going to be inside Copilot. If I have thousands of customers and really, really well defined workflows in another software program. If you have a. I would be like, yes, 100%. If you have a few thousand, I would really stay in tune with what we're doing over the next couple months. Make sure you're on the early February community event as well, just to make sure that's actually going to serve you to the. And you can actually move over and not have too much friction. So with all that being said, George, you want to say hello just so people don't think you're mute.

I'm here, I can talk. Hi everyone. Uh, I just, Yeah, I just want to say I'm super thankful for the people that have already joined. Um, Copilot has kind of been a community built project for the last few months with all the feedback we've been getting. So I'm excited, I'm excited to hear you guys thoughts.

That's all I had to say.

Such a disappointment. All right, so I will say I'll kick this off by saying the one way you could actually help us probably the most. Because I know right now it's like what do you want? And it's very vague. The one thing that you could really, really help us with. If you like your current workflow, the thing that you can do the most to help us is email us a recorded screen share of your workflow. Because like right now you're going to give me like a very detailed something and I might not, it might not make perfect sense to me until I see that video. And so if you could do me a favor. It is Steven George. You want to put this up? Actually here. That's Stephen George. Look at this guy. You want to put in the chat, George? Go ahead and put your email.

Oh, can I do that?

I can put it up on the screen. Check this out.

Yeah, do it on the screen.

Okay. It is Stephen.

George at Copilot.

CRM. Let's see. Dude, have you ever had your name my public.

Email by email in public. No. No.

Check this out, bro. Oh, yeah, dude, that's awesome.

So if you have a. Here, you know what? Let me do this. Let me get better. Email, your video, your screen, recorded workflow two. Let's go. Now we're talking, folks. Bam.

I love it.

Yeah, so that is most optimal because everyone uses. We have noticed this. Everyone uses the chemical treatment application features very, very differently, whether packages, wait list, etc. So if we can see as many of these as possible, it would give us a lot of context. Because I do it one way. That's all I know. And so as much as I can just pump that through, I do feel like if we have a better, better representation of the community, we can serve everyone better. Let's go ahead and hop into some of the questions that came in already or slash comments. Not really questions as much as comments. So go ahead and kick this off. Brent says if it has the functionality of service, all platin is done by the end of February. That would be ideal. Okay.

Turf Nerd Lawn care says I will need the ability to print all invoices and route sheets the day before technicians. I am pretty certain we have that in the works, so thank you. And again, some of these, like, just say what you're thinking because that is very helpful. But above all, send us, send us. The recorded workflow is super helpful for us. Also need the ability to move services from the waitlist to this batch order back to the waiting list. At ease. Okay, that's a great point. Moving it back to the waiting list instead of just going one way. It's a good, good point. So our current idea and kind of schedule is that we will first work on the wait list. And the wait list should be done in the middle of January. Then from there we will move on to packages since we really need the wait list in order for packages to be, to be effective. That's kind of what Will says here. Waiting list and chemical tracking go hand in hand. So I'm excited to see how this feature will be. A lot of other CRMs, I'd say at the beginning we're not going to beat everyone in terms of functionality. But I do think from the sake of simplicity and like usability, especially for new operators, they'll be able to jump into it sooner. And then as time goes on, we'll add the deeper levels of functionality that more experienced operators might need.

All right, next, one single entry for package schedule from estimate right now. Have to enter twice. Okay, got it. So I think we do. Don't we have this as a separate ticket already, George? Like being able to schedule a package from the estimate?

Kind of. You can schedule a whole estimate right now, but you can't. If you wanted to schedule like three lines at once and there was six lines, you couldn't do that.

Got it. Okay.

Waiting list needs an area to put scheduling notes. I'm assuming that would be on in each individual visit. Oh, I see, you're saying scheduling notes like when you think you could put it on. Got it. Yeah. So our idea right now for the. I'm muting you, George. Our idea right now for the waiting list is essentially that any accepted estimate will go to the waiting list. So what will happen is like you're scheduling dispatcher person, they'll just note, they always are going to go to the waiting list to schedule jobs. And then what we believe is going to be beneficial is like here are the estimates or here are the jobs that were accepted from an estimate and it'll be labeled. Here are the jobs that are on the waiting list based upon being in a package with a given window of time for dates. So for example, you're setting up a seven step package and each of those steps, our hope is that you can put a date range of when you want it to show up on the wait list. And then the wait list will be categorized and ranked based upon what is the most highest priority based on how many more days are left for it to be in the waiting list. So for example, if you have a seven day window where you must get a job done, those would be coming close to expiration and be at the top of the waiting list. This is what's going through our head right now. So I'm just sharing this new. Because this is very preliminary, but it's like where our head is at. And as like a waiting list should be where as a scheduler, as a dispatcher, I go there and from the top to the bottom is most important to be scheduled to. Least important to schedule. Least important to schedule is like, hey, sometimes the next six months I need to get this treatment application done. I'll throw in the wait list and I'll have 180 days planning to get done. That would be towards the bottom. Whereas if I've put a set step seven step program and it has two days until it must be done, it would be at the highest priority and we eventually tie in automations that would alert you like, hey, this one's within the next three days. This specific step must be completed.

To add that that to really quick Mike. We also were thinking about adding some sort of functionality where you can basically have steps block next steps. You have three steps and step two needs to happen before step three happens. You can kind of add it as a blocker to step three, something along those lines.

Fantastic. And this is why seeing some of your workflows are gonna be super helpful for us. Cause we have in our mind what we think is gonna do really well. But if we can see all of your feedback, it'll help us refine some of these features to prevent any sort of extra learning you have to do. So again, the people that send us the workflows, you will probably be the most pleasantly surprised when we roll up features. Cause you'll see us try to accommodate certain workflows. Specifically have condition codes for lawns, make it clickable for the technician to click problems in the lawn mowed to mowed too short, water the lawn fungus found, etc. My idea is to make them tags maybe and then can email customers of the conditions of the lawn and then be able to upsell them. I think this honestly could be something that would already be baked into upsells, don't you think, George?

Yeah, I think I think you could use upsells for this or if, if you're saying it in the sense of like we had to skip this lawn because of those issues or something, you can already add skipped notes when you skip a job. So we have that too.

You could technically also do it based on tags. Like have an automation based on like when you add a tag, it would send them an email being like. So you could like skipped lawn due to lawn. You know, wet lawn could be the name of the tag. It fires off an email or text message to them on that too.

Yeah. And you can even use upsells kind of the same way without actually upselling someone. If you wanted to just notify a customer, you can have an upsell do that as well. It's kind of a hack, but it would work.

Yeah, because really all automation or upsell is doing is using automation in the back end to send an email or text template. So you can really use it however you'd like in terms of notifying a client based upon certain inputs. And then you can name those however you'd like as well. So. All right, see what we got. Brian has. It would be great to be able to add video links to job notes. The crew can click on the video link when they arrive on the job site. This is not possible in sa. Yeah, so we actually have a ticket that won't be done by March 1, but it is very similar in terms of what they have at Company cam and videos being able to be attached to specific line items as well as specific estimates. So that is something that's on our roadmap. It's not going to be done by March 1st, like when we're talking about chemical applications, but it is definitely on our horizon. And I do believe. Can't correct me if I'm wrong here, George, can you add a video link already inside of job notes?

You could add it as a link if it's uploaded somewhere else and you just want to share it that way. And I think you can even embed a video too. So if you wanted to copy, like the embed code from YouTube, I believe that works also.

Yeah. And that is simply because we have the email plugin, or, sorry, the. The plugin for email that has video in there. So, Brian, specifically speaking to sa, that's what they're lacking. It's just an extra plugin.

All right, let's see here. I second the condition codes. Yes. I would probably use tags right now and upsells to be able to write off the bat. I do think that down the road, potentially upsells could be something that we change in terms of verbiage, kind of like we do in terms of where you're allowed to currently customize the name of your menus. You could change this down the road to be like condition codes. And then you just literally would.