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

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!

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!

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

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

TL;DR:

• Happy agents lead to better CX outcomes. When agents genuinely enjoy using their platform, it boosts productivity, morale, and customer satisfaction.‍
• Gorgias makes agents’ lives easier. CX teams at Glossier, Tommy John, and Brunt Workwear unanimously preferred Gorgias over legacy systems.‍
• AI helps teams scale without losing the human touch. By handling basic inquiries, AI gives agents more time for high-impact conversations and personalized support
• Agent satisfaction drives business impact. Brands saw improved team efficiency, reduced operational friction, and revenue gains from more focused, empowered agents.

Everyone talks about how important it is for your ecommerce tools to drive business growth, boost productivity, and deliver a high return on investment. But the equally important (yet often overlooked) third layer is how a tool affects the people using it day-to-day. 

The hidden costs of sticking to the CX status quo

The moment CX and ecommerce leaders start noticing slipping KPIs, frustrated agents, or rising support costs, they ask themselves a question, “Is it time to look for something new?” Sticking with the same tool might seem easier — no demos, evaluations, migrations, onboarding, or retraining involved. 

But ignoring the shortcomings of your current CX platform can snowball into larger issues over time. 

When CX agents don’t like the platform they’re working in daily, bigger problems arise:

• Agent productivity declines 
• Morale and employee retention suffer
• Operational costs rise
• Customer experience takes a hit
• Poor data and reporting if agents aren’t using tags or ticket fields correctly

Beyond the thousands of dollars saved in operational costs or hours saved per ticket, Gorgias helps CX agents focus on what they do best — creating the best customer experience possible. 

When a platform makes agents’ lives easier, they have more time to focus on the moments that matter, like proactively reaching out to VIPs, sending surprise birthday gifts, or empathetically handling nuanced tickets. Not to mention, they enjoy doing it. 

At our annual customer conference, Gorgias Connect, we asked three CX leaders to share their experiences using Gorgias. Aside from the impressive FRTs and CX-generated revenue metrics, one theme stood out — they all mentioned how much their agents enjoyed using Gorgias. 

Glossier’s agents have more time to be expert product consultants 

Emily Weiss first launched a beauty blog and community, Into the Gloss, in 2010 as a space dedicated to sharing real information, advice, and tips with real people. 

This laid the groundwork for Glossier, launching in 2014 with a fresh “skin first, makeup second” philosophy. Amidst the “full glam” era of makeup defined by smoky eyes and bold lips, Glossier’s skincare-oriented approach disrupted the norm. 

From the beginning, Glossier has attracted a strong community thanks to its products designed based on community feedback and its social media presence. Today, more than a decade later, the brand has evolved, but its core principles have stayed the same.

As a customer-obsessed beauty brand, it’s no surprise that Glossier takes a thoughtful approach to customer experience. 

We sat down with Cati Brunell-Brutman, Head of CX at Glossier, to dive into how the team uses Gorgias to make their lives easier while creating better relationships with customers. 

Glossier’s proactive approach to customer experience

How do you approach customer experience at Glossier?

I always like saying customer experience vs. customer service because I think customer service feels like we’re just solving problems in a transactional way. Customer experience is proactive and involves looking at the entire customer journey. 

Our team interacts with customers from the moment they first land on the website to when they become repeat users of a product, and eventually, when they become subscribers. There are many opportunities along the way for our team to connect with people, engage in conversations, and make complementary product recommendations. 

This was what our founder really wanted this team to be—beauty editors. Everyone on the CX team is an editor (or a product expert), making curated recommendations. My vision for our CX team is to give them more time to lean into that. 

Simplifying workflows with AI to empower agents

What are you doing differently now to make sure that your team and your business are more resilient? 

My motto for the year is simplify and automate. I don't want anyone on my team to spend their whole day in a Google spreadsheet. So I’m asking questions like, ‘What can I automate? How can I connect tools?’

I really look to my team, especially the newer members, for this, and encourage them to ask, 'Why do we do this?' Because if the answer is because we've always done it that way, that's not a good enough answer for me. 

