Search our articles
Search

Featured articles

Conversational Commerce Metrics

Your Support Team Drives More Revenue Than You Think: Conversational Commerce Metrics

Your chat might be closing more sales than your checkout page. Here’s how to measure it.
By Tina Donati
0 min read . By Tina Donati

TL;DR:

  • Support chats can now be directly tied to revenue. Brands are measuring conversations by conversion rate, average order value (AOV), and GMV influenced.
  • AI resolution rate is only valuable if the answers are accurate and helpful. A high resolution rate doesn’t matter if it leads to poor recommendations — the best AI both deflects volume and drives confident purchases.
  • Chat conversion rates often outperform traditional channels. Brands like Arc’teryx saw a 75% lift in conversions (from 4% to 7%) when AI handled high-intent product questions.
  • Shoppers who chat often spend more. Conversations lead to higher AOVs by helping customers understand products, explore upgrades, and discover add-ons — not just through upselling, but smarter guidance.

Conversational commerce finally has a scoreboard.

For years, CX leaders knew support conversations mattered, they just couldn’t prove how much. Conversations lived in that gray area of ecommerce where shoppers got answers, agents did their best, and everyone agreed the channel was “important”… 

But tying those interactions back to actual revenue? Nearly impossible.

Fast forward to today, and everything has changed.

Real-time conversations — whether handled by a human agent or powered by AI — now leave a measurable footprint across the entire customer journey. You can see how many conversations directly influenced a purchase. 

In other words, conversational commerce is finally something CX teams can measure, optimize, and scale with confidence.

Why measuring conversational commerce matters now

If you want to prove the value of your CX strategy to your CFO, your marketing team, or your CEO, you need data, not anecdotes.

Leadership isn’t swayed by “We think conversations help shoppers.” They want to see the receipts. They want to know exactly how interactions influence revenue, which conversations drive conversion, and where AI meaningfully reduces workload without sacrificing quality.

That’s why conversational commerce metrics matter now more than ever. This gives CX leaders a way to:

  • Quantify the revenue influence of conversations
  • Understand where AI improves efficiency — and where humans add the most value
  • Make informed decisions on staffing, automation, and channel investment
  • Turn CX into a profit center instead of a cost center

These metrics let you track impact with clarity and confidence.

And once you can measure it, you can build a stronger case for deeper investment in conversational tools and strategy.

The 4 metric categories that define conversational commerce success

So, what exactly should CX teams be measuring?

While conversational commerce touches every part of the customer journey, the most meaningful insights fall into four core categories: 

  1. Automation performance
  2. Conversion & revenue impact
  3. Engagement quality
  4. Discounting behavior

Let’s dive into each.

Automation performance metrics

If you want to understand how well your conversational commerce strategy is working, automation performance is the first place to look. These metrics reveal how effectively AI is resolving shopper needs, reducing ticket volume, and stepping into revenue-driving conversations at scale.

The two most foundational metrics?

1. Resolution rate: Are AI-led conversations actually helpful?

Resolution rate measures how many conversations your AI handles from start to finish without needing a human to take over. On paper, high resolution rates sound like a guaranteed win. It suggests your AI is handling product questions, sizing concerns, shade matching, order guidance, and more — all without adding to your team’s workload.

But a high resolution rate doesn’t automatically mean your AI is performing well.

Yes, the ticket was “resolved,” but was the customer actually helped? Was the answer accurate? Did the shopper leave satisfied or frustrated?

This is where quality assurance becomes essential. Your AI should be resolving tickets accurately and helpfully, not simply checking boxes.

At its best, a strong resolution rate signals that your AI is:

  • Confidently answering product questions
  • Guiding shoppers to the right SKU, variant, shade, size, or style
  • Reducing cart abandonment caused by confusion
  • Helping pre-sale shoppers convert faster

When resolution rate quality goes up, so does revenue influence.

You can see this clearly with beauty brands, where accuracy matters enormously. bareMinerals, for example, used to receive a flood of shade-matching questions. Everything from “Which concealer matches my undertone?” to “This foundation shade was discontinued; what’s the closest match?” 

Before AI, these questions required well-trained agents and often created inconsistencies depending on who answered.

Once they introduced Shopping Assistant, resolution rate suddenly became more meaningful. AI wasn’t just closing tickets; it was giving smarter, more confident recommendations than many agents could deliver at scale, especially after hours. 

BareMinerals' AI Agent recommends a customer a foundation that matches their skin tone

That accuracy paid off. 

AI-influenced purchases at bareMinerals had zero returns in the first 30 days because customers were finally getting the right shade the first time.

That’s the difference between “resolved” and resolved well.

2. Zero-touch tickets: How many tickets never reach a human?

The zero-touch ticket rate measures something slightly different: the percentage of conversations AI manages entirely on its own, without ever being escalated to an agent.

This metric is a direct lens into:

  • Workload reduction
  • Team efficiency
  • Cost savings
  • AI’s ability to own high-volume question types

More importantly, deflection widens the funnel for more revenue-driven conversations.

When AI deflects more inbound questions, your support team can focus on conversations that truly require human expertise, including returns exceptions, escalations, VIP shoppers, and emotionally sensitive interactions.

Brands with strong deflection rates typically see:

  • Shorter wait times
  • Higher CSAT
  • Lower support costs
  • More AI-influenced revenue

Conversion and revenue impact metrics

If automation metrics tell you how well your AI is working, conversion and revenue metrics tell you how well it’s selling.

This category is where conversational commerce really proves its value because it shows the direct financial impact of every human- or AI-led interaction.

1. Chat Conversion Rate (CVR): How often do conversations turn into purchases?

Chat conversion rate measures the percentage of conversations that end in a purchase, and it’s one of the clearest indicators of whether your conversational strategy is influencing shopper decisions.

A strong CVR tells you that conversations are:

  • Building confidence
  • Removing hesitation
  • Guiding shoppers toward the right product

You see this clearly with brands selling technical or performance-driven products. 

Outdoor apparel shoppers, for example, don’t just need “a jacket” — they need to know which jacket will hold up in specific temperatures, conditions, or terrains. A well-trained AI can step into that moment and convert uncertainty into action.

Arc’teryx saw this firsthand. 

Arc'teryx uses Shopping Assistant to enable purchases directly from chat

Once Shopping Assistant started handling their high-intent pre-purchase questions, their chat conversion rate jumped dramatically — from 4% to 7%. A 75% lift. 

That’s what happens when shoppers finally get the expert guidance they’ve been searching for.

2. GMV influenced: The revenue ripple effect of conversations

Not every shopper buys the moment they finish a chat. Some take a few hours. Some need a day or two. Some want to compare specs or read reviews before committing.

GMV influenced captures this “tail effect” by tracking revenue within 1–3 days of a conversation.

It’s especially powerful for:

  • High-consideration purchases (like outdoor gear, home furniture, equipment)
  • Products with many options, specs, or configurations
  • Shoppers who need reassurance before buying

In Arc’teryx’s case, shoppers often take time to confirm they’re choosing the right technical gear.

Yet even with that natural pause in behavior, Shopping Assistant still influenced 3.7% of all revenue, not by forcing instant decisions, but by providing the clarity people needed to make the right one.

3. AOV from conversational commerce: Do conversations lead to bigger carts?

This metric looks at the average order value of shoppers who engage in a conversation versus those who don’t. 

If the conversational AOV is higher, it means your AI or agents are educating customers in ways that naturally expand the cart.

Examples of AOV-lifting conversations include:

  • Recommending complementary gear, tools, or accessories
  • Suggesting upgraded options based on needs
  • Helping shoppers understand the difference between product tiers
  • Explaining why a specific product is worth the investment

When conversations are done well, AOV increases not because shoppers are being upsold, but because they’re being guided

