Reach the members who stopped opening Discord

No. SummaryBot 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.

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.

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.

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.

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.

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.

Same plan, different surface. A report is generated and read; a newsletter is edited — voice, schedule and branding tuned over weeks — and its history is a run of published issues. The dashboard gives it its own tab beside Reports.