How to Connect Gorgias to Claude or ChatGPT (6 Workflows to Try Right Now)
A few things to know before you connect Gorgias MCP:
- Compatible AI tools: Claude, ChatGPT, Cursor, and any other MCP-compatible client
- Cost: Included in your existing Gorgias paid plan at no extra cost.
- AI Agent: Not required. Helpdesk-only customers have full access.
- Availability: Currently in open beta, open to all paid plan customers.
Ask your helpdesk anything, and get a real answer from your actual data in seconds.
Gorgias MCP connects your Gorgias account directly to Claude, ChatGPT, Cursor, or any other MCP-compatible AI tool. No more exporting data or re-explaining context every time you need a different angle on your tickets. Ask a question, follow up, and execute, all in the same conversation.
This guide covers what Gorgias MCP is, how to connect it, and six specific workflows you can run in your first session.
What is Gorgias MCP?
The Model Context Protocol (MCP) enables AI systems to link directly with other tools.
The Gorgias MCP provides a first-party bridge, giving you a secure, direct connection between your chosen AI assistant and your Gorgias account.
Once connected, your LLM of choice can:
- Read and search your tickets and customer history
- Analyze patterns across CSAT scores, ticket volume, and resolution time
- Review your macros, rules, and tags
- Audit your AI Agent guidances and handoff tickets
- Draft new AI Agent guidances based on your existing setup
- Check user permissions and team configuration
How to connect Gorgias MCP
Setup takes about five minutes. Here is what you need and how to do it.
What you need:
- A Gorgias paid plan (any plan, AI Agent not required)
- An active subscription to Claude, ChatGPT, Cursor, or another MCP-compatible tool
Steps:
- Open your AI tool and navigate to its settings. Look for an Integrations, Connectors, or MCP section.
- Add a new MCP server using this endpoint: mcp.gorgias.com/mcp?gorgias_subdomain=YOUR-SUBDOMAIN. Replace YOUR-SUBDOMAIN with the part of your Gorgias URL that comes before .gorgias.com.
- Authorize the connection via OAuth. You will be prompted to log into your Gorgias account.
- Open a new chat and ask your first question.
The exact steps vary slightly depending on which AI tool you use.
Read more: The Gorgias MCP setup guide specifically walks through Claude, ChatGPT, and Cursor.
6 workflows to run in your first session
Each workflow below includes the exact prompt to copy. Adjust the specifics to match your store, and run it in your first session.
1. Find out why your CSAT dropped last month
CSAT dips are easy to spot in your dashboard. The cause is harder. Figuring it out usually means opening tickets one by one, building a custom filter, and reading through results one by one.
The prompt:
- "Show me all tickets from the last 30 days with a CSAT rating of 1 or 2. Group them by the most common themes and tell me what customers said."
What you get: A grouped breakdown of the patterns behind your low scores, based on what customers wrote.
Follow-up prompts:
- "Were any of these customers VIPs or high-order-value shoppers?"
- "Which agent handled the most tickets in this group?"
2. Audit your AI Agent handoffs and close the biggest gap
Handoff reports tell you how many tickets AI Agent escalated to your team. They rarely tell you why. Diagnosing the root cause and writing new guidance to fix it are usually two separate tasks that happen days apart, if at all.
With Gorgias MCP, you can do both in the same conversation.
The prompt:
- "Show me the last 50 tickets that AI Agent handed off to a human agent. What are the three most common reasons it couldn't resolve them?"
Then, without starting a new chat:
- "Draft a new AI Agent guidance to handle [the top reason from above]. Use the format of my existing guidances."
What you get: A diagnosis of where AI Agent is struggling and a ready-to-review draft guidance to address the top gap. You apply it manually in Gorgias, but the thinking is done.
Follow-up prompts:
- "Are these handoffs concentrated on a specific product category or ticket tag?"
- "How do these handoff reasons compare to last month?"
3. Map customer friction points to your product pages
This is one of the most powerful early use cases customers have found. By connecting Gorgias MCP with the Shopify MCP, you can link what customers complain about in tickets to the product pages where that friction lives.
To use this workflow, connect both Gorgias MCP and Shopify MCPoto your AI tool first.
The prompt:
- "What are the most common complaints or questions about [product name or category]? For each one, note whether the issue could be addressed by improving the product description, adding sizing information, or clarifying the return policy."
What you get: A prioritized list of friction points tied to specific content gaps on your product pages, ready to hand off to your product or merchandising team.
Follow-up prompts:
- "Which of these friction points appears most often in tickets tagged as returns?"
- "Are any of these issues specific to one variant or size?"
4. Get a custom ticket volume breakdown without building a report
Gorgias's built-in reports cover the core metrics well. But when you need a specific cut, ticket volume by intent for a particular channel, or resolution time broken down by tag, getting there requires an export and a spreadsheet.
Ask for exactly what you need instead.
The prompt:
- "Break down our ticket volume for the last 30 days by intent. Show me the top 10 intents, the volume for each, and the average resolution time per intent."
What you get: A custom breakdown you can copy directly into a slide or share with your team, built from a single question.
Follow-up prompts:
- "Which intent has the highest first-contact resolution rate?"
- "Compare this to the previous 30-day period. What changed the most?"
5. Find every topic your macros don't cover
Every support inbox has repeat questions that agents are still answering manually. Some of those topics may already have a macro, but others show up again and again without consistent macro usage. This workflow helps surface the best candidates to standardize next.
The prompt:
- Look at all tickets from the last 60 days. Which topics or questions appear most often, and for which of them do we see little or no macro usage? List the top 10.
What you get: A ranked list of frequent support topics that appear to be handled manually most of the time, helping your team prioritize where a new or better macro could save the most effort.
Follow-up prompts:
- Draft a macro response for the most common topic in that list.
- Which of these topics has the longest average first response time?
- Which of these topics already use macros sometimes, but not consistently?
6. Clean up your tag taxonomy
Tag libraries tend to grow organically. Over time, teams end up with overlapping labels like return, returns, and return-request, along with tags that are rarely used and naming patterns that make reporting harder to trust. This workflow helps identify cleanup opportunities based on how tags are actually used on tickets.
The prompt:
- Review the tags used on tickets in my Gorgias account. Flag any that appear to overlap in meaning, are used fewer than five times total, or seem inconsistent with the others. Group your suggestions by consolidation opportunity.
What you get: A list of likely tag issues grouped by type duplicates, low-use tags, and inconsistent naming based on actual ticket usage, with consolidation suggestions your team can act on.
Follow-up prompts:
- For the duplicates you flagged, which version is used more often? Thats the one Ill keep.
- Which of these low-use tags have appeared at all in the last 90 days?
- Which consolidation opportunities would have the biggest reporting impact?
Get more out of the data you already have
Everything in the workflows above is already sitting in your Gorgias account. Gorgias MCP just makes it conversational.
Not sure where to start? Try workflow 1 (CSAT drop report) or workflow 6 (tag cleanup) first. Both deliver results quickly and work regardless of how your account is configured.
Gorgias MCP is currently in open beta and available to all paid plan customers.
TL;DR:
- Gaia for Zendesk is a free Chrome extension that analyzes your Zendesk ticket history and identifies gaps in your AI Agent setup.
- It generates ready-to-review guidances, instructions, voice-of-customer analysis, and Copilot procedures nothing is applied without your approval.
- Install it in five minutes and run your first analysis in under a minute.
Getting more out of your Zendesk AI Agent comes down to better configuration. The problem is that auditing your own setup requires time you don't have.
Gaia for Zendesk is a free Chrome extension from Gorgias that clears that backlog in minutes. It connects to your Zendesk account, reads your tickets, and generates the components your AI Agent needs to resolve more conversations without escalation.
Below, you'll find everything you need to get started: how to install Gaia, what it can do, and the use cases teams are already putting it to work for.
Jump to:
- Who is this for?
- What is Gaia for Zendesk?
- Why use Gaia instead of configuring it yourself?
- How to install Gaia for Zendesk
- Four ways to use Gaia for Zendesk
Who is this for?
Zendesk Suite admins and agents who want to set up or improve their Zendesk AI Agent (and, optionally, Zendesk Copilot).
Throughout this article, "AI Agent" refers to Zendesk's own AI Agent feature, not Gorgias's product. Gaia is the Gorgias-built Chrome extension that helps you configure it.
What is Gaia for Zendesk?
Gaia for Zendesk is a free Chrome extension built by Gorgias that connects to your Zendesk account and analyzes your real ticket history.
It autonomously transforms that data into the core components your Zendesk AI Agent needs to resolve more tickets without human intervention: guidances, instructions, voice-of-customer insights, and Copilot procedures.
Gaia opens automatically as a side panel on any .zendesk.com page. You choose a workflow, Gaia runs the analysis and generates structured drafts, and you review and approve what should be applied to your Zendesk workspace.
What Gaia can do:
- Improve your Zendesk AI Agent: Scans escalated tickets, identifies gaps in your existing setup, and proposes targeted updates to your guidances.
- Create your first instructions: Generates 15 best-practice AI Agent instructions, adapted from Gorgias templates and tailored to your ticket data.
- Analyze your tickets: Produces a voice-of-customer report covering ticket volume, intents, and escalation patterns from the last 90 days.
- Create your first procedures: Drafts 10 Copilot procedures using the Gaia WHEN/IF/THEN format (requires the Copilot add-on in Zendesk).
Good to know: Gaia is autonomous in how it analyzes your data and generates recommendations, but nothing is applied without your approval.
Why use Gaia instead of configuring it yourself?
How well your AI Agent performs comes down to how well it is configured. Clear instructions, well-defined intents, and up-to-date procedures are what separate an AI Agent that resolves tickets from one that escalates them and building that foundation manually takes time most teams do not have.
Gaia removes that constraint by turning your existing support data into structured, ready-to-review outputs:
- Skip the blank page. Start from drafts generated from your own ticket history instead of building from scratch.
- Get from setup to first results faster. Gaia analyzes up to 90 days of tickets in minutes and produces implementation-ready content, so you move from setup to value in hours, not weeks.
- Stay in control. Every output is surfaced for review so you can validate accuracy and alignment with your policies.
- Keep improving over time. Re-run Gaia regularly to capture new intents, identify gaps, and maintain coverage as your business evolves.
Tip: Teams that define five or more strong guidances typically see a meaningful lift in the share of tickets their AI Agent resolves without escalation. Gaia is designed to help you reach and expand beyond that baseline quickly.
How to install Gaia for Zendesk
Installation takes about five minutes. You'll need admin access to your Zendesk account to generate an API token.
Make sure you're using Google Chrome or another Chromium-based browser (such as Edge or Brave). Gaia is not available for Safari or Firefox at launch.
Follow these steps:
1. Install the Gaia for Zendesk extension. Go to the Chrome Web Store listing for Gaia for Zendesk by Gorgias and click Add to Chrome. Confirm the permissions to complete installation.
2. Generate a Zendesk API token. In Zendesk, navigate to Admin Center Apps and integrations Zendesk API. Enable Token access if needed, then click Add API token. Copy and store the token securely (it will not be visible again).
3. Open the Gaia extension and add your credentials. Click the Gaia icon in your Chrome toolbar, then open Settings. Enter:
- Zendesk subdomain: the part before .zendesk.com in your account URL (for example, acme if your URL is acme.zendesk.com).
- Email: the email of the Zendesk admin who created the API token.
- API token: paste the token you generated in step 2.
4. Click Save. Gaia will validate the connection.
5. Open any Zendesk page. Navigate to any page in your Zendesk account. Gaia will appear as a side panel where you can select a workflow and begin.
Four ways to use Gaia for Zendesk
Here are the four most common ways teams use Gaia for Zendesk.
1) Audit and improve an existing AI Agent setup
Best for: Teams already using Zendesk AI Agent or Answer Bot but not reaching their automation goals
Select Improve my AI Agent. Gaia analyzes escalated tickets against your current guidances to identify missing intents, unclear instructions, and outdated logic, then proposes prioritized improvements.
2) Bootstrap AI Agent from a blank slate
Best for: Teams starting without an established AI configuration
Select Create my first instructions. Gaia generates a foundational set of 15 instructions covering common ecommerce scenarios (order status, refunds, cancellations, shipping, returns).
3) Run a voice-of-customer analysis
Best for: Support, CX, and operations teams planning improvements or reporting on performance
Select Analyze my tickets. Gaia summarizes ticket volume, top intents, and escalation drivers to highlight where automation or process improvements will have the greatest impact.
4) Roll out Copilot procedures
Best for: Teams using Zendesk Copilot who want consistent, scalable agent workflows
Requires the Copilot add-on in Zendesk. Select Create my first procedures. Gaia converts real agent behavior into structured WHEN/IF/THEN procedures that standardize how common scenarios are handled.
Your AI Agent is resolving less than it should and its costing you
Gaia connects to your Zendesk account, reads your ticket history, and shows you exactly where your setup is falling short. Install the free Chrome extension and run your first analysis in under a minute.
Newsletter Signup
The best in CX and ecommerce, right to your inbox
Featured articles
Ticket Volume: How to Measure It, Benchmark It, and Reduce It
TL;DR:
- Ticket volume is your support workload: It counts every customer inquiry across every channel in a given time period.
- High volume signals friction in your business: Spikes usually point to unclear policies, product issues, or gaps in your website experience.
- Every ticket has a real cost: Agent time, tooling, and overhead add up fast and they compound during peak seasons.
- Automation reduces volume without reducing quality: AI tools and self-service deflect repetitive questions while keeping customers satisfied.
- Measurement drives improvement: Tracking volume by channel, category, and time period reveals exactly where to focus your efforts.
Your ticket volume number is probably wrong. If customers are reaching you through email forwards, Slack DMs, or channels that bypass your helpdesk, those tickets aren't being counted, and your SLA reporting is built on incomplete data. This guide covers how to get an accurate count, break it down by channel and category, and use your vertical benchmark to figure out whether your volume is actually a problem or just normal for your industry.
What is ticket volume?
Ticket volume is the total number of customer inquiries your support team receives across all channels email, live chat, phone, social media, and contact forms within a specific time period. It is the most direct measure of your team's workload.
Do not confuse it with contact rate. Contact rate = tickets orders (or customers). That normalized number is more useful for benchmarking and planning because it accounts for business growth. Raw ticket volume tells you how busy your team is. Contact rate tells you whether support demand is outpacing your business.
How to calculate your ticket volume
Start by looking at the last 30 days of customer conversations, no matter where they currently live.
Pull these four numbers:
- Total customer questions received across all channels
- Breakdown by channel (email, chat, social DMs, phone, contact forms, etc.)
- Breakdown by category (shipping, returns, product questions, account issues)
- Tickets or conversations per order during the same period this gives you your contact rate baseline
Heres how to pull that data depending on your setup:
Gmail or Outlook
Open your inbox or Sent folder and filter by the last 30 days. Count how many customer conversations came in during that period. You can also copy subject lines into ChatGPT or Claude to group conversations by topic.
Shopify Inbox
Go to Inbox > Conversations and review your recent conversations. Count how many messages you received and look for repeated themes or questions.
Any helpdesk (Gorgias, Zendesk, Freshdesk, Help Scout, etc.)
Most helpdesks have ticket reporting or exports built in. Search export tickets or ticket report in your platforms help center. From there, you can pull:
- Total tickets
- Channel breakdown
- Top ticket categories
- Tickets over time
If a large portion of customer questions are still happening in untracked places like Slack DMs, personal inboxes, or Instagram comments, your reporting is incomplete. Before optimizing support operations, route customer conversations into one shared system so you can accurately measure volume, response times, and recurring issues.
Why your volume breakdown matters more than the total
A raw ticket count tells you how busy your team is. The breakdown tells you what to fix.
|
Category |
What high volume signals |
What to do |
|
"Where is my order?" |
No proactive shipping updates; poor tracking page |
Automate WISMO with AI Agent; add tracking link to order confirmation |
|
Returns and exchanges |
Confusing return policy; no self-serve portal |
Add a clear returns page; enable self-serve exchange flows |
|
Sizing and product questions |
Weak product page content |
Add size guides, FAQs, and fit notes directly on product pages |
|
Account and subscription issues |
Customers can't self-serve basic account changes |
Build or improve your Help Center; enable self-serve account management |
|
Payment and billing |
Checkout friction or unclear pricing |
Fix at the source this is rarely a support problem |
Run this categorization for your last 30 days. Your top two or three categories are your highest-leverage targets.
Track volume alongside these KPIs
Ticket volume only tells part of the story. Track it alongside:
- Contact rate (tickets orders) so you know if volume is growing faster than your business
- First response time (FRT) volume spikes show up here first
- Average handle time (AHT) high AHT + high volume = a capacity problem
- Cost per ticket total support costs total tickets, the clearest financial measure
- Backlog size a growing backlog is the earliest warning sign that volume is outpacing capacity
- Deflection rate tickets resolved through self-service or automation without agent involvement
How to reduce ticket volume without reducing quality
Once you know what is driving your volume, address each category at the source. The goal is to eliminate unnecessary tickets.
Automate the highest-volume, lowest-complexity tickets first. WISMO inquiries, order status checks, and basic return initiations require no agent judgment. An AI Agent connected to your ecommerce platform can handle these end-to-end without a human stepping in. When a question is too complex, the AI escalates it with full context attached.
Build self-service content around your top categories. A Help Center that directly addresses your most common ticket types is the highest-leverage tool for sustained volume reduction. Start with your top five categories. Write one article per category. Surface those articles on relevant product pages, in checkout, and in post-purchase emails before customers need to search.
Send proactive messages at the moments that generate the most tickets. Post-purchase is the single highest-value touchpoint: an order confirmation that includes a tracking link, estimated delivery window, and a clear link to your return policy eliminates a large share of inbound questions before they are ever submitted.
Measure deflection, not just volume. Deflection rate, the percentage of issues resolved through self-service or automation, is the metric that tells you whether your volume reduction efforts are actually working. Track it weekly alongside CSAT for automated interactions to make sure quality is holding.
Ticket volume benchmarks
The all-industry average is not your benchmark. Ticket volume per 100 orders varies 2.4x across verticals, so comparing yourself to a cross-industry number will either make you complacent or create false urgency.
According to Gorgias platform data from March 2026 across 14 verticals at the $10M GMV band, here is what tickets per 100 orders actually looks like by vertical:
|
Vertical |
Tickets per 100 orders |
|
Electronics |
46 |
|
Vehicles & Parts |
46 |
|
Hardware |
41 |
|
Luggage & Bags |
32 |
|
Home & Garden |
32 |
|
Sporting Goods |
32 |
|
Baby & Toddler |
24 |
|
Business & Industrial |
25 |
|
Animals & Pet Supplies |
25 |
|
Apparel & Accessories |
22 |
|
Health & Beauty |
21 |
|
Arts & Entertainment |
21 |
|
Food & Beverages |
20 |
|
Toys & Games |
19 |
Source: Gorgias Ecom Lab, March 2026
High ticket volume is not always a sign of poor CX it often reflects product complexity. Electronics brands generate nearly one ticket per two orders because customers have more pre- and post-purchase questions about technical products. Food and Beverage brands generate about one in five. That gap is not a performance difference; it is a category difference.
The right question is not "are we below 10 tickets per 100 orders?" It is "are we above or below our vertical peers?" Find your row. That is your baseline. Then use the reduction tactics above to move below it.
How to predict ticket volume if your tool charges per ticket
If your ticketing tool uses usage-based pricing, where your bill scales with ticket volume rather than agent headcount, forecasting volume directly affects your budget.
The core formula is simple:
Projected tickets = projected orders (tickets per 100 orders 100)
So if you expect 2,000 orders next month and your vertical median is 22 tickets per 100 orders, your forecast is approximately 440 tickets.
But a flat monthly estimate misses the real risk: peak seasons. A volume spike during BFCM that triples your order volume will also triple your ticket count and your bill unless you have guardrails in place.
To build a more accurate forecast:
- Use your contact rate, not raw volume. Divide your tickets by orders for each of the last 12 months. This gives you a stable ratio that accounts for business growth and seasonal swings.
- Apply that ratio to your order forecast. If your marketing team has a sales projection for November, multiply it by your contact rate to estimate support volume.
- Separate your AI-handled tickets from agent-handled tickets. Some platforms bill differently for automated resolutions versus human ones. If you're using an AI Agent to deflect WISMO and returns, those deflected tickets may not count toward your billable volume at all which changes the math significantly.
- Build in a buffer for peak periods. Your contact rate tends to rise during high-demand periods, not just your order volume. First-time customers generate more tickets than repeat buyers, and BFCM brings a disproportionate share of first-timers.
Before signing any usage-based contract, ask two questions: What counts as a billable ticket? And is there a hard cap on monthly charges? Variable billing only works in your favor if you have clear definitions of what triggers a charge and a ceiling on how high costs can go during an unexpected spike.
If your platform bills per ticket resolved by a human agent (not AI), your deflection rate becomes a financial metric, not just an operational one. Every percentage point of additional deflection directly reduces your bill.
Start reducing ticket volume today
Begin by identifying your top ticket categories, then work backward to find the root cause of each one.
From there, layer in self-service content, automation, and proactive messaging to address those root causes directly. The result is a support operation that handles more customers and a team that spends its time on the work that actually requires human judgment.
Book a demo to see how Gorgias helps ecommerce brands reduce ticket volume and improve customer experience at the same time.
{{lead-magnet-2}}
Gorgias AI Agent Pricing, Explained
TL;DR:
- AI Agent is priced per resolved interaction, not per seat or per message. You only pay when the AI fully resolves a conversation on its own.
- Most plans are $0.90 per resolved interaction. Starter plans begin at $1. Plans include 90 to 2,500+ automated interactions per month.
- If you go over your plan, overage fees apply per additional interaction. Rates vary by tier and are lower on annual plans.
- Your automation rate emerges from usage over time. Start by estimating your ticket volume and pick an interaction allotment that fits.
- AI Agent runs on email, chat, and SMS, and includes tone of voice customization, Actions, multi-language support, vision, and performance reporting.
If you're wondering what it costs to add AI Agent to your Helpdesk, you're in the right place. This article walks through how pricing works, what counts as a billable interaction, and how to think about the investment before talking to anyone on our team.
The good news: there are no seat fees, no per-message charges, and no token-based billing. You pay for conversations your AI actually resolves. If you've looked into other AI tools for customer support and found the pricing models confusing or hard to predict, Gorgias AI Agent works differently.
What is a billable interaction?
A billable interaction is counted when the AI resolves a customer conversation entirely on its own. The customer asks something, the AI handles it, the conversation closes. That's one interaction.
If the AI can't fully resolve a conversation and hands it to a human agent, that ticket shifts over to your regular Helpdesk plan. It becomes a standard resolved ticket. You're not charged for both.
A few things that don't count as billable interactions:
- Emails that come in but no one replies to
- Spam or filtered messages
- Conversations resolved by a human agent
This matters most for brands coming from seat-based tools. With Gorgias, your whole team can work in the platform. Agent seats are unlimited. Pricing scales with what your AI is actually doing, not with how many people have access.
Understand the difference between seat-based vs. usage-based pricing.
How AI Agent plans work
AI Agent is an add-on to your Gorgias Helpdesk plan. The two are priced separately but work together. Your Helpdesk plan covers all the conversations your human agents resolve. Your AI Agent plan covers the interactions the AI resolves on its own.
When you choose a plan, you select how many automated interactions you want included per month. Depending on your plan, that ranges from 90 to 2,500+ interactions, with custom interaction numbers available for enterprise. You can see the full breakdown on the Gorgias pricing page.
Each resolved conversation costs $0.90 on most plans. Starter plans begin at $1 per resolved conversation. You only pay for fully automated interactions, meaning conversations the AI handles from start to finish without a human stepping in.
Choosing the right plan
The main input is your average monthly ticket volume. From there, you estimate how many of those conversations AI could realistically handle on its own.
Order status updates, return requests, and shipping questions tend to be the highest-volume ticket types AI resolves well. AI Agent actions shows the full range of what it can handle, which makes it easier to estimate your starting number.
Your actual automation rate, meaning the share of total tickets the AI ends up resolving, emerges from usage over time. Most brands start with their most repetitive ticket types and expand from there as they see results.
Related: Which Gorgias plan should you choose?
What happens if you go over your plan
You're charged an overage fee for each additional automated interaction if you exceed your plan's baseline in a given month. The exact rate depends on your plan tier and whether you're on a monthly or annual subscription.
Generally, the higher your plan tier, the lower your overage rate. Annual plans also carry lower overage rates than monthly plans. So if you're regularly going over, upgrading to a higher tier or switching to annual often works out cheaper than paying overage fees month after month.
If you're on a Support + Shopping Assistant plan, the overage rate is $1.50 per interaction across all paid tiers. If you're on a Support-only plan, rates range from $1.00 to $2.00 per interaction on monthly plans, and $0.83 to $1.67 on annual plans, depending on your tier.
For seasonal businesses, forecasting your customer service volume before peak periods is the best way to choose the right plan size and avoid unexpected fees.
How to think about the cost
At $0.90 per resolved interaction on most plans, each AI resolution costs less than a human agent handling the same ticket. Once you know what a human-resolved ticket costs your business, the comparison becomes straightforward.
For brands building an internal case for the investment, how to pitch AI Agent to your boss covers the ROI framing in detail.
To see what results look like in practice, how 10 brands transformed customer support into revenue has real ecommerce examples.
What's included with AI Agent
AI Agent comes with everything you need to set it up, customize it, and improve it over time:
- Knowledge training AI Agent learns from your Shopify data, store website, Help Center articles, URLs, documents, and custom guidance. The more content it has, the more accurately it responds.
- Tone of voice set instructions for how AI Agent sounds, whether that's professional, friendly, or something else, and it stays consistent across every conversation.
- Actions connect AI Agent to your other tools so it can complete tasks like cancelling an order, processing a return, or modifying a subscription without a human stepping in. See what AI Agent can do.
- Multi-language support AI Agent detects the language a customer writes in and replies in the same language automatically.
- Vision AI Agent can read and understand images, so it can handle tickets where customers share photos of damaged items or order issues.
- Performance reporting track automation rate, CSAT, first-response time, and ticket topics directly in the dashboard.
- Testing preview how AI Agent responds to real customer questions before going live or after making changes.
- Handover to humans AI Agent automatically passes conversations to your team when it lacks confidence, detects frustration, or encounters a topic you've marked for human handling.
Learn more:Gorgias AI Agent guardrails: What they are and how to configure them
Curious what AI Agent would automate for your store?
The best way to get a sense of what AI Agent will cost is to look at your own ticket volume and the types of questions your customers ask most. From there, the right plan becomes much clearer.
If you want to talk through the numbers with someone from our team, book a demo and we'll walk through it with you.
If you'd rather keep exploring first, here are a few good next reads:
- AI Agent keeps getting smarter the latest performance data across the Gorgias customer base
- 10 must-know AI Agent use cases the ticket types brands are automating today
- How 10 brands transformed customer support into revenue real ecommerce results
- How to customize AI Agent with 7 brand voice examples what the experience looks like for customers
{{lead-magnet-2}}
Introducing Helpdesk 2.0: Built for How Agents Work
TL;DR:
- Built directly from agent feedback, Helpdesk 2.0 fixes real workflow pain points. The redesign focuses on reducing friction and helping agents handle more context-heavy tickets.
- A chat-style interface replaces the old email layout. Conversations are easier to follow and resolve in one view.
- Customer context is shown beside the conversation in a right-side panel. Agents can view history, orders, and details without leaving the ticket.
- AI handoffs come with clear summaries. Agents instantly see what happened, what was tried, and what to do next.
- Navigation is simpler and faster across teams. Clean menus, structured queues, and multi-store access keep agents moving efficiently.
Helpdesk 2.0 starts with the people who use it most: the agents.
We spent time understanding customer support from the agent's seat. What do they reach for constantly? What slows them down? What does a better workday look like?
Everything we found is in this brand-new update.
Why we redesigned Helpdesk
Conversational commerce is the new standard.
In customer support, this means customers expect context to remain intact wherever they reach out, whether a conversation starts on social, moves to email, or ends on a call.
This new approach to support has also changed the agent's role. Recurring tickets, like order status checks, shipping updates, and returns, are now handled by AI. What lands in the agent inbox are edge cases that require human judgment and troubleshooting, or tickets that require the full picture.
However, the original Helpdesk was built for a different era of support.
Context was separated across views rather than built into the conversation itself. It's something one in five Gorgias customers flagged, through support tickets, NPS surveys, and conversations with our team. So, we got to work.
Helpdesk 2.0 is the result.
What's new in Helpdesk 2.0
Here's a look at everything that changed.
Read conversations the way they're meant to be read
Conversations have a natural rhythm, one thats already found in every messaging tool we use. We brought that same layout into the helpdesk.
Say goodbye to the 2000s email interface and hello to chat bubbles. This updated design changes how quickly you can orient yourself and resolve the ticket in one go.
Chats with customers now look like real conversations, using the speech bubble style youre familiar with on popular messaging apps.
Check customer history without losing your place
Checking a customer's history used to mean leaving the conversation, an extra step that interrupted what should have been a smooth workflow.
Now, past conversations open in a sidebar next to the active conversation. You can view a customers full history, search through their timeline, and open prior tickets without going to a new page.
[The Customer Timeline allows you to scroll through past tickets, orders, and customer information.]Check past conversations, orders, and customer details in the brand-new Customer Timeline.
See order details the moment you open a ticket
Order information is easier to reference than ever. Open a ticket, and you instantly see the customer's recent orders, marked with product images and invoice details at a glance. Need to dig deeper? Click on an order, and the expanded information appears in the same panel.
For teams using custom integrations, apps are fixed in a quick-access integration menu on the right.
See order details, product images, and totals at a glance on the right panel, without leaving the conversation.
Pick up where AI left off
You shouldn't have to dig through a thread to figure out what AI already tried. Now you don't have to.
When AI Agent escalates a conversation, it includes a concise handover summary that mentions the issue, what actions were taken, and why it was passed to your team.
Escalated tickets include a brief AI-generated handover summary, marked in yellow, for quick reference.
Move faster across every store and team
We restructured and simplified the navigation. The left sidebar organizes everything into clear categories: Inbox, AI Agent, Marketing, and Analytics, so anyone on your team knows exactly where to go.
To quickly update your knowledge base or adjust a workflow, both now live right in the sidebar. For teams managing multiple stores, switching between them is just as straightforward, accessible from the sidebar, so agents can move between inboxes without breaking their flow.
Agents can switch between stores and their corresponding inboxes directly from the left menu.
A workspace that works the way agents do
Support comes down to the person on the other end of the conversation. We built Helpdesk 2.0 is to make sure they have everything they need to show up for that moment.
The best way to see the difference is to work in it. Start a free trial today.
Further reading
What Is an AI Copilot in Customer Service? (And How Gaia Rethinks It)
TL;DR
- An AI copilot in customer service (also called agent assist) is an AI that works next to a human agent: it drafts replies, summarizes the thread, and suggests next steps. A person still reviews and sends.
- The major CX copilots do the same core job. Intercom Copilot gives each agent "a personal AI assistant," Kustomer Envoy writes replies reps "review, edit, and send in seconds," and Gladly Team Assist drafts responses but "never sends on your behalf." Zendesk Copilot goes a step further with supervised actions under agent oversight.
- A copilot's ceiling is a faster human. Every drafted reply still reaches an agent, still requires human approval, and still counts as a ticket a person handled.
- Most copilots are a paid add-on on top of your platform: Intercom Copilot is $29 per agent/mo billed annually, $35 monthly; Zendesk Copilot is an add-on on top of a Suite seat.
- Gaia takes a different path. Gaia is the AI that coaches your AI Agent. Instead of making a human faster on a ticket, it finds where automation is missing and drafts the fix, so more tickets resolve with no human at all. Gaia is free during Open Beta, and you approve every change.
What is an AI copilot in customer service?
An AI copilot in customer service is an assistant that works alongside a human support agent inside the helpdesk. It reads the conversation and helps the agent respond faster: it drafts a reply, summarizes a long thread, pulls the right knowledge, and suggests the next step. The agent stays in control and sends the message. The industry term for this is agent assist.
That is the whole category in one line: a copilot points its intelligence at the person. It makes the human on the ticket quicker and more consistent. It does not resolve the ticket on its own, and it does not change how much your automation handles without a human.
Keep that distinction in mind, because it is the difference that matters when we get to Gaia.
What an AI copilot actually does
Strip away the branding and every CX copilot clusters around four jobs:
- Draft replies. The copilot writes a response grounded in your help center and past conversations. Intercom pitches "instant answers" from "your support materials, wherever they are." Kustomer Envoy "generates on-brand, accurate responses so reps can review, edit, and send in seconds."
- Summarize and catch up. It condenses a long or reassigned thread so the agent knows where things stand. Gladly Team Assist offers "Catch me up" and "Summarize this customer" out of the box.
- Surface context and next steps. It brings customer history, order data, and a recommended next action into the ticket. Kustomer Envoy surfaces "complete customer context" and "next best actions."
- Take supervised actions (some tools). A few copilots act, with the agent watching. Zendesk Copilot can trigger actions like updating fields and processing returns under agent oversight.
Copilots cut onboarding time, lower handle time, and keep tone consistent. If your goal is to help the agents you already staff move faster, a copilot earns its keep.
The copilot ceiling: it makes the human faster, not the AI better
Here is the catch. A copilot removes keystrokes, not tickets.
Every reply a copilot drafts still lands in front of a person who reads it, edits it, and hits send. That ticket still reaches an agent and consumes handle time. You are typing faster, but you are still staffing for the same volume. When your automation rate plateaus, a copilot does nothing to lift it, because a copilot was never pointed at the automation. It was pointed at the human.
That is the ceiling of agent assist: the best case is a faster team, not a smaller queue.
The major CX copilots, compared
A few call-outs:
- Zendesk does more than draft. Its Copilot takes supervised actions, so if you want the copilot to act inside the ticket, it is ahead of a draft-only tool. The action still happens with a human in the loop.
- Kustomer bundles it in. Envoy now ships inside Kustomer's higher tiers, which takes the "you pay extra for the copilot" objection off the table.
- Gladly is explicit about the boundary. "Team Assist never sends on your behalf" sums up the whole category: the AI drafts, the human sends.
Comparing Gorgias to a specific one? See our head-to-head pages for Zendesk, Intercom, Kustomer, and Gladly.
A different approach: Gaia, the AI that coaches your AI Agent
At Gorgias, we took a different bet. Instead of a copilot to make agents faster, we built Gaia: an AI coaching engine that makes your AI Agent better.
The AI Agent is the part of Gorgias that resolves tickets on its own, in two roles: a Shopping Assistant before the sale and a Support Agent after it. Gaia sits above it with one job: keep raising how much the AI Agent resolves without a human.
How Gaia works, in plain terms:
- It reads your real ticket data. Gaia analyzes your conversations, skills, knowledge, and actions to find where automation breaks down: recurring requests you are not covering, unnecessary escalations, and knowledge gaps.
- It is proactive, not on-demand. A copilot waits until an agent opens a ticket. Gaia surfaces what is missing across your AI Agent setup before it costs another month of handle time, and runs one-click audits.
- It drafts the fix. Gaia does not hand you a to-do list. It recommends or generates new Skills and Actions for you to review.
- You stay in control. Every change Gaia proposes needs your explicit approval before it goes live.
The one-line version: a copilot helps people do the work, while Gaia helps your AI Agent do the work better over time.
Gaia completely transformed how we manage our knowledge base. We had it audit our existing content. It flagged duplications and identified missing information. Within minutes it generated a detailed, ready to use draft. All I had to do was review, test, and click publish.
Nicole Parker, Senior Manager of Customer Service at Bare Necessities and PJ Salvage
Copilot vs coaching engine: the real difference
Making a human faster is linear: you save seconds per ticket and still staff for every ticket. Making your AI Agent better compounds: every coaching pass lifts resolution, so the queue shrinks instead of the clock.
Which one is right for you?
Be honest about the job you are hiring for.
- If your priority is helping the agents you already have move faster on the tickets that reach them, a copilot is a reasonable buy. Agent assist has a real place, and it is somewhere Gorgias will go too.
- If your priority is resolving more with no human touch, a copilot will not get you there, because it never touches the automation. Coach the AI that resolves tickets, not the person cleaning up after it.
A copilot helps your team clear the queue. Gaia is built to shrink it.
Try Gaia free in Open Beta or book a Gorgias demo to see AI Agent and Gaia together.
7 CRO A/B Tests to Reduce Customer Support Tickets
Most ecommerce brands treat customer support as a post-purchase problem. It isn't. Plenty of tickets are written long before checkout the moment a shopper can't find an answer, second-guesses the price, or doesn't trust what they're looking at.
At Blend Commerce, we see the same pattern again and again: when a product page answers buyer questions clearly, conversion goes up and support tickets go down.
This article breaks down seven conversion rate optimization (CRO) A/B tests you can run to head off support tickets before they happen built on real buyer psychology, hands-on testing, and patterns we see across high-performing Shopify stores.
TL;DR
If your product pages answer these six buyer questions:
- Will it fix my problem?
- Is it worth the price?
- Do other people love it?
- What's my risk if it flops?
- How long will it take to arrive?
- Can I get help fast?
You'll get:
- Fewer pre-purchase tickets
- More confident buyers
- Stronger conversion rates
- Less pressure on your Gorgias inbox
The tests below show you how.
Download: The Anatomy of the Perfect Product Page
Why most customer support tickets start on the product page
Before we jump into the tests, its important to understand why users contact support in the first place.
More tickets happen because users:
- Cant find key information
- Want reassurance before buying
- Dont trust pricing or value
- Are unsure about delivery or returns
- Need confirmation that help exists if something goes wron
Every one of these reasons maps directly back to unanswered buyer questions on the PDP. Thats where Conversion Rate Optimisation comes in.
The 6 buyer questions that drive support tickets and conversion
Most Where do I find? or Can you confirm? tickets dont start in support. They start on the product page when something important isnt clear enough.
Customers dont consciously think, I have a buyer question. They feel uncertainty. That hesitation is what slows conversion and drives reassurance tickets.
These six buyer questions represent the friction points your PDP must resolve:
1. Will it fix my problem?
If the outcome isnt obvious within a few seconds, users wont keep digging; they either bounce or ask support to confirm it will work for them. This is especially true when users have edge cases like compatibility, sizing, and will this work for X? Strong benefit-first messaging and visible proof mean customers dont need to double-check with your team before they buy. The page answers the question for them.
2. Is it worth the price?
Price objections rarely show up as this is too expensive in a ticket. They show up as:
- Can I get a discount?
- Is there a cheaper version?
- Why is this priced like this?
When the value isnt clearly framed, users either abandon it or look for a human to justify the price. The right CRO elements make the value feel settled before the user has time to second-guess.
3. Do other people love it?
This is the reassurance question. When social proof is thin, generic, or hard to find, users seek confidence externally, often through support. Reviews, UGC, and people like me proof stop tickets like Which one should I choose? because the crowd does the persuading.
4. Whats my risk if it flops?
Risk is the silent conversion killer and a sneaky support-driver. If returns, exchanges, warranty, or guarantees arent clear, users ask preemptive what if questions to protect themselves. When you remove ambiguity around outcomes, you reduce tickets that exist purely to manage fear.
5. How long will it take to arrive?
Shipping ambiguity drives high-volume WISMO-style (where is my order) questions before purchase, not only after. If users cant quickly find delivery cost, ETA, cutoffs, and tracking expectations, theyll ask (or leave). Clear ETA messaging reduces tickets by removing the need for can you confirm delivery to my area by X date?
6. Can I get help fast?
Even confident users hesitate if they fear being stranded after checkout. Visible support options and expectations (how to reach you, response times, self-serve help) reduce last-mile tickets and increase conversion because users feel protected.
Lets look at the A/B tests that directly reduce support tickets by answering these questions proactively.
7 CRO A/B tests that reduce customer support tickets
1. Add product page accordions to answer key buyer questions
Buyer questions addressed:
- 1. Will it fix my problem?
- 5. How long will it take to arrive?
- 6. Can I get help fast?
Why this CRO test reduces support tickets
Users often contact support because they cannot quickly locate delivery timelines, warranty details, return policies, compatibility information, or usage instructions. When key information is buried within long product descriptions, customers escalate to chat for reassurance before committing to purchase.
Introducing structured accordion sections brings clarity to the PDP, allowing shoppers to self-serve answers instantly without leaving the page or interrupting their buying journey.
Data signals that indicate this test is needed
- Support data signal: A high volume of pre-purchase tickets related to shipping, returns, product details, or compatibility questions.
- Behavioural signal: Repeated scrolling around policy content, frequent FAQ page visits, or heatmap friction near dense information blocks.
- Conversion signal: A strong Add to Cart Rate paired with a noticeable drop-off before checkout progression.
- Qualitative signal: Customer phrases such as I couldnt find or Just checking before I buy appear consistently in chats.
- Action trigger: When clarification-based questions make up 1520% or more of pre-purchase conversations, this test is typically high impact.
When these signals appear together, testing clearly labelled accordion menus on the product page (for example, Shipping, Returns, How It Works, and FAQs) allows users to self-serve the information they need without leaving the PDP.
What to include in your A/B test:
- Accordion layout vs long-form static content
- Shipping and returns information is positioned higher versus lower on the page
- Question-based section titles (e.g. How long will delivery take?) versus generic headings
Expected impact on support and conversion
- Reduction in clarification-based support tickets
- Improved mobile usability and scannability
- Lower PDP bounce rate
- Increased checkout progression
Real-life example & test results
In this case, support data and on-site behaviour revealed that customers were struggling to locate key product information on the PDP. Heatmaps showed repeated scrolling and hesitation around dense product descriptions, while competitor analysis highlighted a clearer accordion-based structure that made answers easier to access.
To test whether clarity was the issue, we introduced a structured accordion menu that grouped critical information such as delivery, returns, and product details into clearly labelled, expandable sections. Instead of forcing users to scan long blocks of text, the updated layout allowed them to quickly self-serve the information they needed.
The results were significant. The variant delivered a +15.21% increase in Conversion Rate, a +6% increase in Add to Cart clicks, a +7.33% increase in Checkout visits, and a +22% increase in average session duration compared to the control.
The behavioural insight was clear: when information becomes easier to find, hesitation decreases. Users engaged more confidently with the page and were less reliant on support to clarify basic product details.
See the full A/B test breakdown here.
2. Test per-unit pricing to reduce pricing confusion
Buyer questions addressed:
- 2. Is it worth the price?
Why this CRO test reduces support tickets
Users frequently contact support to request discounts, verify pricing fairness, or clarify the total cost of the product over time. When only a total price is displayed, it can trigger immediate sticker shock, especially for higher-priced or subscription-based products.
Introducing per-unit or per-dose pricing reframes the decision. Instead of focusing on the total outlay, shoppers evaluate affordability in smaller, more digestible increments, such as price per day or per use. This reduces uncertainty and lowers the likelihood of pre-purchase pricing clarification tickets.
Data signals that indicate this test is needed
- Support data signal: Frequent pre-purchase tickets asking about discounts, promo codes, or pricing breakdowns.
- Behavioural signal: High product page engagement paired with a low Add to Cart Rate.
- Conversion signal: Weak subscription uptake, low Revenue per Visitor, or high drop-off after pricing exposure.
- Qualitative signal: Customer phrases such as Do you offer promo codes? or Why is this so expensive? appear consistently in chats.
- Action trigger: A noticeable increase in discount-related queries or subscription selection falling below category benchmarks.
When these patterns appear together, testing alternative pricing communication formats helps shoppers assess affordability instantly and reduces the need for reassurance from support.
What to include in your A/B test:
- Displaying price per dose alongside total price versus total price alone
- Pricing badges near the CTA versus explanatory copy below the Add to Cart button
- Price-per-day framing versus monthly cost framing
- Clear subscription savings callouts versus no explicit savings messaging
Expected impact on support and conversion
- Reduction in pricing clarification tickets
- Increased subscription opt-in
- Lower cart abandonment
- Higher Revenue per Visitor
Real-life example & test results
Support data and on-site behaviour revealed consistent pricing confusion on subscription PDPs. Customers were engaging heavily with pricing sections but hesitating before adding to cart, while support teams were fielding frequent discount and pricing clarification queries. The pattern suggested that shoppers were uncertain about the true cost of committing to a subscription.
To test whether clarity was the issue, we updated the PDP to display price per dose alongside the total price. Rather than presenting a single lump-sum figure, the revised layout introduced a clear $X per dose line directly beneath the headline price, aligning pricing communication with how customers naturally think about product usage and affordability.
The results were measurable. The variant delivered a +5.55% increase in Conversion Rate, a +8.53% increase in Add to Cart Rate, and a +6.46% increase in sessions reaching checkout compared to the original layout.
The behavioural insight was clear: when pricing is reframed in smaller, contextual increments, shoppers assess affordability faster and with more confidence. Reducing cognitive friction around cost lowered hesitation and reduced the need for customers to contact support to validate pricing or perceived value.
3. Use reviews to reduce choice paralysis and support questions
Buyer question addressed:
- 3. Do other people love it?
Why this CRO test reduces support tickets
Customers frequently contact support not because something is broken, but because they are unsure which product to choose. When browsing a category with multiple similar SKUs, the absence of visible social proof forces shoppers to seek human reassurance before committing.
Displaying star ratings and review indicators directly on collection pages introduces trust earlier in the journey. Instead of waiting for the PDP to validate popularity or satisfaction, customers can quickly identify which products are favoured by others, accelerating decision-making and reducing comparison-based support tickets. Visible ratings reduce cognitive load by signalling popularity at a glance, preventing shoppers from over-analysing similar options.
Data signals that indicate this test is needed
- Support data signal: Frequent pre-purchase tickets asking Which product is best? or requesting help choosing between similar options.
- Behavioural signal: High comparison behaviour between similar SKUs, including repeated back-and-forth navigation between PDPs.
- Conversion signal: Low collection-to-PDP click-through rate or heavy traffic to Best Sellers and Popular filters.
- Qualitative signal: Customer phrases such as What do most people buy? or Which one do you recommend? appear consistently in chats.
- Action trigger: A broad product range with limited visible differentiation or unclear popularity indicators.
When these signals appear together, testing the visibility of reviews at the collection level, rather than limiting them to PDPs, helps customers make faster, more confident decisions without needing human reassurance.
What to include in your A/B test:
- Displaying star ratings on collection cards versus no visible ratings
- Adding Customer Favourite or Top Rated badges versus a neutral presentation
- Showing review count alone versus including short rating snippets
Expected impact on support and conversion
- Reduction in comparison-based support tickets
- Faster product selection and decision confidence
- Increased collection-to-PDP click-through rate
Real-life example & test results
During a CRO audit, we identified that product reviews were not visible on collection pages, leaving shoppers without immediate confidence signals while browsing. In a category where trust and product credibility heavily influence purchasing decisions, this absence contributed to choice overload and hesitation before users even reached a PDP.
To test whether earlier visibility of social proof would reduce friction, we added star ratings and review counts directly to product cards on the collection page. Instead of requiring users to click into individual products to validate quality, the updated layout made ratings instantly visible at a glance, allowing shoppers to compare options more efficiently.
The impact was substantial. The experiment delivered a +23.2% increase in overall Conversion Rate and a +73.5% increase in Average Order Value across devices. Mobile performance was particularly strong, with a +69.9% increase in mobile Conversion and a +331.4% increase in mobile Revenue per Visitor compared to the control.
The behavioural insight was clear: surfacing social proof earlier in the browsing journey reduced cognitive friction and strengthened purchase confidence. When users could quickly identify highly rated products, they were more comfortable selecting multiple or higher-value items without seeking additional reassurance from support.
4. Highlight subscription benefits to reduce hesitation and support tickets
Buyer questions addressed:
- 2. Is it worth the price?
- 4. Whats my risk if it flops?
Why this CRO test reduces support tickets
Subscription hesitation is rarely about price alone. It is often driven by uncertainty around cancellation terms, pause or skip flexibility, and the perceived commitment involved. When these concerns are not addressed clearly at the point of selection, customers escalate to support to confirm their risk before proceeding.
Making subscription benefits and flexibility visible near the CTA reduces perceived commitment anxiety. Clear reassurance, such as Cancel anytime or Pause or skip at any time, lowers friction and removes the need for pre-purchase clarification tickets.
Reducing perceived commitment risk is often more impactful than increasing discount incentives, because customers fear being locked in more than they value small savings.
Data signals that indicate this test is needed
- Support data signal: Frequent pre-purchase tickets asking about cancellation policies, pausing options, delivery frequency, or subscription terms.
- Behavioural signal: High interaction with subscription selectors but low subscription uptake.
- Conversion signal: A strong skew toward one-time purchases despite competitive subscription incentives.
- Qualitative signal: Recurring customer phrases such as Can I cancel anytime? or Am I locked in?
- Action trigger: Low recurring revenue growth or subscription churn exceeding internal benchmarks.
When these patterns appear together, testing clearer subscription benefit messaging near the CTA helps remove commitment uncertainty before it becomes a support interaction.
What to include in your A/B test:
- Adding Cancel anytime or Pause or skip anytime reassurance near the subscription selector versus no visible flexibility messaging
- Displaying clear subscription benefit bullet points versus a standard toggle-only layout
- Embedding a short FAQ snippet near the selector versus requiring users to navigate elsewhere for policy details
Expected impact on Ssupport and conversion
- Increased subscription opt-in rate
- Reduction in reassurance-based support tickets
- Higher recurring revenue contribution
Real-life example & test results
In this case, subscription uptake was underperforming despite strong product interest and healthy PDP engagement. Support data revealed recurring pre-purchase questions about cancellation flexibility, pausing options, and perceived commitment risk. Churn levels also suggested that customers were either unclear about the terms at sign-up or hesitant to commit without reassurance.
To test whether clarity and risk framing were limiting adoption, we redesigned the subscription selector and surrounding PDP messaging. The revised layout made flexibility more explicit, highlighting benefits such as convenience and savings alongside clear reassurance copy like Skip, Pause, or Cancel Anytime. Instead of burying subscription details near the pricing block, the variation positioned flexibility messaging directly next to the selector so customers could evaluate value and risk instantly.
The result was a +32% increase in Subscription Orders per Visitor compared to the control, demonstrating that clearer communication of flexibility significantly improved subscription adoption.
The behavioural insight was consistent with risk psychology: when perceived commitment risk is reduced, customers are more willing to opt into recurring purchases. By addressing uncertainty at the point of decision, the test reduced hesitation and lowered the need for pre-purchase clarification from support, while simultaneously increasing recurring revenue.
5. Improve mobile navigation to reduce support queries
Buyer questions addressed:
- 5. How long will it take to arrive?
- 6. Can I get help fast?
Why this CRO test reduces support tickets
Mobile navigation friction often manifests as support tickets rather than immediate drop-offs. When key areas such as gift cards, shipping policies, returns information, or Help pages are difficult to locate on smaller screens, customers turn to chat as a shortcut.
On mobile, navigation clarity directly influences trust. If users struggle to find policy details or brand information quickly, support becomes the fallback mechanism for reassurance. Improving menu visibility and structure reduces this dependency by making essential information accessible within seconds. On mobile, clarity signals legitimacy. When navigation feels intuitive, brand trust increases before the user even reaches a product page.
Data signals that indicate this test is needed
- Support data signal: Frequent Where can I find? tickets related to policies, gift cards, or Help pages.
- Behavioural signal: High mobile bounce rate or repeated navigation attempts within the menu.
- Conversion signal: A significant mobile versus desktop Conversion Rate gap not explained by traffic quality.
- Qualitative signal: Customer feedback referencing difficulty navigating or locating information on mobile.
- Action trigger: Mobile traffic accounts for the majority of sessions (often 60%+), amplifying the impact of navigation friction.
When these patterns appear together, testing a more visual and accessible mobile navigation structure improves information discovery and reduces reassurance-based support queries during browsing.
What to include in your A/B test:
- Visual category tiles versus text-only navigation
- Increased visibility of Help, About, and policy links within the primary menu
- Reordering categories based on purchase intent and traffic behaviour
Expected impact on support and conversion
- Reduction in navigation-related support tickets
- Higher mobile engagement across the browsing funnel
- Improved mobile Conversion Rate
Real-life example & test results
Analysis of site analytics revealed that mobile users were converting at a significantly lower rate than desktop users, despite comparable traffic quality. Session recordings and heatmaps highlighted repeated menu interactions, back-and-forth navigation, and shallow browsing depth, indicating friction in the mobile experience. Support tickets further reinforced the issue, with customers frequently asking where to find gift cards, return policies, and help resources on mobile.
To address this, we redesigned the mobile navigation into a more intuitive, visually structured menu that prominently surfaced key categories, Help & Policies, and support links. Rather than relying on a text-heavy, deeply nested structure, the revised version introduced a clearer hierarchy with icon-supported navigation and essential links positioned at the top of the menu.
The redesign delivered meaningful impact, including a +18% increase in Conversion Rate, a +28% increase in Revenue per Visitor, an +8% increase in Average Order Value, and a +6% increase in Subscription Revenue per Visitor compared to the original experience.
The behavioural insight was clear: when navigation becomes frictionless, product discovery expands. The visually led structure helped users find critical information faster while also exposing them to more categories. Improved clarity not only reduced reliance on support but also increased basket depth and subscription engagement, demonstrating that navigation structure directly influences both conversion performance and revenue growth.
6. Highlight reviews that answer common buyer questions
Buyer question addressed:
- 3. Do other people love it?
Why this CRO test reduces support tickets
Even when social proof is present, users often scan reviews for specific reassurance: Does it work? Will it arrive quickly? Is it easy to use? When these answers are buried deep within long review feeds, customers turn to support for direct confirmation before purchasing.
Customers rarely read every review. They scan for proof that someone like them has achieved the outcome they want.
Highlighting reviews that explicitly address common objections brings reassurance closer to the decision point. By surfacing objection-resolving testimonials near the CTA or product title, you reduce uncertainty and limit the need for live clarification.
Data signals that indicate this test is needed
- Support data signal: Frequent reassurance-based chats asking about results, delivery times, or suitability.
- Behavioural signal: High scroll depth within review sections before Add to Cart interaction.
- Conversion signal: Noticeable drop-off after users engage heavily with reviews.
- Qualitative signal: Recurring phrases such as Has this worked for someone like me? or Is it easy to use?
- Action trigger: A strong review base, but low Add to Cart conversion relative to traffic volume.
When these signals appear together, curating and positioning objection-resolving reviews closer to the decision point reduces uncertainty and limits the need for pre-purchase reassurance from support.
What to include in your A/B test:
- Pinning an objection-answering review near the CTA or product title versus leaving reviews in chronological order
- Adding a Most Helpful Review badge versus a neutral presentation
- Displaying a short before-and-after or results-focused snippet above the fold versus relying on full review feeds
Expected impact on support and conversion
- Reduction in reassurance-based support tickets
- Increased Add to Cart Rate
- Higher Revenue per Visitor
Real-life example & test results
Site analytics and session recordings revealed that users were spending significant time within the review section but progressing weakly from reviews to Add to Cart. Heatmaps showed extensive scrolling behaviour, suggesting that shoppers were actively searching for reassurance before committing. The pattern indicated that social proof existed, but it was not positioned effectively within the decision-making flow. Users were not lacking proof; they were lacking proximity to proof.
To test whether placement was the issue, we pinned a highly relevant, objection-resolving review near the CTA. Instead of requiring users to scroll deep into the PDP to validate product effectiveness, the revised layout surfaced a strong use-case testimonial at the point of decision.
The variant delivered a +11.11% increase in Conversion Rate, a +6.48% increase in Add to Cart Rate, a +6.76% increase in Checkout Visit Rate, and a +2.78% increase in Average Session Duration compared to the control.
The behavioural insight was clear: when relevant social proof is integrated directly into the purchase decision area, hesitation decreases. Highlighting a trusted, outcome-focused review near the CTA transformed passive proof into an active confidence driver, reducing the need for reassurance-based support conversations.
Test homepage value messaging to reduce early-stage support questions
Buyer questions addressed:
- 3. Do other people love it?
- 4. Whats my risk if it flops?
- 5. How long will it take to arrive?
Why this CRO test reduces support tickets
Support tickets often originate before users ever reach a product page. When first-time visitors arrive on a homepage without immediately seeing shipping clarity, return guarantees, or support accessibility, uncertainty forms early in the journey.
If trust signals and risk-reduction messaging are not visible above the fold, customers either abandon or seek reassurance via chat. Addressing these concerns at the homepage level reduces early-stage hesitation and limits reassurance-based support interactions before product exploration even begins.
Early clarity compounds. When risk and legitimacy are established upfront, subsequent pages perform better.
Data signals that indicate this test is needed
- Support data signal: Frequent reassurance tickets from first-time visitors questioning legitimacy, delivery, or return policies.
- Behavioural signal: High homepage bounce rate or shallow session depth from new traffic.
- Conversion signal: Lower Conversion Rate from new visitors compared to returning users.
- Qualitative signal: Customer phrases such as Is this brand legit? or Whats your return policy? appear early in conversations.
- Action trigger: High volume of paid traffic acquisition without strong above-the-fold trust messaging.
When these signals appear together, testing clearer value propositions above the fold, including shipping, returns, and support availability, reduces early-stage doubt and strengthens trust before users navigate deeper into the site.
What to include in your A/B test:
- Displaying trust badges above the fold versus no visible trust reinforcement
- Featuring shipping and returns messaging within the hero section, versus burying it lower on the page
- Including a visible support availability statement versus requiring users to locate contact details elsewhere
Expected impact on support and conversion
- Reduction in early-stage reassurance tickets
- Increased trust among first-time visitors
- Higher first-session Conversion Rate
Real-life example & test results
During a CRO audit, we identified that the homepage lacked clear, above-the-fold value propositions such as shipping benefits, guarantees, and brand differentiators. For first-time visitors, particularly those arriving from paid traffic, this created an immediate trust gap. Users were being asked to explore the site more deeply before understanding what made the brand credible or distinct.
To test the impact of clearer positioning, we introduced two banner variations on the homepage.
Variant 1 emphasised broad, trust-based corporate messaging, while Variant 2 featured a more product-led value proposition strip positioned prominently near the top of the homepage. The goal was to determine whether specific, tangible differentiation would outperform general reassurance messaging.
Before-and-after homepage comparison for a coffee retailer. The redesigned version introduces clearer, benefit-focused value propositions highlighting freshness, roast timing, and shipping speed, helping new visitors understand the brands key differentiators at a glance.
The results favoured clarity and specificity. Variant 2 delivered a +3% increase in Conversion Rate, a +5% increase in Revenue per Visitor, and a +18% increase in Subscription Revenue per Visitor compared to the original experience.
The behavioural insight was revealing: visitors responded more strongly to concrete product differentiation than to generic trust statements. When the homepage immediately communicated what made the product distinct and valuable, early-stage doubt decreased, and purchase confidence increased, without increasing reliance on support for validation.
Bonus tip: Use intent-based chat triggers to reduce low-quality support tickets
Instead of showing chat to everyone, test triggering Gorgias chat based on intent signals such as high cart value, high page depth, and known friction pages. This ensures the chat supports high-intent users without encouraging unnecessary tickets.
How CRO and Gorgias work together to reduce support tickets
Most teams use CRO to increase conversion and Gorgias to handle tickets. In reality, they are solving the same underlying problem: buyer hesitation. The best-performing brands connect them into one loop:
CRO prevents avoidable customer support tickets
A large chunk of your ticket volume is avoidable because its caused by missing clarity, not genuine support needs (pricing confusion, shipping uncertainty, basic product usage questions, reassurance). Your own A/B test list spells this out clearly: users contact support when they need missing information, trust, promo help, or confirmation that support exists.
When CRO closes those clarity gaps, Gorgias becomes more powerful because your agents spend more time on higher-value conversations rather than repeating the same answers.
Better self-serve content improves resolution time and conversion
Gorgias is basically a live feed of customer friction. The fastest way to build a high-impact CRO roadmap is to pull patterns from top ticket tags, most-used macros, and chat transcripts where users hesitate right before purchase. Those themes map almost perfectly to the 6 buyer questions and tell you which part of the PDP is causing confidence to leak.
How better self-serve content improves resolution time and conversion
When you add clearer answers on-site, like FAQs and policies, youre not only reducing tickets, but also making the tickets that still occur easier to solve because customers arrive in chat already educated. This creates shorter conversations, higher CSAT (Customer Satisfaction Score), and fewer back-and-forth messages.
Intent-based targeting turns support into a conversion tool
When CRO reduces low-intent confusion, you can reserve live chat for moments that genuinely drive conversion. This is where CRO + Gorgias becomes a revenue lever: your chat doesnt become a crutch for unclear pages, it becomes a precision assist for high-intent buyers.
The outcome: fewer tickets, better conversations
When these two work together, you dont just reduce ticket volume. You improve ticket quality and increase revenue efficiency across the funnel.
Fix the questions before they become tickets
Most support tickets do not start inside Gorgias. They start earlier, when shoppers cannot find information, feel uncertain, or need reassurance before they buy. When your site answers the six core buyer questions clearly, conversion improves, pre-purchase tickets decline, support conversations become shorter, and customers move forward with greater confidence.
The fastest way to identify where this is happening on your site is to connect CRO analysis with your support data. Patterns in ticket tags, chat transcripts, and recurring customer questions provide a powerful signal for where clarity gaps exist and which tests will have the greatest impact.
If you want a structured framework to audit your product pages against these buyer questions, we have created a free resource that breaks down the exact elements high-performing PDPs use to reduce hesitation and support volume.
Conversations Are Becoming a Revenue Channel: The Data Proves It
TL;DR:
- Customer journeys are collapsing to a single conversation. The traditional browse-and-buy journey is giving way to AI-guided shopping that moves from discovery to purchase in a single exchange.
- 79% of brands say AI-driven conversational commerce has increased their sales and purchase rates.
- AI-only influenced orders grew 63% in a single year, from 2.7 million in Q1 to 4.4 million in Q4.
- Brands treating conversation as a revenue channel. Theyre not just a support function, generating higher AOV, shorter buying cycles, and stronger retention.
The page-based shopping experience dominated for decades. Customers would search, browse, compare, abandon, get retargeted, return, and eventually buy (sometimes).
That journey is no longer the only option.
Shoppers are turning to chat, messaging, and AI-powered tools to find what they need. Instead of clicking through product pages or reading static FAQs, they ask questions, have back-and-forth conversations, and get answers that move them closer to a purchase in real time. The path to checkout has changed, and the brands that recognize this are pulling ahead.
Read our 2026 State of Conversational Commerce Report to learn more about conversation commerce trends from 400 ecommerce decision-makers and 16,000+ ecommerce brands using Gorgias.
{{lead-magnet-1}}
The shopping journey has collapsed into a single thread
The traditional shopping journey was a solo experience. A shopper had a need, searched for options, browsed across sessions, and eventually made a decision often days later, after being retargeted multiple times. Support only entered the picture after the purchase.
The conversation-led journey collapses that timeline:
- A shopper recognizes a need and starts a conversation via chat, messaging, or a search-triggered prompt
- An AI agent asks clarifying questions about preferences, budget, and constraints
- The AI provides personalized product recommendations in real time
- The shopper validates concerns about fit, compatibility, delivery, and returns, all inside the conversation
- The shopper completes the purchase directly within or immediately after that exchange
- The AI picks up the conversation post-purchase for order tracking and proactive support
- A human agent steps in only when the situation calls for it
What used to take days now takes minutes. Discovery, evaluation, and purchase happen in a single thread.
Conversation is a revenue strategy, not a support upgrade
79% of brands agree that AI-driven conversational commerce has increased sales and purchase rates in their business. When brands were asked to rank the highest-return areas:
- 38% cited improved customer support efficiency
- 23% pointed to higher customer retention and loyalty
- 20% saw improved purchase rates
Those numbers reflect something important: the value of conversation compounds. Faster support reduces friction. Better retention raises lifetime value. More confident shoppers buy more often and spend more per order.
The brands seeing the biggest returns aren't just using AI to deflect tickets. They're using it to create one-to-one shopping experiences at scale.
What the data shows about AI-influenced orders
Looking at AI-only influenced orders across key verticals like Apparel and Accessories, Food and Beverages, Health and Beauty, Home and Garden, and Sporting Goods, the growth across a single year was significant.
Across industries, ecommerce brands saw AI step into conversations, reduce shopper hesitation, and drive higher QoQ conversion rates.
Learn more about AI-powered revenue generation in the full 2026 Conversational Commerce Report.
Why brands are making this a strategic priority
84% of brands say the strategic importance of conversational commerce is higher than it was a year ago. 82% agree it will be mainstream in their sector within two years.
That shift is registering at the leadership level because of what conversational commerce does to the buying experience. Creating one-to-one touchpoints earlier in the journey drives higher AOV, shorter buying cycles, and stronger purchase rates. Shoppers who get real-time answers to their questions are more confident.
What this looks like in practice: TUSHY
TUSHY, known for eco-friendly bidets and bathroom essentials, is a useful example of what happens when you take conversational commerce seriously.
Bidets aren't an impulse purchase. Shoppers have real questions about fit, compatibility, and installation. Those questions used to go unanswered until the CX team could respond, often after the customer had abandoned the cart.
TUSHY used Gorgias's AI Agent and shopping assistant capabilities to automate pre-sales support. AI Agent engaged shoppers in real-time conversations, addressed their concerns directly, and built confidence at the moment of highest intent.
This resulted in a 190% increase in chat-based purchases, a 13x return on investment, and twice the purchase rate of human agents.
How to apply this to your strategy
You don't need to overhaul your entire operation to start seeing results. The most effective approach is to start where the impact is clearest and expand from there.
A few places to begin:
- Pre-sales chat. Identify your most common pre-purchase questions (sizing, compatibility, shipping timelines) and ensure your AI can answer them confidently and promptly.
- Product page engagement. Use proactive chat prompts triggered by page behavior to start conversations before shoppers leave.
- Post-purchase follow-up. Let AI pick up the conversation after checkout with order updates and proactive support, reducing inbound volume and building trust.
- Human escalation. Define clearly which situations require a human agent complex issues, emotional exchanges, high-stakes decisions.
Want to see the full picture of where conversational commerce is headed in 2026? Read the full report to explore the data, trends, and strategies shaping the next era of ecommerce.
{{lead-magnet-1}}
AI Is Table Stakes for Ecommerce: What the Data Tells Us About 2026
TL;DR:
- AI adoption is rapidly accelerating. 96% of ecommerce professionals now use AI in their roles, up from 69% in 2024.
- AI has moved beyond support automation. Use cases have evolved into revenue generation, personalization, and logistics.
- Brands are tying AI success to profit-and-loss outcomes. 60% of brands consider AOV a top indicator of AI effectiveness.
A year ago, ecommerce brands were still debating whether AI was worth the investment. That debate is over. Today, nearly every ecommerce professional uses AI to do their job.
The shift isn't just about adoption. It's about what AI is used for and how brands measure its impact. Support automation was the entry point. Now, AI is embedded across the full operation, from product recommendations to inventory control to real-time shopping conversations.
In our 2026 State of Conversational Commerce Report, we break down trends on AI usage among 400 ecommerce decision-makers and 16,000+ ecommerce brands using Gorgias.
{{lead-magnet-1}}
AI adoption has reached a tipping point
If we rewind 12 months ago, the industry was still split on AI. Some ecommerce professionals were excited, but most were still hesitant. In 2024, 69% of ecommerce professionals used AI in their roles. By 2025, that number reached 77%. In 2026, it hit 96%.
The confidence numbers back it up. 71% of brands say they are confident using AI for ecommerce, and 73% are satisfied with its business impact.
In early 2025, only 30% of ecommerce professionals rated their excitement for AI at 10/10. Today, zero percent of respondents describe themselves as hesitant about AI.
AI use cases now span the full ecommerce stack
Using AI in ecommerce is not new. In fact, it dates back to the 1980s with the invention of algorithms and expert systems. And if youve ever leveraged similar product recommendations or chatbots, youve already integrated AI into your ecommerce stack.
Modern AI is far more sophisticated.
With the rise of agentic commerce and conversational AI, brands began leveraging AI agents to automate the processing of repetitive support tickets. Thats still happening today, but the scope has expanded beyond the support queue.
Ecommerce brands are deploying AI across every layer of their operation:
- Customer support automation: 96%
- Product recommendations: 88%
- Automated tracking and status updates: 69%
- Personalization: 64%
- Inventory control: 51%
- Dynamic pricing and discounting: 36%
- Order fulfillment: 18%
When brands were asked which channels contribute most to their AI success, conversational channels dominated. Social media messaging led at 78%, followed by SMS at 70%, and website live chat at 51%. Shoppers want fast, personal conversations, and AI is the best way to deliver that at scale.
Learn more about AIadoption, perception, and use case trends in the full 2026 ConversationalCommerce Report.
How AI is changing CX success metrics
For decades, customer support success meant fast response times and high satisfaction scores. Those are still important indicators of success, but leading brands are adding revenue-focused metrics to their dashboards.
91% of brands still track CSAT as a measure of AI's impact. But 60% now include AOV as a top indicator, and higher-revenue brands earning $20M+ are focusing on metrics like total operating expenses, cost per resolution, incremental revenue, and one-touch ticket rate.
[AI impact measured by 91% customer satisfaction, 60% average order value, and 43% resolution time.]AI can now start a conversation, ease customer doubts, sell, upsell, and recover abandoned carts in a single conversation. When youre only measuring CSAT, youre ignoring the real ROI of conversational AI investment.
AI makes every conversational channel a storefront
Virtual shopping assistants now proactively engage shoppers, adapt to their needs in real time, and offer contextual product recommendations and upsells. When the moment calls for it, they can close the deal with a targeted discount.
Gorgias brands using AI Agent's shopping assistant capabilities nearly doubled their purchase rates and converted 2050% better than those using AI Agent for support only.
Orthofeet, the largest provider of orthopedic footwear in the US, is a concrete example of this in practice. Using Gorgias, they achieved:
- 56% of support tickets automated in 2 months
- Email response times down from 24 hours to 35 seconds
- Double-digit revenue growth without adding headcount.
What this means for your AI strategy
The data tells a clear story: AI has evolved beyond a tool for handling tier 1 support tickets. Its a core part of your revenue generation strategy.
57% of brands are already using AI for 2650% of all customer interactions, and 37% expect that share to rise to 5175% within the next two years. The brands building toward that range now are the ones who will have the operational advantage when it matters most.
The practical question isn't whether to invest in AI. It's where to focus first. Based on where brands are seeing the most impact, three priorities stand out:
- Start with high-volume, low-complexity tickets. WISMO (where is my order) inquiries, return policy questions, and order status updates are where AI delivers the fastest return. Automate these first.
- Expand into conversational channels. Social messaging and SMS are where AI is driving the most success right now.
- Connect AI performance to revenue metrics. If you're only measuring CSAT and response time, you're missing half the story. Add AOV, conversion rate, and incremental revenue to your reporting.
Want to go deeper on the full 2026 conversational commerce trends? Read the complete report for data across every major AI use case in ecommerce.
{{lead-magnet-1}}
The State of Conversational Commerce: 5 Trends Reshaping Ecommerce in 2026
TL;DR:
- AI is resolving tickets, not just replying. AI now handles 31% of customer interactions for ecommerce brands, and that number is expected to nearly double within two years.
- Every channel is becoming a storefront. Conversations are replacing the traditional browse-and-buy journey, with 79% of brands reporting sales from AI-driven interactions.
- AI is shortening the buying cycle. 93% of AI-influenced purchases happen within the first 48 hours of the conversation.
- CX teams are changing, not shrinking. Ecommerce brands are actively hiring for more technical roles to implement, coach, and maintain AI.
- The winning model is hybrid. AI handles volume and speed, while humans handle complexity and judgment.
The way shoppers buy online has shifted and customers are at the center.
They no longer want to scroll through product pages, dig through FAQs, or wait 24 hours for an email reply. They open a conversation, ask a specific question, and expect a useful answer in seconds. Brands that cant deliver these experiences at scale are seeing customer hesitation turn into abandoned carts and lost revenue.
This shift has a name: conversational commerce. It's the practice of using real-time, two-way conversations as your primary sales channel, through chat, AI agents, messaging apps, and voice.
What started as an experiment for early adopters has become a key growth lever, with 84% of ecommerce brands treating conversational commerce as a strategic pillar this year vs. last year.
We surveyed 400 ecommerce decision-makers across North America, the U.K., and Europe to understand how conversational commerce and AI are reshaping the ecommerce landscape. These findings are complemented by aggregated and anonymized internal Gorgias platform data from 16,000+ ecommerce brands.
The State of Conversational Commerce in 2026 trends report breaks down all of the findings, including five key trends shaping the ecommerce landscape.
{{lead-magnet-1}}
Trend 1: AI is table stakes for ecommerce and its no longer just about efficiency
A few years ago, adding an AI chatbot to your site that could provide tracking links and Help Center article recommendations was a differentiator. Today, it's table stakes. McKinsey found that 71% of shoppers expect personalized experiences, and 76% get frustrated when they don't get them.
Right now, most ecommerce professionals use AI, with 93% having used it for at least 1 year. Enthusiasm is accelerating quickly, with only 30% of ecommerce professionals rating their excitement for AI at 10/10 in April 2025. Similarly, while AI adoption rose steadily year over year, it reached a clear peak in 2026.
[Bar chart showing ecommerce professionals using AI: 69.2% in 2024, 77.2% in 2025, and 96% in 2026.]The use cases driving this adoption are practical and high-volume:
- Order tracking and status updates
- Returns, exchanges, and refund requests
- Shipping FAQs and delivery estimates
These are the tickets that flood brands inboxes every day. AI agents resolve them instantly, without pulling teams away from conversations that actually require human judgment.
Explore AI adoption and use case data in more depth in the full report.
Trend 2: Conversations are the new path to checkout
The traditional ecommerce funnel, visit site, browse products, add to cart, check out, is losing ground. Shoppers now discover products on Instagram, ask questions via direct message, and complete purchases without ever visiting a website.
Conversational AI is actively increasing revenue, with 79% of brands reporting that AI-driven interactions have increased sales and conversion in their business.
The practical implication is that every channel is becoming a storefront. Creating personalized touchpoints with customers earlier in the journey, through proactive engagement, is impacting the bottom line.
Read the full report to explore how AI conversions have increased QoQ by industry.
Trend 3: AI is accelerating the purchase cycle
Pre-purchase hesitation is one of the biggest conversion killers in ecommerce. A shopper lands on your product page, has a question about sizing or compatibility, can't find the answer quickly, and leaves. That's a lost sale that had nothing to do with your product.
Conversational AI changes that dynamic. When a shopper can ask a question and get an accurate, personalized answer in real time, the friction disappears.
Brands using Gorgias saw this play out at scale in 2025. When AI Agent recommended a product, 80% of the resulting purchases happened the same day, and 13% happened the next day.
Brands are further accelerating the buying cycle through proactive engagement. On-site features such as suggested product questions, recommendations triggered by search results, and Ask Anything input bars drove 50% of conversation-driven purchases during BFCM 2025.
Explore how AI is collapsing the purchase cycle in Trend 3 of the report.
Trend 4: AI is making CX teams more technical
There's a persistent narrative that AI is making CX teams redundant. The data tells a different story. 62% of ecommerce brands are planning to grow their teams, not cut them. But the scope of those teams is changing.
New roles are emerging around AI configuration and quality assurance. Teams are investing in technical members to write AI Guidance instructions, develop tone-of-voice instructions, and continuously QA results.
CX teams are also bridging the gap between support goals and revenue goals, as the two functions increasingly overlap.
The result is CX teams that are more technical than they were before. Agents who once spent their days answering repetitive tickets are now spending that time on higher-value work: complex escalations, VIP customer relationships, and improving the AI systems and knowledge bases that handle the volume.
Learn more about the evolution of CX roles in Trend #4.
Trend 5: The future is hybrid: AI-first, humans when it counts
Despite increasing AI adoption, data shows that ecommerce brands shouldnt strive for 100% automation. Winning brands are building systems in which AI handles repetitive tier-1 tickets, and humans handle complex, sensitive cases.
AI handles speed and scale. It resolves order-tracking requests at 2 a.m., processes return-eligibility checks in seconds, and answers the same shipping question for the thousandth time without compromising quality.
Human agents handle conversations that require context, empathy, or decisions that fall outside the standard playbook. There are several topics where shoppers still prefer human support.
Successful hybrid systems require continuous iteration, meaning reviewing handover topics, Guidance, and reviewing AI tickets on a weekly basis.
Discover how leading brands are balancing human and AI systems in Trend #5.
Where conversational commerce is heading by 2030
The 2026 trends are about expansion and standardization. The 2030 predictions are about what comes next.
Voice-based purchasing is the biggest bet on the horizon. Only 7% of brands currently use voice assistants for commerce, but 89% expect it to be standard by 2030. The vision is a customer who can reorder a product, check their subscription status, or manage a return entirely over the phone.
Proactive AI is the other major shift. Rather than waiting for a customer to reach out, AI will anticipate needs based on browsing behavior, purchase history, and where someone is in their relationship with your brand. Think of it as the digital equivalent of a sales associate who remembers what you bought last time and knows what you're likely to need next.
Explore where ecommerce brands are allocating their AI budgets in the full report.
Start building your conversational commerce strategy today
The brands winning in 2026 are creating smart, scalable systems where AIhandles volume and humans handle nuance. Theyre treating every conversational channel as an opportunity to serve and sell.
The data is clear: AI adoption is accelerating, customer expectations are rising, and the revenue impact of getting this right is measurable.
{{lead-magnet-1}}
AI in CX Webinar Recap: Building a Conversational Commerce Strategy that Converts
TL;DR:
- Implement quickly and optimize continuously. Cornbread's rollout was three phases: audit knowledge base, launch, then refine. Stacy conducts biweekly audits and provides daily AI feedback to ensure responses are accurate and on-brand.
- Simplify your knowledge base language. Before BFCM, Stacy rephrased all guidance documentation to be concise and straightforward so Shopping Assistant could deliver information quickly without confusion.
- Use proactive suggested questions. Most of Cornbread's Shopping Assistant engagement comes from Suggested Product Questions that anticipate customer needs before they even ask.
- Treat AI as another team member. Make sure the tone and language AI uses match what human agents would say to maintain consistent customer relationships.
- Free up agents for high-value work. With AI handling straightforward inquiries, Cornbread's CX team expanded into social media support, launched a retail pop-up shop, and has more time for relationship-building phone calls.
Customer education has become a critical factor in converting browsers into buyers. For wellness brands like Cornbread Hemp, where customers need to understand ingredients, dosages, and benefits before making a purchase, education has a direct impact on sales. The challenge is scaling personalized education when support teams are stretched thin, especially during peak sales periods.
Katherine Goodman, Senior Director of Customer Experience, and Stacy Williams, Senior Customer Experience Manager, explain how implementing Gorgias's AI Shopping Assistant transformed their customer education strategy into a conversion powerhouse.
In our second AI in CX episode, we dive into how Cornbread achieved a 30% conversion rate during BFCM, saving their CX team over four days of manual work.
Top learnings from Cornbread's conversational commerce strategy
1. Customer education drives conversions in wellness
Before diving into tactics, understanding why education matters in the wellness space helps contextualize this approach.
Katherine, Senior Director of Customer Experience at Cornbread Hemp, explains:
"Wellness is a very saturated market right now. Getting to the nitty-gritty and getting to the bottom of what our product actually does for people, making sure they're educated on the differences between products to feel comfortable with what they're putting in their body."
The most common pre-purchase questions Cornbread receives center around three areas: ingredients, dosages, and specific benefits. Customers want to know which product will help with their particular symptoms. They need reassurance that they're making the right choice.
What makes this challenging: These questions require nuanced, personalized responses that consider the customer's specific needs and concerns. Traditionally, this meant every customer had to speak with a human agent, creating a bottleneck that slowed conversions and overwhelmed support teams during peak periods.
2. Shopping Assistant provides education that never sleeps
Stacy, Senior Customer Experience Manager at Cornbread, identified the game-changing impact of Shopping Assistant:
"It's had a major impact, especially during non-operating hours. Shopping Assistant is able to answer questions when our CX agents aren't available, so it continues the customer order process."
A customer lands on your site at 11 PM, has questions about dosage or ingredients, and instead of abandoning their cart or waiting until morning for a response, they get immediate, accurate answers that move them toward purchase.
The real impact happens in how the tool anticipates customer needs. Cornbread uses suggested product questions that pop up as customers browse product pages. Stacy notes:
"Most of our Shopping Assistant engagement comes from those suggested product features. It almost anticipates what the customer is asking or needing to know."
Actionable takeaway: Don't wait for customers to ask questions. Surface the most common concerns proactively. When you anticipate hesitation and address it immediately, you remove friction from the buying journey.
3. Implementation follows a clear three-phase approach
One of the biggest myths about AI is that implementation is complicated. Stacy explains how Cornbreads rollout was a straightforward three-step process: audit your knowledge base, flip the switch, then optimize.
"It was literally the flip of a switch and just making sure that our data and information in Gorgias was up to date and accurate."
Here's Cornbreads three-phase approach:
- Preparation. Before launching, Cornbread conducted a comprehensive audit of their knowledge base to ensure accuracy and completeness. This groundwork is critical because your AI is only as good as the information it has access to.
- Launch and training. After going live, the team met weekly with their Gorgias representative for three to four weeks. They analyzed engagements, reviewed tickets, and provided extensive AI feedback to teach Shopping Assistant which responses were appropriate and how to pull from the knowledge base effectively.
- Ongoing optimization. Now, Stacy conducts audits biweekly and continuously updates the knowledge base with new products, promotions, and internal changes. She also provides daily AI feedback, ensuring responses stay accurate and on-brand.
Actionable takeaway: Block out time for that initial knowledge base audit. Then commit to regular check-ins because your business evolves, and your AI should evolve with it.
Read more: AI in CX Webinar Recap: Turning AI Implementation into Team Alignment
4. Simple, concise language converts better
Here's something most brands miss: the way you write your knowledge base articles directly impacts conversion rates.
Before BFCM, Stacy reviewed all of Cornbread's Guidance and rephrased the language to make it easier for AI Agent to understand.
"The language in the Guidance had to be simple, concise, very straightforward so that Shopping Assistant could deliver that information without being confused or getting too complicated," Stacy explains. When your AI can quickly parse and deliver information, customers get faster, more accurate answers. And faster answers mean more conversions.
Katherine adds another crucial element: tone consistency.
"We treat AI as another team member. Making sure that the tone and the language that AI used were very similar to the tone and the language that our human agents use was crucial in creating and maintaining a customer relationship."
As a result, customers often don't realize they're talking to AI. Some even leave reviews saying they loved chatting with "Ally" (Cornbread's AI agent name), not realizing Ally isn't human.
Actionable takeaway: Review your knowledge base with fresh eyes. Can you simplify without losing meaning? Does it sound like your brand? Would a customer be satisfied with this interaction? If not, time for a rewrite.
Read more: How to Write Guidance with the When, If, Then Framework
5. Black Friday results proved the strategy works under pressure
The real test of any CX strategy is how it performs under pressure. For Cornbread, Black Friday Cyber Monday 2025 proved that their conversational commerce strategy wasn't just working, it was thriving.
Over the peak season, Cornbread saw:
- Shopping Assistant conversion rate jumped from a 20% baseline to 30% during BFCM
- First response time dropped from over two minutes in 2024 to just 21 seconds in 2025
- Attributed revenue grew by 75%
- Tickets doubled, but AI handled 400% more tickets compared to the previous year
- CSAT scores stayed exactly in line with the previous year, despite the massive volume increase
Katherine breaks down what made the difference:
"Shopping Assistant popping up, answering those questions with the correct promo information helps customers get from point A to point B before the deal ends."
During high-stakes sales events, customers are in a hurry. They're comparing options, checking out competitors, and making quick decisions. If you can't answer their questions immediately, they're gone. Shopping Assistant kept customers engaged and moving toward purchase, even when human agents were swamped.
Actionable takeaway: Peak periods require a fail-safe CX strategy. The brands that win are the ones that prepare their AI tools in advance.
6. Strategic work replaces reactive tasks
One of the most transformative impacts of conversational commerce goes beyond conversion rates. What your team can do with their newfound bandwidth matters just as much.
With AI handling straightforward inquiries, Cornbread's CX team has evolved into a strategic problem-solving team. They've expanded into social media support, provided real-time service during a retail pop-up, and have time for the high-value interactions that actually build customer relationships.
Katherine describes phone calls as their highest value touchpoint, where agents can build genuine relationships with customers. We have an older demographic, especially with CBD. We received a lot of customer calls requesting orders and asking questions. And sometimes we end up just yapping, Katherine shares. I was yapping with a customer last week, and we'd been on the call for about 15 minutes. This really helps build those long-term relationships that keep customers coming back."
That's the kind of experience that builds loyalty, and becomes possible only when your team isn't stuck answering repetitive tickets.
Stacy adds that agents now focus on "higher-level tickets or customer issues that they need to resolve. AI handles straightforward things, and our agents now really are more engaged in more complicated, higher-level resolutions."
Actionable takeaway: Stop thinking about AI only as a cost-cutting tool and start seeing it as an impact multiplier. The goal is to free your team to work on conversations that actually move the needle on customer lifetime value.
7. Continuous optimization for January and beyond
Cornbread isn't resting on their BFCM success. They're already optimizing for January, traditionally the biggest month for wellness brands as customers commit to New Year's resolutions.
Their focus areas include optimizing their product quiz to provide better data to both AI and human agents, educating customers on realistic expectations with CBD use, and using Shopping Assistant to spotlight new products launching in Q1.
Build your conversational commerce strategy now
The brands winning at conversational commerce aren't the ones with the biggest budgets or the largest teams. They're the ones who understand that customer education drives conversions, and they've built systems to deliver that education at scale.
Cornbread Hemp's success comes down to three core principles: investing time upfront to train AI properly, maintaining consistent optimization, and treating AI as a team member that deserves the same attention to tone and quality as human agents.
As Katherine puts it:
"The more time that you put into training and optimizing AI, the less time you're going to have to babysit it later. Then, it's actually going to give your customers that really amazing experience."
Watch the replay of the whole conversation with Katherine and Stacy to learn how Gorgiass Shopping Assistant helps them turn browsers into buyers.
{{lead-magnet-1}}
2025 Ecommerce Trends: AI Adoption and Smarter Tech Stacks
TL;DR
- Ecommerce teams are overwhelmed by app overload, with 42% using six tools dailyleading to inefficiencies, rising costs, and poor customer experiences.
- Top brands are consolidating their tech stacks, choosing deeply integrated, ecommerce-specific platforms to simplify operations and lower costs.
- AI adoption and excitement are accelerating, with 77.2% of ecommerce professionals using AI daily and 55.3% rating their excitement as an 8-10 out of 10.
- Gorgias powers AI-driven support and sales in one platform, through a single workspace that helps ecommerce teams resolve faster, sell smarter, and operate more efficiently.
At Gorgias, we work with over 16,000 ecommerce brands and one common challenge emerges over and over:
Ecommerce tools are essential, but too many tools becomes a burden.
With different teams responsible for different functions, brands risk creating a disconnected tech stack that causes inefficiencies, reduces productivity, and ultimately impacts profitability.
Ecommerce teams are shuffling between tabs, copying and pasting order numbers, searching for customer data, and trying to piece it all together. Its not only inefficientits expensive, frustrating, and unsustainable as you scale.
So we dug into that data.
Our 2025 Ecommerce Trends Report surveyed ecommerce professionals across industries and job roles to understand what they really think about tech stacks and AIs role in it.
{{lead-magnet-1}}
Ecommerce professionals are approaching app overload
There is now an ecommerce app for every possible use case a brand could need. But as businesses adopt new technologies for each part of their customer journey, their teams end up working out of dozens of platforms.
The study found that 42.28% of ecommerce pros use at least six apps daily to perform their role. Regardless of the number of apps used, integration and compatibility are a must. When technologies dont talk to each other, you spend time context-switching instead of focusing on customer experience.
For Audien Hearing, Gorgiass open API allowed them to create an integration with its warehouse software to manage returns directly in Gorgias rather than a shared Google spreadsheet. This integration helped them reduce returns by 5%, protecting their margins and leading to higher customer satisfaction.
Read more: How Audien Hearing Increased Efficiency for 75 Agents and Reduced Product Returns by 5%
Consolidation is the smartest move a brand can make
The most successful ecommerce brands arent necessarily using more toolstheyre using smarter tools. Leading businesses are opting for platforms that are deeply integrated, AI-compatible, and built specifically for ecommerce needs.
A growing tech stack also comes with a growing tech budget. Each new app has new costs, including subscriptions, set-up, management, and development fees. They quickly add up.
Nearly 40% of ecommerce professionals spend $5,000 to $50,000 annually on their tech stack.
Different roles have different priorities
We asked ecommerce professionals what they actually value in their tools. Unsurprisingly, the answer changed based on who we were talking to.
Top tool benefits included:
- Revenue growth for support leaders, revenue-focused roles, and founders
- Simplified workflows and time savings for support agents
Theres a clear difference between what ecommerce leaders and agents value in a tool and considering both is key to success.
Why brands hesitate to consolidate
Despite the benefits of using fewer, well-integrated tools, there are a few things that hold brands back from consolidating their tech stacks.
We asked respondents:
What, if any, are the biggest deterrents to consolidating your tech stack?
Top concerns are:
- Compatibility issues with existing software (52.4%)
- Direct costs (fees for software licenses, subscriptions, or customizations) (47.6%)
- Time required (40.3%)
AI adoption is acceleratingand its driving results
AI is dominating the world of ecommerce. It impacts every aspect of the customer journey, from brand discovery to the post-purchase experience. AI is actively reshaping the way ecommerce professionals work, so we wanted to know how they feel about it.
- 77.2% of ecommerce professionals use AI and automation to perform their role in 2025, compared to 69.3% in 2024.
- 55.3% of respondents rate their excitement for AI as an 8-10, compared to 45.6% in 2024.
Despite growing usage and excitement, teams still have their concerns with AI:
Read more: 8 AI Trends in Ecommerce: Whats Changing and How to Prepare
The AI shiftFrom just a support tool to a sales engine
The most impactful use cases weve seen arent just about reducing support ticket volume. AI is now driving revenue, increasing conversion rates, and enabling 24/7 coverage without expanding headcount.
Gorgiass AI Agent is now capable of virtual sales assistance through personalized product recommendations, dynamic discounts to reduce cart abandonment, and cross-sells and upsells.
Top brands are already leveraging these new capabilities and seeing results. For example:
- TUSHY uses a Gorgias AI Agent to accurately answer pre-sale questions, leading to a 15% conversion rate, with AI Agent driving 2x more sales than human agents.
- Trove Brands enabled an AI Agent named Wally that cut misshipments by 70%, meaning reducing unwanted charges, avoidable fulfillment costs, high return rates, and customer frustration.
- Caitlyn Minimalist uses AI to reduce response times by 99% and saw a 150% increase in ticket conversions.
Gorgias: A one-tab tool for Conversational AI
We asked one final question to make ecommerce folks really reflect on how they work:
How many tabs do you currently have open?
The average ecommerce professional works with 22 open tabs. Were not here to judge, but if youre looking to close a few of those tabs, Gorgias might be what youre missing.
Gorgias replaces all that complexity with a single workspace. From support to sales, order management to automation, it all happens inside one platform.
Ecommerce businesses can now leverage Gorgiass Advanced AI for both support and sales. Within the same AI Agent, ecommerce brands can
- Fully resolve customer inquiries, not just respond
- Provide order tracking details
- Cancel, edit, and manage orders in Shopify and integrated apps
- Process returns and exchanges
- Provide tailored product recommendations
- Drive conversions
- And much more!
Get your copy of the 2025 Ecommerce Trends Report
This blog just skims the surface of what we uncover in our 2025 Ecommerce Trends report.
Want the full story?
Download the complete 2025 Ecommerce Trends: AI Adoption & Smarter Tech Stacks report to access:
- Data-backed insights and trends from ecommerce professionals
- The biggest barriers to consolidationand how to overcome them
- Real-world case studies from leading brands like TUSHY, Caitlyn Minimalist, and July that are winning with AI
- Tactical recommendations to future-proof your ecommerce stack through AI-powered consolidation
{{lead-magnet-1}}
5 Holiday Onsite Campaigns to Maximize Year-End Sales
Not sure where to go once the Black Friday and Cyber Monday excitement settles down? Don't worryyou're not alone. Many ecommerce brands will celebrate the uplift in sales from the four-day shopping frenzy without realizing there's a huge opportunity to keep the momentum going.
The holiday shopping season is your final chance to drive sales, delight customers, and end the year strong. These five proven campaigns will help you capture last-minute shoppers, increase repeat purchases, and maximize results.
1. Gift finder campaign: make gifting easy
Help shoppers find the perfect gift or gift bundle by linking existing resources in the campaign or offering pre-sales assistance through a conversational campaign (recommended).
Shoppers love personalized recommendations. A gift finder campaign highlights curated suggestions that simplify their decision-making.
- How it works: Trigger a message when shoppers spend over 15 seconds on a product page.
- Example message: Looking for the perfect gift? This [product] is a fan favorite and pairs perfectly with [accessory]. Complete your gift with just one click! OR;
- Example message #2: Not sure what to get? We can help! Click here to chat with us about finding the perfect gift.
- Why it works: Gift bundles increase average order value (AOV) by 20%.
Pro tip: Highlight top-rated products or seasonal bestsellers to build trust.
2. Last-minute shopper campaign: create urgency
Encourage quick action as deadlines approach.
Last-minute shoppers are in a rush, so combining urgency with a discount is the perfect motivator.
- How it works: Use an exit-intent popup during the final shopping days.
- Example message: Still need gifts? Use code HOLIDAY10 for 10% off and get delivery by [date]. Hurrytime is running out!
- Why it works: Exit-intent campaigns double engagement and reduce bounce rates by 37%.
Pro tip: You can also set a cart value threshold, ensuring that tailored offers are only provided to shoppers once theyve added the minimum to their cart. You can also use a unique discount code rather than a generic code to drive a higher CTR.
3. Post-BFCM re-engagement campaign: boost loyalty
Turn Black Friday shoppers into repeat customers.
Reconnect with returning buyers by rewarding them for their loyalty.
- How it works: Display a personalized offer when previous shoppers return to your site.
- Example message: Thanks for shopping with us on Black Friday! Heres an exclusive 15% loyalty discount for your next holiday purchase.
- Why it works: Repeat customers typically spend more, with a 10% boost in gross merchandise value (GMV).
Pro tip: Use the customers previous purchase to recommend complementary products.
4. AI-powered product recommendation: upsell effortlessly
Suggest relevant items to increase cart value.
Use AI to offer personalized product recommendations based on what shoppers are browsing or have in their cart.
- How it works: Show a message at checkout or when shoppers add an item to their cart, utilizing our tagging conditions to create highly targeted audience segments.
- Example message:Love [product]? Add [related item] to complete the set! Customers who bought this also loved [product 2].
- Why it works: Personalized upsell recommendations increase AOV by up to 15%.
Pro tip: Highlight frequently bought together items or exclusive bundles for the holidays.
You can easily set up product recommendations shown on your cart page with Gorgias Convert:
5. Holiday new arrivals campaign: spotlight seasonal exclusives
Build excitement with fresh, holiday-themed products.
Shoppers love discovering new arrivals, especially during the holiday season.
- How it works: Target homepage visitors or holiday collection browsers.
- Example message: Just in time for the holidays! Explore our exclusive [product line] and find the perfect gift.
- Why it works: Announcements for new products increase conversions by 6%.
Pro tip: Use festive visuals and emphasize limited availability to drive urgency.
Dont forget to A/B test your campaigns
Testing helps you discover what works best for your audience. Experiment with different offers, visuals, or CTAs to optimize results.
- Example: Test two versions of a free shipping upsell campaign.
- Version A: Spend $15 more to get free shipping!
- Version B: Youre $15 away from free shipping. Add [product] to your cart now!
- Result: Version B may outperform because it includes a clear product recommendation, reducing customer effort.
Pro tip: Track key metrics like click-through rate (CTR) and AOV to measure success.
These holiday campaigns are proven to boost sales and customer engagement during the busiest time of year. Use tools like Gorgias Convert to launch, personalize, and optimize your strategies seamlessly.
Dont waitend the year strong with campaigns that deliver results!
{{lead-magnet-1}}
Building delightful customer interactions starts in your inbox
Looking for other resources?
Win more customers with better conversations
Start driving revenue from every conversation
The Conversational AI platform for ecommerce.
Get updates on Gorgias
| Web Proxy Viewer | New URL | Original Page |