4. ROI of AI-powered conversations: The metric your leadership cares most about

ROI compares the revenue generated by conversational AI to the cost of the tool itself — in short, this is the number that turns heads in boardrooms.

Strong ROI shows that your AI:

  • Does the work of multiple agents
  • Drives new revenue, not just ticket deflection
  • Provides accurate answers consistently, at any time
  • Delivers a high-quality experience without expanding headcount

When ROI looks like that, AI stops being a “tool” and starts being an undeniable growth lever.

Related: The hidden power and ROI of automated customer support

Engagement metrics that indicate purchase intent

Not every metric in conversational commerce is a final outcome. Some are early signals that show whether shoppers are interested, paying attention, and moving closer to a purchase.

These engagement metrics are especially valuable because they reveal why conversations convert, not just whether they do. When engagement goes up, conversion usually follows.

1. Click-Through Rate (CTR): Are shoppers acting on the products your AI recommends?

CTR measures the percentage of shoppers who click the product links shared during a conversation. It’s one of the cleanest leading indicators of buyer intent because it reflects a moment where curiosity turns into action.

If CTR is high, it’s a sign that:

  • Your recommendations are relevant
  • The conversation is persuasive
  • The shopper trusts the guidance they’re getting
  • The AI is surfacing the right product at the right time

In other words, CTR tells you which conversations are influencing shopping behavior.

And the connection between CTR and revenue is often tighter than teams expect.

Just look at what happened with Caitlyn Minimalist. When they began comparing the results of human-led conversations versus AI-assisted ones over a 90-day period, CTR became one of the clearest predictors of success. Their Shopping Assistant consistently drove meaningful engagement with its recommendations — an 18% click-through rate on the products it suggested.

That level of engagement translated directly into better outcomes:

  • AI-driven conversations converted at 20%, compared to just 8% for human agents
  • Many of those clicks led to multi-item purchases
  • Overall, the brand experienced a 50% lift in sales from AI-assisted chats compared to human-only ones

When shoppers click, they’re moving deeper into the buying cycle. Strong CTR makes it easier to forecast conversion and understand how well your conversational flows are guiding shoppers toward the right products.

AI Agent recommends a customer with jewelry safe for sensitive skin

Discounting behavior metrics

Discounting can be one of the fastest ways to nudge a shopper toward checkout, but it’s also one of the fastest ways to erode margins. 

That’s why discount-related metrics matter so much in conversational commerce. 

They show not just whether AI is using discounts, but how effectively those discounts are driving conversions.

1. Discounts offered: Are incentives being used strategically or too often?

This metric tracks how many discount codes or promotional offers your AI is sharing during conversations. 

Ideally, discounts should be purposeful — timed to moments when a shopper hesitates or needs an extra nudge — not rolled out as a one-size-fits-all script. When you monitor “discounts offered,” you can ensure that incentives are being used as conversion tools, not crutches.

This visibility becomes particularly important at high-intent touchpoints, such as exit intent or cart recovery interactions, where a small incentive can meaningfully increase conversion if used correctly.

2. Discounts applied: Are those discounts actually influencing the purchase?

Offering a discount is one thing. Seeing whether customers use it is another.

A high “discounts applied” rate suggests:

  • The offer was compelling
  • The timing was right
  • The shopper truly needed that incentive to convert

A low usage rate tells a different story: Your team (or your AI) is discounting unnecessarily.

This metric alone often surprises brands. More often than not, CX teams discover they can discount less without hurting conversion, or that a non-discount incentive (like a relevant product recommendation) performs just as well.

Understanding this relationship helps teams tighten their promotional strategy, protect margins, and use discounts only where they actually drive incremental revenue.

How CX teams use these metrics to make better decisions

Once you know which metrics matter, the next step is building a system that brings them together in one place.

Think of your conversational commerce scorecard as a decision-making engine — something that helps you understand performance at a glance, spot bottlenecks, optimize AI, and guide shoppers more effectively.

In Gorgias, you can customize your analytics dashboard to watch the metrics that matter most to your brand. This becomes the single source of truth for understanding how conversations influence revenue.

Here’s what a powerful dashboard unlocks:

1. You learn where AI performs best (and where humans outperform)

Some parts of the customer journey are perfect for AI: repetitive questions, product education, sizing guidance, shade matching, order status checks. 

Others still benefit from human support, like emotional conversations, complex troubleshooting, multi-item styling, or high-value VIP concerns.

Metrics like resolution rate, zero-touch ticket rate, and chat conversion rate show you exactly which is which.

When you track these consistently, you can:

  • Identify conversation types AI should fully own
  • Spot where AI needs more training
  • Allocate human agents to higher-value conversations
  • Decide when humans should step in to drive stronger outcomes

For example, if AI handles 80% of sizing questions successfully but struggles with multi-item styling advice, that tells you where to invest in improving AI, and where human expertise should remain the default.

2. You uncover what shoppers actually need to convert

Metrics like CTR, CVR, and conversational AOV reveal the inner workings of shopper decision-making. They show which recommendations resonate, which don’t, and which messaging actually moves someone to purchase.

With these insights, CX teams can:

  • Refine product recommendations
  • Improve conversation flows that stall out
  • Adjust the tone or structure of AI messaging
  • Draft stronger scripts for human agents
  • Identify recurring questions that indicate missing PDP information

For instance, if shoppers repeatedly ask clarifying questions about a product’s material or fit, that’s a signal for merchandising or product teams

If recommendations with social proof get high engagement, marketing can integrate that insight into on-site messaging. 

Conversations reveal what customers really care about — often before analytics do.

3. You prove that conversations directly drive revenue

This is the moment when the scorecard stops being a CX tool and becomes a business tool.

A clear set of metrics shows how conversations tie to:

  • GMV influenced
  • AOV lift
  • Revenue generated by AI
  • ROI of conversational commerce tools

When a CX leader walks into a meeting and says, “Our AI Assistant influenced 5% of last month’s revenue” or “Conversational shoppers have a 20% higher AOV,” the perception of CX changes instantly.

You’re no longer a support cost. You’re a revenue channel.

And once you have numbers like ROI or revenue influence in hand, it becomes nearly impossible for anyone to argue against further investment in CX automation.

4. You identify where shoppers are dropping off or hesitating

A scorecard doesn’t just show what’s working, it surfaces what’s not.

Metrics make friction obvious:

Metric Signal

What It Means

Low CTR

Recommendations may be irrelevant or poorly timed.

Low CVR

Conversations aren’t persuasive enough to drive a purchase.

High deflection but low revenue

AI is resolving tickets, but not effectively selling.

High discount usage

Shoppers rely on incentives to convert.

Low discount usage

You may be offering discounts unnecessarily and losing margin.

Once you identify these patterns, you can run targeted experiments:

  • Test new scripts or flows
  • Adjust product recommendations
  • Add social proof or benefit framing
  • Reassess discounting strategies
  • Rework messaging on key PDPs

Compounded over time, these moments create major lifts in conversion and revenue.

5. You create a feedback loop across marketing, merchandising, and product

One of the biggest hidden values of conversational data is how it strengthens cross-functional decision-making.

A clear analytics dashboard gives teams visibility into:

  • Unclear or missing product information (from repeated questions)
  • Merchandising opportunities (from your most popular products)
  • Landing page or PDP improvements (from drop-off points)
  • Messaging that resonates with real customers (from AI messages)

Suddenly, CX isn’t just answering questions — it’s informing strategy across the business.

CX drives revenue when you measure what matters

With the right metrics in place, CX leaders can finally quantify the impact of every interaction, and use that data to shape smarter, more profitable customer journeys.

