Building software is humbling. No matter how well you design a product, the real world has a way of introducing scenarios you never anticipated, and customers who find brilliantly creative ways to use (and occasionally break) what you’ve built.
Over the years, Moki’s team has worked with organizations across retail, hospitality, healthcare, manufacturing, transportation, and dozens of other industries. Each partnership has taught us something. This post is a reflection on the most valuable lessons our customers have shared, lessons that have shaped the platform and the way we think about mobile device management.
Lesson 1: The Device Is Never “Just” a Device
Early in our history, we thought about MDM primarily as a technical problem: how do you push policies to a device efficiently? What we learned from customers is that every device represents a moment of truth with an end user, a customer trying to check in, a patient accessing health information, a traveler checking a flight status.
When a device goes down, it’s not an IT incident, it’s a customer experience failure. This realization shaped how Moki thinks about uptime monitoring, alerting, and response time. We don’t just track whether a device is “online”, we track whether it’s functioning the way a real user would need it to.
Lesson 2: “Set It and Forget It” Will Eventually Hurt You
We’ve seen this pattern repeatedly: an organization deploys 50 kiosks, everything works great for 6 months, and then a combination of OS updates, app changes, and gradual hardware degradation creates a slow-motion crisis. Suddenly half the fleet is underperforming and nobody knows when it started.
The lesson: MDM is not a deployment tool, it’s an ongoing management discipline. Our blog on why “set it and forget it” is the wrong MDM strategy goes deeper on this, but the short version is that devices need regular attention even when they seem fine. Scheduled maintenance, proactive monitoring, and periodic configuration audits are what separate good fleet management from lucky fleet management.
Lesson 3: Complexity Kills Adoption
We’ve seen organizations invest in enterprise MDM platforms with every feature imaginable, and then use about 10% of those features because the interface is so complex that only one person on the team truly understands it. When that person leaves, the MDM becomes an expensive mystery box.
Customers taught us that ease of use isn’t a “nice to have”, it’s a critical success factor. If your IT team can’t quickly figure out how to push an app update or remotely restart a device, the platform isn’t doing its job.
This principle is baked into Moki’s design philosophy. We build for the operations manager who needs to check device status from a phone while on a factory floor, not just the IT architect who designed the deployment.
Lesson 4: Remote Locations Are Where MDM Pays for Itself
Organizations with a single location or a centralized IT team often don’t fully appreciate MDM’s value at first. It’s the multi-location operators, retail chains, restaurant franchises, healthcare networks, who feel it most viscerally.
One customer with 40+ retail locations told us: “Before Moki, a manager would call IT about a broken kiosk, IT would create a ticket, and we’d either drive 2 hours to fix a 5-minute problem or let it sit broken for days. Now we fix it in the same phone call.”
That compression of response time, from days to minutes, is transformative for businesses where device uptime directly connects to revenue.
Lesson 5: The Enrollment Experience Sets the Tone
Customer feedback consistently identifies device enrollment as the most anxiety-inducing part of an MDM implementation. Organizations with hundreds of devices to onboard worry about it becoming a multi-week IT project.
What we’ve learned is that zero-touch enrollment is a genuine game-changer for these customers. When devices can be enrolled automatically, simply by powering on and connecting to Wi-Fi, it removes the biggest friction point from deployment. The organizations that invest time in setting up zero-touch enrollment properly always report it as one of the best decisions they made.
Lesson 6: Support Quality Is the Product
We’ve heard many variations of the same story from customers who came to Moki from larger MDM providers: “The platform had more features, but when something went wrong, we were on our own.” Support ticket queues measured in days. Unhelpful documentation. Account managers who disappear after the sale.
This feedback reinforced something we believed from the start: for the kinds of organizations Moki serves, businesses where devices are core to operations, support quality isn’t a bonus feature, it’s part of the product. When a kiosk goes down during a busy Saturday, you don’t need a ticket number. You need someone who picks up the phone.
Lesson 7: The Best MDM Implementations Are Collaborative
The organizations that get the most out of Moki aren’t the ones who read the documentation and figure it out alone. They’re the ones who treat implementation as a partnership. bringing their operational knowledge to the table and letting Moki’s team bring the platform expertise.
They share context: “Our devices are in a high-traffic public environment and get physically abused.” “Our staff turnover is high so we need everything to be idiot-proof.” “We have locations in areas with unreliable Wi-Fi.” That context shapes how we configure the platform for them, and the results are dramatically better.
If you’re evaluating MDM solutions, we’d encourage you to evaluate the vendor relationship, not just the product features. The platform you can grow with, supported by a team that knows your environment, is worth far more than a feature checklist.
A Thank You to Our Customers
Every lesson in this post came from a real conversation with a real customer facing a real challenge. We’re grateful for the organizations that have trusted Moki with their most business-critical devices, given us honest feedback when things weren’t working, and pushed us to build a better product.
If you’re not yet a Moki customer and you want to experience this kind of partnership firsthand, schedule a demo or start a free trial. We’d love to learn from you, too.