Working example, built for Boat World MN

Five brands, a parts counter and a body shop, and one phone number to reach all of it

Boat World MN's own site lists Tahoe, Bentley, Princecraft, Avalon and MirroCraft (plus Montego Bay pontoons) under one roof at the East Bethel lot, along with a marine parts department and boat storage. There is no online scheduling, order-status page or live chat anywhere on the site: sales and service both route through one phone number and Sales@boatworldmarine.com. That matches a specific, unresolved BBB complaint on file: a customer who paid for a boat and then made "multiple phone calls with questions about protocol and boat information with no return calls."

What's real: Boat World MN's About Us page (fetched directly) lists Tahoe, Bentley, Princecraft, Avalon, MirroCraft and Montego Bay pontoons, a marine engine repair/parts department, boat storage, and a body shop run through a named partner, George's Repair, not an in-house department. Its BBB profile lists Randy Crumpler as owner, 13 years in business, an A rating (not accredited), and one unresolved complaint describing exactly the post-purchase communication gap this page is scoped around. The site itself has no order-status page, booking widget or live chat; contact is one phone number, (763) 434-9655, and Sales@boatworldmarine.com.

What's illustrative: the sample tickets below are fictional, not real customers or boats. Because the body shop is run by an outside partner (George's Repair) rather than in-house, this prototype tags every ticket by department so a body-shop job is visibly distinct from a parts order or a sales delivery, instead of guessing at an internal process Boat World MN hasn't published anywhere.

Log a new ticket

Open queue, longest stuck first

One shared view across sales delivery, the parts counter and the George's Repair body shop, instead of each area only knowing its own jobs.

Check the status of an order

Try BWMN-1001, BWMN-1002, BWMN-1003 or BWMN-1004 from the office view's sample queue.

What I'd flag before this goes further

Only the four sample reference codes above return anything. This isn't connected to a real sale or work order, so it can't look up an actual customer's boat. A real build would read from whatever Boat World MN already tracks orders and repairs in, likely a simple shared spreadsheet or Airtable base the sales floor, parts counter and George's Repair can all update.
Automatic SMS/email pings are simulated as an internal log entry here, not actually sent. A real build wires each stage change to an SMS or email provider so the customer update goes out the moment staff mark the change, instead of relying on someone remembering to call back.
Two different flows are scoped here on purpose: a delivery checklist for a boat that's been sold (rigging, registration, walkthrough, handoff) and a parts/repair tracker for service and body-shop jobs. Both are the proposed structure, not a copy of an internal process Boat World MN already runs, since no such system is visible on the public site.
The body shop is a named outside partner, George's Repair, per Boat World MN's own About Us page, not an in-house team. Any real build would need to confirm how status updates actually flow back from that partner before promising real-time accuracy on body-shop jobs specifically.