Meet Marcus

Kanupi's service advisor, and your shop's co-pilot

Marcus is the layer that runs underneath every Kanupi product, carrying your standards onto every surface. He talks to your customers, helps your service advisors, listens to your techs at the bay, watches your schedule, and keeps every ticket tuned to your preferences, so each one goes out the way you would write it, at the margins you set. Same Marcus, same memory, every surface.

You'll also meet Mia. Same advisor, same memory, and you can choose who you talk with in the chat.

Marcus across Kanupi

Marcus isn't a chat widget bolted onto the side of your software. He's woven into every service Kanupi offers, which means the context he picks up on one surface follows the customer (and the work order) everywhere else.

Parts & Labor: Marcus checks fitment from the VIN, ranks every connected supplier's results by your brands and margins, attaches the labor at your shop rate, and fills the cart, so the quote is right before anyone sorts through a wall of SKUs.

Bays: Marcus watches part ETAs, tech skill sets, bay availability, and customer approvals against your live schedule. When something slips, a back-ordered part, a no-show, a comeback, he rebalances the floor before it becomes a fire.

Smart Inspections: Techs talk into their phone at the lift; Marcus turns it into a structured inspection report, an itemized quote the customer can approve from their phone, and a rebalanced schedule, without anyone walking back to the service desk.

Marcus Live (the customer-facing voice): Phone, web widget, SMS, email, and the Reserve Garage all run on the same Marcus with the same memory. Your customer never has to repeat herself, whether she booked an appointment three months ago on the website or just texted you a photo of her dashboard.

Reserve: Marcus knows which members are in which tier, what perks they're owed, when their next service is due, and when the work they deferred comes back around. Loyalty stops being a punch card and starts driving repeat revenue.

You build the playbook. Marcus runs it.

The thing that makes Kanupi different: you don't adapt to the software, it adapts to you. Every preference, threshold, and rule is yours to set, and you can tune the whole Owner Playbook just by talking to Marcus. He'll flag adjustments based on what he's seeing in your shop's actual data, then ask, he never changes your standards on his own.

Parts preferences: "Marcus, prefer my first-call supplier over the cheapest option whenever the margin difference is under 8%." Done. He'll also surface when a preference is costing you money and ask if you want to revisit it.

Schedule rules: Tell Marcus how you want bays prioritized, waiters before drop-offs, oil changes only before 11am, no diag work on Fridays, and he'll enforce it. When the rules cost you a booking, he tells you exactly which one and why.

Inspection thresholds: Decide what gets flagged as "recommend now" vs. "watch next visit." Marcus learns from your approvals and pushback and refines the defaults the more your team uses it.

Customer tone & cadence: Set how Marcus talks to your customers, formal, casual, or somewhere in between, and how often he follows up after a quote, a no-show, or a completed job. He'll show you the open and approval rates so you can dial it in.

Reserve tier design: Marcus helps you size membership tiers, price perks, and forecast lifetime value before you commit. Once live, he flags which perks are getting used and which are dead weight on your margin.

Profitability nudges: Marcus watches the numbers the same way your accountant would, labor margin by job type, parts margin by supplier, tech utilization, conversion on inspection upsells, and surfaces the one or two things that, if tuned, would move the needle most. Then he asks if you want him to make the change.

How Marcus works under the hood

Marcus is grounded in automotive service data, repair patterns, failure modes, manufacturer specs, and the industry-standard ACES (Aftermarket Catalog Exchange Standard) fitment catalog, and in your shop's own standards and historical data once you're connected. Every recommendation is traceable: you can ask him why he ranked a part first, why he rebalanced a bay, or why he flagged a customer for a follow-up, and he'll show his work, back to the rule in your playbook that drove it.

Marcus's memory is per-shop and per-customer. Your data trains your Marcus, not the model itself or any other shop's instance.

What Marcus is, and isn't

Marcus is an assistant, not a replacement for your service advisors, techs, or owner-operator instincts. Marcus makes the obvious decisions automatic, surfaces the non-obvious ones for a human to make, and always says when confidence is low. The owner's preferences are the final word: Marcus enforces them and never overrides them.

Want to see Marcus in your shop? shops@kanupi.com, or book a demo from the For Shops page.