Customer storyOrosoft logo

Support staff mention eesel on a Freshdesk ticket and get a draft grounded in past tickets

OroSoft supports its Neo bullion ERP through Freshdesk. When a support agent needs a reply, they mention eesel on the ticket and it drafts one from six thousand resolved tickets and the help center, always saying which ticket or article it is based on. It is early days.

Industry
Software for the precious metals industry
Based in
India
With eesel since
May 2026
6,100past tickets it answers fromFreshdesk history since April 2026, re-synced every night
20help center and reference filesthe official policies and procedures
14draft replies in a month8 Aug to 8 Sep 2026, each one asked for by a support agent
May 2026when the setup starteda copilot for the support team, not a customer-facing bot
orosoft.com
Orosoft website
How it runs

What happens when a customer writes to Orosoft

  1. 1
    A client raises a ticket

    Bullion traders using the Neo suite write in through Freshdesk.

  2. 2
    A support agent asks eesel

    An agent mentions eesel, which searches resolved tickets first.

  3. 3
    It drafts, and cites its source

    It mirrors a past answer and names the ticket or article it used.

  4. 4
    If it cannot find an answer, it says so

    With no support found, eesel leaves a note asking for a person.

Connected integrations

  • Freshdesk

Agents at work

  • eesel13 runs in 30 days

The company

OroSoft builds software for the precious metals industry. Its Neo Product Suite covers trading, refining, financials and reporting for bullion businesses, and the company says it has been doing this for more than two decades, with over 100 clients and a team of more than 160. Clients run their trading and back office on it, so support questions are specific and technical.

Visit Orosoft at orosoft.com

The problem

Most support questions have been answered before, somewhere in years of Freshdesk history. The answer is in a resolved ticket, but finding it means searching, reading and rewriting. OroSoft wanted a way for a support agent to get that first draft, grounded in how the team actually resolved the same problem last time, without leaving the ticket.

How it runs

OroSoft connected Freshdesk to eesel in May 2026 and loaded its help center and about 6,100 tickets. The setup is deliberately a copilot: eesel writes for the support team, and only the team writes to clients.

  • On request. eesel wakes when a support agent mentions it on a Freshdesk ticket. If they ask for a draft, it posts one on the ticket as a draft reply. If they ask a question, it answers in an internal note.
  • Resolved tickets first. It is told to prefer resolved or closed tickets, weight the recent ones, and treat the help center as the source of truth for policy. If the two disagree, it follows the more recent.
  • Match the precedent. When a past ticket fits, the draft copies its structure, tone and length. A short answer that worked before stays short.
  • Grounded or nothing. Every draft says what it is based on. If it cannot ground a reply, it leaves a note asking for human review instead.
  • Kept current. It re-syncs Freshdesk tickets every night and the help center every Monday, in Indian time.

A month of work

This is an early setup. Between 8 August and 8 September 2026 the team asked eesel for help on 13 Freshdesk tickets and it left 14 draft replies, running about 53 knowledge searches to write them. The volume is small by design: it drafts only when asked.

What is next

The agent is also set up to draft automatically when a new ticket or customer reply arrives, and that path is not switched on yet. Turning it on would put a draft on every ticket before an agent opens it, the way the mention flow does today for the tickets they choose.

A month of work

What eesel did, from its own records

Every count on this page comes from eesel's activity log for Orosoft, 8 Aug to 8 Sep 2026. The only estimate is the money and time saved, and the receipt shows how it is worked out.
$100
of people’s time a month, $1,000 a year
3 hours
about 0 working days, every month

$40 is an international benchmark for an hour of support time, not Orosoft’s own cost.

Conversations handled, 8 Aug to 8 Sep 202613
×Minutes a person would spend on one12
=Hours of people’s time3
×Cost of an hour, all in$40
=A month$100
A year$1,000
Freshdesk tickets and other live work
Live work per week, the last 13 weeks
036Week of 15 Jun: 5Week of 22 Jun: 222 JunWeek of 29 Jun: 1Week of 6 Jul: 26 JulWeek of 13 Jul: 3Week of 20 Jul: 520 JulWeek of 27 Jul: 0Week of 3 Aug: 63 AugWeek of 10 Aug: 3Week of 17 Aug: 517 AugWeek of 24 Aug: 2Week of 31 Aug: 331 AugWeek of 7 Sept: 0
Show as a table
Week ofRuns
15 Jun5
22 Jun2
29 Jun1
6 Jul2
13 Jul3
20 Jul5
27 Jul0
3 Aug6
10 Aug3
17 Aug5
24 Aug2
31 Aug3
7 Sept0
What it did
Actions taken in the customer's tools, last 30 days
Knowledge searchesKnowledge searches: 5353Draft replies for the teamDraft replies for the team: 1414
Show as a table
ActionCount
Knowledge searches53
Draft replies for the team14

Hire an eesel teammate for your support

Connect your helpdesk, let it learn from your past tickets, and start with drafts before it replies on its own.

Start free