A step the desk no longer waits on.
Helpdesk automation is any repeatable step on a ticket that runs without a person starting it: a classification, a route, a drafted reply, a field written back. The desk stays the system of record.
The word covers a wide range. A rule that sets a priority is automation. So is a model that drafts the resolution. Buyers who treat those as the same product end up comparing a macro to an agent.
A new inbox is a different project.
Replacing the helpdesk moves queues, history, SLAs, and the integrations hung off them. That is a platform migration. Automation assumes the desk stays and does the step inside the instance you already license.
A chat window in front of the queue can deflect a contact. Deflection is not the same claim as a ticket whose record changed. Ask which of those you are being shown.
Ask where the step ends.
Ask whether the automation only suggests, or whether it can write the field, the reply, and the status the rest of the company already trusts. A suggestion a person still has to paste has not finished the job.
Ask what happens on the cases it should not touch. A useful automation has a handoff, not only a success path. The agent-assist guide is the version of that question about who still sends the work.
Some queues should stay manual.
Leave a step manual when the cost of a wrong write is higher than the cost of the wait: a regulated change, a refund above a line you set, a customer you have promised a person. Automation that cannot name that line is not ready.
If the desk itself is ending, automate the next system, not this one. An automation project will not rescue a platform you have decided to exit.