Scheduled Reports
Email a daily, weekly, or monthly summary of your support metrics to the bot owner
Scheduled reports send an HTML email summarising your server's support metrics on a schedule you choose. They are for bot owners who want the numbers from Stats in their inbox without opening the dashboard: how many tickets came in, how fast the team answered, who resolved the most, and how satisfied users were.
Scheduled reports is an Enterprise feature. Each server can have up to 5 reports. Reports are always sent to the bot owner's account email; there is no recipient list. Only the bot owner can create, edit, test, or delete reports. Dashboard staff see each report with an Owner only badge and cannot change anything.
Setting up a report
Open Scheduled reports
Go to General → Scheduled reports. The block shows "Reports go to" followed by the owner email that will receive them.
Click Add report
The Add a report dialog opens. Give it a Name such as Weekly summary. Names are 1 to 50 characters.
Choose a frequency and time
Under How often, pick Daily, Weekly, or Monthly. Weekly reports also ask for a Day; monthly reports ask for a Day of the month from 1 to 28. Set the Time (a whole hour, 00:00 to 23:00) and the Time zone the hour should be read in.
Pick the metrics to include
Tick at least one under What to include. Leaving all six unticked shows "Pick at least one thing to include".
Create it
Leave Send this report on and click Add report. The report appears in the list with its schedule and time zone, for example "Every Monday at 09:00 (UTC)", and what it includes.
Send a test
Open the ⋯ menu on the report row and choose Send a test email. The row shows Sending a test email…, then Test email sent. A test uses the same period and metrics as the real report and lands in the owner inbox within a minute or two. You can send one test per report every 5 minutes.
Settings
| Setting | Allowed values | Default |
|---|---|---|
| Name | 1 to 50 characters | empty (required) |
| How often | Daily, Weekly, Monthly | Weekly |
| Day | Sunday to Saturday (weekly only) | Monday |
| Day of the month | 1 to 28 (monthly only) | 1 |
| Time | 00:00 to 23:00, whole hours | 09:00 |
| Time zone | Any time zone, for example Europe/Berlin or Asia/Kolkata | your browser's time zone |
| What to include | Ticket volume, Response time, Time to solve, Staff performance, Category breakdown, Satisfaction (at least one) | all six |
| Send this report | on or off | on |
Days 29 to 31 are not offered for monthly reports so that every month delivers on the same day. Daylight saving changes are handled by the time zone you pick; the report keeps arriving at the same local hour.
What each report covers
The period ends at the moment the report is sent and reaches back depending on the frequency:
| Frequency | Period covered |
|---|---|
| Daily | The previous 24 hours |
| Weekly | The previous 7 days |
| Monthly | The month before delivery, ending at the time it is sent (for example 15 September to 15 October) |
Within that period the metrics are counted as follows:
The numbers follow the same rules as Stats, so a report and the dashboard agree for the same period.
- Ticket volume: Created and Total are the tickets created in the period, and Open is how many of those are still open. Closed counts the tickets closed in the period, whenever they were opened, like the Closed number on Stats.
- Response time: the time to the first staff reply on tickets created in the period, shown as Median, 9 in 10 within (the 90th percentile), Fastest, and Slowest. Replies slower than 7 days are left out.
- Time to solve: the time from opening to closing for tickets created in the period that are closed now, shown the same way and titled Time to close in the email. Tickets open longer than 365 days are left out. Durations under an hour display as minutes, longer ones as hours and minutes.
- Staff performance: a Top staff list of up to 10 staff members, counted like the team page: a ticket created in the period counts for every staff member who claimed, answered, or closed it, and never for the member who opened it. Each row shows their tickets, how many of those they closed, their typical (median) first reply time, and their rating with the number of ratings.
- Category breakdown: the top 5 categories of tickets created in the period, with counts and percentages. Thread tickets count under the button or option they were opened with, or their parent channel when none was recorded, like the Stats page's ticket types.
- Satisfaction: average rating out of 5, the share of positive ratings, and the number of responses. This needs Closing tickets → Ratings to be turned on for the server (see Configuration).
What the email looks like
The subject is <Report Name> - <Server name>. The email opens with a headline such as "Acme Support had 42 new tickets." and a short summary line ("30 were closed. Median first response was 12 min."), followed by a card for each selected metric.
Sections with no data for the period are omitted; if nothing is available the email says "No data is available for this period." A View analytics button opens the dashboard, and the footer carries an Unsubscribe from this report link.
Managing reports
- Pause: edit the report and turn Send this report off. The row shows Paused and nothing is sent until you turn it back on. Pausing is allowed even after a downgrade (a switch on the row), so you can always stop email.
- Edit: Edit report in the row's ⋯ menu opens the same dialog with the current values.
- Delete: Delete report in the ⋯ menu asks for confirmation ("Delete this report?"). Deleting is permanent.
- Last sent: each row shows when the report last went out, or Not sent yet. If the last delivery failed, a Last email failed pill appears next to the name with the reason on hover.
Unsubscribing and resubscribing
The Unsubscribe from this report link in the email works without signing in and needs no confirmation. It unsubscribes the owner from every report on that server, not just the one that sent the email, and the General → Scheduled reports block then shows an Unsubscribed notice with the date. Test sends are blocked while unsubscribed. The bot owner can click Resubscribe on the block to resume delivery; dashboard staff cannot.
Limits and gotchas
Reports go to the bot owner's account email only. If that account has no email address, creation succeeds but every send fails with "Bot owner does not have an email address configured". Sign in to the dashboard with a Discord account that has a verified email.
- Up to 5 reports per server. At the cap the block shows "You've reached the maximum of 5 reports." and Add report is greyed out.
- Reports are checked once an hour, so a report set for
09:00arrives shortly after nine, not on the exact minute. - If the dashboard is offline for a stretch, missed occurrences are sent afterwards, but only a limited number are caught up: about two days for daily, one week for weekly, and one month for monthly.
- Reports need a completed server setup. Creating one on an unconfigured server shows "Guild configuration not found. Please complete the initial setup first."
- After a downgrade from Enterprise, existing reports stop sending. You can still disable or delete them.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| "Please wait before sending another test report." | One test per report is allowed every 5 minutes | Wait five minutes and try again |
| Report row shows Last email failed | The last delivery failed; the hover text shows the reason | Fix the cause (usually a missing owner email or an invalid time zone) and send a test |
| No emails arrive but the row says success | The message was delivered to the owner email but filtered | Check spam and any filters for mail from ticketcord.com |
| Each report shows Owner only and has no ⋯ menu | You are dashboard staff, not the bot owner | Ask the bot owner to make the change |
| "You have unsubscribed from scheduled reports. Resubscribe to send test emails." | The unsubscribe link in a past email was clicked | Click Resubscribe on the General → Scheduled reports block (owner only) |
| The Scheduled reports block shows only an Enterprise badge, at the end of the General page | The bot owner's plan is not Enterprise | Upgrade at ticketcord.com/pricing |
| A metric card is missing from the email | No data for that metric in the period; empty sections are hidden | Nothing to fix; widen the frequency if the period is too short to contain data |
Common questions
Can I send the report to my whole team? No. Reports go to the bot owner's account email only. Forward it, or set up a mail rule that redistributes messages with the report's subject line.
What time will my report actually arrive? Shortly after the hour you picked, in the time zone you picked. Delivery runs hourly, so expect it within the first few minutes past the hour.
Why can't I choose the 31st for a monthly report? Only days 1 to 28 are available so that every month, including February, sends on the same day.
Does a daily report cover yesterday or the last 24 hours? The 24 hours before it is sent. A report at 09:00 covers 09:00 yesterday to 09:00 today. Weekly covers the previous 7 days and monthly covers the month leading up to delivery, rather than the previous calendar month.
I unsubscribed by accident. How do I get reports back? Open General → Scheduled reports for the server as the bot owner and click Resubscribe. Unsubscribing applies to all reports on that server, so one click restores all of them.
How many reports can I create? Five per server on the Enterprise plan. Each can have its own frequency, time, and metric selection, so a daily volume report and a monthly satisfaction report can coexist.
Do reports include AI token usage? No. Token usage lives on AI usage and is not part of scheduled reports.
Join our Discord server for support
Was this page helpful?
Last updated on