Compensation Reports
Work out what each staff member earned from the tickets they handled, review it, lock the period and export it
Compensation reports turn ticket work into pay. You set what a ticket pays, TicketCord adds up what each staff member earned in a period from the tickets they replied in and closed, you review every amount with the tickets behind it, add bonuses or corrections, then lock the report and export it. It is for server owners who pay their support team per ticket.
Compensation reports is an Enterprise feature and is kept per server. Only the bot owner can open it: dashboard staff never see pay rules, reports or amounts. TicketCord never moves money. A report is a calculation you review and export, and you pay your team your own way.
You can also reach it from a server's Stats: click See team, then Compensation.
Setting your pay rules
Open Compensation
Go to Compensation and click Set pay rules.
Choose a currency and a time zone
Pick the Currency you pay in, or No currency (points) if you pay in points or an in-game currency. The Time zone decides when the days of the reports you create start and end.
Set what a ticket pays
Enter Pay per ticket, for example 1.50. Under Pay per ticket type you can give a ticket type its own amount; leave a type empty to pay the normal amount, or enter 0 to pay nothing for it.
Decide who is paid
Choose Who is paid for a ticket and what happens When several staff replied (see How a ticket is paid).
Save
Click Save rules. The rules apply to every draft report right away.
Pay rules
| Setting | Allowed values | Default |
|---|---|---|
| Currency | USD, EUR, GBP, CAD, AUD, NZD, CHF, SEK, NOK, DKK, PLN, CZK, HUF, RON, TRY, BRL, MXN, INR, PHP, SGD, HKD, ZAR, AED, JPY, KRW, or No currency (points) | USD |
| Time zone | Any time zone, for example Europe/Berlin | your browser's time zone |
| Pay per ticket | 0 to 1,000,000 with up to two decimals. JPY and KRW take whole numbers, from 0 to 100,000,000 | empty (required) |
| Pay per ticket type | The same range, per ticket type, up to 100 types | empty (the normal amount) |
| Who is paid for a ticket | Who claimed it or Who closed it | Who claimed it |
| When several staff replied | Pay one person, Share equally or Share by replies | Pay one person |
| Tickets the member closed | on or off | off |
Ticket types are the same as on the Stats page: a channel ticket's type is its Discord category, and a thread ticket's type is the button or menu option it was opened with (see ticket types). The list shows the types your server had tickets in during the last 90 days. A category's amount follows the category when you rename it.
Changing the currency does not convert your amounts: 1.50 stays 1.50 in the new currency. A draft report created under the old currency can no longer be calculated; delete it and create it again.
Which tickets count
A ticket counts in the report whose period contains its last close, when both of these are true:
- A staff member replied in it. A ticket nobody on your team replied in never counts. That leaves out tickets Atlas solved on its own.
- Staff closed it. A ticket the member closes after a staff member asked to close it with
/closerequestcounts for that staff member.
With Tickets the member closed on, a ticket the member closed on their own also counts, as long as a staff member replied in it.
Never counted, whatever the settings:
- tickets closed for inactivity (auto-close), closed because the member left the server, or closed by the bot for any other reason;
- tickets with no staff reply;
- the member who opened a ticket: nobody is paid for their own ticket, even if they are staff.
A ticket is paid once. If it is reopened and closed again before its report is finalized, it simply counts in the period of its last close. If it is reopened after its report was finalized, it is not paid a second time; later reports list it as In an earlier report.
How a ticket is paid
With Pay one person, the whole ticket goes to one staff member:
- Who claimed it: the staff member who has the ticket claimed when it closes. If nobody claimed it, whoever closed it.
- Who closed it: the staff member who closed it (or asked to close it). If the member closed it, whoever claimed it.
- A ticket the member closed that nobody claimed goes to the staff member who replied most.
With Share equally, the ticket is split evenly between the staff members who replied in it. A staff member who claimed or closed the ticket without replying gets no share.
With Share by replies, the ticket is split by how often each staff member answered the member. Several messages in a row count as one answer: a new answer only counts once the member has written again. If Ari answered three times and Sam once, Ari gets three quarters of the ticket and Sam one quarter.
Shares are rounded to the smallest unit of your currency and always add up to the ticket's amount.
Tickets closed before answers were counted are shared equally under Share by replies. They are marked Shared equally (closed before replies were counted) in the report.
Creating and reviewing a report
Create the report
On Compensation, click New report, choose the First day and Last day of the pay period, and click Create report. The form starts on the previous calendar month.
Check the amounts
The report opens as a Draft. Total to pay, Tickets counted, Staff paid and Tickets not counted sit at the top, then the Staff table with each staff member's tickets, the amount From tickets, their Adjustments and their Total.
Look at the tickets behind an amount
The Tickets card lists every closed ticket of the period with what it pays and to whom, or why it is not counted. Click a staff member's name in the Staff table to show only the tickets they closed, claimed or replied in, including tickets they get No share of, so you can see why. Each row opens the ticket.
Add adjustments
Click Add adjustment for a bonus or a correction: pick the Staff member (or Someone else and their Discord user ID), enter the Amount (start with a minus sign to deduct) and a Note saying why.
Finalize
When the period has ended and the amounts are right, click Finalize report and confirm.
A draft is calculated from your tickets and pay rules every time you open it, so it changes while tickets close or when you change a rule. A period is a range of whole days, at most 92 days long, and the periods of two reports cannot overlap.
A report keeps the time zone your pay rules had when you created it. Changing Time zone later applies to new reports only: the days of an existing report, draft or finalized, do not move.
Finalizing, exporting and deleting
A finalized report lists only the tickets it pays: tickets that were not counted are no longer listed, and the staff filter shows the tickets that member has a share of.
Finalizing locks a report: its pay rules, every ticket's amounts and the adjustments are stored as they were when you confirmed. Later changes do not touch it: new pay rules, a ticket that is reopened or deleted, or message content removed by your retention setting. You can finalize once the last day of the period has ended in the report's time zone.
Finalize stores exactly what you reviewed. If something changed between opening the report and confirming (a ticket was reopened, a rule or an adjustment changed), nothing is finalized and you see "The numbers changed since you opened the report. Check them again, then finalize."
Exporting is available on finalized reports:
- Export CSV on the Staff card: one row per staff member with Staff member, Discord ID, Tickets, From tickets, Adjustments, Total and Currency.
- Export CSV on the Tickets card: one row per staff member per ticket with Ticket, Closed (in UTC), Ticket type, Ticket pay, Split, Staff member, Discord ID, Share weight, Amount and Currency.
Deleting: click Delete report. A draft is removed with its adjustments. A finalized report asks you to type DELETE; deleting it frees its tickets for a new report, which is calculated from your tickets and pay rules as they are then. Files you already exported do not change. A finalized report can only be deleted while no finalized report of a later period exists, so delete the later ones first.
Limits and gotchas
- A report covers at most 92 days and reads at most 50,000 closed tickets. Use shorter periods on a very busy server.
- A server keeps up to 500 reports, and a report up to 200 adjustments. A note is up to 200 characters.
- An adjustment is between -10,000,000 and 10,000,000 (between -1,000,000,000 and 1,000,000,000 in JPY and KRW) and cannot be zero.
- A finalized report cannot be edited. To correct it, delete it and create it again, or add an adjustment to a later report.
- A staff member's name is the one recorded on their tickets. An adjustment for someone with no tickets in the period shows their Discord ID.
- A ticket deleted from TicketCord before its report is finalized is no longer counted.
- After a server is restored with RestoreCord, set Pay per ticket type again: the restored categories are new categories, so their tickets pay the normal amount until you do.
- If your plan no longer includes compensation reports, finalized reports stay readable and exportable and reports can still be deleted (a finalized one only while no finalized report of a later period exists). Creating, changing and calculating reports needs Enterprise again.
Troubleshooting
| What you see | Cause | Fix |
|---|---|---|
| "Another report already covers part of this period." | The period overlaps an existing report, draft or finalized | Choose days that no other report covers, or delete the other report |
| "Choose a period of up to 92 days that has already started." | The period is longer than 92 days, or its first day is in the future | Shorten the period or move its first day |
| "You can finalize a report once its period has ended." | The last day has not ended yet in the report's time zone | Finalize after that day |
| "The numbers changed since you opened the report. Check them again, then finalize." | A ticket, a pay rule or an adjustment changed after you opened the report | Review the amounts again and click Finalize report |
| "This period has more than 50,000 closed tickets. Use a shorter period." | The period has too many closed tickets for one report | Delete the report and create shorter periods |
| This report cannot be calculated | The currency of your pay rules changed after the draft was created, or no pay rules are saved | Delete the draft and create it again, or save your pay rules |
| "Delete the finalized reports of later periods first." | A later period is already finalized | Delete the later finalized reports first, newest to oldest |
| A ticket shows No staff reply although staff helped | Nobody with a staff role wrote in the ticket (for example the help was given in voice) | Add an adjustment for that staff member |
| A ticket shows Closed automatically | It was closed for inactivity, because the member left, or by the bot | Auto-closed tickets never count; add an adjustment if you want to pay for it |
Common questions
Does TicketCord pay my staff? No. TicketCord never moves money. A compensation report adds up what each staff member earned; you export it and pay your team with your own payment method.
Who can see compensation reports? Only the bot owner. Dashboard staff cannot open the page, the pay rules or any report, whatever their roles.
Are tickets Atlas answered paid? Only when a staff member also replied in the ticket, and staff closed it or, with Tickets the member closed on, the member closed it. A ticket Atlas solved on its own, with no staff reply, never counts.
Are tickets closed by auto-close paid? No. Tickets closed for inactivity, because the member left the server, or by the bot never count. Add an adjustment if you want to pay a staff member for one.
What happens when a ticket is reopened? Before its report is finalized, it counts in the period of its last close. After its report was finalized, it stays in that report and is not paid again: a later report lists it as In an earlier report.
Can I change a finalized report? No. A finalized report is locked. Delete it and create it again (only possible while no later period is finalized), or put the correction into a later report as an adjustment.
Do I have to use calendar months? No. A period is any range of days up to 92 days, so weekly, two-weekly and monthly periods all work. The periods of two reports cannot overlap.
I pay in an in-game currency. Can I use that? Yes. Choose No currency (points) under Currency. Amounts then show as plain numbers with up to two decimals.
Join our Discord server for support
Was this page helpful?
Last updated on