What the desk already includes.
Built-in helpdesk AI is the assistant, bot, or agent the platform vendor sells on top of the desk you run. It is licensed with that product, configured in that admin, and it answers inside that product's own model of a ticket.
That is the right place to start when the work never leaves the desk: suggest a reply, deflect a known question, route a ticket to a group the desk already knows. You are not buying a second system of record.
What an external layer adds.
An external layer is a separate product that logs into the instance you already run. It reads the ticket there, and it can write back there. The difference is reach: the work often continues in an ERP, a CRM, or another desk the helpdesk does not own.
Adding a layer is not a plan to turn the helpdesk off. The desk remains the queue your team opens. The layer is how work that starts in that queue finishes in the systems around it.
Stay, switch, or add.
Teams searching for an alternative usually mean one of three paths. Use the AI that shipped with the desk. Switch helpdesks, which is a migration. Or keep the desk and add a layer that works inside it.
Those paths are not interchangeable. A migration replaces the queue, the history, and the integrations. A layer leaves them. Built-in AI improves the desk you have, inside the limits of what that desk can see.
Questions that pick the path.
Ask where a finished ticket has to land. If the answer is only inside the helpdesk, built-in AI may be enough. If the answer includes a system the helpdesk does not write to, you are describing a layer, whether or not you have named one.
Ask who owns the failure. Built-in AI fails inside one vendor's admin. A layer fails across a boundary, and someone has to be able to see both sides. Neither path is free of review, and neither should be sold as a switch you throw on day one.