NEW:
Turn Customer Data into Revenue with AI-Powered Smart Campaigns
.webp)
Welcome to the eighth episode of Flyntlok Unlocked.
The idea here is to take you behind the scenes, unlocking Flyntlok product insights, with the very people building and implementing the tools you use every day. Thank you for joining us!
I’m your host Jenny Moebius, Flyntlok’s CMO, and today we're talking about one of the most valuable resources inside any equipment dealership:
technician time. And how to save technician time, in this case, using AI.
Dealers are constantly looking for ways to improve technician productivity, get more work through the shop, and grow service revenue. But there's a problem.
Not every minute of a technician's day is spent servicing equipment. They also have to document what they found, what caused the problem, and what they did to fix it. And, documentation matters. You need good service records.
But every minute a technician spends stopping to type is a minute they aren't turning a wrench. Multiply that across every technician, every work order, every day — and what looks like a small administrative task starts consuming real shop capacity.
So the question becomes:
How do you get the documentation you need without sacrificing the technician productivity that drives service revenue?
That's exactly the problem we’re solving with our newest AI-powered tool: Smart Tech Notes.
--
Host: Jenny Moebius, CMO, Flyntlok
Guest: Bomby Kitchpanich, Senior Software Engineer, Flyntlok
Technician time is one of the most valuable, and finite, resources inside an equipment dealership.
Every hour technicians can spend diagnosing, repairing, inspecting, and servicing equipment is productive capacity for the service department. But not every minute of a technician’s day is spent turning a wrench. There’s also the documentation that comes with every job: recording what the customer reported, what caused the issue, and what was done to fix it.
That documentation matters. Dealerships need clear service histories, accurate warranty submissions, and records that service writers can confidently share with customers.
The challenge is getting those records without allowing the administrative work behind them to eat away at technician productivity.
In Episode 8 of Flyntlok Unlocked, host and Flyntlok CMO Jenny Moebius sits down with Bomby Kitchpanich, Senior Software Engineer at Flyntlok, to demonstrate Smart Tech Notes, Flyntlok’s AI-powered approach to technician documentation.
The premise is straightforward: instead of stopping to type detailed service notes, technicians can simply explain what they did out loud. Smart Tech Notes transcribes that explanation, understands the service terminology being used, cleans up the language, and structures it into professional Complaint, Cause, and Correction notes.
The result is about more than saving a few keystrokes. It’s about giving technicians more of their day back for revenue-producing work.
Bomby begins by describing a workflow familiar to service departments everywhere.
A technician works on a machine, completes a repair or moves a job forward, and then needs to document everything that happened: the work performed, additional issues discovered, parts used, and other relevant details.
There are generally two ways that happens, and neither is particularly efficient.
A technician might complete a long stretch of work and then return to a computer afterward, trying to remember everything that happened and reconstruct it in detail.
Or the technician might document the job incrementally: perform a task, stop working, clean up, walk over to a computer, type a note, then return to the machine and figure out where they left off.
Do that repeatedly throughout the day and the interruptions start to compound.
As Bomby explains, technicians are being pulled away from the work they were ultimately hired to perform. Jenny connects that operational friction directly to dealership economics: technician time is finite. If a dealership has eight hours of technician capacity available in a day, every portion of that time spent on administrative work is capacity that cannot be used to diagnose, repair, inspect, or maintain equipment.
What feels like a small inefficiency on one repair order becomes much more significant when it is multiplied across every technician, every work order, and every day the shop is open.
There is another problem when technicians feel pressure to get back to the machine quickly: the notes themselves can suffer.
A rushed technician might leave out context, use shorthand that isn’t clear to someone else, or provide a description that makes perfect sense to the technician who performed the work but not necessarily to the service writer who needs to turn it into a customer-facing explanation or warranty claim.
As Bomby puts it, work can get “lost in translation.”
The service writer then has to decipher the notes, rewrite them, determine which parts were used, understand what hours should be associated with the work, or go back to the technician for clarification.
In other words, the dealership can effectively pay for the administrative burden twice: once when the technician stops productive work to document the job, and again when the service writer has to clean that documentation up.
Bomby draws an analogy to his own work as a software engineer. He enjoys building and writing code; documentation is something he knows is necessary, but it interrupts the flow of the work he wants to be doing. He sees a similar dynamic with technicians.
The objective, then, isn’t to eliminate good documentation. It’s to make producing good documentation dramatically easier.
That is the problem Smart Tech Notes was designed to solve.
Bomby describes it simply: technicians speak into a microphone and explain what they did, while Flyntlok produces a cleaned-up, well-formatted write-up that a service writer can use.
During the episode, Bomby demonstrates the workflow inside a Flyntlok work order.
Rather than manually typing into Complaint, Cause, and Correction fields, the technician selects the AI voice-notes option and starts recording.
From there, the technician can speak naturally.
There is no requirement to dictate perfectly structured notes or speak in formal sentences. The technician can describe the repair the same way they might explain it to another person standing next to the machine.
To demonstrate, Bomby deliberately gives Smart Tech Notes a challenging example. He rambles for roughly 30 seconds, includes filler words, jumps between topics, uses industry terminology and shorthand, and even remembers an additional customer complaint partway through his explanation.
He describes a 1,000-hour service, engine oil and filters, fuel filters, an air filter, hydraulic oil, differential fluids, grease, and an air-conditioning problem. He also includes specifications such as oil weights, refrigerant type, refrigerant quantity, and the final vent temperature.
Within seconds, Flyntlok transforms the explanation into an organized Complaint, Cause, and Correction record.
Instead of handing the service writer a raw voice transcript, the AI breaks the work into a scannable structure and formats technical language appropriately.
The technician reviews the result, applies it, and can move on to the next task.
One of the most important elements of Smart Tech Notes is that it doesn’t ask technicians to adopt an entirely new workflow.
The feature is available on both desktop and mobile.
That matters particularly for technicians who work throughout the shop with a company-issued phone or tablet, as well as field technicians servicing equipment at a customer location. They don’t have to return to a workstation simply to document the job.
The larger design principle is to let technicians capture the information in the flow of doing the work.
They perform the work, explain what happened while the information is fresh, review the resulting note, and continue.
That simplicity is also one of Bomby’s favorite parts of the feature. In the episode’s lightning round, he explains that Flyntlok isn’t telling technicians to completely change how they use the DMS. Smart Tech Notes simply gives them an easier option for completing something they already have to do.
That makes the value easier for technicians to understand—and makes adoption easier as well.
Voice transcription itself isn’t new.
And that distinction is important.
Simply replacing a keyboard with dictation doesn’t completely solve the dealership’s problem. If a technician speaks for 30 seconds and the service writer receives 30 seconds of unedited, rambling speech converted word-for-word into text, someone still has to clean it up.
The administrative work has simply moved from the technician to the service writer.
Smart Tech Notes adds another layer.
Bomby explains that the AI is designed to understand both sides of the service workflow: how technicians naturally describe their work and how service writers need that work structured afterward.
That means Smart Tech Notes can:
In the demonstration, the system correctly interprets and formats terminology that generic dictation software could easily misunderstand.
The goal isn’t perfect transcription.
The goal is usable service documentation.
For Jenny, this is where the value of Smart Tech Notes becomes most important.
The feature isn’t really about saving a technician a few keystrokes.
It’s about what happens when Flyntlok takes more of the transcription, writing, formatting, and structuring work off that technician’s plate.
For technicians who aren’t fast typists, or simply didn’t choose their profession because they wanted to spend their day behind a keyboard, the time savings can be immediate.
And saved technician time translates into additional productive capacity.
That creates several potential benefits for the dealership:
As Jenny summarizes during the conversation: time is money.
For a service department, the ultimate opportunity is to create more productive capacity from existing headcount and put more technician time toward the work that drives service revenue.
The initial version of Smart Tech Notes starts with voice, but customer feedback quickly highlighted another opportunity.
Service writers pointed out that plenty of technician notes already exist as written text. Some come from older work orders. Some technicians may simply prefer typing rather than recording their voice.
So the question from service writers became: what about us?
Flyntlok is extending the same AI-powered cleanup capabilities to existing written notes.
Rather than requiring a voice recording, a user will be able to take an existing Complaint, Cause, and Correction entry and ask Flyntlok to improve it with AI.
The underlying idea is the same: remove unnecessary administrative work regardless of how the information originally entered the system.
Jenny also connects this development back to a larger Flyntlok product philosophy: AI may allow the company to build faster, but customer feedback helps determine where that speed should be directed.
Smart Tech Notes itself is an example of that cycle.
When Jenny asks what surprised Bomby most while building Smart Tech Notes, his answer is the speed at which people understood its value.
During early demonstrations, dealers immediately grasped what the feature could do.
The response was essentially: When can I start using it?
That reaction gave the development team a strong signal to move quickly.
According to Bomby, Flyntlok went from those early demonstrations to putting the feature in the hands of beta users in less than a month. Less than another month later, it had been released more broadly.
The rapid adoption reinforces one of the central themes of the episode: some of the most useful applications of AI aren’t necessarily the most futuristic.
They solve an existing, repetitive problem that people encounter every day—and make that problem noticeably easier.
Smart Tech Notes may remove one piece of administrative friction, but Bomby sees additional opportunities for AI throughout the service workflow.
One is using a dealership’s own service history and data more intelligently.
In the future, AI could potentially help technicians understand recommended work based on previous repairs, surface relevant corrective steps, or reference information contained in official manufacturer documentation.
That would bring AI into the front end of the service process as well—not just documenting what happened after the repair, but helping technicians access the right information while determining what needs to happen next.
Bomby also sees opportunities to expand the use of voice.
Today, Smart Tech Notes reduces the need to type. But technicians still use a mouse or touchscreen to move through the work order, complete steps, and close out portions of the workflow.
A future voice-driven interface could potentially allow technicians to navigate more of that process without stopping to click through screens at all.
The common thread is reducing the number of administrative interactions sitting between technicians and productive service work.
Smart Tech Notes reflects the type of AI Flyntlok is focused on building.
Not AI added to a product simply so “AI” can appear on a feature list.
And not AI designed to replace the people whose expertise keeps the dealership running.
Instead, it’s AI aimed at the repetitive administrative work surrounding those people.
Technicians still provide the diagnosis, judgment, experience, and hands-on expertise. Smart Tech Notes simply makes it easier to turn that expertise into the documentation the rest of the dealership needs.
The equation is straightforward:
Less time typing.
More productive technician capacity.
Less rewriting for service writers.
More opportunity to move revenue-producing work through the shop.
For dealerships working to improve service productivity and protect margins, the value of saving a few minutes isn’t really about the minutes themselves.
It’s about what the dealership can do with them.
As Jenny closes the episode, Smart Tech Notes helps technicians spend more of their day doing the work they enjoy, and the work that ultimately drives service revenue.
Until next time, keep building the world around us.
