A Note on Our Current Support Response Times

Dear Yarbo Family,

Since May, our support ticket backlog has been growing. The start of mowing season, combined with our expanding user base, brought a significant increase in ticket volume. At the same time, while implementing several important platform and service improvements, some of our internal diagnostic workflows were temporarily impacted, affecting resolution efficiency. We believe these improvements couldn’t wait — but we should have planned better for the service impact they would cause. That’s on us.

Some tickets have gone days without any response at all. We know what that feels like — you reached out, and heard nothing back. That’s not acceptable, and we’re not going to dress it up with excuses. We own this, and we sincerely apologize to every member of the Yarbo Family who has been affected.

What Team Yarbo Is Doing About It

:wrench: Growing Our Team We are significantly scaling up both our customer service team and field service engineers (FSE), with new members joining this month and onboarding continuing into next month — and we’re not just hiring: our customer service lead and engineers are personally overseeing the recruitment process, providing one-on-one training, guidance, and support to every new team member who comes on board.

We’re not looking to fill seats. We’re looking for people who genuinely care about getting your problems solved.

:gear: Improving Our Processes We’ve done a full overhaul of our ticket handling and replacement workflows, and strengthened our diagnostic SOPs to help our team resolve issues faster and more effectively. We are also introducing AI-assisted diagnostic tooling to help our team more accurately identify the root cause of issues and determine the right solution — so that when our agents respond, they’re responding with the right answer.

:speech_balloon: Staying Present Across Every Channel Every active ticket is being monitored and tracked by our team to ensure nothing gets lost in the queue. At the same time, Team Yarbo remains present across our Facebook community, official forum, and Discord — answering questions, providing guidance, and supporting users directly while tickets are being processed.

:clipboard: How Our Ticket System Works To keep our queue moving and ensure no ticket is forgotten, here’s how our closure process works: if we haven’t heard back from you within 24 hours of our reply, we’ll send a follow-up email. If there’s still no response after another 48 hours, the ticket will be automatically closed — but it won’t disappear. All closed tickets remain visible in your Support Center, and you can reopen one at any time with a single click. If you reply to a closed ticket, it reopens automatically.

:open_book: Your Self-Service Knowledge Base We also want you to have somewhere to turn while you wait. Our Yarbo Wiki is home to a growing library of troubleshooting guides and feature explainers — we’d encourage you to check it out first, as your answer may already be there.

The Wiki is a living resource, and we know it’s not complete yet. If you come across a topic we haven’t covered, please leave a comment at the bottom of the page — your feedback directly shapes what we write next.


Where We’re Headed

As new team members come on board and our process improvements take hold, we’ll be driving response times down and working through the backlog as fast as we can.

To every member of the Yarbo Family: we know your trust in us wasn’t given lightly. “We’re a growing company” isn’t something we’ll hide behind — what we owe you is action, not explanation.

Team Yarbo

I’ve notice the better response time in just the last day or so.

It helps the app is running a little smoother too.

Just got an update on one of my tickets that was total crap. It essentially told me that due to support taking so long to look at my ticket, that I was unable to get help with my issue. The logs which captured the issue had been overwritten. Essentially, this starts the whole process from the beginning and how is that helpful to anyone?! For what it’s worth, that ticket was opened 21 days ago now. If overwriting the logs was a possibility, you would have thought that would have been the first thing they did…pull the logs. Instead, they asked me for a video and wanted me to clarify the time/date that it occurred. I provided them right away…then waiting for weeks to be told I was out of luck. Ridiculous!!

We are sorry for this. I’ve checked your ticket #204314 in our system and it seems the issue has not occurred again.

If the issue happens again, please feel free to use the “Record Issue” function and update us through the existing ticket thread. We will investigate it as soon as possible.

Hello,

First of all, thank you for outlining the reason for the substandard response time. I was beginning to think I myself was being ignored.

Having run a technical support group, I do understand the challenges involved with balancing resources with the expected demand.

Here’s my plea. I have two outstanding tickets that have not yet been resolved. One stretching back to early June, the other is more mission critical. My Yarbo system is currently unusable.

Is there any way to get someone to look at these tickets? I’ve gone back to using my riding mower until the Yarbo is back up and running.

I appreciate any help you can provide.

Regards,

Rob Donald

Carleton Place, Ontario

Tickets 215505 & 208471

@Yarbo-Forum help please

I was hoping this would be the first year that we would be able to fully use Yarbo. It would probably also be the last year, because this is the last year of warranty we have. Is warranty extended for another mowing season when support is silent or do we get our money back when no support is provided?

Thing is: Yarbo breaks down often. It is hard to notice defects when it can’t be operated. It can’t be operated when there is no grass. I guess we’re afraid that by the end of warranty your team will be deaf to reason even if issues were already there. Perhaps even for the current issues. We would like a fully working Yarbo for at least one full mowing season which is not much to ask for the price.

Thanks for your understanding! Regarding your support ticket #208471, we have already initiated the replacement process for you. It may take a little more time before the replacement can be shipped, and it’s currently expected to be sent out within about a week.

As for your ticket #215505, our support team will follow up with you as soon as possible. Thank you for your patience and understanding!

#207488 please take care of my issue ; it’s been sitting almost a month!

@yjjadara Hi there, sorry for the delayed response. I’ve reached out to our team and asked them to review your case as soon as possible.

Hello,

I think Yarbo management needs to start thinking about how to compensate customers who experience excessively long wait times in their tickets being addressed and ultimately solved.

I myself have a non operational system for a couple of weeks without any clear indication of when I might see a resolution to the problem. I know from reading the various online forums, I am certainly not the only one in this position.

I live in eastern Ontario, where the grass cutting season is relatively short. Losing a month or more of use represents a non-insignificant portion of my season.

What is Yarbo prepared to do to make this right?

Rob Donald

I agree with you, Rob. They should treat us customers, not as beta users!!!

Really sorry for the inconvenience caused. I’ve checked your ticket and asked the FSE team to follow up as soon as possible.

We truly appreciate your understanding, including the compensation-related concern, and we will make sure it is properly reviewed as part of the follow-up.

@Yarbo-Forum, this is simply not acceptable.
Yarbo’s lack of proper planning is not my problem, it’s theirs. I don’t want to hear excuses, I want action. What are you doing to solve my problem “now”.

First I waited over a month to receive my Yarbo. I barely mapped the yard and started it mowing, when the right track locked up. Less than 4 hours of actual run time!

Support has been slow to respond to my requests and when they do respond, they are not resolving the issue.

One message going back and forth ONE TIME a day (if I’m lucky) is NOT support.

I want my ticket (216077) resolved.
I paid $6,000. USD for this machine and so far I have absolutely nothing to show for it. This may not be a lot of money to some, but to ME this is a huge amount to spend on a product that does not work.

Hi there, I completely understand your frustration, and I’m sorry for the delay and inconvenience you’ve experienced.

I’ve just reached out to our team and asked them to prioritize your case and provide an update as soon as possible. You can expect to receive a response within 24 hours, and I will also continue to follow up on the progress to make sure there are updates moving forward.

Thank you for your patience while we work on this.

Our FSE has just confirmed that we will initiate a brand-new Core replacement for you. The team will provide the next update through your support ticket soon.

Thank you for your patience and understanding.