Customer storyClutchLoop logo

Returns go to the portal and product questions get an answer, without a person on the ticket

ClutchLoop runs eesel as Loopy on Gorgias, Shopify and the website chat. Loopy replies to returns and product questions itself, looks up live prices and stock in Shopify, tags the ticket, and steps back the moment a person is already handling it.

Industry
Consumer products, phone accessories
Based in
United States
With eesel since
April 2026
Working with
Arron Ben
230Gorgias tickets handled in a month8 Aug to 8 Sep 2026
180replies sent to customers directlyabout seven in ten conversations, no person needed
76live product lookups in Shopifyprices, colours and stock, never from a stale page
27website chats answeredin the customer's own language
clutchloop.com
ClutchLoop website
How it runs

What happens when a customer writes to ClutchLoop

  1. 1
    A customer writes in

    Email or chat wakes Loopy, which reads the thread and past tickets.

  2. 2
    Returns and replacements go to the portal

    US customers get a reply pointing them to ClutchLoop's returns portal.

  3. 3
    Product questions get answered

    Loopy answers from site content and checks Shopify for price and stock.

  4. 4
    Everything else waits for a person

    Loopy leaves other topics to the team and stays out if someone replies.

Connected integrations

  • Gorgias
  • Shopify
  • Slack
  • wWebsite

Agents at work

  • Loopy268 runs in 30 days

The company

ClutchLoop makes a patented phone tether that keeps a phone attached to its owner, against drops and theft. The first prototype was tested in 2022, and the company says more than 150,000 people have used the product since. The current range is the ClutchLoop II ecosystem, sold from its Shopify store, with customer support in Gorgias.

Visit ClutchLoop at clutchloop.com

The problem

A direct-to-consumer accessory brand gets the same few questions at volume. Where is my order. How do I return this. Which model has the metal anchor. Is the DayTrip colour back in stock. Most have a fixed answer or a fixed next step, and a person typing it out one ticket at a time is slow for the customer and dull for the team.

The team wanted the routine handled without them, but with a clear line: the agent should answer what it can answer well, send returns where returns go, and never talk over a person who is already in the conversation.

How it runs

ClutchLoop connected Gorgias, Shopify and its website to eesel in April 2026 and named the agent Loopy. Loopy reads about 590 pages from clutchloop.com, the Shopify catalogue and the Gorgias history, plus a short set of policies written by the team.

  • Gorgias tickets. A customer message wakes Loopy. It reads the full thread and looks up the customer's other tickets before deciding anything.
  • Two things it replies to on its own: return, refund and replacement requests from US customers, which it sends to the returns portal, and product questions, which it answers from the site content and live Shopify data.
  • Everything else is for the team. Loopy does not reply, and it drafts or leaves an internal note where that saves time. If a team member is already active in the thread, it does nothing.
  • Shopify first for anything live. Prices, variants and stock come from Shopify at the moment of asking, not from crawled pages that may be out of date.
  • Website chat. The Loopy bubble on clutchloop.com answers order status, returns and product questions, and can create a Gorgias ticket for the team when a chat needs one. Replies come back in the language the customer wrote in.
  • Tone. Short, friendly and plain, with public links only. No made-up answers: if the policies do not cover it, Loopy says so and hands over.

A month of work

Between 8 August and 8 September 2026 Loopy handled about 230 Gorgias tickets and 27 website chats for ClutchLoop. It sent about 180 replies directly, looked up 76 products in Shopify, tagged 75 tickets, drafted 43 replies for the team, left 30 internal notes and created 3 tickets from chat. The work is spread through the day and night, with a small peak in the US afternoon.

A month of work

What eesel did, from its own records

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

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

Conversations handled, 8 Aug to 8 Sep 2026255
×Minutes a person would spend on one5
=Hours of people’s time21
×Cost of an hour, all in$25
=A month$500
A year$6,000
Gorgias tickets and other live work
Live work per week, the last 13 weeks
091182Week of 15 Jun: 111Week of 22 Jun: 12522 JunWeek of 29 Jun: 106Week of 6 Jul: 1826 JulWeek of 13 Jul: 177Week of 20 Jul: 18120 JulWeek of 27 Jul: 96Week of 3 Aug: 173 AugWeek of 10 Aug: 1Week of 17 Aug: 3817 AugWeek of 24 Aug: 92Week of 31 Aug: 11531 AugWeek of 7 Sept: 9
Show as a table
Week ofRuns
15 Jun111
22 Jun125
29 Jun106
6 Jul182
13 Jul177
20 Jul181
27 Jul96
3 Aug17
10 Aug1
17 Aug38
24 Aug92
31 Aug115
7 Sept9
When the work arrives
Hour of day, UTC. 35% of it lands between 10pm and 7am, when nobody is at a desk.
00:00 UTC: 900:0001:00 UTC: 402:00 UTC: 1803:00 UTC: 1404:00 UTC: 805:00 UTC: 606:00 UTC: 606:0007:00 UTC: 408:00 UTC: 909:00 UTC: 510:00 UTC: 411:00 UTC: 212:00 UTC: 712:0013:00 UTC: 1414:00 UTC: 915:00 UTC: 1616:00 UTC: 1817:00 UTC: 1418:00 UTC: 1118:0019:00 UTC: 2120:00 UTC: 1521:00 UTC: 1722:00 UTC: 1223:00 UTC: 12
Show as a table
Hour (UTC)Runs
00:009
01:004
02:0018
03:0014
04:008
05:006
06:006
07:004
08:009
09:005
10:004
11:002
12:007
13:0014
14:009
15:0016
16:0018
17:0014
18:0011
19:0021
20:0015
21:0017
22:0012
23:0012
What it did
Actions taken in the customer's tools, last 30 days
Public replies sentPublic replies sent: 182182Product lookupsProduct lookups: 7676Tickets taggedTickets tagged: 7575Draft replies for the teamDraft replies for the team: 4343Internal notesInternal notes: 3030Knowledge searchesKnowledge searches: 1919Order lookupsOrder lookups: 55Tickets created for the teamTickets created for the team: 33Order changesOrder changes: 11
Show as a table
ActionCount
Public replies sent182
Product lookups76
Tickets tagged75
Draft replies for the team43
Internal notes30
Knowledge searches19
Order lookups5
Tickets created for the team3
Order changes1
Where the work comes from
Share of live runs by channel, last 30 days
Gorgias tickets: 228 (89%)website chats: 27 (11%)
Show as a table
  • Gorgias tickets 89%
  • website chats 11%
ChannelRuns
Gorgias tickets228
website chats27

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