I’m focusing on finding those moments to simplify things so that the team can concentrate on impactful work, such as creating connections and engaging with people. That’s what I really want my team to focus on because it’s what brings value to their work, our customers, and the brand. 

How did your team react when you switched to Gorgias from your previous platform? 

We actually had our agents weigh in on this. We showed them demos of all the platforms we were considering and had them attend the meetings to speak with the teams. 

Then, we ran a poll in Slack and asked the team, ‘If you were making this decision, what platform would you choose?’ All of the agents unanimously voted for Gorgias. So, we’re definitely fans. 

How has implementing AI into your CX strategy affected the team?

Throughout the industry, I think people are concerned that there’s going to be a transition to a state where CX is 100% AI, everybody is going to lose their jobs, and customers won’t be able to talk to a person. 

But as we've implemented AI at Glossier, we’ve maintained the same team size as when we first started. We just have so much more automation of things like with WISMO tickets, returns, exchanges, and basic tickets that we don’t need a human to answer with macros for six hours straight. 

Deeper human-to-human connections powered by better tools

With the additional capacity, what can your team now focus on?

The team is actually able to do more work because they're not dealing with an antiquated technical system, which makes their jobs easier and also saves us money in the long run.

Now, our agents can perform tasks that actually require a human. AI can send out tracking links, and people can do the people work. 

We receive a lot of questions about our products, like how to use them or specific recommendations. And that's when we want a person to sit down, look at the customer’s selfie, and do a shade match. Then our editors can ask follow-up questions about what the shopper is looking for and why. 

What makes your agents unique, and how does Gorgias help support them?

One of the things that I really love about Glossier is that our editors — our agents — are people, and we have customers who know them by name. 

It’s really unique, and they’re almost like internet celebrities within our community. I'll go to our Reddit page and see customers posting screenshots of their conversations with our agents, and other customers will reply saying ‘Oh my gosh, yes!’ or ‘They helped me too!’ 

Customers will DM us things like ‘This editor recommended a lipstick for me. It was great, I love it. Can that person recommend a blush for me as well?’ 

Being able to aggregate all those conversations across social media DMs, emails, and chats in one place is invaluable.

Where would your team be without Gorgias? 

Having a really bad time in Gmail.

Tommy John found that Gorgias was the perfect fit for its CX team

In 2008, Tom Patterson was a medical salesperson frustrated with ill-fitting undershirts. This problem he faced every day was the catalyst for him to found Tommy John, a dual-gender underwear, loungewear, and apparel company. 

Tommy John launched with its flagship product, the Stay-Tucked Undershirt, to solve Tom’s initial struggle that he knew other customers were also facing. Fast-forward a few years, and Tommy John expanded into more categories with innovative underwear product lines 

Customer comfort has always been the main priority for Tommy John, embedded in everything from product design to its Best Pair Guarantee. The CX team is responsible for maintaining a customer experience that is just as smooth and seamless as the products they're buying. 

Max Wallace, CX Director at Tommy John, shared his experience migrating from a legacy platform to Gorgias and how it impacted his team. 

The search for a platform that supported both customers and agents

What motivated you to find a new platform? 

We knew we had to seriously explore other options when we were assigned yet another Customer Success Manager on our former platform after having gone through several in a short span. It felt like we were starting from scratch every time, which made it challenging to elevate our CX alongside such a critical partner.

We wanted to do right by our customers and our agents, ensuring they had the reporting and tools they needed, plus more. Gorgias really offered all of those things.

What was most important to you and your team when evaluating helpdesks? 

We didn’t want anything that was reinventing the wheel. One platform we looked at wasn’t doing the agents justice by only allowing them to view their own tickets. 

We really wanted our agents to have a holistic understanding of the volume we’re receiving, which Gorgias provides. Now they have this fleshed-out understanding of every customer interaction, and that’s been a game-changer. They’ve been loving it.

Gorgias gave agents the tools they needed to thrive 

How has Gorgias impacted agent productivity and impact? 

We have definitely seen greater speed and productivity.  Even something as simple as macro suggestions has helped steer new agents in the right direction. That’s going to be huge during peak seasons, like BFCM. 

