In this SuiteDash 101, I’m debunking the real differences between Support Tickets and Work Requests—because I keep seeing people use tickets for client tasks and then wonder why it feels clunky. I walk you through both modules inside SuiteDash, what the client sees, and what actually happens after something is submitted. Support Tickets are a standalone module: you can set inboxes, priorities, statuses, tags, permissions, and saved replies, and you can even build custom ticket forms. But the big thing to understand is that tickets don’t automatically connect to your other modules—so you’re basically managing a conversation and then manually turning it into a “tracking process.” Work Requests, on the other hand, are built for “request of work” and they connect internally to Projects, Estimates, and Invoices. I show you how Work Request settings work (free form vs itemized, attachments required or not, notifications, and what happens when you convert). The magic is the conversion: I can turn a request into a project/task flow, or into an estimate/invoice, which is way more task-driven and ops-friendly. I also share the caveats—like attachments landing in project files/public files instead of directly on the task—and my best-practice recommendation: if you’re task-driven, use Work Requests; if you want a simple ticketing space, Support Tickets still works.