Skip to content

Billing: Usage

For: Account owners and administratorsRequires: The Admin and Billing permissions, and a usage-based planScreenshots show sample data

The Usage tab of AdminBilling shows how much of your plan’s ticket allowance the current payment period has used, where those billable conversations came from and how each earlier period compared. Administrators use it to see extra-ticket charges coming and to decide whether a larger plan would pay off. It holds charts only: nothing you do here changes your plan or your bill.

Availability: needs the Admin and Billing permissions, like the rest of Billing; see User permissions and roles. The tab exists only for companies on a usage-based plan, Ticket-Based in the plan comparison; a company on a user-based plan has no Usage tab. See What each plan includes. For the other tabs, see Billing and Billing: Payment.

  • Know what counts. A ticket or chat counts once, when the first reply goes out, however long the conversation gets. Know what counts as a billable ticket.
  • See this period at a glance. A bar compares the conversations answered so far with your plan’s allowance, next to how many you would expect by today. Check this period’s usage.
  • Find out where the usage comes from. Switch the ring chart to tickets or chats to see each connected account’s share. See which accounts use your allowance.
  • Compare periods. One card per payment period shows created, answered and over the allowance, with a chart for the year. Compare payment periods.
  • Read the pricing FAQ. Five short answers about billable tickets, message volumes and sales tax. Read the pricing FAQ.
  • Download the detail. A spreadsheet lists every billable ticket and chat of a period. Download the statistic.
The Usage tab of Billing in Replyco, selected and highlighted in the left tab list. On the left, Usage by payment period shows a green bar at 237/350, then Tickets: 214, Chats: 23 and Expected usage: 225, with the FAQ and Download Statistic buttons. On the right, Usage by type has a select set to General, a date range from 2026-02-18 to 2026-03-18 and a ring chart split into Tickets and Chats. Below starts Total usage by month with a year picker set to 2026 and one card per payment period: 18 Dec - 18 Jan 402/318, 18 Jan - 18 Feb 451/367/17 with the overage in red, and 18 Feb - 18 Mar 298/237.
Usage compares the conversations answered this payment period with the tickets your plan includes.
What this screenshot shows
Screen
Billing (/billing?tab=overview)
Highlighted
tab “Usage”, left-tab-list, selected. shows the usage of the ticket allowance
Also visible
Usage by payment period 237/350, Tickets 214, Chats 23, Expected usage 225; Usage by type: General, 2026-02-18 to 2026-03-18; monthly cards 402/318, 451/367/17, 298/237
Purpose
the screen at a glance
RegionWhat it showsWhat you do there
Usage by payment period, top leftA bar of used against included tickets, then Tickets, Chats and Expected usageCheck how far into the allowance you are
Buttons, top leftFAQ and Download StatisticRead the pricing answers, export the detail
Usage by type, top rightA select, a date range and a ring chartSee the split between tickets and chats, or per account
Total usage by month, belowA year picker, one card per payment period, the year’s totals and a chartCompare periods

A ticket becomes billable when Replyco sends the first message on it: a reply from your team or an auto-response. It counts once, in the payment period in which that first message went out, however many messages follow. A chat counts the same way, when your team sends its first answer. For example, a customer who writes six times about one late parcel and gets four replies is one billable ticket. Forwarding a message creates a new ticket, which counts once when the forward is sent; the ticket you forwarded from does not become billable through it. To forward a message, see Create Ticket.

What does not count:

  • a ticket nobody replies to, for example spam you resolve or archive without answering;
  • the Welcome ticket Replyco creates for a new company;
  • conversations answered during your free trial.

Because auto-responses count as replies, an auto-response rule makes every ticket it answers billable, even if your team never writes back. To see which rules send automatic replies, see Auto-responses for tickets.

Usage by payment period covers your current payment period, from your subscription day of the month to the same day of the next month. The bar reads used/included, for example 237/350 on the M plan, and its colour tells you how close you are:

Share of the allowance usedExample on the M plan (350)Bar
Below 75 %262Green
From 75 %263Yellow
From 95 %333Red
Over 100 %351Red, and Overage: 1 appears in red