If you're ready to measure — and scale — the impact of your conversations, tools like Gorgias AI Agent and Shopping Assistant give CX teams the visibility, accuracy, and performance needed to turn every interaction into revenue.

Want to see it in action? Book a demo and discover what conversational commerce can do for your bottom line.

{{lead-magnet-2}}

min read.
AI Alignment

AI in CX Webinar Recap: Turning AI Implementation into Team Alignment

By Gabrielle Policella
0 min read . By Gabrielle Policella

TL;DR:

  • Implement quickly and iterate. Rhoback’s initial rollout process took two weeks, right before BFCM. Samantha moved quickly, starting with basic FAQs and then continuously optimizing.  
  • Train AI like a three-year-old. Although it is empathetic, an AI Agent does not inherently know what is right or wrong. Invest in writing clear Guidance, testing responses, and ensuring document accuracy. 
  • Approach your AI’s tone of voice like a character study. Your AI Agent is an extension of your brand, and its personality should reflect that. Rhoback conducted a complete analysis of its agent’s tone, age, energy, and vocabulary. 
  • Embrace AI as a tool to reveal inconsistencies. If your AI Agent is giving inaccurate information, it’s exposing gaps in your knowledge sources. Uses these early test responses to audit product pages, help center content, Guidance, and policies.
  • Check in regularly and keep humans in control. Introduce weekly reviews or QA rituals to refine AI’s accuracy, tone, and efficiency. Communicate AI insights cross-functionally to build trust and work towards shared goals.

When Rhoback introduced an AI Agent to its customer experience team, it did more than automate routine tickets. Implementation revealed an opportunity to improve documentation, collaborate cross-functionally, and establish a clear brand tone of voice. 

Samantha Gagliardi, Associate Director of Customer Experience at Rhoback, explains the entire process in the first episode of our AI in CX webinar series.

Top learnings from Rhoback’s AI rollout  

1. You can start before you “feel ready”

With any new tool, the pre-implementation phase can take some time. Creating proper documentation, training internal teams, and integrating with your tech stack are all important steps that happen before you go live. 

But sometimes it’s okay just to launch a tool and optimize as you go. 

Rhoback launched its AI agent two weeks before BFCM to automate routine tickets during the busy season. 

Why it worked:

  • Samantha had audited all of Rhoback’s SOPs, training materials, and FAQs a few months before implementation. 
  • They started by automating high-volume questions such as returns, exchanges, and order tracking.
  • They followed a structured AI implementation checklist. 

2. Audit your knowledge sources before you automate

Before turning on Rhoback’s AI Agent, Samantha’s team reviewed every FAQ, policy, and help article that human agents are trained on. This helped establish clear CX expectations that they could program into an AI Agent. 

Samantha also reviewed the most frequently asked questions and the ideal responses to each. Which ones needed an empathetic human touch and which ones required fast, accurate information?  

“AI tells you immediately when your data isn’t clean. If a product detail page says one thing and the help center says another, it shows up right away.” 

Rhoback’s pre-implementation audit checklist:

  • Review customer FAQs and the appropriate responses for each. 
  • Update outdated PDPs, Help Centre articles, policies, and other relevant documentation.
  • Establish workflows with Ecommerce and Product teams to align Macros, Guidance, and Help Center articles with product descriptions and website copy. 

Read more: How to Optimize Your Help Center for AI Agent

3. Train your AI Agent in small, clear steps

It’s often said that you should train your AI Agent like a brand-new employee. 

Samantha took it one step further and recommended treating AI like a toddler, with clear, patient, repetitive instructions. 

“The AI does not have a sense of good and bad. It’s going to say whatever you train it, so you need to break it down like you’re talking to a three-year-old that doesn’t know any different. Your directions should be so detailed that there is no room for error.”

Practical tips:

  • Use AI to build your AI Guidance, focusing on clear, detailed, simple instructions. 
  • Test each Guidance before adding new ones.
  • Treat the training process like an ongoing feedback loop, not a one-time upload.

Read more: How to Write Guidance with the “When, If, Then” Framework

4. Prioritize Tone of Voice to make AI feel natural

For Rhoback, an on-brand Tone of Voice was a non-negotiable. Samantha built a character study that shaped Rhoback’s AI Agent’s custom brand voice.

“I built out the character of Rhoback, how it talks, what age it feels like, what its personality is. If it does not sound like us, it is not worth implementing.”

Key questions to shape your AI Agent’s tone of voice:

  • How does the AI Agent speak? Friendly, funny, empathetic, etc…?
  • Does your AI Agent use emojis? How often?
  • Are there any terms or phrases the AI Agent should always or never say?

5. Use AI to surface knowledge gaps or inconsistencies

Once Samantha started testing the AI Agent, it quickly revealed misalignment between Rhoback’s teams. With such an extensive product catalog, AI showed that product details did not always match the Help Center or CX documentation. 

This made a case for stronger collaboration amongst the CX, Product, and Ecommerce teams to work towards their shared goal of prioritizing the customer. 

“It opened up conversations we were not having before. We all want the customer to be happy, from the moment they click on an ad to the moment they purchase to the moment they receive their order. AI Agent allowed us to see the areas we need to improve upon.” 

Tips to improve internal alignment:

  • Create regular syncs between CX, Product, Ecommerce, and Marketing teams.
  • Share AI summaries, QA insights, and trends to highlight recurring customer pain points.
  • Build a collaborative workflow for updating documents that gives each team visibility. 

6. Build trust (with your team and customers) through transparency 

Despite the benefits of AI for CX, there’s still trepidation. Agents are concerned that AI would replace them, while customers worry they won’t be able to reach a human. Both are valid concerns, but clearly communicating internally and externally can mitigate skepticism. 

At Rhoback, Samantha built internal trust by looping in key stakeholders throughout the testing process. “I showed my team that it is not replacing them. It’s meant to be a support that helps them be even more successful with what they’re already doing," Samantha explains.

On the customer side, Samantha trained their AI Agent to tell customers in the first message that it is an AI customer service assistant that will try to help them or pass them along to a human if it can’t. 

How Rhoback built AI confidence:

  • Positioned AI as a personal assistant for agents, not a replacement.
  • Let agents, other departments, and leadership test and shape the AI Agent experience early.
  • Told customers up front when automation was being used and made the path to a human clear and easy.

Read more: How CX Leaders are Actually Using AI: 6 Must-Know Lessons

Putting these into practice: Rhoback’s framework for an aligned AI implementation 

Here is Rhoback’s approach distilled into a simple framework you can apply.

  1. Audit your content: Ensure your FAQs, product data, policies, and all documentation are accurate.
  2. Start small: Automate one repetitive workflow, such as returns or tracking.
  3. Train iteratively: Add Guidance in small, testable batches.
  4. Prioritize tone: Make sure every AI reply sounds like your brand.
  5. Align teams: Use AI data to resolve cross-departmental inconsistencies and establish clearer communication lines.
  6. Be transparent: Tell both agents and customers how AI fits into the process.
  7. Refine regularly: Review, measure, and adjust on an ongoing basis.

Watch the full conversation with Samantha to learn how AI can act as a catalyst for better internal alignment

📌 Join us for episode 2 of AI in CX: Building a Conversational Commerce Strategy that Converts with Cornbread Hemp on December 16.

{{lead-magnet-1}}

min read.
Food & Beverage Self-Service

How Food & Beverage Brands Can Level Up Self-Service Before BFCM

Before the BFCM rush begins, we’re serving food & beverage CX teams seven easy self-serve upgrades to keep support tickets off their plate.
By Alexa Hertel
0 min read . By Alexa Hertel

