Reach the members who stopped opening Discord
SummaryBot reads your week in Discord and drafts an issue from what members actually said, so the people who never log in still hear what they missed.
- $100/mo · Enterprise
- Written from real messages, with links copied from them
- You press send, not us
Why a newsletter, not another dashboard
The one message that still reaches people who stopped showing up
Members leave quietly. The issue is written for the one who stopped opening Discord.
The problem
Discord only reaches the people who open Discord. A member who misses two weeks has no thread to come back to and no reason to look, and nothing in a server goes out to them. Delivery in Discord is optional here for exactly that reason: an issue posted to a server someone has stopped reading is the one copy that does not help.
The mechanism
The newsletter is assembled from what members actually said that week, and the links in it are copied from those messages rather than composed. Shout-outs are built from messages two or more distinct people reacted to. Newcomers who introduced themselves get a welcome and a place to say hi. A section carries at most one ask, and a link glyph with no real destination behind it is stripped rather than faked.
How it works
Three things to set up once, then an issue on the schedule you choose.
Point it at your channels
Choose the channels an issue can draw from, and set the voice: community name, audience, tone, how members are addressed, what each section is called. Channels you have opted out of stay out, and so do the threads inside them. In Discord, /newsletter needs Manage Server. In the dashboard, the server owner and anyone with Administrator, Manage Server, Manage Channels or Manage Roles can edit it.
It composes the week’s issue
On your schedule, in your server’s own timezone, SummaryBot builds the issue from the week’s real messages. Every quotation has to be the member’s own words, in order, all of them (the checker forgives typography, never wording), and a paraphrase in quotation marks costs the item. A name that belongs to nobody who was there costs the item.
You review and send
Once GoHighLevel is connected and the push is switched on, each issue lands in your account as a new email draft by default, or inside your own template if you pick that on the Integrations tab, and you press Send. Prefer somewhere else? Point it at a webhook and the issue arrives as a signed event you can route yourself; posting to Discord is optional.
What is actually in an issue
Every block below is a real part of the pipeline. Nothing here is a placeholder.
- 1
Subject line and intro
Written for the week, with your own subject prefix and greeting if you set one. An unsupported fact here is reported, re-prompted once, and falls back rather than shipping.
- 2
Threads
The conversations the week was actually about, with links copied from the messages themselves: copied, never composed, and a link the checker cannot trace is dropped rather than printed.
- 3
Highlights
The moments worth reading if you read nothing else.
- 4
Stats
The numbers are copied from the deterministic stats pass; the sentence around them is written for your community.
- 5
Shout-outs
Built from three kinds of member: the ones two or more distinct people reacted to, the ones who started a real conversation, and the newcomers who just introduced themselves. Each one is written to end on a short, direct ask aimed at that person by name.
- 6
Quotes
The week’s best lines that the themes did not already cover, and only ones another member reacted to. A week with none simply has no quote block.
- 7
Upcoming events
Pulled from your public Luma calendar feed, which we connect for you, and never written by the AI. The model is not allowed to emit an event at all, and anything that looks like one is deleted from its output before the calendar’s own block is added. Third-party event titles are made inert, so a calendar entry cannot become a live link in your letter. The window counts whole days in your newsletter’s timezone. By default it opens when the issue is written; ask us and we set it to open on the day the letter is sent instead, so a letter written on Monday and sent on Tuesday leaves Monday’s events out.
- 8
Replays
Post a recording in the replays channel we set up with you and it becomes a card, with the jump link to the post it came from. The channel does not have to be one the issue is written from: its posts fill the card and nothing else, and a channel you have opted out of stays out. No model touches this block.
- 9
Editor’s note and sign-off
Your own note, in your own name.
Section names are yours to rename. The order is fixed, so an issue ends on named people rather than on a wall of counts. Thread and highlight items are written to open on a plain topic headline by default: a label in the words your members used, like “Pricing a first brand deal”, repeated rather than reworded when a topic comes back. Prefer headlines that name the stake or the question? Set Headline style to Editorial in the dashboard.
What’s included
The Newsletter plan is SummaryBot’s Enterprise tier. Here is what the plan adds.
- The weekly newsletter
- An issue composed from your community’s own messages, on a weekly, daily or manual cadence, in your server’s timezone.
- Newsletter tab in the dashboard
- Edit voice, schedule, sections and branding beside your Reports; a paused newsletter keeps its configuration.
- Custom instructions
- Two boxes: Every time, a standing note applied to every issue, and Just this week, a note for the next issue that is used once and then cleared.
- Refresh this issue
- Write the newest issue again in place (same number, same date, and the same GoHighLevel draft where SummaryBot holds its reference) with your current settings. The version it replaces is saved first, and nothing goes to your list.
- Delivery
- Your GoHighLevel account as a draft, a signed webhook, a Discord post, or any combination.
- One template, several zones
- Map each kind of section to its own slot in your existing email template, and narrow a slot to the channels you name.
- More than one letter
- A server can run several newsletters side by side. A second one is a deliberate act: run setup again with a different name, or add it in the dashboard. It carries its own channels, schedule and voice.
- Intelligence Reports
- /report: themes ranked by how many people took a side, with the sign kept so rejection shows as clearly as support.
- Saved report layouts
- Save a layout with standing instructions and reuse it on every run.
- Report delivery
- A Discord post with the full report attached, an email to an address you configure, or a native Notion page with a real table, with citations assembled from the real cited text.
- Engagement tuning
- Set which reactions count as positive and which as negative, and how hot topics are ranked.
- Forum groups
- Bundle related forum posts and analyse them as one subject.
- Custom intent taxonomy
- Configure the categories a Standard Digest classifies into and the dashboard filters by.
- Release calendar
- Keep the server’s releases on file so a report can be anchored to the ship you just made.
- Exports
- Whole-server CSV, one file per channel or one combined.
- Forum exports
- One row per post, with its reaction total and reply count, so the posts people engaged with can be ranked.
- Attachment bundling
- Export with the real attachment files included: the one export path that is Enterprise-only.
- Alerts
- Keyword, author and channel alerts, included here and on every plan.
- Privacy controls
- Exclude a channel from summaries, and its threads go with it. Ask us for a retention period and stored summaries older than it are deleted.
“Unlimited” is the monthly token allowance. A single summary still tops out at 50,000 messages and a 365-day window.
Export depth is not a plan feature: every plan honours the export command’s own 1–365 day bound.
Alerts are listed because you get them, not because this plan unlocks them: there is no tier check on alerts anywhere in the code.
More on the plan: All plans and pricing·Intelligence Reports in the guide
Who this is for
Three rooms with the same problem: the people who matter most stopped showing up.
Course and membership communities
Paid members who go quiet are the ones you least want to lose. A weekly letter reaches them where they still read, built out of the conversations their cohort was actually having.
Game studios and product teams
Players drift between patches. Anchor an issue to the week’s real threads and ship it to everyone, including the ones who are not in the server right now, with a link back to every conversation.
Large community managers
A server most of whose members have stopped opening it. Name the members the room reacted to, welcome the newcomers who introduced themselves, and give both a reason to come back.
What happens when something goes wrong
Never the same scheduled issue twice
The scheduled slot is claimed before the work starts, so a second attempt does nothing rather than queueing behind the first.
If the AI can’t run, you still get an issue
The plain digest ships as the issue, held to the same link checks as a composed one.
If something fails, a person is told
The notice goes to the last human who pressed Generate, and missing permissions are surfaced at setup while the admin is still there.
Also in the plan
Intelligence Reports
A report reads the channels you pick, over the window you set, and ranks what people raised by how many of them took a side. The newsletter tells your members what happened; a report tells you what they asked for, what broke and what they pushed back on.
Ranked by how many people took a side
Themes are ordered by the people for plus the people against, so a theme the room rejected, or split down the middle, rises instead of cancelling itself out; the Weight column, people for minus people against, keeps its sign.
Counts tallied by code
The model sorts messages into themes and names the messages behind each one; the people, message and reaction counts shown for a theme are tallied from those messages by code, and a message id the model made up is ignored. Which side a message is on is the model’s reading, and the themes table says so. Put citations in their own section and every quote there is the member’s own text, read off the message.
Three styles, three layouts
Write it for a product team (themes and decisions), as a community recap (themes, no decisions), or bugs first. Then pick a layout: the full report, Signals (positive, negative, bugs and a summary), or Bug triage (every bug, then the top friction, then what people asked for, then the summary).
Layouts you save once
Build your own on the dashboard’s Layouts tab, in the order you want and under headings you write, with theme lists as bullets or a table. Attach it to a report by name, and an edit to it reaches every report using it on that report’s next run. A layout can carry standing instructions of up to 2,000 characters: they come first on every run, and anything typed for that run is added after them.
Delivered to Discord, email or Notion
Run from Discord, it posts in the channel you ran it from, with the full report attached as Markdown and PDF. From the dashboard it can go to a Discord channel, an email address or both. A report can also be written to a native Notion page with a real table.
A Standard Digest that remembers
Like every report, it can run on a schedule or on demand: every week on a day and hour you pick, every day at an hour you pick, or whenever you press Generate now. Each item is matched against earlier weeks by its title, word for word, and the model is told to reuse an earlier item’s wording when it recurs. A match is filed as Recurring, or stays Handled if your team marked it handled on the dashboard; a new or reworded item is filed as New.
How to run one
In Discord
/report is set to Manage Server by default. Pick up to 25 channels (text, announcement or forum) and a window: a number of days, since your last release, or between two releases. Narrow it to a keyword if you like, save the setup with save_as and run it again later with saved. One report per server every five minutes.
On the dashboard
On the Reports tab, pick the channels a report reads, its layout and where it goes, then press Generate now whenever you want a fresh one.
Up to 50,000 messages per report, shared across the channels it reads.
Enterprise only: on any other plan /report answers with an upgrade prompt, and the dashboard refuses to create a report.
One plan
The Newsletter is SummaryBot’s Enterprise tier, priced as one thing.
Newsletter
AI credits
Unlimited tokens
Unlimited messages
- A weekly issue written from your community’s messages
- Drafted into your GoHighLevel account for you to send, or routed anywhere else by signed webhook
- Intelligence Reports, saved layouts, Notion and email delivery
- Whole-server and forum exports, attachments included
- Up to 50,000 messages per summary, 365-day lookback
Newsletter is SummaryBot’s Enterprise plan. Talk to us and we set it up with you. The dashboard’s Enterprise button starts a Stripe checkout only when a price is configured for it.
Frequently asked questions
Do you send the email?
No. SummaryBot never sends email to your list. It writes the issue and puts it in your GoHighLevel account: as a new email draft by default, or inside your own template if you choose that on the Integrations tab. You open it, read it, and press Send. The integration has no subject, no sender and no recipient list to work with, so it could not send even if someone tried to make it.
Where does the content come from?
The week’s real messages in the channels you picked. Every quotation has to be the member’s own words, in order, all of them (the checker forgives typography, never wording), or the item is deleted. Every name has to belong to somebody who was actually there. Links are copied from real messages rather than composed, and a link the checker cannot trace is dropped rather than printed.
What happens on a quiet week?
You still get a draft, and you decide. Blocks with nothing behind them simply do not print: no quote pool, no empty events heading, no invented shout-out from a message nobody reacted to. There is no skip command, and pausing does not skip an issue either: a pause holds the schedule where it was, so an issue whose time passes while the newsletter is paused composes shortly after you resume, unless the newsletter is saved in the dashboard editor in the meantime, which moves it to the next scheduled time after the save. An issue you do not want to send is one you delete in GoHighLevel.
Can members opt out?
Admins control it at the channel level: opt a channel out and it is excluded, and threads inside it are excluded with it. You can also run the whole letter anonymously: member names are withheld from the structured blocks the writer is given, the quote pool is dropped entirely rather than de-named, and the finished issue is re-checked for any name that should not be in it. Email recipients unsubscribe in GoHighLevel, which owns the list.
Can I change the voice and the branding?
Yes. Community name, audience, tone, greeting, what you call your members and which pronoun to use, your subject prefix, your sign-off name, your section titles and your headline style. Custom instructions has two boxes. Every time is a standing note applied to every issue. Just this week steers the next issue only: it is used once and then cleared, and the dashboard shows the note the last issue used. Both are treated as style guidance, not as instructions that can override the rules about quotes, names and links, and the writer is told a Just this week note may change what the issue leads with but may not add a fact the week’s messages do not contain.
Can I redo an issue after it is written?
The newest one, yes. Refresh this issue writes it again in place (same issue number, same date, the same week of messages as they read now) with your current settings, including a Just this week note if one is saved, which it then uses up. The version it replaces is saved first. If GoHighLevel push is on and SummaryBot holds the reference to the issue’s draft, that same draft is replaced, so edits you made to it inside GoHighLevel are overwritten; without that reference nothing is pushed, and the dashboard says which applies before you confirm. A new draft is made only when the old one can no longer be written to: you deleted it in GoHighLevel, or the connection now points at a different sub-account or a different kind of GoHighLevel object. Nothing goes to your list, your newsletter’s Discord channel or your webhook, and a refresh that cannot produce a verified issue replaces nothing. It is refused within an hour of the next scheduled issue, while something else is composing for that newsletter, and for five minutes after the last refresh.
Is the newsletter one of the Intelligence Reports?
Yes. It is the third format, beside the Standard Digest and the Custom Report, on the same plan. It works differently: a report is generated and read; a newsletter is edited, with voice, schedule and branding tuned over weeks, and its history is a run of published issues. That is why the dashboard gives it its own tab beside Reports.
Let us set up next Monday’s issue
Show us your server and we will walk through what a first issue would look like: which channels it reads, how it sounds, and where the draft lands.
Talk to us on DiscordAlready convinced? Add SummaryBot to your server