I added a support desk to LaraFoundry this week. The first commit in the slice removed a package instead of adding one.
LaraFoundry is a reusable SaaS core for Laravel that I'm extracting in public from an older app of mine. Auth, multi-tenancy, roles, activity log, notifications, billing seam, and now support tickets. The rule for every module is the same: lift the proven idea out of the old code, modernise it, harden it, and make it something you can composer require into a fresh Laravel app without inheriting a pile of assumptions.
Tickets is where that rule got interesting, because the old code didn't own its ticket model. It leaned on a third-party ticket library.
Why a ticket package is wrong for a reusable core
A third-party ticket package is a perfectly reasonable choice when you're building one app. You get tables, a model, a status enum and a UI scaffold for free.
