Help desk links an agent can find in the middle of a ticket

The answer exists. Finding it during the ticket is the job

A customer is on the line asking why their invoice shows a charge from a plan they cancelled. You know there is a doc about proration. You know it's in Notion, or maybe Confluence, and there's also a newer version somebody made because the old one was wrong. Meanwhile you need the internal admin panel to look at the account, the billing provider's dashboard, the status page in case this is the incident from Tuesday, and the escalation sheet if it turns out to be a bug.

That is four surfaces, and you're alt-tabbing across them with someone waiting. Handle time isn't going up because agents are slow — it's going up because the retrieval step has no fixed address.

For new agents it's worse. Ramp is mostly learning where things are, and the standard tools for teaching that — a shared doc of links, a pinned message in the team channel — decay quietly. The pinned message is two years old and three of its links 404.

Required boards so every agent has the same set

Build the support board once: Admin & internal tools, Knowledge base & macros, Escalation, Status & incident, Billing, Policy. Then mark it required. It appears on every agent's account automatically and members can't remove it, which means the answer to "where's the escalation matrix" is the same for everyone, permanently.

Ramp time in support is mostly retrieval time — fix where the links live and a new agent is useful in days instead of weeks.

Keep it view-only for agents. The master list is edited by the support lead and read by everyone else, and the cap is enforced in both the web app and the extension. Nobody accidentally renames the escalation link or deletes the old billing panel that team two still uses. Give the leads "Can share" so they can add a new hire to the right boards without an admin round trip.

• One required board every agent gets on their first login
• View-only for agents; edit rights for the support lead who owns the list
• Separate boards per queue or product line, shared only with the team that works it
• Text blocks for the things that aren't links: escalation thresholds, the on-call rotation rule, refund limits by tier

The tools are already open, because they're the new tab

The new tab is the most-visited page of a workday, and in support that's a lot of new tabs. Through the extension, your boards become that page: it renders instantly from a local cache and is searchable, so mid-ticket you press the new-tab shortcut, type "proration", and land on the right doc without a detour through a wiki homepage and its search box.

Search from the extension popup does the same thing without leaving the ticket view. Saving is a keyboard shortcut, a right-click, or the popup — so when an agent finds the good version of a doc at 3pm, it goes on the board in two seconds and the next agent doesn't repeat the search.

Onboarding, offboarding, and the churn support teams actually have

Support teams turn over. A new agent's setup should be one action: add them, and the required boards are already there — no onboarding doc with forty links, six of which are dead. When someone leaves, revoke access in one action and every link stays with the team. If they owned a board, reassign it to their successor.

The honest limit: Linksley is not a knowledge base and not a help desk. It does not store articles, hold macros, route tickets or report on anything — there are no analytics dashboards and no integrations with Zendesk, Intercom or Slack. It points at your existing tools, fast, from a place agents already look. If your problem is that the content itself is bad, a link organizer won't fix that. Also worth knowing: extensions cover Chrome, Edge, Firefox and Opera, and there is no Safari extension or mobile app.