TL;DR:

  • Most food & beverage support tickets during BFCM are predictable. Subscription cancellations, WISMO, and product questions make up the bulk—so prep answers ahead of time.
  • Proactive CX site updates can drastically cut down repetitive tickets. Add ingredient lists, cooking instructions, and clear refund policies to product pages and FAQs.
  • FAQ pages should go deep, not just broad. Answer hyper-specific questions like “Will this break my fast?” to help customers self-serve without hesitation.
  • Transparency about stock reduces confusion and cart abandonment. Show inventory levels, set up waitlists, and clearly state cancellation windows.

In 2024, Shopify merchants drove $11.5 billion in sales over Black Friday Cyber Monday. Now, BFCM is quickly approaching, with some brands and major retailers already hosting sales.

If you’re feeling late to prepare for the season or want to maximize the number of sales you’ll make, we’ll cover how food and beverage CX teams can serve up better self-serve resources for this year’s BFCM. 

Learn how to answer and deflect customers’ top questions before they’re escalated to your support team.

💡 Your guide to everything peak season → The Gorgias BFCM Hub

Handling BFCM as a food & beverage brand

During busy seasons like BFCM and beyond, staying on top of routine customer asks can be an extreme challenge. 

“Every founder thinks BFCM is the highest peak feeling of nervousness,” says Ron Shah, CEO and Co-founder of supplement brand Obvi

“It’s a tough week. So anything that makes our team’s life easier instantly means we can focus more on things that need the time,” he continues. 

Anticipating contact reasons and preparing methods (like automated responses, macros, and enabling an AI Agent) is something that can help. Below, find the top contact reasons for food and beverage companies in 2025. 

Top contact reasons in the food & beverage industry 

According to Gorgias proprietary data, the top reason customers reach out to brands in the food and beverage industry is to cancel a subscription (13%) followed by order status questions (9.1%).

Contact Reason

% of Tickets

🍽️ Subscription cancellation

13%

🚚 Order status (WISMO)

9.1%

❌ Order cancellation

6.5%

🥫 Product details

5.7%

🧃 Product availability

4.1%

⭐ Positive feedback

3.9%

7 ways to improve your self-serve resources before BFCM

  1. Add informative blurbs on product pages 
  2. Craft additional help center and FAQ articles 
  3. Automate responses with AI or Macros 
  4. Get specific about product availability
  5. Provide order cancellation and refund policies upfront
  6. Add how-to information
  7. Build resources to help with buying decisions 

1) Add informative blurbs on product pages

Because product detail queries represent 5.7% of contact reasons for the food and beverage industry, the more information you provide on your product pages, the better. 

Include things like calorie content, nutritional information, and all ingredients.  

For example, ready-to-heat meal company The Dinner Ladies includes a dropdown menu on each product page for further reading. Categories include serving instructions, a full ingredient list, allergens, nutritional information, and even a handy “size guide” that shows how many people the meal serves. 

The Dinner Ladies product page showing parmesan biscuits with tapenade and mascarpone.
The Dinner Ladies includes a drop down menu full of key information on its product pages. The Dinner Ladies

2) Craft additional Help Center and FAQ articles

FAQ pages make up the information hub of your website. They exist to provide customers with a way to get their questions answered without reaching out to you.   

This includes information like how food should be stored, how long its shelf life is, delivery range, and serving instructions. FAQs can even direct customers toward finding out where their order is and what its status is. 

Graphic listing benefits of FAQ pages including saving time and improving SEO.

In the context of BFCM, FAQs are all about deflecting repetitive questions away from your team and assisting shoppers in finding what they need faster. 

That’s the strategy for German supplement brand mybacs

“Our focus is to improve automations to make it easier for customers to self-handle their requests. This goes hand in hand with making our FAQs more comprehensive to give customers all the information they need,” says Alexander Grassmann, its Co-Founder & COO.

As you contemplate what to add to your FAQ page, remember that more information is usually better. That’s the approach Everyday Dose takes, answering even hyper-specific questions like, “Will it break my fast?” or “Do I have to use milk?”

Everyday Dose FAQ page showing product, payments, and subscription question categories.
Everyday Dose has an extensive FAQ page that guides shoppers through top questions and answers. Everyday Dose

While the FAQs you choose to add will be specific to your products, peruse the top-notch food and bev FAQ pages below. 

Time for some FAQ inspo:

3) Automate responses with AI or macros

AI Agents and AI-powered Shopping Assistants are easy to set up and are extremely effective in handling customer interactions––especially during BFCM.  

“I told our team we were going to onboard Gorgias AI Agent for BFCM, so a good portion of tickets would be handled automatically,” says Ron Shah, CEO and Co-founder at Obvi. “There was a huge sigh of relief knowing that customers were going to be taken care of.” 

And, they’re getting smarter. AI Agent’s CSAT is just 0.6 points shy of human agents’ average CSAT score. 

Obvi homepage promoting Black Friday sale with 50% off and chat support window open.
Obvi 

Here are the specific responses and use cases we recommend automating

  • WISMO (where is my order) inquiries 
  • Product related questions 
  • Returns 
  • Order issues
  • Cancellations 
  • Discounts, including BFCM related 
  • Customer feedback
  • Account management
  • Collaboration requests 
  • Rerouting complex queries

Get your checklist here: How to prep for peak season: BFCM automation checklist

4) Get specific about product availability

With high price reductions often comes faster-than-usual sell out times. By offering transparency around item quantities, you can avoid frustrated or upset customers. 

For example, you could show how many items are left under a certain threshold (e.g. “Only 10 items left”), or, like Rebel Cheese does, mention whether items have sold out in the past.  

Rebel Cheese product page for Thanksgiving Cheeseboard Classics featuring six vegan cheeses on wood board.
Rebel Cheese warns shoppers that its Thanksgiving cheese board has sold out 3x already. Rebel Cheese  

You could also set up presales, give people the option to add themselves to a waitlist, and provide early access to VIP shoppers. 

5) Provide order cancellation and refund policies upfront 

Give shoppers a heads up whether they’ll be able to cancel an order once placed, and what your refund policies are. 

For example, cookware brand Misen follows its order confirmation email with a “change or cancel within one hour” email that provides a handy link to do so. 

Misen order confirmation email with link to change or cancel within one hour of checkout.
Cookware brand Misen follows up its order confirmation email with the option to edit within one hour. Misen 

Your refund policies and order cancellations should live within an FAQ and in the footer of your website. 

6) Add how-to information 

Include how-to information on your website within your FAQs, on your blog, or as a standalone webpage. That might be sharing how to use a product, how to cook with it, or how to prepare it. This can prevent customers from asking questions like, “how do you use this?” or “how do I cook this?” or “what can I use this with?” etc. 

For example, Purity Coffee created a full brewing guide with illustrations:

Purity Coffee brewing guide showing home drip and commercial batch brewer illustrations.
Purity Coffee has an extensive brewing guide on its website. Purity Coffee

Similarly, for its unique preseasoned carbon steel pan, Misen lists out care instructions

Butter melting in a seasoned carbon steel pan on a gas stove.
Misen 

And for those who want to understand the level of prep and cooking time involved, The Dinner Ladies feature cooking instructions on each product page. 

The Dinner Ladies product page featuring duck sausage rolls with cherry and plum dipping sauce.
The Dinner Ladies feature a how to cook section on product pages. The Dinner Ladies 

7) Build resources to help with buying decisions 

Interactive quizzes, buying guides, and gift guides can help ensure shoppers choose the right items for them––without contacting you first. 

For example, Trade Coffee Co created a quiz to help first timers find their perfect coffee match: 

Trade Coffee Co offers an interactive quiz to lead shoppers to their perfect coffee match. Trade Coffee Co

Set your team up for BFCM success with Gorgias 

The more information you can share with customers upfront, the better. That will leave your team time to tackle the heady stuff. 

