Gorgias AI agent pricing: costs, billing rules, and a CLI budget review

What you are paying for

The Gorgias AI Agent handles support and shopping conversations. Its documented setup provides one agent per connected Shopify store, with email, chat, and SMS coverage. Older subscribers may need an upgrade for the shopping role. Do not infer that every helpdesk integration or channel has the same AI capabilities.

This retained Gorgias product illustration shows the support interface, not a current price quote or billing screen.

A useful budget separates three questions: which subscription you have, how usage is counted, and what happens above the included allowance. I would collect those account details before assigning a dollar value to a projected automation rate.

Current versus legacy billing

Gorgias's billing guide gives the current counting rules. Its legacy pricing guide explains the older model:

An interaction qualifies as automated when no human involvement is needed within 72 hours. A helpdesk reply makes a ticket billable; an internal note or tag alone does not. Multiple replies inside the same ticket do not each become another billable ticket.

Legacy eligibility depends on account and upgrade history, not simply the year in an article title. For an account created before May 28, 2025, an admin can check Settings > Billing & usage, then the Shopping Assistant page. The legacy guide says an upgrade prompt there identifies the legacy model for an active AI Agent subscription. Check the account before assuming either column applies.

Gorgias uses this older interface example in its legacy billing guide. It illustrates the upgrade prompt, not a universal requirement for new accounts.

Build a monthly estimate from your account

The public pricing page describes Helpdesk plus AI Agent and volume-based Voice and SMS add-ons. Use the selected plan and your account's Billing & usage details for the actual rates and allowances. An old screenshot or a quoted annual rate is not enough to establish your current terms.

Collect these inputs for the same billing period:

• The helpdesk subscription charge and included billable tickets.
• The automation subscription or commitment, included interactions, and extra-usage rate.
• The counting model that applies to your account.
• Voice, SMS, or other agreed add-on charges.
• Expected ticket and automation usage, counted separately.

Calculate extra usage only after applying the appropriate allowances. Do not multiply every automated interaction by an overage rate if some are already included. Conversely, do not count AI resolutions only in the automation column when the current model also counts them as helpdesk tickets.

For a planning example, suppose 1,000 distinct replied-to tickets include 300 AI-only resolutions and 700 tickets requiring people. Under the current model, that is 1,000 helpdesk tickets and 300 automated interactions before allowances. Under the eligible legacy model, it is 700 helpdesk tickets and 300 automated interactions. This is a counting example, not a quote; apply your own subscription terms.

Check what a proposed saving actually measures

A higher automation percentage does not, by itself, establish lower total spending. Compare the full bill and the outcomes for the same period. Record whether the customer received a correct answer, whether a promised action happened, and whether a human had to intervene.

For a returns pilot, a draft that explains the policy is not yet a resolved customer conversation. A private note may help a human reply but should not be reported as a customer-facing resolution. These distinctions matter both for quality and for comparing Gorgias's outcome-based charge with a task-based alternative.

Keep your baseline Gorgias costs when estimating an additional teammate. Replacing some native AI work does not remove the helpdesk subscription, and an eesel spending limit does not cap Gorgias usage.

Review an alternative support budget through eesel CLI

If you are considering an eesel teammate inside Gorgias, compare the work each service bills for before comparing rates. Eesel's current pricing is task-based, not a flat monthly allowance of interactions. On pay as you go, there is no platform fee or monthly minimum. A regular support ticket or chat session is $0.40 for the whole interaction, not each reply, and tasks are billed regardless of outcome. Annual commitments and Enterprise have different terms.

That distinction matters for a pricing comparison. Gorgias's automation charge depends on its resolution rules; eesel's regular-task charge does not disappear simply because a person eventually needs to help. Keep the existing Gorgias subscription and any applicable Gorgias usage charges in your budget when adding eesel.

