Customer storyLuxedo logo

Home projector questions get a troubleshooting draft in Gorgias, one step at a time

Luxedo runs eesel on Gorgias for its residential customers. On a new ticket, eesel checks the customer is a home user, searches past tickets and help content, and leaves an internal note with a draft reply and a summary for the support team.

Industry
Projection mapping systems
Based in
United States
With eesel since
July 2026
Working with
Gary Shaeffer
1,000Gorgias tickets, macros and articles it answers fromabout 1,040 items from Gorgias plus 16 files
21tickets prepared for the team in a month8 Aug to 8 Sep 2026; the trigger went live in the last week of August
27internal notes lefteach with a draft reply and what the team needs to know
Residential onlywho it works forschools, gyms and other commercial buyers stay with the sales team
luxedo.com
Luxedo website
How it runs

What happens when a customer writes to Luxedo

  1. 1
    A customer writes in

    Tickets from email, web and social reach Gorgias and wake eesel.

  2. 2
    It checks this is a home customer

    Commercial, spam and call records are skipped, residential goes on.

  3. 3
    It reads before it writes

    It searches past tickets, macros and articles and uses only those.

  4. 4
    One note, two parts

    A draft reply plus a team summary, and a person sends it.

Connected integrations

  • Gorgias

Agents at work

  • eesel22 runs in 30 days

The company

Luxedo makes projection mapping systems. Its Courts system turns a school gym floor into a light show for game nights: four projectors, integrated audio, installed in a day, with three tiers to suit different rafter heights and lighting. The site lists 246 schools across 42 states. Luxedo also sells projectors to home customers, and it is those customers the eesel setup serves.

Visit Luxedo at luxedo.com

The problem

Home projector support is technical. A customer has a projector that will not connect, content that will not play, or a subscription question, and the useful reply is a single next step, not a checklist of everything that might be wrong. The same inbox also holds pricing enquiries, sales leads from schools, and call records, none of which should get a support draft.

When a ticket does need a person, the team wanted to pick it up with the diagnostics already gathered, so the customer does not have to explain the problem twice.

How it runs

Luxedo connected Gorgias to eesel in July 2026, spent August building the knowledge and the instructions, and switched the ticket trigger on in the last week of August. One agent handles it.

  • It wakes on every new message on a Gorgias ticket, then decides whether to act. Commercial and institutional buyers, phone-call tickets, spam and surveys are skipped so nothing is spent on them.
  • It troubleshoots one step at a time. The draft identifies what the customer is trying to do, what is happening instead, and the simplest next step, then asks whether that fixed it. It never sends a long list of possible fixes.
  • It only says what the knowledge says. No invented specifications, warranty terms, pricing or compatibility. If the material is incomplete or conflicting, the note says the ticket needs a person.
  • Some things always go to the team: possible hardware failure, replacement equipment, warranty decisions, refunds or billing, anything about electrical safety, and any customer who asks for a person.
  • Before escalating, it gathers what the specialist will need: error messages, when it started, what has been tried, photos if there are any. That summary is the second half of the note.
  • The team can @mention eesel on any ticket to bring it in, and each morning at 7am New York time it reviews the workspace and emails a short note to the owner.

A month of work

Between 8 August and 8 September 2026 eesel prepared 21 Gorgias tickets for Luxedo, left 27 internal notes and ran about 85 knowledge searches. It is early days: the trigger has been live for a few weeks, and the setup work of August, syncing about 1,000 Gorgias items and writing the instructions, is what the first tickets ran on.

A month of work

What eesel did, from its own records

Every count on this page comes from eesel's activity log for Luxedo, 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
4 hours
about 1 working days, every month

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

Conversations handled, 8 Aug to 8 Sep 202621
×Minutes a person would spend on one10
=Hours of people’s time4
×Cost of an hour, all in$25
=A month$100
A year$1,000
Gorgias tickets and other live work
Live work per week, the last 13 weeks
0612Week of 15 Jun: 0Week of 22 Jun: 022 JunWeek of 29 Jun: 0Week of 6 Jul: 06 JulWeek of 13 Jul: 0Week of 20 Jul: 020 JulWeek of 27 Jul: 0Week of 3 Aug: 03 AugWeek of 10 Aug: 0Week of 17 Aug: 017 AugWeek of 24 Aug: 7Week of 31 Aug: 1231 AugWeek of 7 Sept: 2
Show as a table
Week ofRuns
15 Jun0
22 Jun0
29 Jun0
6 Jul0
13 Jul0
20 Jul0
27 Jul0
3 Aug0
10 Aug0
17 Aug0
24 Aug7
31 Aug12
7 Sept2
What it did
Actions taken in the customer's tools, last 30 days
Knowledge searchesKnowledge searches: 8585Internal notesInternal notes: 2727Draft replies for the teamDraft replies for the team: 2121
Show as a table
ActionCount
Knowledge searches85
Internal notes27
Draft replies for the team21

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