Reports
Send analytics and SEO summaries on a schedule by email, WhatsApp or Telegram, opening with a plain-language AI read of the period.
A scheduled report emails your headline numbers, an SEO summary, and a spreadsheet of the detail — on a schedule you choose. It's built for the people who want the numbers but never log in: a client, a manager, a stakeholder who reads email and nothing else.
#Creating a report
Open Reports in the sidebar and choose New report. Each report belongs to one workspace and covers either every site in it or a specific selection.
- Name — how you'll tell it apart from your other reports. It doesn't appear in the email.
- How often — daily, weekly, or monthly.
- Sites — leave empty to include every site in the workspace, including ones you add later.
#When reports arrive
Reports are sent in the morning, UTC. What each one covers follows from its frequency:
- Daily — every morning, covering the previous 24 hours.
- Weekly — Monday mornings, covering the previous week.
- Monthly — the 1st of each month, covering the previous month.
Daily is the most frequent option available. No report is ever sent more than once in a 24-hour period.
#Email, WhatsApp and Telegram
A report can go out by email, WhatsApp, Telegram, or any mix of them. They carry the same numbers in the form each medium suits:
- Email — the full summary, the SEO table, and the spreadsheet attached.
- WhatsApp — headline numbers, the top three SEO movers, and the dashboard link. No attachment: a spreadsheet in a chat thread is rarely opened.
- Telegram — headline numbers, the AI summary, the top SEO movers, and links to the full report and the live dashboard.
#Sending reports to WhatsApp
WhatsApp is an app you connect once per workspace, on plans that include it. Open Apps → WhatsApp, turn it on, and add each number that should get reports. Quantalog sends a 6-digit code to that WhatsApp; enter it to verify the number. Then, in a report's Delivery settings, turn on WhatsApp and tick the numbers it goes to. You can add up to 10 numbers per workspace.
#Sending reports to Telegram
Turn on Telegram under delivery and tick the chats the report goes to. With the Quantalog bot you can link a new chat right there:
- Your own chat — press Connect my chat. Telegram opens the Quantalog bot; press Start and come back. The chat appears in the list, already ticked.
- A group — press Add to a group and pick the group in Telegram. Everyone in it sees the report, which suits a team or a client group.
Linked chats belong to the workspace's Telegram connection, so any report can tick them and form alerts can use them too. Send /stop to the bot in a chat to stop messages there.
#Who receives it
You always receive your own reports. Beyond that, add any address you like — recipients don't need a Quantalog account, and never see your dashboard unless you explicitly include a live link.
Every email carries an unsubscribe link, and recipients can remove themselves without signing in. Someone who unsubscribes stays visible in your recipient list, marked as opted out, so a report that stopped arriving is never a mystery. Re-adding them by hand won't resubscribe them — that choice is theirs to reverse.
#What's in the email
Each section is optional, so a report can be as narrow as you want.
- Analytics summary — visitors, pageviews, sessions, bounce rate, average session, and pages per session, each with its change against the previous period.
- AI summary — a short plain-language read of the period at the top of the email. See below.
- SEO scores — the latest score for each audited page, and how many points it moved since the last report.
- Spreadsheet attachment — an
.xlsxfile with the summary plus a sheet per breakdown: top pages, referrers, channels, countries, devices, browsers, goals, and SEO. - Live dashboard link — a button opening your public dashboard.
#The AI summary
Above the numbers, each report opens with two or three sentences in plain language: what changed over the period, the most likely reason for it, and one thing worth doing about it. It exists because a table of figures tells you what happened and leaves the why as homework — and most people reading a forwarded report never get that far.
A real example, from a week where a link did well:
It is written by a language model reading the same figures you can see in the email, and it is labelled AI summary wherever it appears. That label is deliberate: the paragraph draws conclusions about cause, and a conclusion drawn from traffic data can be wrong. Treat it as a starting point for a look at the dashboard, not as a finding.
- It only uses your own figures. The model sees the same headline numbers and breakdowns that appear in the report, and nothing else — no data from other workspaces, and nothing from outside Quantalog.
- It stays quiet when the data is thin. Below about thirty visitors in the period, every percentage swing is noise, so the summary is left out rather than inventing a story about a handful of visits.
- It says so when nothing happened. A quiet week gets one sentence saying exactly that, with no recommendation attached.
- It never delays your report. If the summary can't be written, the report goes out on time without it.
The summary is on by default and needs the analytics section switched on, since it's written from those figures. Turn it off per report with the AI summary checkbox under What to include — worth doing if you send reports to clients under your own name and would rather write the commentary yourself.
It doesn't count against your Orbit AI question allowance. A report you scheduled shouldn't spend the questions you were going to ask.
#Testing before it goes out
The send icon on any report mails a copy to you immediately, marked as a test. It's built from exactly the same data and template as the real thing, so what you see is what your recipients will get. Test sends go only to you — never to the rest of the list. For Telegram, choose Send Telegram test from the report's menu to post a test copy to its chats.
#Pausing and deleting
Switching a report to inactive keeps every setting and recipient but stops delivery, which is the right move for a client project on hold. Deleting removes the schedule and its recipient list for good.
If a send fails — a mail server rejecting an address, most often — the report shows a warning icon with the reason, and tries again on its next scheduled run rather than retrying immediately.