API / Integration
A documented interface, and the live connections built on it, that let a help desk exchange data and trigger actions across the rest of your software stack.
An API (application programming interface) is a documented contract for how two systems talk: one program requests data or an action in a fixed format, and the other answers the same way. An integration is what you build on that contract — the connection between your help desk and the CRM, billing system, order database, or identity provider. Most run over REST calls the help desk makes to pull context in, plus webhooks that fire the other way to push events out the moment they happen.
The point in support is to kill the swivel chair. When the ticket already shows the customer's plan, last order, and open bugs, the agent answers instead of hunting across tabs — and that hunting is expensive. A Harvard Business Review study of Fortune 500 employees found people toggled between applications roughly 1,200 times a day, spending nearly four hours each week just reorienting after the switches. Integrations also automate the plumbing — opening tickets from other systems, syncing status, triggering follow-ups — so work moves without someone copy-pasting it.
What it hides: an integration is a dependency you don't own. APIs get rate-limited, versioned, deprecated, and quietly changed, and every break lands on your queue. "Prebuilt" marketplace connectors are often shallow — a one-way field sync, not the two-way workflow you assumed — so the real depth only surfaces once you're live. And each connection widens both the attack surface and the total cost of the stack: someone has to maintain the auth, watch the logs, and re-certify it at renewal. Count integrations as systems you run, not features you bought.