Yuma logo

Yuma

Yuma is an ecommerce support agent that plugs into the helpdesk you already use. The core of Yuma. AI agents plug into your helpdesk and handle WISMO, returns, refunds, cancellations, subscription changes, and address edits end to end. A separate sales widget and a social queue sit beside that inbox work. You connect the helpdesk and Shopify, Yuma trains on past tickets and brand voice, and you set how confident an automated reply must be before it sends. Billing is not per seat.

Official website · yuma.ai

Pricing model
Paid
Main input
Helpdesk ticket and store data
Output
Reply, action, or human handoff
Access
Demo; 30 days on us

Is Yuma right for you?

Choose Yuma when the job is resolving ecommerce tickets inside Gorgias, Zendesk, Kustomer, Gladly, or Re:amaze, especially where-is-my-order, returns, refunds, cancellations, subscription changes, and address edits. Billing is for a full resolution only when no human touches the ticket. It is a weak fit if you want a new helpdesk or a per-seat inbox. The annual figures are labeled illustrative, and the bundle follows your forecast.

A good fit for

  • Automating WISMO, returns, refunds, and order edits inside a helpdesk you already run.
  • Paying for fully resolved tickets rather than seats, with a human handoff when the Handbook is silent.
  • Adding a product-page Q&A or social queue only if you accept those as separate add-ons.

Know the trade-offs

  • Annual prices are called illustrative and assume a 12-month commitment paid upfront.
  • A human touch voids the resolution charge, and monthly overage is a flat $1.50.
  • Sales AI is its own subscription; Social AI pricing depends on scope.

Tickets, channels, setup, and the resolution bill.

Act on the order, or hand the ticket back

The core of Yuma. AI agents plug into your helpdesk and handle WISMO, returns, refunds, cancellations, subscription changes, and address edits end to end. The same block says they take actions, not just send replies, with 75+ pre-built automations, real-time carrier data, and brand voice across channels. On the support page, one written Handbook in plain language is what runs the conversation across email, chat, SMS, WhatsApp, social DMs, outbound outreach, and phone calls. Where the Handbook is silent, Yuma doesn't improvise. It hands the ticket to a person and logs the gap as a question you answer once. A sample thread names the steps: detect WISMO, pull the Shopify order, note a carrier exception, draft an on-brand reply, and pass QC checks. Shopify actions listed include refunds, order edits, cancel or pause, discount codes, and order history. Gorgias is a one-click install that can auto-reply or draft, apply tags, and escalate by intent.

Official documentation

Keep storefront and social work on their own add-ons

The homepage splits the product into Support AI, Sales AI, and Social AI. Sales AI is an on-page Q&A widget for sizing, compatibility, ingredients, and comparisons, answering in brand voice. Social AI monitors Facebook and Instagram, auto-replies to routine questions, hides spam, amplifies positive mentions, and flags churn signals. Ask Yuma is described as reading tickets the other agents handle, finding what is breaking, and shipping a fix. Sales AI and Social AI are add-ons. Sales AI runs on its own subscription. Social AI pricing depends on scope. A free CX audit is separate: connect a helpdesk, get a history report, and keep it even if you do not buy.

Official documentation

Connect the helpdesk, then set the confidence bar

Setup on the homepage is three steps. Connect: plug Yuma into Gorgias, Zendesk, Kustomer, Gladly, or Re:amaze and into Shopify, described as live in hours, not weeks. Train: Yuma learns from past conversations, your knowledge base, and your brand voice, with 15-20 safety checks on every reply before it sends. Automate: you set the confidence threshold, and what the agents cannot handle goes to the team with full context. The support page says agents read the store, helpdesk, subscriptions, and marketing platform in real time. The visible integration list includes Shopify, Gorgias, Zendesk, Kustomer, Klaviyo, Loop Returns, Recharge, ShipStation, ShipBob, Salesforce Service Cloud, and Front, plus a line for 50+ more across helpdesks, 3PLs, returns, loyalty, and shipping. A policy change is described as something you make once so every channel follows it. The page also says support can run in 180+ languages, 24 hours a day.

Official documentation

Pay for a full resolution, not for a seat

Every plan carries a 12-month commitment and pays only for fully automated resolutions. Figures are illustrative annual prices, paid upfront. Your exact bundle is built around your forecast. A support ticket that Yuma handled from start to finish, end to end, with no human involved at any point. A human touch removes the charge. The count is once per resolved ticket, not once per action. On monthly plans, extra full resolutions are billed at a flat $1.50 each, and conversations or escalations are still never charged. Annual plans are described as having no overage: usage pauses at the end of the bundle and resumes at renewal. No implementation fee No overage on annual plans 4.8 average CSAT SOC 2 Type II Starter Smaller brands getting their core inbox automated. $14,400 /yr ~ $1.20 per resolution 12,000 resolutions / year Growth Scaling DTC teams automating the bulk of their inbox. $40,000 /yr ~ $0.83 per resolution ~ 48,000 resolutions / year Scale High-volume brands running automation as core infrastructure. $90,000 /yr ~ $0.75 per resolution ~ 120,000 resolutions / year Past 120,000 resolutions a year your rate keeps dropping toward the $0.55 floor. We size a bundle to your numbers. Growth says annual plans have no overage fees, and its 30% automation line depends on your processes and the onboarding timeline.

Official documentation

Ways to use Yuma