If you’re looking for an AI-assist this season, check out Gorgias’s suite of products like AI Agent and Shopping Assistant

{{lead-magnet-2}}

min read.
Create powerful self-service resources
Capture support-generated revenue
Automate repetitive tasks

Further reading

Customer Support To Increase Sales

How to leverage customer support to increase sales?

By
14 min read.
0 min read . By

Most customers are loyal to brands because they know what level of service they can expect. As a result, providing an above-average customer experience is key to increase repeat in sales.

It’s relatively easy to provide great support when you get started with your store: your team gets a few dozens of support requests a day, and they respond to them almost instantly. The thing is, this level of service is very hard to maintain as you scale. Response time usually drops, and most brands start using standardized macros to keep up with the pace, which is a poor customer experience.

Your sales have increased, good. Now, you need to get your customer support up to speed

alt


Source: Gorgias customers during the Thanksgiving peak

At Gorgias, we’ve been chatting with 400 stores over the past year, and we’ve seen a lot of them working on crossing this “chasm”.

This post shares learning on how you can build a customer support organization that will scale with your business, and provide best-in-class customer service, which will drive customer retention.

Step 1: Run an audit of your support organization

A good place to start is to list the most common reasons customers are contacting you about. Go ahead and manually classify 200 tickets from your support inbox. This should take you about an hour. You can build categories from scratch, or use this spreadsheet of the most common requests for e-commerce companies we built.


alt
Most frequent support requests in e-commerce. Source: Gorgias customers


Now, you should be able to understand what problems are causing the most pain to customers.

If a specific type of request is above 10% of requests, then it’s a good candidate for optimization. For instance, if you’re getting a lot of “where is my order” questions, here are a few things you can do to deflect those:

  • Add a tracking section for customers to track their package on your site. Aftership can help here.
  • Send updates to customers about issues with delivery, through SMS or email.

Now that you have a good understanding of the reasons customers are contacting you for, you can map the customer journey, and identify what actions your agents need to take to respond to tickets.

Later, you can use this for training purposes, and to identify optimization opportunities.

At Piper, we basically studied the whole customer journey and tried to identify all reasons why someone could contact us (based on previous history). This helped us quickly identify where customers were "blocked"

Finally, let’s analyze the efficiency of your team. Of course, every business is different, but you can use this table to figure out how efficient your agents are compared to other stores. A good metric to track it is ticket closed per month. Just make sure that satisfaction remains consistent.

alt

Related: Learn more about the impact of live chat on sales. And see how Gorgias live chat can help you turn more browsers into buyers with chat campaigns.

Step 2: Figure out how you can improve the customer experience

Now, let’s work on creating “wow moments” for your customers. If you manage to exceed customers expectations when they contact you, you’re most likely to increase their loyalty and have them refer your store to their friends.

Here are a few ways you can create “wow moments”.

Make it easy for customers to contact you

You should be where your customers are. For example, if you have a Facebook page with a large audience, consider it as a real customer support channel. The point is, you should provide the same level of assistance across all support channels that your customer will use.

Also, don't be afraid to contact customers first, especially when they have items in their shopping cart. Offering help or a discount code at the right time could make the difference between a sale and an abandoned cart.

Example: providing high quality support on Facebook
70% of customers consider Facebook as a live chat support. To maximize customer satisfaction, your response time should be no more than 1 min. You’ll then be listed as a very responsive page, which will encourage your customers to respond.

alt

You can also leverage public posts to build relationship with your customers. Another easy way to facilitate customer communication is to remove the need for customers to repeat themselves. On your support platform, make sure your merge Facebook conversations with email tickets. This way, if the customer switches channel, your team will have access to the context of what the customer said before.

Related: Check out our trends and best practices for customer support.

Personalize every interaction with customer support

You should leverage every data point you have about the customer to personalize the way you communicate with them:
For how long they have been a customer
Their order preference
Their location
The days of the “we value your business” are over.

Always go an extra mile for your customers. If the customer asks for the status of their order, don’t respond only with the tracking number. Go get the order status on UPS so the customer doesn’t have to do it themselves when they’ll receive your email in the subway with poor network connection.

alt

Another good thing to do is to use a specific tone with your customer, that matches the brand image you want to convey.

If you’re into gifs, you can use them to build a brand tone your own set of gifs, designed for your own brand, and use them in your support emails. You can hire an illustrator on Upwork for that, or build them yourself.

Related: Tips to respond to angry customer emails.

Step 3: Give your team the “ironman suit” for support

Now that you know the level of support you aim at giving your customers, and you know what actions your agents need to take to get the delivery info, create an RMAs, etc., you can start optimizing the process for them.

Display rich customer profiles for your agents

To personalize messages, your agents need to have access to customer data. You can leverage the standard Shopify integration from your help desk as a starting point.

Though, it can be relevant to connect other data points to your help desk:

  • Display fulfillment data. Shippo is great for that
  • Inventory data: Stitch, display inventory to the reps
  • NPS responses
  • Responses to last promotions

If you’re on Zendesk, enabling the Shopify integration is a good start: it shows how much the customer has spent, and the past orders.

Some Gorgias customers have pretty advanced widgets that display data from Shopify, Stitch & Shipstation. This way, all the customer information is available.

Empower your reps to perform actions from support conversations

You can create custom widgets for your help desk, so that your agents can trigger actions from your help desk. Here are the most helpful actions:

  • Create a coupon
  • Place a replacement order
  • Cancelling an order
  • Create an RMA

This is a bit more tricky to implement. You need to build a custom app with buttons that will trigger actions - there are some good tutorials for Zendesk, Freshdesk & Help Scout. At Gorgias, we’ve built integrations with Stitch, Shipstation to embed these actions in the product, and enable you to add your own.

Other 3rd party apps like Chargedesk enable you to refund customers in one click.

alt

Step 4: Track your progress

Our goal here is to improve the customer experience to drive sales. A good way to track the efficiency of your support work is to compare the behavior of customers that have been in contact with customer support from those who have not.

Shopify helps you easily to this. You can create an integration between your help desk and Shopify to tag customers who reach out to support, using the Shopify API. Say you add a “customer_support” tag to them.

alt

Then, you can use Shopify statistics to monitor how the cohort of customers who have been in touch with your support team behaves, and assess the impact of your efforts with customer support.

alt

Another way to proceed is to tag orders that generated a support tickets. This way, if you work on improving delivery notifications, you can monitor the impact.

Final thoughts

Building a scalable support team that provides an amazing customer experience takes time.

Try to test different “wow moments”, iterate on the way you personalize messages, on the tone you’re using, and always track your progress. Among the teams we surveyed, several mentioned they managed to increase sales repeat by 30% after implementing these tactics.

Want to learn more about how customer support can improve your conversion rate and lead to more purchases? Check out our guides to ecommerce upselling and Shopify abandoned cart recovery.

Celery Gorgias

Celery + Gorgias

By
1 min read.
0 min read . By

Celery just released their API on Github, currently in beta. Here are some of the cool stuff you can do with it in Gorgias.

Display customer information

When you receive an email from a customer, you can connect your Celery account and see customer information (orders, shipping address, etc.). Here’s what it looks like:


Customer info from Celery

To configure it, grab your Celery access_token, head to integrations, and add an HTTP integration using this URL:
https://api.trycelery.com/v2/orders?buyer.email={ticket.requester.email}

Then you can customize the sidebar to only show the Celery data you need to respond to customers. Click the cog and simply drag and drop elements you want to show.

Select the data you want to show about your customers

Refunds, order change... without leaving tickets

Celery’s API enables you to perform a few actions from your favorite helpdesk:

  • Edit an order
  • Cancel an order
  • Issue a refund
  • Create a coupon

