We sat down with Garrett Jobgen, General Manager of J4 Commercial Services, for a Fireside Chat during a Service Pro AI webinar. J4 is an air compressor supplier headquartered in Texas, and today runs reactive and preventative maintenance contracts across 14 states, traveling nationwide for installs. As one of the first to get his hands on the new AI Connector for Service Pro (MCP), he’s wired it into Claude, alongside NetSuite, Slack, and Microsoft 365, giving him one place to see across his entire tech stack.
Watch the full conversation below.
From Generic AI to Grounded AI
“…If you connect it [AI] to real data, real context, that’s when you start getting real value out of it.
—Garrett Jobgen, J4 Commercial Services
Garrett’s AI journey started the way a lot of people’s do. He picked up ChatGPT first, using it for email drafts and light research, then moved into troubleshooting and researching state compliance codes. From there, he discovered Claude and its growing library of connectors, including ones for NetSuite and Slack.
Early on, he ran into a familiar problem. “Sometimes it would make stuff up or hallucinate,” Garrett said. “But if you connect it [AI] to real data, real context, that’s when you start getting real value out of it.”
Garrett isn’t the only service leader noticing how generic aI falls short; see the differences between Service Pro AI and Generic AI here.
That distinction changed how he used AI from that point forward. Instead of treating it as a standalone tool, he started connecting it directly into his actual tech stack.
The Service Pro AI Connector closes that gap, bringing his Service Pro data directly into the AI tools he already uses.
What Garrett Is Actually Using the AI Connector For
Today, Garrett has the AI Connector wired into pretty much everything: NetSuite, Slack, and Microsoft 365, including SharePoint, document libraries, and customer email correspondence. “It gives a lot of good context for whatever agent you’re using or whatever platform you’re using,” he said. Since MCP is an open standard, he added, “whatever tool you use… it’s able to meet you there.”
That connected view lets him track metrics that used to require pulling data from multiple places by hand: response time, true completion time, time to estimate, and time to invoice. He can also look at customer history over time, whether the same issue keeps coming up or something new each visit, all surfaced automatically instead of requiring a manual pull.
Building and Sharing AI Skills Across a Team
Garrett didn’t roll AI out to his whole team on day one. He tested it himself first, then bought a Claude team plan and handed out seats to upper management and admins, letting each department try building something useful for their own work.
The results made the case on their own. “It was just a no brainer how much time it was saving,” Garrett said. “It kind of paid for itself.” Adoption spread from there. “Now everybody in my office, pretty much down to the coordinator level and parts ordering level, has a seat, and they’re using it,” he said. “They’re building skills. We’re sharing skills with each other.”
That same instinct, testing something himself before expanding access, carried over to the AI Connector. He’s already using it personally and, in his words, “slowly testing and rolling it out internally” for the rest of his team.
His Advice for Getting Started
Garrett’s own rollout mirrors what MSI Data recommends to anyone turning on the AI Connector for the first time: start read-only, get comfortable, and expand access from there. He tested it personally before handing it to his team, and he’s still finding new use cases. One he’s building right now is a skill that automatically flags stagnant orders so nothing sits without anyone noticing.
He’s also watching closely as new product features come out of Service Pro AI. When we asked him about our new features, Invoice Ready Notes, which helps turn technician notes into clean, invoice-ready summaries, Garrett’s reaction was immediate. “It gives you a good kind of situational awareness of the notes, rather than having to read the whole notes of all the technicians,” he said. “You can just read a paragraph, or a couple sentences, and get a bird’s eye view of exactly where we stand on that order.”
Want the abbreviated version? Watch the Fireside Chat here.
Want to hear Garrett answer live questions during the Q&A? Get the full webinar recap here.
Start Your Free Trial of Service Pro AI
Garrett’s story is a real-world example of how great AI can be when it’s made for the service industry, connected and grounded in your data, and shared with a curious and integrated team.
Either way, the trial is the place to start. You’ll get a dedicated Forward Deployed Engineer working alongside your team from day one, and features like the AI Connector are ready to turn on as soon as you’re set up.
Start Your Free Trial of Service Pro AI
Frequently Asked Questions
What is the AI Connector (MCP)?
A feature in Service Pro AI built on the Model Context Protocol, an open standard that lets AI assistants like Claude, ChatGPT, or Copilot connect directly to your Service Pro data. It’s included in your existing Service Pro AI license.
How did Garrett start using AI at J4?
He started with ChatGPT for general tasks like email drafts and research, then moved to Claude once he discovered its library of connectors, including ones for NetSuite and Slack.
How is J4 using the AI Connector today?
Garrett has it connected across NetSuite, Slack, and Microsoft 365, giving his team visibility into service data, customer email history, and document libraries in one place. He uses it to track metrics like response time, time to estimate, and time to invoice.
What’s Garrett’s advice for getting started?
Start read-only, get comfortable with it, and expand access as your team gets more familiar. That’s the same approach Garrett took at J4, testing it himself before rolling it out to the rest of his team.