One incident, a dozen tickets. See how they connect.

When something breaks, the tickets pile up: the customer complaints, the duplicates, the task that's blocked, the change that caused it all. Nobody sees the whole chain, so the same problem gets solved twice and the missed SLA three tickets away goes unnoticed. Ticket Linking lets agents link tickets and say how they relate, shows every link in the sidebar, and draws the whole chain in one map.

A Freshservice incident, Card payments failing at checkout, with the Ticket Linking panel in the sidebar: four linked tickets grouped as Related to, Blocks, Is duplicated by and Is caused by, each with its status and priority, and a Link a ticket box below.
Every linked ticket, grouped. Each link shows how the tickets relate, with the other ticket's status and priority. Closed tickets are struck through.

Link it once. Both tickets know.

The app sits in the ticket sidebar. A link is saved on both tickets at once, each with the label for its own side, so the other agent sees it too.

Seven link types

Related to, Blocks, Is blocked by, Duplicates, Is duplicated by, Causes and Is caused by. Pick one side and the other ticket gets its opposite. Find a ticket by its number or by words from its subject.

Both sides in sync

Linking updates both tickets, and removing a link from either one removes it from both. An optional private note on each ticket keeps the change in its activity.

The whole chain

A map of the ticket's links and their links, three levels deep, with missed SLAs in red. Click a ticket to see how it connects. Export it as PDF, PNG or CSV for reviews and audit files.

What the agent sees in the ticket.

Watch it working. Linking tickets, both sides in sync, the map of the whole chain and the exports, in two minutes. There's also a one-minute version.

Screenshots taken in a real Freshservice, on test tickets.

The Link a ticket box in the sidebar with the link type list open: Related to, Blocks, Is blocked by, Duplicates, Is duplicated by, Is caused by and Causes, and a found ticket, INC-80, ready to link.
Say how they relate. Pick the link type from this ticket's side. The other ticket gets the opposite label.
A confirmation that INC-80 was linked, and the ticket's Ticket links field showing rel:71 blocks:72 dup-by:70 caused-by:69, above the updated list of linked tickets.
Saved on the tickets. Links live in a Ticket links field on each ticket, so there's no extra database, and they stay when the app is uninstalled.
The All tickets linked to #68 window: a map of 12 linked tickets from left to right, with INC-69, Payment gateway TLS certificate expired, outlined in red as resolution overdue by 12h 2m, and Copy as CSV, Export CSV, Export PNG and Export PDF buttons.
The whole chain in one map. Up to three levels and 50 tickets, left to right or top to bottom, with closed tickets hidden or shown and missed SLAs marked.
The map from top to bottom with a path highlighted and the line: INC-68 is caused by INC-69, INC-69 is blocked by INC-74, INC-74 is blocked by INC-77, resolution overdue by 12h 2m.
How is this one connected? Click any ticket and the map spells out the path back to the one you're on.

Setup: about five minutes.

Copy an API key

From an agent who can view and update every ticket agents may link. On Freshdesk, an admin's key also lets the app create its Ticket links field by itself. On Freshservice, API keys are off by default: turn it on for that agent under Admin → Agents.

On Freshservice, add the field

Freshservice has no API to create ticket fields, so add a single-line text field named Ticket links under Admin → Field Manager → Ticket Fields, in each workspace that will use links.

Install and open a ticket

In Admin → Apps, search for Ticket Linking, and fill in your helpdesk domain (such as acme.freshservice.com), the API key, and whether links should be logged as private notes. The app is coming to the Freshworks Marketplace soon.

Links stay on your tickets.

Each link is saved in the Ticket links field of the two tickets, as ticket numbers and a link type. The app has no database and no servers of its own, and sends nothing to Red Lotus or anyone else. The exports are made in the agent's browser.

The API key is kept as a secure installation parameter and only used on Freshworks' servers, so it never reaches agents' browsers and we never see it. Agents only see the details of tickets their role lets them open; the others show as locked. The app sets no cookies and uses no analytics.

$0.50 per agent per month.

$0.50 per agent per month
7 link types, each with its opposite
0 servers or databases of our own

Ticket Linking is sold through the Freshworks Marketplace, and Freshworks handles billing, renewals, cancellations and refunds. You can cancel by uninstalling the app.

Common questions.

Does it work on Freshdesk and Freshservice?

Yes, on both, in the ticket sidebar, and on Freshdesk Omni. On Freshservice, tickets can be linked across workspaces.

Where are the links stored?

In a single-line text field called Ticket links on each ticket. There is no app database, and uninstalling the app keeps every link. Agents can read the field, and even fix a link by hand.

Does it change my tickets?

Only the Ticket links field, and, if you leave the option on, a private note on each ticket when a link is added or removed. Each link is a ticket update, so it changes the ticket's updated time and can trigger automations that run on updates.

Can agents see tickets they aren't allowed to open?

No. The app applies each agent's ticket access: a linked ticket they can't open shows only its number, and search leaves it out.

How many links can a ticket have?

About 60 with three-digit ticket numbers and about 36 with six-digit ones. The map shows up to three levels and 50 tickets, and says how many it left out.

How do I get support?

Email info@redlotus.com.br. We aim to reply within 3 business days, or 5 for critical issues.

Stop solving the same problem twice.

Questions about Ticket Linking, or a link type you'd like it to have? Write to us.

Back to all solutions