Sales, Marketing & SupportDone with custom-built or unnamed agent
Resolve helpdesk tickets end to end for online stores
An agent inside a store's helpdesk reportedly processes refunds, creates shipping labels and edits subscriptions on Recharge, Loop and Skio (roundup claims).
- What They Did
- The article is a vendor roundup, and its Yuma entry matches this use case. Yuma sits inside an existing helpdesk such as Gorgias, Zendesk, Kustomer or Re:amaze. It is described as processing refunds, creating labels, editing subscriptions on Recharge, Loop and Skio, and reading order, shipping and payment context. No setup steps are described.
- How It Went
- Yuma publishes per-customer automation rates, all vendor-stated: 89% at EvryJewels, 70% at Clove, 64% at Tediber, and about 40% in the first days elsewhere. The article gives no independent verification.
- Worth Knowing
- Pricing is quote-based, and how much the agent can do depends on the underlying helpdesk and your integrations. The article suggests testing a refund in a sandbox before signing.
Try it yourself with custom-built or unnamed agent
Set up an agent for my helpdesk [Gorgias, Zendesk, etc.] that reads new tickets about refunds, shipping labels, and subscription changes in [Recharge, Loop, or Skio]. For each ticket, prepare the exact action and a reply draft, and put them in a review queue. Do not issue refunds, create labels, edit subscriptions, or send replies until I approve each one.
Do this with a skill.
These SkillShop playbooks do this exact job.