Gorgias AI Agent actions and automated tasks: what it does and how to set it up in 2026

What the Gorgias AI Agent actually is

Before the action list, it helps to get the vocabulary right, because Gorgias doesn't call these things "automated tasks" generically. The product splits the AI Agent's behaviour into named parts, and the names matter once you're inside the builder.

There's one AI Agent per connected Shopify store, and it plays two roles from the same subscription: a support agent that handles post-purchase work (returns, tracking, cancellations) and a shopping assistant that handles pre-purchase work (product questions, recommendations, upsells). Underneath that sit three concepts you'll touch constantly:

• Skills are "a set of instructions for one or more intents," per the Gorgias docs. A skill bundles a trigger (an intent like Return / Request), instructions written in a WHEN/IF/THEN model, and a knowledge toggle. Skills are the primary way you steer the agent.
• Actions are, in Gorgias's own words, "a series of tasks that AI Agent performs on your behalf in multiple connected apps." This is the layer that does something real in Shopify, Recharge, or Loop.
• Guidance is reference knowledge the agent pulls by relevance rather than by intent, for general questions like "do you have physical stores?"

The one relationship to hold onto: an Action only runs when the AI Agent calls it from inside a Skill or Guidance. Adding an action to a skill is what makes the agent actually attempt it when a matching conversation lands. If you've read our overview of the Gorgias AI Agent and come away unsure how skills and actions connect, that's the link to keep in mind.

Every action the Gorgias AI Agent can take

Gorgias ships a template library of the most common ecommerce requests, reachable at AI Agent > Train > Support Actions, where you either create from a template or build a custom action. Here's the full catalogue, grouped by what the agent is doing.

The community read on this is consistent: the actions earn their keep when a real chunk of your tickets need them. As one ecommerce operator put it on a Reddit thread comparing Gorgias and Zendesk:

"If a meaningful chunk is WISMO, address changes, cancels, refunds, exchanges, Gorgias usually feels worth it because the agent can do the work inside the ticket with Shopify context right there."

u/cavalry18, r/CRM

One thing worth flagging early: answering an FAQ from your help center isn't an "action" in Gorgias's sense, it's handled by knowledge retrieval. Actions are specifically the steps that change something in a connected app.

How an action actually fires

Knowing the catalogue is one thing. Knowing how a request turns into a completed action is what lets you debug it later. The flow is more deterministic than "the AI figures it out."

A message arrives, Gorgias classifies its intent automatically (you don't create intents, they're built in), a matching skill picks it up, and the skill's instructions run their steps in order, including any actions. When you build or edit an action, you're configuring four things, per the Gorgias docs on creating an action:

1. Name and description. The description is load-bearing, not decoration: the agent uses it to decide whether the action applies to a given request. Gorgias recommends spelling out when it applies, what it does not do, and what customers sound like when they ask for it.
2. Conditions. Choose no conditions, all conditions, or at least one. Conditions read Shopify customer fields (ID, email, tags) and order fields (amount, fulfilment status, address). The classic example: only offer a return if the order is under 30 days old.
3. Require customer confirmation. Optional in general, but automatically forced on for anything irreversible, cancelling an order, editing an address, cancelling a subscription. The agent has to get a yes before it executes.
4. Steps. Added through Add Steps, pick the app, pick what to do. Steps run top to bottom, are drag-reorderable, and each can require app authentication (usually an API key).

If you outgrow the templates, the Advanced options editor opens a visual canvas where you can fire HTTP requests to apps Gorgias doesn't natively integrate, collect shopper inputs as variables, and branch the logic. Two warnings come straight from the docs: it's meant for people comfortable making HTTP requests, and once you switch to Advanced options you can't go back to the basic editor. And when a step fails, the agent posts a "failed to execute one or more steps" note and hands the ticket to your team, so you debug failures through the action event log rather than guessing.

How to set up an automated task, step by step

Most automated tasks start as a skill. Here's the path from the Gorgias docs on creating a skill, which lines up with our own Gorgias AI setup guide:

1. Go to AI Agent > Skills > Create skill and choose a template (returns, cancellations, order status, address updates) or start from scratch. You can also open existing Guidance and convert it to a skill.
2. Write the instructions in WHEN/IF/THEN form, up to a 30,000-character limit. WHEN is the linked intent, IF holds your branching conditions ("if the order is older than 30 days"), THEN is the ordered steps including any actions. The docs are firm on referencing your actual policies and timelines, not generic ones, and you insert variables and actions inline at the right step.
3. Link intents. Click Link intents and pick one or more. Intents are detected automatically, but a single intent can only belong to one skill, so linking it here removes it from any other skill. Teams commonly pair the return and exchange intents, which is exactly the kind of refund-versus-exchange classification that trips up simpler bots.
4. Set the knowledge toggle. On (the default) means your instructions lead and knowledge fills gaps. Off means instructions only, which you'd use for a legally sensitive process.
5. Test it. Enter a triggering message, send, and use Show reasoning to see why the agent answered the way it did.
6. Enable it. Until you do, changes save as a draft.

For information that applies across many conversations rather than one request type, you write Guidance instead (up to 100 per store, same 30,000-character limit each). The docs' own decision rule is clean: a step-by-step procedure for one request is a skill, general info that applies broadly is guidance.

A quick reality check before you start: this is genuine configuration, not plug-and-play. You're authoring skills, building actions with conditions and authenticated steps, writing guidance, setting tone and handover topics, and (next section) keeping your rules from colliding with all of it. Worth knowing if you're weighing the setup effort against the payoff.