And the fact that agents can move seamlessly between conversations without losing context means they’re handling more interactions, faster, with less frustration. They feel confident in their workflows, rather than being bogged down in repetitive tasks.

Within two months, using Gorgias’s AI Agent has enabled agents to minimize time-consuming manual tasks and spend more time with high-intent customers, generating over $100,000 in sales. 

I’m confident Gorgias will help us achieve our goal of making selling and CX much more integrated. We do want to reward our team for their efforts in driving sales, and we can track conversion rates per agent in Gorgias.

Why was voice integration such a priority for your team?

Before, our agents didn’t have visibility into previous phone calls that other agents had taken. I can't tell you how many times there has been confusion regarding what's going on with the customer because our agents did not have visibility into the customer’s history. We’d have to pull the call recording, pass it along, and by then, the customer would have already been waiting.

So it was essential for us to find a helpdesk that we could use voice with. Now with Gorgias Voice, agents can look back in the timeline, listen to the call, or even read a transcript or AI-generated summary. That’s just been amazing, and they’re loving that. 

Tying revenue back to call tickets, where most of our upselling and cross-selling happens, has been another huge win.

Tommy John’s agents unanimously prefer Gorgias

How did agents react after the switch?

The number one thing that validates that we made the right decision is that our agents truly love Gorgias.

Two weeks after going live, we asked, ‘Do you feel you will be more efficient working in Gorgias than our previous platform?’ And it was unanimous — Gorgias, completely. And this was just two weeks in, with everyone still getting their feet wet. 

We sent out a survey, and seeing every single person answer in favor of Gorgias told me everything I needed to know about how quickly the team was adapting and how much they preferred the platform.

What has been the CX team’s feedback after using Gorgias for a while? 

Gorgias has really paid off for our agents in terms of their efficiency. Being able to transition seamlessly from a phone call to a follow-up email with just one click is amazing. And having all of that in the timeline — phone calls, emails, chats — that can’t be beat. 

Brunt Workwear’s team stays engaged by helping more customers each day

Eric Girouard founded Brunt Workwear in 2019 to fill a gap in the market for comfortable, high-quality workwear for skilled tradespeople. He came from blue-collar roots himself, and many of his friends and family also work in the trades.

Eric started the company in his garage, focusing on direct-to-consumer sales. Brunt Workwear aims to create products that aren’t just for tradespeople, but are actually built by them.

The workwear brand incorporates a significant amount of customer feedback into the design process to create products that actually make their lives easier. Brunt Workwear’s commitment to its customers is even more evident in its product naming convention — each product is named after a specific tradesworker. 

When we spoke with Ruth Trieger, Director of Customer Experience, she shared how the CX team achieves its goal of making solutions as easy as possible for their busy customers — and why agent satisfaction can’t be overlooked.

How Brunt Workwear makes every customer feel at home

How do you think about the state of CX today?

The best retail or CX advice I’ve ever received is to think of everyone who walks into your store or visits your website as someone entering your home. For every visitor, you will do some basic things, such as taking their coat or offering them something to eat or drink. But if you truly want to make someone feel welcome, you’re going to meet them in a way that aligns with their preferences and makes them feel like they’re a part of something. 

When you make someone feel welcome, they build an emotional connection with a brand that far transcends any product. That’s a powerful thing. 

As I consider customer experience and the growth of AI, I realize there is a constant need to deliver fantastic experiences while using the right amount of resources. If you can do that while still creating a memorable experience, you have a customer for life.

Making life easier for customers and agents with an intuitive platform 

What is your goal when designing experiences for Brunt Workwear’s customers?

Our customer is very busy and very hardworking. They have very little spare time. So if or when something goes wrong, I encourage my team to think, ‘How can we make the solution as easy as possible?’ That’s our goal — to put ourselves in their shoes and reduce friction wherever we can. 

AI can handle repetitive questions, allowing our agents to jump in quickly when nuance or empathy is needed most. What matters is making sure we are there for customers in the moments that really count.

