Mike Minutes Mastermind 04/21/22

A recorded Mike Minutes mastermind (4/21/22) where Mike Andes answers operator questions about running field-service businesses. Main themes: changing invoicing cadence (monthly→weekly) and requiring card-on-file via the credit-card-ask automation; reasons to avoid weekly customer receipts for mowing (to reduce churn); how dispatch reminders/tags work in Service Autopilot/Zooper; paystub treatment of performance bonuses vs. deductions; and why bulk automated price increases are technically possible but risky—manual adjustments are recommended for smaller lists.
Questions this video answers
Change the credit-card-ask automation wording to state a credit card is required to get on service; verify card-on-file before scheduling and re-send the card request email if missing.
Change each customer's billing frequency to weekly so draft invoices are completed at the end of each week rather than the month.
No. Pay stubs show hourly wages (hours × rate) and a performance bonus (performance dollars); P4P deductions appear on the daily report as manual adjustments, not on pay stubs.
Add the dispatch tag to the customer's profile; the service-dispatch reminder automation (currently only for recurring services) will then email them (e.g., a 'we're coming tomorrow' notice).
Technically possible but risky. Mike recommends doing manual price updates for smaller lists (<~500 customers) to avoid errors; alternatively use custom fields and email templates to communicate increases without mass-changing all future job prices.
Chapters
Good morning guest nation. Hope you're all doing fantastic. I'm gonna go ahead and open up some questions. I didn't really have anything specific to go over a whole lot this morning. Let me go ahead and share.
Boom, boom, boom. Okay, I think we had four questions coming so let me go through these. Let's see here. I want to switch weekly. I want to switch to weekly invoicing and card on file for mowing customers. How should I make that switch? Trying to figure out the workflow of getting cars involved before mowing can mows can be scheduled. Should be an adjustment to automations would command center call. I am full service although I don't want to put a burden on you guys. Or should I get, should I call to get cards myself? You shouldn't have to call honestly I would just adjust the credit card ask automation that's currently in there and just change your verbiage to be a little bit more forceful. Like right Now I'd say 80 plus percent of people just put their cards on anyways because the way we pitch it. But you could say in there that credit card is required in order to get on service and then what you would do is before you schedule the job, before you actually put it on the schedule, you'd make sure that they have a card and file. If they don't just drop in an email and then they can do it again or send the credit card ask email again manually and just you know put this needs to be done in order to get on the schedule. But again if you just change the credit card ask automation and say in order to get on the schedule a credit card on file is required. If you change that one thing and bold that you'll probably get 95% conversion right off the bat. So the last thing you want to be doing is calling people for cards because half the time you get their voicemail, half the time they're not next to their wallet and it's just. You're just wasting time honestly. So you want the automation to carry it and it can in terms of switching to weekly you got to change everyone's billing frequency to weekly and then that would turn draft invoices into complete invoices at the end of the week instead of the end of the month. So that's, that's what you would do in order to make that switch.
Maps do you show? And just so everyone's clear, the reason we don't do that is because when the mowing slows down I don't want to be reminding Someone four times a week with a receipt that we're coming. I'd rather just do it once a month and then once a month do the one click estimate email. That's why we don't do it. I know for a cash flow perspective it's better the same thing with collecting up front, but I'm more concerned about them opening up the one click estimate email because down the road that will be the driving force of all your leads. And then secondarily is the fact that when the grass slows down, a larger percentage of your customers will pause or reduce their service frequency if they are constantly reminded via an invoice or credit card charge on their billing statement. So. So I know it's not as good from a cash flow perspective, but I'm willing to take that hit in order to only get maybe 5 or 10% of customers to reduce services for us. Like locally for example, it's July, August, some of you it, it might be December. January slows down just a little bit. For mowing, I'd rather keep them on a a higher frequency by not reminding them them seeing a charge every single week of on their account and then email, invoice receipt, et cetera. Do you show deductions from P4P on pay stubs or do you just let the crew know how much they missed on because of the ls? Yeah, so it doesn't show in the pay stubs because all it's going to show on the pay stubs is their hourly rate multiplied by the hours and then a bonus which is the performance dollars.
And in terms of letting them know how much they missed that would be on the daily report. They would see that in the manual adjustments. So they would. They do see it. They just don't see on their pay stubborn. The only thing they see in their paste of if they see performance dollars.
Here Nick. Service dispatch reminder. Does a client get an email of the service being dispatched for mowing and projects every single time you dispatch or do you have to physically add the tag to their account in order for them to get it? Yes, if you add the tag to their account then going forward they will get email notification that you are coming tomorrow. And so you can adjust all of that inside of the service dispatch reminder automation. This service autopilot and if you want that changed currently it is only for recurring services. If you want for projects for example, you would need to change that automation to include those services. Right now it's only for like recurring services and that tag is currently mostly used for someone that is on a recurring basis and wants to be notified the day before for whatever reason, they just want to know that you're coming tomorrow. So there's obviously more, more individualized ones like the dog poop pickup, one reminder to open, unlock their gate, things like that. But if you just want to generalize, hey, we're showing up tomorrow, just letting you know there's an automated message, then that's what you would do. Just add the tag, their profile and then whatever you want, whatever services you want that attached to just make sure you change in the automation to make sure that it's done correctly.
In Super. Do you think that they would add a feature like as soon as a job gets dispatched and assigned, it will send them an email with the employee's face and like a short bio about themselves? I think people would really like that. Yeah. So it kind of goes back to that same thing. Like this is possible now in service autopilot, it's possible in Zooper. I'm sure the bottom line is two things. When you start over communicating with a customer, you do open up room for error. So when you have one or two employees, this would work really well. When you have three or four might even work well. But when you have 10, 15 employees, someone doesn't show up. And now a job that's been dispatched and moved to someone else and do they get an email again or do they just show up as a different person? So things like that, logistically, you know, when you start getting larger and larger, start becoming very more, a lot more operational drag. And then secondarily would be again, I don't really want to email them every single week just about who's coming to their property. I'd rather just because they're not going to, they're going to end up not opening up that email eventually. If you have a couple employees, they're going to see it's going to be the same person every time. And if you have a lot of employees, you're going to start getting people being picky and choosing who they want. And so I think from an estimator standpoint, it makes sense. And that's why again, you can do the in service autopilot. We already have the automation built for Zooper to do on your way notifications to the customer letting them know you're on their way. And you could put in the resource picture or something like that there. But I'm not, I don't really want to bother a customer every single week with who's coming to their property. Which is opening me up to issues but then also again diluting that one click estimate email that is going to be the driving force of all your marketing eventually. So I know, I know when you're first getting started that the value of that email and that one click SM email is lower. But as your, your database grows it literally you protect that thing with your life because it is your marketing budget, which is zero, but it replaces your marketing budget. You don't have to go out and spend money on leads. So you start to defend it a lot more as you start to see that value. So I don't think there's any more. Just double check. Nope. Okay. No more questions there. Feel free in the comments. If you'd like to make a comment or ask a question in the Facebook or YouTube, feel free to ask a question. I'll stick around here for a second.
Cool. Let's see anything coming in yet. But I'll stick around just for a second in case someone's typing.
Can you shed some light if Zooper will have the ability to bulk increase pricing? It sounds easy but can become a very complex task to develop in code side.
This is something that you, that is, that can be done.
Just trying to think. I know right now they don't have the functionality and I know that some things are possible in code and then other things when you do it, you just know you're going to open yourself up to a massive amount of error. And so if you, if you were to do bulk price increasing, actually changing the job prices is very complex and it opens up like I don't even know if I'd do that. If I had less than 500 customers and I was price increasing them all or a segment of them. I just do it manually. Like the extra day it's going to take you to change all their prices manually. I want to make sure they're done right. Because just messing up 5 or 10% of them because of a technological issue or because something's read wrong in the code and then change the jobs and then maybe the scheduling is messed up or something like that. I would want no margin of error when I'm raising the prices. So I'm sure, like I know it's possible. It's just a matter of do you actually want an automated system that will change the price on all recurring jobs going forward? Like just open yourself to a lot of margin of error based upon like, okay, if I filter certain things, I want to raise only these people's prices and I want you to change all the jobs going forward, that. That's a steep task. I would much rather just at the beginning of the year when I'm sending out, hey, we're getting started. Give the price increase there, have it tied to the custom fields. Those can be updated much faster. The email can be sent out using those, those custom fields to pull in the number. But actually changing, like, all the recurring jobs and things like that, there's not a feature right now in super, and I'm not really going to push for it, honestly, because I just see a massive amount of error potentially happening. I would never leave one click of a button to a massive price increase. And even if you have 30 or four customers, it becomes like, well, then why not just do it manually? You could probably do it in a couple hours. And so I don't know if I would ever trust, ever trust a manual price increase that would change the jobs going forward, honestly.
And like I said, when it comes to super features, there's something that we would. We kind of all talk about, see which one or two we want to kind of push forward. And I know that opens me up to having to make that decision and turning which ones are most priority for us all. But at least we have the flexibility and there's stuff that we can change instead of having to just do workaround after workaround after workaround with service. Hot pot.
Cool. All right, that's all the questions I got today, so thanks so much, everyone. I'll see you tomorrow morning.










