Support tickets are the foundation of customer support, nothing works without it. The idea of tickets is simple - a customer has a concern about your product or service, they raise that concern in the form of a ticket which gets assigned to a customer support agent. The agent then needs to address that concern and resolve it as quickly, politely, and with as little back-and-forth as possible such as to ensure that the customer doesn’t go through a bad experience.
Sounds simple, but the challengers only uncover themselves when things scale. More customers mean more tickets and more tickets mean more workload on each agent to resolve those queries. But that’s not the kicker - if you receive two tickets at once, or, if you have a backlog of tickets, how do you decide which one to solve first? Sure, you can continue resolving them one after another without paying much attention to order or priority, but your customers are waiting. A lot hangs in the balance when your customer service becomes questionable; you face the risk of churn and loss of business. What’s more, some concerns are a lot more severe than others. In critical cases, your customer’s entire functioning depends on you resolving their issue, so, how can you not prioritize that over other issues?
The idea of faster resolutions has more to do with structure than mostly anything else. You can use tools and tech stacks that aid in resolving tickets faster but that is but a catalyst, not the foundation.