Under the bar, Tickets and Chats split the number. Expected usage is where you would be if you used the allowance evenly: the days since the period started, divided by the days in the month, times the allowance. On 21 March, 20 days into a period that began on 1 March, that is 20 ÷ 31 × 350, about 226. When the used number runs well ahead of the expected one, the period is likely to end over the allowance.

Tickets over the allowance are charged one by one at your plan’s extra ticket price, on the next invoice; see Check the upcoming invoice. When you have used 90 % or more, Change Plan on the Subscription tab is outlined in red; to compare plans, see Subscribe to a plan.

  1. Under Usage by type, open the select, which starts at General.

  2. Choose Tickets for billable tickets per connected account, or Chats for billable chats per chat account or Live Chat widget.

  3. Change the date range if you want another period. It starts with the current payment period.

The Usage tab of Billing with Usage by type switched to Tickets: the highlighted select on the right now reads Tickets, above the date range 2026-02-18 to 2026-03-18. The ring chart below it has one part per connected account that had tickets answered in the period: Northwind Electronics UK, northwind-electronics, Northwind Store, support@northwind-electronics.example.com and NorthwindHome (the legend shortens the last two), with Northwind Electronics UK the largest. On the left, Usage by payment period still shows 237/350 with Tickets: 214 and Chats: 23.
Switch Usage by type to Tickets or Chats to see which accounts use your allowance.
What this screenshot shows
Screen
Billing (/billing?tab=overview)
Highlighted
combobox “Tickets”, right-column, Tickets selected. shows billable tickets per account
Also visible
pie per account: Northwind Electronics UK, northwind-electronics, Northwind Store, support@northwind-electronics.example.com, NorthwindHome; date range 2026-02-18 to 2026-03-18
Purpose
where usage comes from

General splits the period into tickets and chats. Hover a part of the ring to see its number. In the example, Northwind’s Amazon account, Northwind Electronics UK, brings in the most billable tickets, followed by the eBay account; the names are the account names on Accounts. The general split always uses the English words Tickets and Chats.

Total usage by month shows one card per payment period of the chosen year, from the period that starts in December of the year before. Each card reads created/answered, and a third number in red when the period went over the allowance. Hover the info icon for the legend: Total number of tickets/Total tickets with answer/Overage.

Total usage by month on the Usage tab of Billing, with the year picker set to 2026. Three cards stand for the payment periods 18 Dec - 18 Jan (402/318, yellow edge), 18 Jan - 18 Feb (451/367/17, red edge, the 17 in red) and 18 Feb - 18 Mar (298/237, green edge). The middle card's figures are highlighted and its tooltip reads "Total number of tickets/Total tickets with answer/Overage". Below, Tickets limit: 350, Total tickets count: 1151 and Total tickets count with response: 922, then a chart with Created as a line, Tickets with responses as bars and Tickets limit as a red line at 350.
Each card reads created / answered / over the allowance for one payment period.
What this screenshot shows
Screen
Billing (/billing?tab=overview)
Highlighted
text “”, monthly-cards, tooltip open. explains the three numbers
Also visible
cards 402/318, 451/367/17, 298/237; Tickets limit 350, Total tickets count 1151, with response 922; combo chart Created, Tickets with responses, Tickets limit
Purpose
compare payment periods
Card edgeWhen
GreenBelow 75 % of the allowance answered
YellowFrom 75 % up to 95 %
RedAbove 95 %

Under the cards, Tickets limit shows your plan’s allowance, Total tickets count every ticket and chat created in the year’s periods, and Total tickets count with response the billable ones. The chart draws Created as a line, Tickets with responses as bars and Tickets limit as a red line; on a yearly plan it adds Total Tickets with responses, the running total. Created counts every conversation, answered or not, so the gap between the line and the bars is the work that never cost you anything.

In the example, the period from 18 January to 18 February ended at 367 answered conversations, 17 over the M plan’s 350, and those 17 were charged on the invoice of 18 February; see Billing: Payment.

Select FAQ. A dialog titled New Customer - App Pricing FAQ Questions answers five questions: What counts as a billable ticket?, How many messages should I expect each month?, Do I pay for every message I get?, How many questions can a team member handle in a day? and Is there sales tax for my Replyco subscription?. Close it with the cross.

