CRM Command Center
Give every customer promise an owner and a next step
Jenny Moebius sits down with Flyntlok engineers Michael Sharp and Ula Lapkus to walk through the revamped CRM Tasks: a task list built around each salesperson, a task page with the full customer story, click-to-call, texting and a quick path from follow-up to lead.
Hosted by Jenny Moebius
.webp)
Plays right here. Free, with no form to fill out.
About this episode
Every dealership makes promises all day: I’ll call you back, I’ll send you a quote, let me check on that machine. Multiply them across every salesperson, department and location, and hundreds of follow-ups compete for attention.
Ula Lapkus demos the revamped CRM Tasks, and Michael Sharp explains why the team calls it the Customer Relationship Command Center. Because it’s built into the DMS, every follow-up sits next to the machines, orders and history your team already works from.
What you’ll hear
- Follow-up is a revenue problem. A callback can become a sale and a quote can become an order. When follow-ups live on sticky notes and in someone’s head, opportunities go cold.
- Start small, then add context. A task can be as simple as Call Jane back. Link the customer, contact, machine or lead when it helps. Once it has a due date, the follow-up chases the salesperson.
- Context before the call. The Task Details page puts the customer’s machines, sales orders, work orders, leads, conversations and history in one place.
- Less CRM homework. Click-to-Call opens the activity with the details filled in, and texts sit right in the task.
- From follow-up to opportunity. Promote a task into a lead with its details already filled in, then archive the task or keep working it.
Who’s on this episode
Jenny Moebius hosts every episode of Flyntlok Unlocked.

.png)

The conversation, section by section
The value isn’t the task. The value is what happens because somebody followed through on that task.
Jenny Moebius, host of Flyntlok Unlocked
Every equipment dealership makes promises all day long. On their own, none of them sounds complicated. Multiplied across every salesperson, department, location and customer, they become hundreds of follow-ups competing for attention, scattered across sticky notes, notebooks, phones and inboxes.
The problem: follow-up gets harder as a dealership grows
Ula hears it from dealers all the time: follow-ups on paper, on phones, in notebooks or in someone’s head, and one office covered in sticky notes. That works when a dealership is small. Add people and locations, and quotes go unanswered and opportunities go cold. Michael puts the cost plainly: lost revenue and a worse customer experience.
From a task list to a customer relationship command center
The new experience starts with two areas: a Task List that shows everything needing attention, and a redesigned Task Details page that brings the context and actions for each follow-up into one workspace. The list tells you what needs attention. The details page tells you why, and gives you the tools to act.
A CRM view that works the way each employee works
The Task List shows each task’s name, description, due date, status, priority and primary contact. Sort, filter, add or remove columns and save the layout that fits you. A salesperson asks what to do today. A manager asks which tasks across the team are overdue.
Capturing a follow-up without creating more work
A task can start as simple as Call Jane back. Add a description, due date, priority, assignee, customer, contact, machine, make and model or related lead when it helps. Pick the customer and Flyntlok pulls up their contacts. Once the task has a due date, the follow-up chases the salesperson instead of the other way around.
Giving employees the context to have the conversation
The Task Details page shows the due date, status, priority, primary and secondary assignees, customers and contacts, machines, sales orders, work orders, leads, activity history, conversations and files. A secondary assignee stays in the loop if the salesperson is out, so the story doesn’t leave with one employee.
Why a CRM built into the DMS matters
At an equipment dealership the equipment is part of the relationship. Because CRM Tasks live inside Flyntlok, a follow-up connects to the machine a customer owns, the quote they received and the work done on their equipment. A separate tool only knows a name and a list of activities.
Making the CRM part of the work, not homework after it
Click-to-Call from the contact on a task opens the activity with the details already filled in. Texts sit in the task’s Conversations tab, with quick responses for common replies. Less jumping between tabs, less retyping and fewer did-you-put-that-in-the-CRM moments.
Preserving the history of the relationship
Every update, activity and conversation stays with the task. When a conversation from the start of the year matters again months later, the history is there, and managers can see whether calls are being made and quotes are moving.
When a follow-up becomes a real sales opportunity
Sometimes the task really is just Call John about his mower. If John says he’s ready to look at a replacement, promote the task into a lead with the details already filled in, then archive the task or keep working it. Conversation, follow-up, opportunity, sale.
The payoff: consistency, better experiences, more revenue
Fewer opportunities go cold, less time goes to hunting for information, managers see the pipeline, and customers get a consistent experience. As Michael points out, customers who know a dealership is proactive and reliable are more likely to come back.
Saving seconds for more time with customers
Ula’s hope: no more logging the call after the call, jumping between tabs, retyping what the system already knows or digging for customer history. A minute here and a few seconds there add up to more time with customers.
Bringing customer conversations to the forefront
Michael is most excited about texting. Conversations that used to live in different parts of Flyntlok now sit right inside the customer workflow, easier to find and easier to keep going.
The takeaway: the value isn’t the task
Relationships drive this industry, and they’re built on small things: remembering the callback, following up on the quote, knowing which machine the customer asked about. CRM Tasks put those promises in one place, connected to the customer and equipment already in the DMS.
What has shipped since this episode
Every change below comes from the Flyntlok release notes, which come out about every two weeks.
Oct 1, 2026 · Sales & CRM
Bulk Edit for Tasks and Leads
Update up to 20 Tasks or Leads at once instead of opening them one by one.
Oct 29, 2026 · Sales & CRM
Assign Inbox conversations
Hand a customer conversation to a salesperson, who gets a notification when the customer replies.
Oct 29, 2026 · Mobile
Flyntlok Mobile beta, starting with Sales and CRM
A closed beta of the new Flyntlok Mobile app for five users, with Sales and CRM first.
Want every change? See all release notes
Every follow-up in one list, tied to the customer.
CRM Tasks are built into Flyntlok, so every follow-up sits next to the machines, orders and service history your team already works from.
- Leads, quotes and follow-ups on one customer record
- Campaign lists built from machines owned and service history
- Two-way texting, with each reply routed to the customer’s salesperson

What dealers ask
Got a topic for the show?
Suggest a topicWhat is the CRM Command Center?
It’s what the Flyntlok team calls the revamped CRM Tasks: a Task List you can sort, filter and save your own way, and a Task Details page that puts the customer, contacts, machines, orders, conversations and history behind each follow-up in one place.
Is Flyntlok’s CRM a separate system?
No. It’s built into Flyntlok, so tasks link to the machines, sales orders, work orders and leads already in your DMS.
Can a follow-up turn into a sales opportunity?
Yes. Promote a task into a lead with its details filled in, then archive the task or keep working it.
More episodes
Previous and next episodes
Sales & CRM
All episodes (the page script picks previous, next and related episodes from this list)


.webp)
.webp)
%2520(2).webp)
.webp)

.webp)
%2520(1).webp)
%2520(2).webp)
%2520(1).webp)