Here’s an example of how you can cancel an order from Gorgias itself. Say you already have a macro to cancel an order. Add an HTTP action to it, in this case:
https://api.trycelery.com/v2/orders/{ticket.requester.customer.data[0].number}/order_cancel

Then, when you use this macro and send it to the customer, it will automatically cancel the last order at the same time:

Action in celery from Gorgias

We hope this integration with Celery can save you time. If you'd like to try Celery with Gorgias, shoot us a note! At support@gorgias.com.

PostgreSQL Backup

PostgreSQL backup with pghoard & kubernetes

By Alex Plugaru
2 min read.
0 min read . By Alex Plugaru

TLDR: https://github.com/xarg/pghoard-k8s

This is a small tutorial on how to do incremental backups using pghoard for your PostgreSQL (I assume you’re running everything in Kubernetes). This is intended to help people to get started faster and not waste time finding the right dependencies, etc..


pghoard is a PostgreSQL backup daemon that incrementally backups your files on a object storage (S3, Google Cloud Storage, etc..).
For this tutorial what we’re trying to achieve is to upload our PostgreSQL to S3.

First, let’s create our docker image (we’re using the alpine:3.4 image cause it’s small):


FROM alpine:3.4

ENV REPLICA_USER "replica"
ENV REPLICA_PASSWORD "replica"

RUN apk add --no-cache \
   bash \
   build-base \        
   python3 \
   python3-dev \
   ca-certificates \
   postgresql \
   postgresql-dev \
   libffi-dev \
   snappy-dev
RUN python3 -m ensurepip && \
   rm -r /usr/lib/python*/ensurepip && \
   pip3 install --upgrade pip setuptools && \
   rm -r /root/.cache && \
   pip3 install boto pghoard


COPY pghoard.json /pghoard.json.template
COPY pghoard.sh /

CMD /pghoard.sh

REPLICA_USER and REPLICA_PASSWORD env vars will be replaced later in your Kubernetes conf by whatever your config is in production, I use those values to test locally using docker-compose.

The config pghoard.json which tells where to get your data from and where to upload it and how:

{
   "backup_location": "/data",
   "backup_sites": {
       "default": {
           "active_backup_mode": "pg_receivexlog",
           "basebackup_count": 2,
           "basebackup_interval_hours": 24,
           "nodes": [
               {
                   "host": "YOUR-PG-HOST",
                   "port": 5432,
                   "user": "replica",
                   "password": "replica",
                   "application_name": "pghoard"
               }
           ],
           "object_storage": {
               "aws_access_key_id": "REPLACE",
               "aws_secret_access_key": "REPLACE",
               "bucket_name": "REPLACE",
               "region": "us-east-1",
               "storage_type": "s3"
           },
           "pg_bin_directory": "/usr/bin"
       }
   },
   "http_address": "127.0.0.1",
   "http_port": 16000,
   "log_level": "INFO",
   "syslog": false,
   "syslog_address": "/dev/log",
   "syslog_facility": "local2"
}

Obviously replace the values above with your own. And read pghoard docs for more config explanation.

Note: Make sure you have enough space in your /data; use a Google Persistent Volume if you DB is very big.

Launch script which does 2 things:

  1. Replaces our ENV variables with the right username and password for our replication (make sure you have enough connections for your replica user)
  2. Launches the pghoard daemon.

#!/usr/bin/env bash

set -e

if [ -n "$TESTING" ]; then
   echo "Not running backup when testing"
   exit 0
fi

cat /pghoard.json.template | sed "s/\"password\": \"replica\"/\"password\": \"${REPLICA_PASSWORD}\"/" | sed "s/\"user\": \"replica\"/\"password\": \"${REPLICA_USER}\"/" > /pghoard.json
pghoard --config /pghoard.json


Once you build and upload your image to gcr.io you’ll need a replication controller to start your pghoard daemon pod:

apiVersion: v1
kind: ReplicationController
metadata:
 name: pghoard
spec:
 replicas: 1
 selector:
   app: pghoard
 template:
   metadata:
     labels:
       app: pghoard
   spec:
       containers:
       - name: pghoard
         env:
           - name: REPLICA_USER
             value: "replicant"
           - name: REPLICA_PASSWORD
             value: "The tortoise lays on its back, its belly baking in the hot sun, beating its legs trying to turn itself over. But it can't. Not with out your help. But you're not helping."
         image: gcr.io/your-project/pghoard:latest

The reason I use a replication controller is because I want the pod to restart if it fails, if a simple pod is used it will stay dead and you’ll not have backups.

Future to do:

  • Monitoring (are you backups actually done? if not, do you receive a notification?)
  • Stats collection.
  • Encryption of backups locally and then uploaded to the cloud (this is supported by pghoard).

Hope it helps, stay safe and sleep well at night.

Again, repo with the above: https://github.com/xarg/pghoard-k8s

Running Flask Celery With Kubernetes

Running Flask & Celery with Kubernetes

By Alex Plugaru
5 min read.
0 min read . By Alex Plugaru

At Gorgias we recently switched our flask & celery apps from Google Cloud VMs provisioned with Fabric to using docker with kubernetes (k8s). This is a post about our experience doing this.

Note: I'm assuming that you're somewhat familiar with Docker.


Docker structure

The killer feature of Docker for us is that it allows us to make layered binary images of our app. What this means is that you can start with a minimal base image, then make a python image on top of that, then an app image on top of the python one, etc..

Here's the hierarchy of our docker images:

  • gorgias/base - we're using phusion/baseimage as a starting base image.
  • gorgias/pgbouncer
  • gorgias/rabbitmq
  • gorgias/nginx - extends gorgias/base and installs NGINX
  • gorgias/python - Installs pip, python3.5 - yes, using it in production.
  • gorgias/app - This installs all the system dependencies: libpq, libxml, etc.. and then does pip install -r requirements.txt
  • gorgias/web - this sets up uWSGI and runs our flask app
  • gorgias/worker - Celery worker

Piece of advice: If you used to run your app using supervisord before I would advise to avoid the temptation to do the same with docker, just let your container crash and let k8s handle it.

Now we can run the above images using: docker-compose, docker-swarm, k8s, Mesos, etc...

We chose Kubernetes too

There is an excellent post about the differences between container deployments which also settles for k8s.

I'll also just assume that you already did your homework and you plan to use k8s. But just to put more data out there:

Main reason: We are using Google Cloud already and it provides a ready to use Kubernetes cluster on their cloud.

This is huge as we don't have to manage the k8s cluster and can focus on deploying our apps to production instead.

Let's begin by making a list of what we need to run our app in production:

  • Database (Postgres)
  • Message queue (RabbitMQ)
  • App servers (uWSGI running Flask)
  • Web servers (NGINX proxies uWSGI and serves static files)
  • Workers (celery)

Why Kubernetes again?

We ran the above in a normal VM environment, why would we need k8s? To understand this, let's dig a bit into what k8s offers:

  • A pod is a group of containers (docker, rtk, lxc...) that runs on a Node. It's a group because sometimes you want to run a few containers next to each other. For example we are running uWSGI and NGINX on the same pod (on the same VM and they share the same ip, ports, etc..).
  • A Node is a machine (VM or metal) that runs a k8s daemon (minion) that runs the Pods.
  • The nodes are managed by the k8s master (which in our case is managed by the container engine from Google).
  • Replication Controller or for short rc tells k8s how many pods of a certain type to run. Note that you don't tell k8s where to run them, it's master's job to schedule them. They are also used to do rolling updates, and autoscaling. Pure awesome.
  • Services take the exposed ports of your Pods and publishes them (usually to the Public). Now what's cool about a service that it can load-balance the connections to your pods, so you don't need to manage your HAProxy or NGINX. It uses labels to figure out what pods to include in it's pool.
  • Labels: The CSS selectors of k8s - use them everywhere!

