FreshDesk: Your Single Source of Truth

Created by Amy Sara Price, Modified on Tue, 19 May at 12:42 PM by Amy Sara Price

Trade Shield  |  Knowledge Centre FRESHDESK GUIDE

FreshDesk: Your Single Source of Truth

How to use FreshDesk to raise, track, and resolve every request — for every team at Trade Shield.

? 10 min read    8 sections    All Trade Shield team members

?

✨ Did You Know?

Without tickets, we cannot show you stats like these.

73%

of tickets resolved within SLA targets

4.2h

avg first response time this month

18%

upload errors up — product fix triggered

These numbers only exist because teams log tickets. If it is not in FreshDesk — for us, it did not happen.

1

Why FreshDesk is our single source of truth

Right now, requests come in from everywhere. A Teams message here. An email there. Someone stops you in the corridor. A sticky note on the monitor. Each of these feels harmless on its own — but together, they create a problem: we cannot measure what we cannot see.

When everything flows through a FreshDesk ticket, we can measure it, report on it, improve it — and show the whole business what each team actually does.

This applies to customer requests AND internal team requests. Sales needing something from Customer Delivery. L&D requesting a fix from Dev. Account Management chasing a data file. All of it — one ticket.

ⓘ Tip: FreshDesk is not just for the Support Team. Every person at Trade Shield may need to raise, view, or contribute to a ticket at some point.

2

What is a ticket?

A ticket represents a single issue or request. One problem, one ticket. Think of it as the customer file for that issue — everything you need lives in one place.

Ticket Field What it tells you Example
Requester Who raised it jane@clientcompany.com
Status Where it sits in the process New / Open / Pending / Resolved
Priority How urgent it is Low / Medium / High / Urgent
Owner Who is responsible for resolving it Roxanne / JP / Amy
Full History Every reply, note, and update ever made Full audit trail from day 1

⚠ Golden Rule: Every ticket must have an owner. No orphan tickets. If it does not have an owner, it is at risk.

3

When should YOU raise a ticket?

This is for everyone — not just the Support Team:

Situation Team Raise a ticket?
Customer asks a question or logs an issue Support / All ✓ Yes — always
You spot a bug or platform error Dev / Product / Any ✓ Yes — log it
Sales needs a data file from Customer Delivery Sales / Delivery ✓ Yes — tag the team
You need a training session or L&D resource L&D ✓ Yes — track it
You message someone on Teams with a work request Any ⚠ Also raise a ticket

ⓘ Tip: Please continue to be human beings and have conversations. But after you have had that conversation — put it in the ticket.

4

How to raise a ticket

Option A (email) is the quickest:

✉ Option A — Email

support@tradeshield.ai

FreshDesk creates the ticket automatically. You get a confirmation with your ticket number.

? Option B — Portal

support.tradeshield.ai

Select a category, add attachments, and see all your previous tickets in one place.

ⓘ Tip: Include who it is affecting, what the problem is, when it started, and attach a screenshot if you have one.

5

Tracking your ticket

Every ticket moves through statuses — these are a living signal of how support is performing.

NEW
OPEN
PENDING
RESOLVED

SLAs — our commitments to customers on response and resolution time. Breaching an SLA is a broken promise.

⚠ Note: Only resolve a ticket when the issue is actually resolved. Closing early erodes trust and breaks your SLA data.

6

Reply vs Note vs Thread — what is the difference?

Feature Who sees it? Use it when...
Reply Customer ✓ Sending official communication to the customer. Be clear, empathetic, and professional.
Note Team only ✓ Leaving context for colleagues — called, no answer — Dev investigating — waiting on AM to confirm.
Thread Depends Managing multiple conversation streams — customer conversation AND internal Dev thread, side by side.

ⓘ Remember: Reply = the customer voice channel. Note = the team backstage conversation. If you spoke to a customer on the phone — put a note on the ticket. Always.

7

Why your ticket data matters to the whole business

FreshDesk is a business intelligence engine. Every ticket tells us something about our product, processes, and customers.

For Product & Dev

20 tickets in a week about the same issue? That is a product signal — not just a support problem.

For L&D

Recurring how-do-I tickets reveal training gaps. We use this data to build courses on our learning platform.

For Account Management

Via Freshsuccess, ticket volume feeds into churn risk scores. AM gets alerted before a client decides to leave.

⚠ This only works with clean data. Poorly logged tickets give wrong churn scores — meaning AM misses at-risk clients. Ticket hygiene is everyone responsibility.

8

Key takeaways & golden rules

FreshDesk is everyone responsibility

Not just Support. Every person at Trade Shield may need to raise, view, or contribute to a ticket.

?

If it is not in the ticket, it did not happen

The verbal conversation, the WhatsApp, the email — none of that is visible unless it is in FreshDesk.

?

Tickets drive improvement

Ticket patterns inform product decisions, training priorities, process changes, and where we need more resource.

?

Good habits from day one

Log clearly. Update regularly. Close correctly. These habits make the whole team stronger.

Quick Reference — The FreshDesk Flow

Need to raise a ticket?Email support@tradeshield.ai or use support.tradeshield.ai
Add internal context?Use a Note (internal only — customer will not see)
Respond to the customer?Use Reply — this goes to them directly
Close a ticket?Only when the issue is actually resolved

Need more help?

The support team is ready to assist

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article