How does Gorgias help your team achieve these goals compared to previous platforms you’ve worked with?

I come from a customer service training background, and I am used to teams needing weeks to train someone on a platform. With Gorgias, I was able to navigate the system myself in very little time. 

As a young but fast-growing brand, we have to be very nimble and change things quickly. Gorgias enables us to do that with a level of ease I've never experienced in my career, so we’re really grateful for the platform. 

I love that our agents can interface with the platform in a way that is very easy, which is good for them. From a productivity and metrics standpoint, if they’re moving easily through a platform, I also know that means they’re able to accomplish more touchpoints with our customers — more phone conversations, more emails, more chats. And that means we are helping more people. 

How does improved agent satisfaction tie back to business results?

At the end of the day, if you don’t have a happy, high-functioning team, you have literally nothing in all the world. We have a talented team, and the more customers they interact with, the more likely those people are to stay with the brand. So we see an increase in customer lifetime value when our agents can spend more time with our customers. 

Gorgias helps agents move from mountains of tickets to meaningful connections 

What additional opportunities does AI open up for your team?

AI is not replacing the human touch; it’s giving us more room to lean into it. It reduces friction so that CX agents can take on higher-value work like running close-the-loop programs, proactively reaching out on the phone, and answering faster. 

If a customer is asking, ‘Where is my order?’, I don’t need to take up an agent’s time with that because AI can get them a simple, fast answer. Then, when another customer needs somebody’s time, they’re there because that person isn’t answering a mountain of tickets. 

That’s the exciting part, AI handles the repetitive stuff, and our agents get to focus on making real connections. 

How has Gorgias enabled you to communicate the value of CX to the broader business internally? 

The reporting in Gorgias has allowed us to become a true strategic partner in the business. CX sees everything: what’s working, what’s not, and what customers are asking about. For every new product launch, every campaign, and every change, my team is on the front lines. With Gorgias’s reporting, we can bring that insight back to the rest of the organization and help shape smarter decisions.

What’s been cool is that we’re now part of the feedback loop in a much more meaningful way. Without Gorgias, we would not be able to add the same level of value as a strategic partner. That’s where I see our role continuing to shift — becoming more proactive, faster at serving customers, and a critical business function. 

At the end of the day, CX knows what’s working, what isn’t, and how customers are feeling. The more we vocalize that, the better off the entire company is.

Choose a CX platform that your CX team actually wants to use

Happy, empowered agents deliver the kind of experiences that keep customers loyal and businesses growing. 

Glossier, Tommy John, and Brunt Workwear show what’s possible when teams have a platform designed for them. More efficiency, more impact, and more human connections. Because when agents love their platform, everyone wins.

TL;DR

• Conversational commerce builds trust. Real-time conversations replace static help pages with authentic interactions that drive confidence and loyalty.
• bareMinerals boosted conversions by 5%+ using Gorgias Shopping Assistant to guide shade matching in real time, and saw zero returns on AI-assisted purchases.
• Tommy John reduced wait times and grew revenue, automating post-purchase updates while freeing agents to focus on higher-value, relationship-driven support.
• Orthofeet and Arc’teryx proved conversations convert. Chat turned returns and product questions into loyalty- and revenue-building moments.

You’re seconds away from hitting “buy now,” but one last question nags at you: does this shade actually match my skin tone? You open a live chat, only to be met with a bot that pastes a help-center article. So you close the tab.

Today’s shoppers crave immediacy and authenticity. They expect real answers, not ticket numbers. Yet too many ecommerce brands still rely on static FAQs, delayed email replies, or chatbots that feel anything but conversational. The result is often missed sales, frustrated customers, and eroding loyalty.

Conversational commerce bridges that gap. By meeting customers where they are, in real time and on their terms, brands can turn every interaction into an opportunity to build confidence and connection.

In this post, we’ll explore how leading ecommerce brands use Gorgias to strengthen trust and loyalty through real-time conversations across the entire customer journey, from discovery to delivery and beyond.

What is conversational commerce (and why it’s the future of ecommerce)