The dialog New Customer - App Pricing FAQ Questions, opened by FAQ on the Usage tab of Billing. The first question, What counts as a billable ticket?, is highlighted; its answer says a ticket becomes billable when a user or an auto-response rule replies, however many messages it holds. Four more questions follow with their answers: How many messages should I expect each month?, Do I pay for every message I get?, How many questions can a team member handle in a day? and Is there sales tax for my Replyco subscription?. A cross at the top right closes the dialog.
The FAQ answers the five pricing questions new customers ask most.
What this screenshot shows
Screen
Billing (/billing?tab=overview)
Highlighted
text “What counts as a billable ticket?”, dialog, shown. none
Also visible
five questions with answers
Purpose
what counts as a billable ticket
  1. Select Download Statistic.

  2. Under Select period, choose the dates. The dialog starts with the current payment period.

    The dialog opened by Download Statistic on the Usage tab of Billing. Under the label Select period, the date range runs from 2026-02-18 to 2026-03-18, the current payment period, with a calendar icon to change it. Below, the blue Download button is highlighted; it saves a spreadsheet of every ticket and chat that received its first reply in the period. A cross at the top right closes the dialog without downloading.
    Download Statistic saves the billable tickets and chats of the chosen period as a spreadsheet.
    What this screenshot shows
    Screen
    Billing (/billing?tab=overview)
    Highlighted
    button “Download”, dialog-bottom, enabled. downloads tickets_<date>.xlsx
    Also visible
    Select period 2026-02-18 to 2026-03-18
    Purpose
    export the billable conversations
  3. Select Download.

Your browser saves a spreadsheet named tickets_ followed by the date, with two sheets. tickets lists every ticket whose first reply went out in the period, with its ticket number, account, creation date, last message date, subject and number of messages. messages lists every chat first answered in the period, with its date, the customer’s email address and a link. When the period has nothing billable, Replyco shows No data found for selected filters instead. The file holds customers’ email addresses, so store and share it as you would other customer data.

The Usage tab of AdminBilling, in the order the screen shows it. Nothing on the tab is saved; every date and select returns to the current payment period when you open the tab again.

Where

Top left.

What

A bar of used/included for the current payment period (on XL, the calendar month and your company’s agreed limit), green below 75 %, yellow from 75 %, red from 95 %. Below: Tickets, Chats, Expected usage, and Overage in red when used is over the allowance.

Why

The one number to watch during the month.

Where

Under the bar, left button.

What

Opens New Customer - App Pricing FAQ Questions with five questions and answers. Read-only.

Why

The pricing rules in the product’s own words, at the point you need them.

Where

Under the bar, right button.

What

Opens a dialog with Select period (default: the current payment period, cannot be cleared) and Download, which saves the spreadsheet of billable tickets and chats.

Why

Check a surprising number ticket by ticket, or hand the list to your accounts team.

Where

Top right: a select and a date range above a ring chart.

What

The select offers General (tickets against chats, the default), Tickets (per connected account) and Chats (per chat account or Live Chat widget). The date range starts with the current payment period and cannot be cleared. Both reload the chart at once.

Why

Tells you which channel drives your bill.

Where

Below, with a year picker on the right.

What

The year picker (default: this year) chooses the periods shown. One card per payment period with created/answered and, when over, the overage in red; an info icon explains the numbers. Then Tickets limit (only when your plan has an allowance), Total tickets count, Total tickets count with response and a chart with Created, Tickets with responses and Tickets limit. Cards scroll sideways when a year has more than fit.

Why

Seasonal peaks show up here, so you can move to a larger plan before the busy months.

PartShown when
The Usage tabThe Admin and Billing permissions, and a usage-based plan; see User permissions and roles
OverageThe period is over the plan’s allowance
Tickets limitYour plan has a ticket allowance
Total Tickets with responses in the chartA yearly plan
used/included Ticket(s) used at the bottom of the sidebarEvery user, once the period passes 80 % of the allowance, yellow up to 100 % and red beyond
TopicFact
What countsA ticket or chat, once, when Replyco sends its first message on it: a reply or an auto-response.
What does notUnanswered tickets, the Welcome ticket, conversations answered during the trial.
Payment periodFrom your subscription day of the month to the same day of the next month; on XL the calendar month.
AllowancesS 50, M 350, L 2,500 tickets a period; over that, 0.32 each on S and M and 0.30 on L, in your plan’s currency.
Extra ticketsCharged on the next invoice, as a line of the upcoming invoice.
FreshnessThe tab reads the counts each time you open it.
LanguageAccount names as connected; the general split reads Tickets and Chats in English.
Personal dataThe downloaded spreadsheet contains customer email addresses.