There are more concepts like volumes, claims, secrets, but let's not worry about them for now.


Postgres

We're using Postgres as our main storage and we are not running it using Kubernetes.

Now we are running postgres in k8s (1 hot standby + pghoard), you can ignore the rest of this paragaph.

The reason here is that we wanted to run Postgres using provisioned SSD + high memory instances. We could have created a cluster just for postgres with these types of machines, but it seemed like an overkill.

The philosophy of k8s is that you should design your cluster with the thought that pods/nodes of your cluster are just gonna die randomly. I haven't figured our how to setup Postgres with this constraint in mind. So we're just running it replicated with a hot-standby and doing backups with wall-e for now. If you want to try it with k8s there is a guide here. And make sure you tell us about it.

RabbitMQ

RabbitMQ (used as message broker for Celery) is running on k8s as it's easier (than Postgres) to make a cluster. Not gonna dive into the details. It's using a replication controller to run 3 pods containing rabbitmq instances. This guide helped: https://www.rabbitmq.com/clustering.html

uWSGI & NGINX

As I mentioned before, we're using a replication controller to run 3 pods, each containing uWSGI & NGINX containers duo: gorgias/web & gorgias/nginx. Here's our replication controller web-rc.yaml config:

apiVersion: v1
kind: ReplicationController
metadata:
 name: web
spec:
 replicas: 3 # how many copies of the template below we need to run
 selector:
   app: web
 template:
   metadata:
     labels:
       app: web
   spec:
     containers:
     - name: web
       image: gcr.io/your-project/web:latest # the image that you pushed to Google Container Registry using gcloud docker push
       ports: # these are the exposed ports of your Pods that are later used by the k8s Service
         - containerPort: 3033
           name: "uwsgi"
         - containerPort: 9099
           name: "stats"
     - name: nginx
       image: gcr.io/your-project/nginx:latest
       ports:
         - containerPort: 8000
           name: "http"
         - containerPort: 4430
           name: "https"
       volumeMounts: # this holds our SSL keys to be used with nginx. I haven't found a way to use the http load balancer of google with k8s.  
         - name: "secrets"
           mountPath: "/path/to/secrets"
           readOnly: true
     volumes:
       - name: "secrets"
         secret:
           secretName: "ssl-secret"
And now the web-service.yaml:apiVersion: v1
kind: Service
metadata:
 name: web
spec:
 ports:
 - port: 80
   targetPort: 8000
   name: "http"
   protocol: TCP
 - port: 443
   targetPort: 4430
   name: "https"
   protocol: TCP
 selector:
   app: web
 type: LoadBalancer

That type: LoadBalancer at the end is super important because it tells k8s to request a public IP and route the network to the Pods with the selector=app:web.
If you're doing a rolling-update or just restarting your pods, you don't have to change the service. It will look for pods matching those labels.

Celery

Also a replication controller that runs 4 pods containing a single container: gorgias/worker, but doesn't need a service as it only consumes stuff. Here's our worker-rc.yaml:

apiVersion: v1
kind: ReplicationController
metadata:
 name: worker
spec:
 replicas: 2
 selector:
   app: worker
 template:
   metadata:
     labels:
       app: worker
   spec:
     containers:
     - name: worker
       image: gcr.io/your-project/worker:latest

Some tips

  • Installing some python deps take a long time, for stuff like numpy, scipy, etc.. try to install them in your namespace/app container using pip and then do another pip install in the container that extends it, ex: namespace/web, this way you don't have to rebuild all the deps every time you update one package or just update your app.
  • Spend some time playing with gcloud and kubectl. This will be the fastest way to learn of google cloud and k8s.
  • Base image choice is important. I tried phusion/baseimage and ubuntu/core. Settled for phusion/baseimage because it seems to handle the init part better than ubuntu core. They still feel too heavy. phusion/baseimage is 188MB.

Conclusion

With Kubernetes, docker finally started to make sense to me. It's great because it provides great tools out of the box for doing web app deployment. Replication controllers, Services (with LoadBalancer included), Persistent Volumes, internal DNS. It should have all you need to make a resilient web app fast.

At Gorgias we're building a next generation helpdesk that allows responding 2x faster to common customer requests and having a fast and reliable infrastructure is crucial to achieve our goals.

If you're interested in working with this kind of stuff (especially to improve it): we're hiring!

New Navigation Template Sharing

New navigation & template sharing in the Extension

By
1 min read.
0 min read . By

We've released a new version of the Chrome Extension, with sharing features and a new navigation bar. We hope you'll love it!

Share templates inside the extension

Before, the only way to share templates with your teammates was to login on Gorgias.io.

If you're on the startup plan, when you create a template, you can choose who has access to it: either only you, specific people, or your entire team.

The account management section is now available in the extension, under settings.

New navigation

Tags are now available on the left. It's easier to manage hundreds of templates with them.
You can also navigate through your private & shared templates. Shared templates include templates shared with specific people or with everyone.

We hope you'll enjoy this new version of our Chrome Extension. As usual, your feedback & questions are welcome!


No items found.
Seed Round

We've raised a Seed Round!

By
1 min read.
0 min read . By

Today, we’re thrilled to announce that we’ve raised a $1.5 million Seed round led by Charles River Ventures and Amplify Partners, to help build our new helpdesk.

We’re incredibly grateful to early users, customers, mentors we’ve met both at and Techstars.

We started the journey with Alex at the beginning of 2015 with our Chrome extension, which helps write email faster using templates. We’ve been pleased all along with customers telling us about how helpful it was, especially for customer support.

While building the extension, we’ve realized that a big inefficiency in support lies in the lack of integration between the helpdesk, the payment system, CRM and other tools support is using. As a result, agents need to do a lot of repetitive work to respond to customer requests, especially when the company is big.

That’s why we’ve decided to build a new kind of helpdesk to enable customer support agents to respond 2x faster to customers. You can find out more and sign up for our private beta here.

When a company has a lot of customers, support becomes repetitive. We want to provide support teams with tools to automate the way they treat simple repetitive requests. This way, they have more time for complex customer issues.

We'll now focus on this helpdesk and on growing the team, oh, and if you'd like to join, we're hiring! We're super excited about this new helpdesk product. If you’re using the extension, don’t worry.

Romain & Alex

Outlook Support New Editor

Outlook support & New editor

By
1 min read.
0 min read . By

We've been busy, but not deaf!

Last few months we got lots of feedback about our extension and found to our delight that most people are satisfied, but still a few recurrent issues came up:

  • The HTML/WYSIWYG editor sucks.
  • No support for Outlook.com.

We listened and now we're presenting:

  • A brand new editor
  • Support for outlook.com
  • More on the Rich-Text editor

WYSIWYG editors for the web are notoriously buggy and are just difficult to develop.

I have yet to see one that is bug free. There are few venerable editors that do a good job like TinyMCE, FKEditor or CKEditor.. but they are big and all have edge cases that break the intended formatting and add a lot of garbage html.

There are newer good quality editors in town such as Redactor. The one that got my attention and finally landed in Gorgias is this wonderful editor called which is super lightweight, uses modern content-editable (no i-frames) and 'just works' most of the time. That's not to say it's perfect, but it's good enough and I'm satisfied with it's direction in terms of development.

Enjoy it and as always send us bug-reports or feedback on: support@gorgias.com

No items found.

How to Pitch Gorgias Shopping Assistant to Leadership

By Alexa Hertel
min read.
0 min read . By Alexa Hertel