Conversational commerce is the blending of conversation and shopping. Instead of forcing customers to navigate pages, FAQs, or documents, brands engage shoppers in real time through natural, two-way dialogue. This usually takes place over:

• Chat
• SMS
• Social media DMs
• Voice assistants

Unlike traditional live chat, you meet customers wherever they are. Conversational commerce easily switches across channels (chat, SMS, Instagram, WhatsApp, etc.) while preserving context, tone, and personalization. 

The goal is to make every interaction feel as natural as a text with a friend, but with the power to guide a purchase, resolve an issue, or suggest a product.

So, how are top brands putting conversational commerce into practice to build real trust? Let’s dive into four examples.

bareMinerals builds confidence to purchase with product guidance

Imagine browsing foundation shades late at night, unsure which one will suit your skin tone. That hesitation is often enough to make a shopper abandon their cart.

That was the challenge for bareMinerals. More than half of their incoming support tickets were product questions. Many of them were about shade matching, formulation updates, or discontinued SKUs.

They needed a way to replicate the helpfulness of a beauty advisor you can call on as you browse a store.

So bareMinerals brought in Shopping Assistant, an AI-powered virtual beauty consultant built to answer product-discovery questions in real time.

It integrates with their Shopify catalog (so it never suggests out-of-stock items), trained on the nuances of context, product benefits, and discontinued color conversions.

Here’s what happened within 30 days:

• Increased conversions: bareMinerals saw a 5%+ conversion uplift and a 5.5% increase in average order value (AOV).
• No returns: There were zero returns on AI-influenced purchases during that first month, even within a standard 30-day return window.
• Increased ROI: It generated 8.8x ROI and accounted for ~3.9% of gross merchandise volume (GMV).
• Happier customers: CSAT on AI-handled tickets outpaced human agents (AI: 5.0 vs. human: 4.6). Plus, bareMinerals’ CX team now reviews AI conversations to train human agents on phrasing, tone, upselling moves, and recognizing intent.

Takeaway: By offering real-time, contextual product guidance that mirrors an in-store consultant, bareMinerals eliminated guesswork, reduced returns, and strengthened trust before a single purchase is finalized.

Tommy John relieves post-purchase anxiety with instant order updates

One of the most anxiety-inducing moments for any shopper? Waiting for their order. Questions like “Has my order shipped yet?” or “Where’s my package?” often lead to multiple back-and-forth contacts, burdening support and testing customer patience.

Underwear brand Tommy John experienced this firsthand. Their CX team felt the strain of repetitive, predictable post-order questions, which could be better spent on complex cases. The team needed an automated fix without a huge lift, and so they adopted AI Agent.

AI Agent handled the bulk of their routine tickets, pulling from order data and pre-configured guidance to reply instantly without agent involvement.

See how AI Agent instantly jumped in to help a customer who needed to change their address:

The impact was immediate:

• Faster resolution times: Many customers receive real-time status updates without the wait time.
• Reduced ticket load: Agents no longer spend time on repetitive, low-value queries.
• More bandwidth for agents: Agents can focus on complex issues or proactive outreach.
• Revenue impact from support: Within just two months, support-driven sales from phone calls alone reached $106K+, with 20% of calls converting into purchases.
• Customer and team satisfaction: Average phone wait times dropped (~34% improvement), CSAT climbed, and agents unanimously preferred Gorgias over their legacy tools.

Takeaway: Post-purchase communication is a trust moment. Fast, accurate, and proactive responses reassure customers that their order matters.

Orthofeet maintains trust with a speedy returns process

Returns are often a brand’s biggest trust test. When a customer navigates through the hassle of a return, they’re watching closely: Is this going to be smooth and transparent, or frustrating and impersonal?

Orthofeet, a leading orthopedic footwear brand knew this too well. Before Gorgias, their CX stack was disjointed, a combination of Freshdesk, Dialpad, and outsourced chat. As they grew, this meant tickets piled up without central visibility. They needed a tool that gathered every piece of context in one place. 