A ticket becomes billable when Replyco sends the first message on it, a reply from your team or an auto-response. It counts once, in the payment period of that first message, however many messages follow. Forwarding a message creates a new ticket, which counts once when the forward is sent. You see the count on AdminBilling under the Usage tab.

Does an auto-response make a ticket billable?

Section titled “Does an auto-response make a ticket billable?”

Yes. An auto-response is a message Replyco sends, so a ticket it answers counts once, even if your team never replies. If your usage is higher than expected, check which auto-response rules are active; see Auto-responses for tickets.

Does a ticket with ten messages count ten times?

Section titled “Does a ticket with ten messages count ten times?”

No. A ticket counts once, when the first message from your side goes out, however long the conversation becomes afterwards. The Usage tab of AdminBilling counts tickets and chats, never messages.

Do tickets we resolve without replying count?

Section titled “Do tickets we resolve without replying count?”

No. A ticket nobody replies to is never billable, so spam or notifications you resolve or archive without answering cost nothing. They still appear under Created in the Total usage by month chart, which counts every conversation.

Do chats count against the ticket allowance?

Section titled “Do chats count against the ticket allowance?”

Yes. A chat counts once, when your team sends its first answer, and it is added to the same allowance as tickets. Usage by payment period on the Usage tab shows Tickets and Chats separately under the bar.

No. Conversations answered during your free trial are not billed and are left out of Total usage by month on the Usage tab. Counting starts with your first payment period; see Subscribe to a plan.

Expected usage on the Usage tab is the number you would have reached by today if you used your allowance evenly: the days since the period started, divided by the days in the month, times the allowance. When the used number is well above it, the period is heading over the allowance.

Why is the bar red when we are still under the allowance?

Section titled “Why is the bar red when we are still under the allowance?”

The bar in Usage by payment period turns red from 95 % of the allowance, before you go over, and yellow from 75 %. Tickets beyond 100 % are charged one by one. To compare larger plans, see Subscribe to a plan.

What do the three numbers on a monthly card mean?

Section titled “What do the three numbers on a monthly card mean?”

Each card under Total usage by month reads created/answered, plus a third number in red when the period went over the allowance: the tickets charged extra. Hover the info icon on the card for the legend.

How much does a ticket over the allowance cost?

Section titled “How much does a ticket over the allowance cost?”

The extra ticket price of your plan: 0.32 on S and M and 0.30 on L, in your plan’s currency, plus tax. Extra tickets appear as a line of the next invoice on the Subscription tab; see Check the upcoming invoice.

The Usage tab of AdminBilling exists only for companies on a usage-based plan, Ticket-Based in the plan comparison; a company on a user-based plan does not have it. You also need the Billing permission; see User permissions and roles.

Which tickets are in the downloaded statistic?

Section titled “Which tickets are in the downloaded statistic?”

Every ticket whose first reply went out in the chosen period, on the sheet tickets, and every chat first answered in the period, on the sheet messages. Select Download Statistic on the Usage tab, choose the dates and select Download.

SymptomWhat to check
The Usage tab is missingYour company is on a usage-based plan, not a user-based one, and you have the Billing permission
Usage is higher than you expectedAuto-response rules that reply to every ticket; each such ticket counts once. Check Auto-responses for tickets, then compare Tickets per account under Usage by type
A month shows a red third numberThat period went over the allowance; the number is the tickets charged extra, which appear on that period’s invoice on Billing: Payment
The ring chart is emptyThe chosen date range has no billable tickets or chats; widen the range
Download shows No data found for selected filtersNothing was answered in the chosen period; choose other dates
The numbers differ from a dashboardDashboards count activity; this tab counts only conversations with a first reply, once, in the period of that reply. See Dashboard