The eesel CLI helps you inspect what your eesel teammate is set up to do and what it has been doing. It operates the same agent and workspace as the dashboard. You can type commands yourself, use the JSON output in a script, or ask Claude Code, Cursor, or Codex to perform a bounded review. It does not inspect or configure the native Gorgias AI Agent's subscription.

Start with a read-only usage review

With Node.js 18.17 or newer, sign in and identify the workspace before interpreting its bill:

npx @eesel/cli login
npx @eesel/cli whoami
npx @eesel/cli agents
npx @eesel/cli billing
npx @eesel/cli status --agent TEST_AGENT_ID
npx @eesel/cli automations --agent TEST_AGENT_ID
npx @eesel/cli activity --agent TEST_AGENT_ID

Replace TEST_AGENT_ID with the agent you intend to review. Billing returns workspace information; do not label the whole workspace's bill as the cost of one Gorgias queue. Other agents or types of work may contribute. Inspect Activity and the dashboard's task and date filters when reconciling charges.

These commands answer different questions:

For a coding-agent review, keep the initial request read-only:

Review this eesel workspace's billing, the selected agent's automations, and its recent activity. Explain what work could contribute to the bill and what evidence is missing. Separate workspace totals from this agent's work. Do not create automations, run chats, change permissions, or change the spending limit.

Structured output makes this practical without requiring the coding agent to infer settings from screenshots. It does not make missing attribution data appear. If the outputs do not establish a per-queue cost, report that gap and check the underlying records.

Budget a narrow pilot, not the entire inbox

In eesel, the trigger and filter determine which conversations reach the teammate. The Gorgias integration guide distinguishes a public customer-message trigger from an on-demand trigger when a teammate mentions @eesel in an internal note. A public-message trigger can apply to later replies as well as new tickets. Do not equate its event count with unique billed tasks.

Start a pilot only after inspecting existing automations and action permissions. An on-demand private-note workflow can let a human choose test conversations and inspect drafts before allowing public replies. Creating an automation changes the workspace and may enable it immediately; it is not part of the read-only review above. Full Gorgias authorization requires a person to approve access, and a help-center-only connection does not provide ticket actions.

If you also want to check how the agent explains your policy, first confirm the policy is available and keep customer-facing and order-changing actions disabled. Use a fictional question:

npx @eesel/cli new --name "returns-budget-pilot" --agent TEST_AGENT_ID
npx @eesel/cli chat "Fictional case: a shopper asks whether an opened item is eligible for return. Explain the policy you have and identify missing information. Do not contact anyone or change records." --agent TEST_AGENT_ID

A new conversation is not an isolated workspace, and the prompt does not revoke tool permissions. The CLI guide treats chat as billed work, so do not describe this as a free cost simulation. This answer checks policy handling; it does not demonstrate a resolved Gorgias ticket or predict a month's costs.

For the real pilot, record the selected tickets, task activity, delivered notes, public replies, and handovers separately. Review quality as well as spend. A low-cost answer that promises an ineligible refund is not a successful test.

Set a spending limit and check what it covers

Use Workspace settings > Billing & Usage to review eesel's monthly cap. The documented default is $250; a card is required before the limit is editable. At the cap, new work stops while work already in progress finishes. This limit governs eesel, not your Gorgias bill.

After an authorized pilot, run npx @eesel/cli billing and inspect Activity again. Reconcile the results with the chosen period and records instead of multiplying a trigger count by a task rate. A shared workspace with other active agents needs that separation before you attribute a change in spending to the pilot.

This eesel example shows task activity, not a Gorgias invoice or a per-queue cost report. Use your own workspace records to reconcile the pilot.

Compare the bill and the result

For native Gorgias AI Agent, check your account's ticket allowance, automation allowance, rates, overages, and legacy status. For eesel, check which tasks ran, the workspace's billing state, and the limit you set. Neither a successful demo nor a headline rate establishes the complete monthly cost.

Try eesel with your Gorgias helpdesk, then use the CLI to review a narrow pilot's setup and activity before expanding its coverage.