That’s when they implemented AI Agent. As AI Agent handled tier-1 queries, like validating return eligibility under Orthofeet’s policy and directing customers to the returns portal, agents gained more time to focus on VIP customers, nuanced issues, and phone conversations.

The results were powerful:

• Automated workflow: They automated 56% of tickets in under two months, far exceeding their original target.
• Faster response times: Email first-response times dropped from ~24 hours to 35 seconds; chat FRT improved from minutes to 13 seconds.
• Stable headcount: The team could maintain high growth while keeping headcount stable, all while elevating service quality.
• Customers became AI champions: Customers embraced the AI-driven experience. One even sent a handwritten note praising their “friendly” and “helpful” AI.

Takeaway: Conversational commerce helps you blend technology and humanity to deliver scalable, emotionally resonant support. Even when things go wrong, a thoughtful conversational experience can repair, rather than erode, trust.

Arc’teryx increases conversions with personalized recommendations

Conversational commerce can create selling moments inside conversations you already have with shoppers. 

Arc’teryx, known for its technical outdoor gear, wanted to guide customers choosing between products like the Beta AR and Beta SL jackets. With Shopping Assistant, they turned real-time product questions into opportunities to upsell, cross-sell, and educate.

When shoppers linger on a page or ask for comparisons, the AI offers quick, tailored recommendations, suggesting the right jacket, complementary layers, or accessories. The result? More confident buyers and higher-value orders.

The results speak volumes:

• Increase in conversions: Arc’teryx achieved a 75% increase in conversion rate (from 4% to 7%) after rolling out Shopping Assistant.
• Influenced revenue: The tool influenced 3.7% of overall revenue, meaning conversations directly drove meaningful sales.
• Substantial ROI: They also saw 23x ROI on their AI Agent investment. 

Takeaway: Smart, conversational prompts transform everyday chats into meaningful sales moments,  proving support channels can drive revenue, not just resolve tickets.

Trust is the new conversion metric

Every conversation is a chance to earn (or lose) trust. Whether it’s helping a shopper find their perfect shade, tracking an order, or smoothing out a return, conversations can turn moments of uncertainty into opportunities for connection.

Brands like bareMinerals, Tommy John, Orthofeet, and Arc’teryx prove that conversational commerce builds stronger relationships, higher retention, and measurable revenue.

The future of ecommerce will revolve around conversations that create trust at every click.

If you want to see how Gorgias can bridge support and sales for you, book a demo today.

{{lead-magnet-2}}

TL;DR:

• Get instant context with Ticket Summaries. Jump into any conversation without digging through past messages or tabs.
• Organize tickets and customers with Ticket and Customer Fields. Attach properties to tickets and customers to see the whole picture, then turn it into reportable data.
• Support global customers with real-time translations. Engage in natural conversations in your customer’s language without paying for another tool.
• Resolve urgent issues with Priority Scoring. Rank tickets by importance, so high-value or sensitive issues don’t get overlooked.
• Onboard quickly with in-house migration. Whether you’re coming from Zendesk or Richpanel, Gorgias handles the move for you.

We recently unveiled the latest upgrades to Gorgias Helpdesk during Moments that Matter: Meet the Modern Helpdesk. 

The event was hosted by Bora Shehu, VP of Product Design, with updates from John Merse (VP of Product), Fraser Bruce (Senior Solutions Consultant), Nicole Simmen (Senior Manager, Customer Implementation), and a customer story from Michael Duran (Operations Manager, Authentic Brands).

From quality of life improvements to brand new features, here’s what’s waiting for you in Gorgias.

Watch the full presentation here:

Support faster with built-in ticket summaries

Agents shouldn’t have to dig for context. Every conversation now comes with Ticket Summaries. Whether an agent has jumped into a ticket mid-conversation or is dealing with a new customer, these AI-generated summaries tell the whole story in no time.

We’ve also given the Customer Timeline a makeover. Now, you can glance at past tickets and order updates in one clean view. Plus, a dedicated Order View lets agents dive into past purchases without leaving the ticket or opening a new tab.

Enrich your data with detailed ticket and customer properties

Agents have always had visibility into customer history, but now that context is easier to act on.

