Revenue statistics

Updated 5 days ago by Jean

Important: Feature only available on Advanced and higher plans.

What is revenue statistics?

The following statistic parameters are very important to be familiar with:

  • Converted tickets: Tickets that were followed by a sale within 5 days;
  • Conversion rate: Ratio between created and converted tickets;
  • Total sales from support: Sum of amount paid by customers for orders associated with tickets (converted tickets). Refunds and order adjustments are taken into account.

Converted tickets are requests such as questions around delivery, returns, etc.

When your agents are responding to tickets, they have an opportunity to influence the sale, and to convert the customer.

Revenue statistics allow you to measure how much money your support team is generating by helping customers through the purchasing journey.

You can also track breakdown of sales metrics per agent ("Sales per agent") and number of new tickets and converted tickets per day ("Sales per day").

It is always possible for all statistics to adjust the ticket channel and period of time you need to check.

Here is the preview of Revenue Statistics in the Gorgias dashboard. Navigate over to Statistics by using the menu on the top left and select " Revenue" from the drop down. 

What are the benefits of this feature?

Support is typically viewed as a cost center. Your agents' job is to respond as fast as possible to customers, period.

In the context of e-commerce, your agents are not only responding to customers request, they are also trying to convert customers. Though, there is no easy way to track how much money your support team is generating. Some merchants have tried to connect their chat with Google Analytics to send chat events there and track conversion, but this not ideal because it's hard to set up and it doesn't account for sales that happen from a different device or channel. For instance, I'm a prospective customer, I ask questions to an agent from my laptop in the morning. Then I buy the product from my laptop in the evening. Google Analytics wouldn't associate the sale with the conversation.

That's why we built an easier way to track the revenue that is generated by converted tickets.

How to use revenue statistics?

You can start to check the revenue statistics after you have a few weeks of tickets inside Gorgias.

Ask your agents if they think they are relevant and accurate. If so, you can create an incentive for them to hit certain numbers, and add the revenue generated from converted tickets as one of your support KPIs.

We now take into account refunds and other adjustments done on orders to calculate statistics. Thanks to this, we are going to display more accurate values.

Frequently asked questions

  1. What if the customer creates two tickets at the same time?
    In that case, we only attribute the potential sale to the ticket that's the closest to the sale date.
  2. If an order is placed, but then canceled, it will be removed from the revenue?
    On order update/cancelation we update the sale in the revenue stats, so if the order is canceled the customer is refunded and so we should display a sale of 0$.
  3. Are pre-sale tickets now called tickets created, or do we display all tickets created there?
    We have no longer any pre-sale tickets notion, we consider all support tickets like possible pre-sale tickets that's why we now display the number of created tickets.
  4. When changing the store to display the revenue statistics, tickets created number stays the same for a certain agent, is this intentional?
    The number of created tickets is not related to a Shopify store and so the number doesn't change when the selected integration does.
  5. Are tickets with orders Pending counted in the Revenue Stats or is it only for paid orders?
    Yes, this is intended, only paid orders are displayed in revenue statistics.
  6. What happens with the unassigned ticket that is followed by the sale but assigned to the user later on?
    The ticket will remain unassigned under revenue statistics even if assigned to the user later on.

How did we do?

Powered by HelpDocs (opens in a new tab)