NEW:
Save Technician Time and Drive More Service Revenue with Voice-to-Text, AI-Powered Tech Notes
.webp)
Welcome to the nineth 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 something deceptively simple:
Following up with your customers.
And when one of those follow-ups gets forgotten, the customer may have to chase YOU.
Worse, a big opportunity can quietly go cold.
And that's where this becomes more than a productivity problem.
It's a revenue problem.
So today we're going behind the scenes of Flyntlok's newly revamped CRM Tasks: what we've started calling our Customer Relationship Command Center.
And importantly, this isn’t a separate CRM bolted onto your dealership software. It’s built directly into Flyntlok, so the customer relationship lives alongside the equipment, transactions, service history, and operational data your team already works with every day.
--
Host: Jenny Moebius, CMO, Flyntlok
Guests
Every equipment dealership makes promises to customers all day long.
“I’ll call you back.”
“I’ll send you a quote.”
“Let me check on that machine.”
“I’ll follow up with you next week.”
Individually, none of those promises sounds complicated. But multiply them across every salesperson, department, location, and customer, and suddenly a dealership has hundreds of follow-ups competing for attention.
And too often, those follow-ups are scattered across sticky notes, personal notebooks, phones, inboxes—or simply living in someone’s head.
In Episode 9 of Flyntlok Unlocked, host Jenny Moebius sits down with Flyntlok engineers MA Sharp and Ula Lapkus to take a closer look at Flyntlok’s newly revamped CRM Tasks—what the team has started calling the Customer Relationship Command Center.
The goal is bigger than creating a better to-do list. It’s about giving every customer promise an owner, the right context, a clear next step, and a much better chance of ultimately becoming revenue.
And because the CRM is built directly into Flyntlok, those customer relationships don’t live in a separate system disconnected from the dealership. They live alongside the machines, leads, transactions, work orders, contacts, and other operational information employees are already using every day.
Before jumping into the product, Jenny, MA, and Ula start with the problem dealers are trying to solve.
Ula has heard a wide range of approaches from equipment dealers: follow-ups written down on paper, stored on employees’ phones, kept in notebooks, or simply remembered mentally. One dealership even described an office covered in Post-it Notes containing different customer reminders.
Those systems may work when a dealership is small and everyone knows what everyone else is doing.
But as more employees join the business—and especially as the dealership adds locations—the cracks become much easier to see.
A salesperson takes a day off. Someone else needs to speak with their customer.
A customer calls asking about a previous conversation. Nobody can immediately see what was promised.
A quote goes out, but nobody remembers to follow up.
An opportunity that looked promising quietly goes cold.
According to MA, the downstream impact is straightforward: lost revenue and a worse customer experience.
When customers repeatedly have to call a dealership for updates, confidence starts to erode. And when follow-ups disappear into a busy employee’s day, a potential sale can disappear with them.
That makes follow-up much more than an organizational problem.
It’s a revenue problem.
A callback could become a sale. A quote followed up at the right time could become an order. A conversation that seems casual today could become a major equipment opportunity six months from now.
And in an industry built heavily on relationships, the customer shouldn’t have to chase the dealership to keep that relationship moving.
At the center of the new experience is a major rethink of Flyntlok CRM Tasks.
MA describes tasks as an important part of the sales pipeline. Rather than treating them as isolated reminders, Flyntlok is making them increasingly connected to the larger DMS and the customer information already stored there.
The revamped experience starts with two key areas:
One way to think about it is simple:
The Task List tells you what needs your attention. The Task Details page tells you why it needs your attention—and gives you the tools to act on it.
That distinction is what starts transforming a task manager into a true customer relationship workspace.
Ula begins the demo with the CRM Task List.
Employees can see their tasks along with information such as the task name, description, due date, status, priority, and primary contact.
But dealerships—and the people working inside them—don’t all need to look at CRM information the same way.
So the table can be sorted, filtered, and customized.
An employee can add or remove columns and save the layout that works best for them.
That matters because a salesperson may primarily want to answer:
What do I need to do today?
A manager may instead want to know:
Which tasks across my team are overdue?
Or:
Where are our highest-priority customer follow-ups?
The underlying information stays consistent, but each employee can organize it around the decisions they actually need to make.
One of the biggest barriers to CRM adoption is friction.
If documenting a quick customer promise takes five minutes and requires filling out an enormous record, employees simply aren’t going to capture everything.
The new task workflow is intentionally designed to start small.
A salesperson could create a task as simple as:
“Call Jane back.”
From there, they can add as much context as the situation requires: a description, due date, priority, status, assignee, customer, contact, machine, make and model, or related lead.
During the demo, Ula creates a callback task and links it to a customer and a John Deere make and model.
Once the customer is selected, Flyntlok automatically surfaces the contacts associated with that customer. Rather than forcing the salesperson to search somewhere else for a phone number or recreate information that already exists inside the DMS, the CRM brings that information directly into the task.
That makes capturing a promise fast enough to become part of the natural workflow.
And perhaps most importantly, once the task has a due date, the employee no longer has to personally remember when the follow-up should happen.
The follow-up starts chasing the salesperson instead of the salesperson having to remember the follow-up.
Creating the task is only the beginning.
The redesigned Task Details page is where the “command center” concept really becomes apparent.
Instead of showing an employee nothing more than “Call customer,” Flyntlok brings together the information that helps them understand the relationship before making that call.
Employees can see and manage information such as:
A secondary assignee can also be added so someone else can stay informed and receive notifications if the primary salesperson is unavailable.
That becomes particularly valuable in a dealership environment where customer relationships can span employees, departments, and locations.
Instead of the customer story disappearing when one employee is out, the context stays with the relationship.
And because records can be linked directly to the task, employees don’t have to reconstruct the story months later.
If the conversation involved a particular machine, sales order, work order, or customer record, that connection can remain attached to the task.
As Jenny explains in the episode, there’s a significant difference between seeing “Call customer” and actually being ready to call that customer.
The Task Details page helps make those answers available before the conversation begins.
This context also highlights one of the most important aspects of Flyntlok’s CRM: it’s built into the DMS.
Equipment dealerships don’t manage generic customer relationships.
The equipment itself is part of the relationship.
A salesperson may need to know exactly which machine a customer owns, which model they are currently considering, which quote they received, or where a particular opportunity stands.
That’s different from a disconnected CRM that only knows a customer name and a list of sales activities.
Because CRM Tasks live inside Flyntlok, they can connect directly to the operational information surrounding that customer.
As Ula explains, a generic task-management tool might know the name and description of the task. But employees could still find themselves repeatedly typing the same phone numbers, customer details, machine information, and notes.
Flyntlok already knows the customer behind the task.
That means the follow-up can become part of the broader customer relationship rather than another isolated record employees have to maintain.
One of the most common CRM frustrations happens after someone completes the actual customer interaction.
A salesperson makes the call.
Then they have to remember to log the call.
They send a text.
Then they have to document the text somewhere else.
They have a productive conversation.
Then they’re asked later: “Did you put that in the CRM?”
Flyntlok is trying to eliminate that gap between doing the work and documenting the work.
During Ula’s demo, she shows how an employee can use Click-to-Call directly from the contact attached to a task.
Once the call starts, Flyntlok automatically opens the activity modal with information already populated—including who was called, the phone number, and associations with the related customer and task.
The employee can quickly add any additional notes and save the activity.
Instead of making the call and then relying on the salesperson to remember to document it later, the workflow naturally captures the activity while it’s happening.
The same philosophy applies to SMS.
From the Conversations tab, employees can see their text interactions with the customer and respond without leaving the task. Quick responses can also make common replies easier to send.
The result is less jumping between tabs, less duplicated data entry, and less “CRM homework” at the end of the day.
The CRM becomes part of having the customer conversation.
The Task Details page also creates a running history of what has happened.
Employees can see updates, activities, conversations, and changes associated with the task.
That creates continuity.
If an employee spoke with a customer at the beginning of the year and the conversation becomes relevant again months later, the dealership can return to that relationship with more of the history intact.
That history matters for managers, too.
Instead of trying to piece together what happened by asking multiple employees or searching through separate tools, managers can gain more visibility into whether calls are being made, customers are being followed up with, quotes are progressing, and opportunities are moving through the pipeline.
The goal is not simply to collect more CRM data.
It’s to make the right information visible to the people who need it—and capture as much of it as possible automatically.
Not every customer conversation starts as a sales opportunity.
Sometimes the right CRM action really is just:
Call John about his mower.
But relationships evolve.
During that conversation, John might suddenly say he’s ready to start looking at a replacement machine.
Now the follow-up has become something more.
Flyntlok lets employees promote a task directly into a lead.
Instead of leaving the task, creating a brand-new sales opportunity, and reentering all of the information that was already captured, the employee can move naturally into the sales pipeline with information prefilled.
They can archive the original task if the follow-up is complete or continue using it if additional actions are still needed.
It creates a much more natural progression:
Conversation → Follow-Up → Opportunity → Sale
The employee doesn’t have to decide that every customer interaction is a formal sales opportunity before the relationship has reached that point.
They can begin with the relationship, capture the promise, follow through, and promote it into the pipeline when genuine buying interest emerges.
For MA, the ultimate payoff comes back to a few fundamental dealership outcomes.
First, there’s revenue protection.
When follow-ups are captured and worked consistently, fewer opportunities are allowed to quietly go cold.
Second, there’s less time spent searching for information.
Employees shouldn’t need to find an old sticky note, search through multiple systems, or locate the one coworker who happens to remember what happened with a particular customer.
The information should be available to the broader team.
Third, managers get better visibility into customer activity and the pipeline.
And finally, there’s consistency in the customer experience.
A dealership can preserve conversation history and relationship context over time, making it easier to provide proactive, informed service whenever that customer comes back.
That consistency helps build the kind of customer relationships equipment dealerships depend on.
As MA points out, happy customers who know a dealership is proactive and reliable are more likely to come back and continue doing business.
The technology may begin with a task.
But the business result is the relationship created by consistently following through.
Asked what she hopes salespeople can stop doing once they begin using the revamped CRM experience, Ula points to the little administrative tasks that add up throughout the day.
Logging the call after the call.
Jumping between tabs to find information.
Reentering details the system already knows.
Searching for customer history.
None of those individual actions necessarily consumes a large amount of time.
But saving a minute here and several seconds there across every customer interaction gives employees something much more valuable back:
more time to actually work with customers.
That’s especially important in an industry where relationships remain such a fundamental part of how dealerships grow.
Technology should make maintaining those relationships easier—not create another layer of administrative work around them.
For MA, one of the most exciting parts of the new direction is SMS.
Text conversations existed within different areas of Flyntlok previously, but the new CRM philosophy is bringing those conversations much more prominently into the customer relationship workflow.
The goal is to make communication easier to find, easier to continue, and more naturally connected to the activity the employee is already performing.
That same philosophy runs throughout the entire CRM Command Center:
Make the next step obvious.
Make the context easy to find.
Capture activity automatically wherever possible.
And keep the employee close to the customer rather than buried in administrative work.
The CRM Command Center ultimately gets at something fundamental about equipment dealerships:
Relationships drive this industry.
And those relationships are built through hundreds of seemingly small actions.
Flyntlok’s revamped CRM Tasks bring those customer promises into one central place, connect them to the customer and equipment context already inside the DMS, preserve calls and conversations, make the next step visible, and create a direct path from a simple follow-up to a real sales opportunity.
Because as Jenny summarizes at the end of the episode:
The value isn’t the task. The value is what happens because somebody followed through on that task.
That might mean a better customer experience.
It might mean an opportunity that doesn’t go cold.
It might mean another machine sold.
And over time, it can mean stronger relationships and more revenue for the dealership.
That’s the real promise behind Flyntlok’s Customer Relationship Command Center.
.png)