Ticket Fields automatically tags tickets with AI-detected reasons, whether that’s shipping questions or product feedback, to help organize your conversations more effectively.

Then, add in another layer of data using Customer Fields (in beta) to note whether you’re speaking to a longtime, VIP customer or a customer with a history of high returns.

All of this data can be funneled into your ticket reports, making it easier for your team to discover new insights about your products, support quality, and more.

Speak every customer’s language with instant translations

Taking your brand global doesn’t have to mean hiring a whole new team or spending extra on a localization tool. AI-powered translations (in beta) will soon be available on the helpdesk.

Finally, your team will be able to support customers in any language in real-time. Customers write in their native language, agents respond in theirs, and the exchange feels natural on both sides.

Never miss urgent tickets with Priority Scoring

How many times has an urgent ticket been buried at the bottom of your inbox? The new Priority Scoring system prevents that by automatically labeling tickets as Low, Normal, High, or Critical based on your Rules. 

For example, you might label a negative Facebook comment with threatening sentiment as ‘High,’ or bump high-value shoppers to the top with a ‘Critical’ label. This ensures your team always sees the conversations that need the most attention, so no sensitive issue slips through the cracks.

Shape every call journey with the new IVR flow builder

Now in beta, our flow-based IVR (interactive voice response) system lets teams on Gorgias Voice build customized call journeys for every type of conversation. Route customers through interactive menus, segment them based on their data, or direct them to voicemail, and schedule SMS follow-ups and callbacks.

To match agent availability, you can set business hours per phone number and per channel across storefronts. Teams also have more flexibility with ring strategies (ring available agents all at once or one at a time), wrap-up time between calls, and faster availability refreshes.

Stay on top of every goal with custom dashboards

We understand that CX teams need more than surface-level KPIs—they need to know what’s actually driving performance, revenue, and retention. 

With Dashboards, you can build reports focused on CX data you care about, from agent performance to product return trends. Then, filter by store or sub-brand to zoom in on the details each team is responsible for.

We’re also introducing the Human Response Time metric to show how quickly your team responds to escalations from AI Agent. This gives you a clear sign of what issues require human attention, how fast they’re resolved, and whether you need to adjust staffing.

Effortless, in-house migration for new joiners

Leave the moving to us—we now manage migrations in-house. Depending on your plan, our Implementation team will transfer emails, customers, macros, and more for you. Combined with 99.99% uptime, switching platforms is smoother, faster, and more reliable than ever.

For accelerated performance, consider our 50-in-50 implementation program, which aims to resolve 50% of your ticket volume using AI Agent within 50 days.

Enterprise customers receive a dedicated Enterprise CSM, optimization workshops, and 24/7 support to get the most out of Gorgias from day one. 

What’s coming next

Our teams are hard at work changing the landscape of customer experience. Here’s what’s on the Gorgias Product Roadmap:

• Cleaner, minimal interface. We’re giving our UI a new look to reduce clutter and highlight key information, making conversations front and center.
• Detailed order view. Quickly view past purchases and make order updates without opening new tabs or interrupting your workflow.
• Shop right in chat. Soon, product photos, descriptions, and even customer reviews will be shown directly in Gorgias Chat, so shopping experiences are as frictionless as possible.
• Scheduled CSV exports. Prove the value of CX with automated exports, perfect for stakeholders, whether they use Gorgias or not. 
• New integration with Assembled Workforce Management. Our partnership will help you leverage Gorgias ticket data to optimize forecasting and agent scheduling.
• Role-based access control. Decide which dashboards, views, conversations, and settings can be accessed by each user role.
• Okta single sign-on. Let your team sign in to Gorgias using the same authentication service you use for the rest of your tech stack.

The future of support starts with your helpdesk

Our latest helpdesk updates make it easier than before to create memorable customer moments.

As Bora Shehu, our VP of Product Design, said, “We hope that the tools we’re building help you spend less time on robotic work, and more time on impactful human work that grows your businesses through the power of conversations.”

If you’re not on Gorgias yet and want to see what’s possible, book a demo today.

{{lead-magnet-1}}