TL;DR:

  • Position Shopping Assistant as a revenue-driving tool. It boosts AOV, GMV, and chat conversion rates, with some brands seeing up to 97% higher AOV and 13x ROI.
  • Highlight its role as a proactive sales agent, not just a support bot. It recommends products, applies discounts, and guides shoppers to checkout in real time.
  • Use cross-industry case studies to make your case. Show leadership success stories from brands like Arc’teryx, bareMinerals, and TUSHY to prove impact.
  • Focus on the KPIs it improves. Track AOV, GMV, chat conversion, CSAT, and resolution rate to demonstrate clear ROI.

Rising customer expectations, shoppers willing to pay a premium for convenience, and a growing lack of trust in social media channels to make purchase decisions are making it more challenging to turn a profit.  

In this emerging era, AI’s role is becoming not only more pronounced, but a necessity for brands who want to stay ahead. Tools like Gorgias Shopping Assistant can help drive measurable revenue while reducing support costs. 

For example, a brand that specializes in premium outdoor apparel implemented Shopping Assistant and saw a 2.25% uplift in GMV and 29% uplift in average order volume (AOV).

But how, among competing priorities and expenses, do you convince leadership to implement it? We’ll show you.

Why conversational AI matters for modern ecommerce

1) Meet high consumer expectations

Shoppers want on-demand help in real time that’s personalized across devices. 

Shopping Assistant recalls a shopper’s browsing history, like what they have clicked, viewed, and added to their cart. This allows it to make more relevant suggestions that feel personal to each customer. 

2) Keep up with market momentum

The AI ecommerce tools market was valued at $7.25 billion in 2024 and is expected to reach $21.55 billion by 2030

Your competitors are using conversational AI to support, sell, and retain. Shopping Assistant satisfies that need, providing upsells and recommendations rooted in real shopper behavior. 

3) Raise AOV and GMV

Conversational AI has real revenue implications, impacting customer retention, average order value (AOV), conversion rates, and gross market value (GMV). 

For example, a leading nutrition brand saw a GMV uplift of over 1%, an increase in AOV of over 16%, and a chat conversion rate of over 15% after implementing Shopping Assistant.

Overall, Shopping Assistant drives higher engagement and more revenue per visitor, sometimes surpassing 50% and 20%, respectively.

AI Agent chat offering 8% discount on Haabitual Shimmer Layer with adjustable strategy slider.
Shopping Assistant can send discounts based on shopper behavior in real time.

How to show the business impact & ROI of Shopping Assistant

1) Pitch its core capabilities

Shopping Assistant engages, personalizes, recommends, and converts. It provides proactive recommendations, smart upsells, dynamic discounts, and is highly personalized, all helping to guide shoppers to checkout

Success spotlight

After implementing Shopping Assistant, leading ecommerce brands saw real results:

Industry

Primary Use Case

GMV Uplift (%)

AOV Uplift (%)

Chat CVR (%)

Home & interior decor 🖼️

Help shoppers coordinate furniture with existing pieces and color schemes.

+1.17

+97.15

10.30

Outdoor apparel 🎿

In-depth explanations of technical features and confidence when purchasing premium, performance-driven products.

+2.25

+29.41

6.88

Nutrition 🍎

Personalized guidance on supplement selection based on age, goals, and optimal timing.

+1.09

+16.40

15.15

Health & wellness 💊

Comparing similar products and understanding functional differences to choose the best option.

+1.08

+11.27

8.55

Home furnishings 🛋️

Help choose furniture sizes and styles appropriate for children and safety needs.

+12.26

+10.19

1.12

Stuffed toys 🧸

Clear care instructions and support finding replacements after accidental product damage.

+4.43

+9.87

3.62

Face & body care 💆‍♀️

Assistance finding the correct shade online, especially when previously purchased products are no longer available.

+6.55

+1.02

5.29

2) Position it as a revenue driver

Shopping Assistant drives uplift in chat conversion rate and makes successful upsell recommendations.  

Success spotlight

“It’s been awesome to see Shopping Assistant guide customers through our technical product range without any human input. It’s a much smoother journey for the shopper,” says Nathan Larner, Customer Experience Advisor for Arc’teryx. 

For Arc’teryx, that smoother customer journey translated into sales. The brand saw a 75% increase in conversion rate (from 4% to 7%) and 3.7% of overall revenue influenced by Shopping Assistant. 

Arc'teryx Rho Zip Neck Women's product page showing black base layer and live chat box.
Arc’teryx saw a 75% increase in conversion rate after implementing Shopping Assistant. Arc’teryx 

3) Show its efficiency and cost savings

Because it follows shoppers’ live journey during each session on your website, Shopping Assistant catches shoppers in the moment. It answers questions or concerns that might normally halt a purchase, gets strategic with discounting (based on rules you set), and upsells. 

The overall ROI can be significant. For example, bareMinerals saw an 8.83x return on investment.  

Success spotlight

"The real-time Shopify integration was essential as we needed to ensure that product recommendations were relevant and displayed accurate inventory,” says Katia Komar, Sr. Manager of Ecommerce and Customer Service Operations, UK at bareMinerals. 

“Avoiding customer frustration from out-of-stock recommendations was non-negotiable, especially in beauty, where shade availability is crucial to customer trust and satisfaction. This approach has led to increased CSAT on AI converted tickets."

AI Agent chat recommending foundation shades and closing ticket with 5-star review.

4) Present the metrics it can impact

Shopping Assistant can impact CSAT scores, response times, resolution rates, AOV, and GMV.  

Success spotlight

For Caitlyn Minimalist, those metrics were an 11.3% uplift in AOV, an 18% click through rate for product recommendations, and a 50% sales lift versus human-only chats. 

"Shopping Assistant has become an intuitive extension of our team, offering product guidance that feels personal and intentional,” says Anthony Ponce, its Head of Customer Experience.

 

AI Agent chat assisting customer about 18K gold earrings, allergies, and shipping details.
Caitlyn Minimalist leverages Shopping Assistant to help guide customers to purchase. Caitlyn Minimalist 

5) Highlight its helpfulness as a sales agent 

Support agents have limited time to assist customers as it is, so taking advantage of sales opportunities can be difficult. Shopping Assistant takes over that role, removing obstacles for purchase or clearing up the right choice among a stacked product catalog.

Success spotlight

With a product that’s not yet mainstream in the US, TUSHY leverages Shopping Assistant for product education and clarification. 

"Shopping Assistant has been a game-changer for our team, especially with the launch of our latest bidet models,” says Ren Fuller-Wasserman, Sr. Director of Customer Experience at TUSHY. 

“Expanding our product catalog has given customers more choices than ever, which can overwhelm first-time buyers. Now, they’re increasingly looking to us for guidance on finding the right fit for their home and personal hygiene needs.”

The bidet brand saw 13x return on investment after implementation, a 15% increase in chat conversion rate, and a 2x higher conversion rate for AI conversations versus human ones. 

AI Agent chat helping customer check toilet compatibility and measurements for TUSHY bidet.
AI Agent chat helping customer check toilet compatibility and measurements for TUSHY bidet.

6) Provide the KPIs you’ll track 

Customer support metrics include: 

  • Resolution rate 
  • CSAT score 

Revenue metrics to track include: 

  • Average order value (AOV) 
  • Gross market value (GMV) 
  • Chat conversion rate 

Shopping Assistant: AI that understands your brand 

Shopping Assistant connects to your ecommerce platform (like Shopify), and streamlines information between your helpdesk and order data. It’s also trained on your catalog and support history. 

Allow your agents to focus on support and sell more by tackling questions that are getting in the way of sales. 

{{lead-magnet-2}}

Building delightful customer interactions starts in your inbox

Registered! Get excited, some awesome content is on the way! 📨
Oops! Something went wrong while submitting the form.
A hand holds an envelope that has a webpage coming out of it next to stars and other webpages