Where Gorgias rules fit, and the double-reply trap

Here's the part that catches people. Gorgias has a second automation system running alongside the AI Agent: the Rules engine, classic if-this-then-that automation that acts on every ticket whether the AI touches it or not. Rules live at Workflows > Tools > Rules, and their actions include tagging, assigning, closing, replying, and applying a macro.

The sequencing fact that matters: rules run first, and the AI Agent picks up after. So if you have a rule with a "reply to customer" or "apply macro" action and the AI Agent also responds, the customer gets two messages. The fix is to switch the rule off or add a condition so it doesn't fire on tickets the AI handles. Older accounts that still have legacy autoresponder rules get them auto-disabled when the AI Agent is enabled on email, but it's worth checking yours.

Gorgias gives you two pre-built rule templates designed for this overlap, per its guide to using rules with AI Agent:

• Prevent AI Agent from answering tags tickets ai_ignore and stops the agent from responding or taking any action, useful for VIP customers or sensitive keywords.
• Re-open low CSAT AI Agent tickets auto-reopens an AI-resolved ticket that gets a low CSAT score and routes it back to a human.

You can't set a rule condition on "assigned to AI Agent" directly, but the agent auto-tags every ticket it touches (ai_handover, ai_ignore, and others), and those tags are the reliable way to target it. One more nuance that surprises people: the AI Agent does not use your macros at all. It writes its own replies from skills and knowledge; macros stay a human-only tool.

What automating a task actually costs

This is the section most teams skim to, so let's be direct. Gorgias AI Agent uses outcome-based, per-resolution billing, and two separate fees can stack on a single ticket.

Per the Gorgias billing docs, a helpdesk ticket fee applies to any ticket that gets at least one message from the helpdesk, and an automation fee applies on top only when the AI Agent resolves a ticket without handing it to a human. So a fully AI-resolved conversation costs ticket fee plus automation fee; a ticket the AI escalates costs the ticket fee only. "Resolved" means the customer doesn't need a human within 72 hours.

Here's how that lands across the plans, billed by ticket volume rather than seats:

A worked example: say you're on Pro and the AI fully resolves 1,000 conversations in a month. That's roughly $360 for the plan, plus 1,000 × $0.90 in automation fees, so about $900 on top of base before any ticket overage. Annual billing trims up to 16% off the plan fee but doesn't touch the per-resolution rate. If you want to sanity-check your own numbers, our Gorgias AI pricing breakdown and the automation add-on guide go deeper.

This is where the community gets vocal. On the same Reddit thread, the cost-creep concern came up repeatedly:

"Gorgias is awesome if you're super deep into Shopify workflows... The downside is the price adds up quick once your volume grows."

u/ShoddyPut8089, r/CRM

The rough consensus from people who've run it: Gorgias pays off when 40% or more of your tickets need direct Shopify actions. If most of your volume is conversational, you may be paying a premium for actions you rarely fire.

Where the Gorgias AI Agent falls short

A fair guide names the limits, not just the features. A few are worth knowing before you commit.

It's Shopify or nothing. The AI Agent requires a Shopify store connected to Gorgias, and its conditions and variables draw from Shopify order and customer fields. Brands on BigCommerce, Magento, or WooCommerce are left leaning on custom HTTP actions rather than the native path.

Channel coverage is narrower than the helpdesk's. The AI Agent resolves conversations on email and chat (with SMS as a more recent, add-on-dependent addition). It does not run on Voice, and while social channels like Facebook and Instagram are supported for human agents, AI Agent resolution isn't documented for those DMs.

One agent per store. Multi-store brands manage each store's agent separately, duplicating skills and guidance store to store.

There's a stated ceiling. Gorgias's own marketing caps automation at "60% of email and chat conversations," which implies the remaining 40% still needs people. And testing carries a real risk: actions run in a test conversation can mutate live customer and order data unless you target a fake profile.

There's also a sharper point buried in the community discussion, and it's the one that reframes the whole exercise:

"What's usually overlooked is that most teams optimize for handling tickets faster, not for reducing them."

u/Andrutex, r/ecommerce

That's the right lens. The goal of any Gorgias automation isn't a faster reply, it's a ticket that never needed a human in the first place.

Alternatives when you're not all-in on Shopify

If you're a Shopify-native brand and a healthy share of your tickets are order actions, Gorgias's AI Agent is a strong, purpose-built fit, and our honest Gorgias review says as much. The friction shows up when your setup doesn't match those assumptions: you run support across more than one helpdesk, you're on a non-Shopify cart, or the per-resolution math gets uncomfortable as volume climbs.

That's the gap a layer-on-top AI agent fills. Instead of replacing your helpdesk, it plugs into the one you already have, Zendesk, Freshdesk, Gorgias itself, or your inbox, and automates the same kinds of order, return, and FAQ work without locking you to one storefront. If you're shopping around, we've also rounded up the best Gorgias alternatives and the best AI for Shopify customer support.

Try eesel

eesel is an AI teammate that lives inside the helpdesk and apps you already use, so you don't have to migrate off your current setup to automate order tracking, returns, refunds, and product questions. You brief it in plain language the way you'd onboard a new hire, it connects to Shopify and 100+ other tools, and it can take real actions on tickets rather than just drafting replies.

The differentiator most teams care about: eesel lets you simulate the agent against your past tickets before it ever replies to a customer, so you can see your real resolution rate and refine behaviour with no surprises and no live-data risk. Pricing is usage-based with no per-resolution surcharge and a clear spend cap, so the cost doesn't quietly scale with your ticket volume. You can start free and point it at your existing queue in minutes.