Answer a where-is-my-order ticket

A suggested WISMO pass follows the actions the pages name. The order question arrives, Yuma reads the Shopify order and the carrier, and it replies in brand voice if the Handbook covers the case. You set the confidence threshold so a weak match waits for a person, with context on the handoff. The weather-hold sample on the support page is their illustration. Coverage still depends on the Handbook you write.

Refund only when the Handbook allows it

A suggested refund path follows the Handbook rule. The support page says Yuma can issue a refund, edit an order, or pause a subscription from the helpdesk thread when the policy allows it. Where the Handbook is silent, Yuma doesn't improvise. It hands the ticket to a person and logs the gap as a question you answer once. That log is the documented way a missing policy becomes a question you answer once, instead of an invented exception. Suggested only as that control. A full resolution, the billable event, requires that no person stepped in. If an agent edits the reply, the pricing FAQ says the ticket is excluded from usage.

Put product questions on the storefront widget

A suggested pre-purchase setup is the Sales AI widget, not the support bundle. The homepage describes answers on the product page for sizing, compatibility, ingredients, and comparisons. The pricing add-on says that shopping agent runs on its own subscription, so it is not assumed to be inside Starter, Growth, or Scale. This suggestion keeps storefront questions separate from ticket resolutions. Social comments and DMs are a third add-on, also scoped in a conversation rather than given a shown price.

How to get started with Yuma

  1. 1

    Connect the stack

    Plug Yuma into the helpdesk and the Shopify store. The homepage names Gorgias, Zendesk, Kustomer, Gladly, and Re:amaze.

  2. 2

    Train the Handbook

    Let it learn from past conversations, the knowledge base, and brand voice. Silent policies are handed to a person and logged.

  3. 3

    Set the threshold

    Choose the confidence level for an automatic send. Anything below it goes to the team with context.

  4. 4

    Match a bundle to the forecast

    Compare Starter, Growth, and Scale as illustrative annual prices, then book a demo so the bundle uses your volume.

Illustrative annual resolution bundles.

Check live pricing

The pricing page says figures are illustrative annual prices, paid upfront, on a 12-month commitment, and that the exact bundle follows your forecast. First 30 days are on them, with no implementation fee. Search-result Shopify listing prices were not copied.

Starter

A smaller brand automating the core inbox.

$14,400/yr.

Illustrative annual price, paid upfront.

  • About $1.20 per resolution
  • 12,000 resolutions a year
  • Monthly over-quota ticket listed at $1.50

Growth

A team automating most of the inbox.

$40,000/yr.

Illustrative annual price, paid upfront.

  • About $0.83 per resolution
  • About 48,000 resolutions a year
  • No overage fees on annual plans

Scale

High-volume automation as infrastructure.

$90,000/yr.

Illustrative annual price, paid upfront.

  • About $0.75 per resolution
  • About 120,000 resolutions a year
  • Rate can drop toward the $0.55 floor above that volume

Past 120,000 resolutions a year the page says the rate keeps dropping toward the $0.55 floor and the bundle is sized to your numbers. Add-ons are a separate conversation.

Alternatives to Yuma

Zendesk

You need the helpdesk itself, not an agent plugged into one.

Yuma's pages describe installing into Zendesk and leaving macros and routing in place. This page states no Zendesk price.

Yuma: common questions

What does Yuma charge for?

A full resolution is a ticket handled end to end with no human involved, counted once, not per action. If an agent steps in, it is excluded. Conversations and escalations are not charged, and the page says it never charges per seat.

Source
Are the Starter, Growth, and Scale prices final?

No. They are illustrative annual prices, paid upfront, and the exact bundle follows your forecast. The cards show $14,400/yr, $40,000/yr, and $90,000/yr, with a per-resolution figure beside each total.

Source
What happens after the included resolutions run out?

On annual plans, usage pauses when the bundle ends and resumes at renewal, with no overage. Monthly plans bill extra full resolutions at a flat $1.50 each. Above 120,000 resolutions a year, the rate is described as falling toward the $0.55 floor.

Source
Is there a free period or a setup fee?

The pricing page says the first 30 days are on them and there is no implementation fee. The homepage says to start a 30-day free trial. These pages do not show an ongoing free inbox plan.

Source
Which helpdesks and store actions are named?

The homepage names Gorgias, Zendesk, Kustomer, Gladly, and Re:amaze, plus Shopify. Shopify actions on the support page include refunds, order edits, cancel or pause, discount codes, and tracking. Other named tools include Klaviyo, Loop Returns, Recharge, and Salesforce Service Cloud.

Source
Does a silent policy still get an answer?

The support page says that where the Handbook is silent, Yuma does not improvise. It hands the ticket to a person and logs the gap as a question you answer once. That is separate from the confidence threshold on the homepage, which sends low-confidence cases to the team with context.

Source

Sources & last checked

Oct 6, 2026 · NavHunt editorial

NavHunt did not run Yuma, did not connect a helpdesk, and did not request a quote. This profile only restates the public homepage, pricing page, and Support AI page. Merchant quotes and percentages shown on those pages are not treated as measurements. This description is based on Yuma's official materials reviewed on 2026-10-06, including Yuma homepage, Yuma pricing, Yuma Support AI.

Price Yuma from your ticket volume.

Read the resolution rule first, then compare the illustrative annual bundles with your forecast.

Explore Yuma