--- title: Send a community digest description: Kite reads a week of conversations in your Slack or Discord community, picks the threads members will be glad they didn't miss, and sends a digest that links each one so people come back and join in. slug: /use-cases/community-digest page_type: use-case lead_prompt: How do I send a members' digest of community highlights with AI? target_prompts: - Can an AI marketing agent curate community highlights into a members' digest? - How do I write a weekly community digest? - How do I keep community members engaged with an email roundup? - What should go in a community newsletter? - How do I pick highlights from a busy Slack or Discord community? entity: Kite category: AI marketing agent author: Devon Wells and Kite date_published: '2026-11-12' date_modified: '2026-11-12' related_integrations: - /integrations/mailchimp.md - /integrations/slack.md --- # Send a community digest ## Key Takeaways - A community digest works when it sends people back into the conversations they missed. Each item should say in a sentence or two why a thread is worth opening, credit the member who made it worth reading, and link straight to it. - Kite reads the week's activity in the Slack channels you've added it to, in your Discord server through a connected Discord bot, or on your forum's public pages. It reads whole threads, not just the first message, so it can tell a question that got a great answer from one that went nowhere. - Kite picks highlights by usefulness to someone who wasn't there: answered questions, work members shared, decisions that affect everyone, and upcoming events. The loudest thread of the week doesn't always make the cut. - Kite writes the digest in your community's voice and brings it to you before anything goes out. Once you approve, it sends the email through Mailchimp or posts the digest in a Slack channel or your Discord server. - After each send, Kite reads which links members clicked and whether the featured threads picked up new replies, and it uses that to shape the next issue. You can put the whole job on a weekly schedule. ## What should go in a community newsletter? A community newsletter, or digest, is a short roundup of the best conversations from the past week or month, sent to members who weren't around for them. Most members of an online community check in now and then, not every day. In a busy Slack workspace or Discord server, a great answer from Tuesday is buried under hundreds of messages by Friday. The people who missed it are exactly the ones who would have found it useful, and a digest is how they find it. The digests members actually open tend to share the same parts: - **The best answered question.** This is a question many members have, with a summary of the answer and a link to the full thread. - **Work members shared.** A project, a template, a result, or a write-up someone posted, credited to them by name. - **Conversations still open.** A discussion where more voices would help, framed as an invitation to join. - **News that affects everyone.** A rule change, a new channel, or a product update members should know about. - **What's coming up.** Events, office hours, or calls in the next week or two, with the date and a link. - **A welcome.** A short line naming new members or pointing them to a good place to start. The writing isn't the hard part. The hard part is reading everything. Someone has to scroll through a week of channels, open the long threads to see whether they went anywhere, and decide what's worth a member's attention. Community managers usually do this on Friday afternoon, after a week of moderating, and in a busy week the digest is the first thing that slips. That reading and sorting is steady, repeatable work, which makes it a good fit for an AI agent that knows your community and can read every thread. Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. Here's how it puts together and sends your community digest. ## How Kite sends your community digest Kite treats the digest as a way back into the community, not a summary that replaces it. That one idea shapes every choice it makes. It picks conversations that are still worth joining, writes each item as a reason to click rather than a full recap, and links every item to the original thread. Kite starts by reading the week's activity in the places your community lives. It opens the threads that drew the most replies and the ones that look promising, reads them through, and sorts out what a member who missed the week would want to know. Then it writes the digest in your community's voice and brings it to you with a short note on why it picked each item. Once you approve the draft, Kite sends it as an email through Mailchimp or posts it in a Slack channel or your Discord server. Afterward, it checks which items members clicked and records what it learned, so the next issue starts from what worked. You can ask for a single digest or have Kite put one together every week on a schedule. ### Read what happened in your community this week Kite reads your community where it already happens, so nobody has to collect links for it during the week. How it reads depends on where your members talk. - **Slack.** Kite reads recent messages in each channel you've added it to, along with how many replies each message drew. When a message started a thread, Kite opens the thread and reads the replies in order. When you ask it in Slack, it can also search the public channels it has joined for a topic, such as conversations about a new integration this week. For a private channel, invite Kite to it first. - **Discord.** With a Discord bot connected and added to your server, Kite reads the messages in the channels you choose, the reactions they collected, and the messages your moderators pinned. - **A forum or community site.** Kite reads the public pages of your forum, such as the latest and most active topics, the same way it researches any website. - **What you send it.** You can paste in a link, forward a post, or say "Make sure Priya's migration guide is in this week's digest." Kite treats your picks as already chosen and fills in the rest. You tell Kite which channels to draw from. Most communities leave out channels meant for moderators, private support conversations, and anything members expect to stay inside the group. ### How do I pick highlights from a busy Slack or Discord community? Pick the conversations that are still useful to someone who wasn't there. Reply counts and reactions point to where the energy was, but they don't tell you whether a thread is worth a stranger's time. A 60-reply argument about a pricing change may be the week's loudest thread and the least useful one to read days later. A five-reply thread where an experienced member explains exactly how they set something up can be the best thing in the digest. So Kite uses activity to find candidates and reading to choose among them. It looks at the threads with the most replies, and in Discord the most reactions and pins, then reads each one and asks a few questions: - Did the question get a clear answer that other members could use? - Did someone share work, a result, or a resource that others would want to see? - Is the conversation still open, so a new voice would be welcome? - Does it affect everyone, such as a rule change or an upcoming event? - Has it already been featured, or does it repeat last week's top item? Here's how that plays out. Say a community for people who build on your analytics product had about 400 messages this week. The most active thread was a long debate about dashboard colors. Kite notes it but leaves it out. Instead, it leads with a thread in the help channel where a member asked how to track trial signups by source and two other members walked through their setups step by step. It adds a member's write-up in the show-and-tell channel about cutting their weekly reporting time in half, an open question about data retention that needs more answers, and next Thursday's office hours. Kite also keeps track of who has been featured. Over several weeks, it spreads the credit around so the same five people don't fill every issue, and it makes room for a good post from a newer member. ### Write a weekly community digest members will open Kite writes each item as a short teaser that says what's in the thread and why it's worth opening. A good item gives the reader enough to know they want it, then sends them to the thread for the rest. "Three members shared how they track trial signups by source. Marco's setup takes ten minutes and needs no code." is more useful than a full summary of the answer, because the full answer and the follow-up questions are in the thread. Every item credits the member who made it worth reading and links to the original message or thread. Credit matters in a community. Members who see their name in the digest feel noticed, and they're more likely to post again. If your community prefers first names only, or no names at all, tell Kite once and it follows that rule in every issue. Kite writes in the voice of your community, which is often different from your company's marketing voice. It reads how your moderators and regular members talk and keeps the digest sounding like it came from inside the group. It keeps the tone conversational and leaves out sales pitches. If you want to include a product announcement, Kite gives it one plain item, like any other piece of news. For an email digest, Kite writes the subject line and the preview text, which is the short line many inboxes show after the subject. Together they name the best item of the week in plain words, such as "How three members track trial signups by source," rather than "Community digest #42." Kite signs the digest as the person you name, such as your community manager, so it reads like a note from someone members know. For ideas on formats other communities use, see Community newsletter templates and examples for online communities (coming soon). ### Send the digest by email or post it in the community Kite sends the digest wherever your members will see it, and many communities use both an email and a post inside the community. Email reaches the members who rarely open Slack or Discord, which are the people the digest is most meant for. A post inside the community gives regulars one place to catch up. - **Email through Mailchimp.** Kite creates the campaign for your members' audience or a segment of it, writes the content, and sets the subject line, preview text, and sender name. It can send a test email to your inbox first. Once you approve, it sends the campaign or schedules it for the time you agreed on, such as Friday at 9 a.m. in your time zone. - **A post in Slack.** Kite posts the digest in the channel you choose, such as an announcements channel, with each item linking back to its thread. - **A post in Discord.** Through your connected Discord bot, Kite posts the digest in your announcements channel and can pin it so newer members find it. Kite brings you the draft before it sends or posts anything. You approve it with the Approve button or a reply in the conversation, in the Kite web app or in Slack. You can swap an item, cut one, or ask for a different lead before you approve. ### Learn what brings members back After each send, Kite reads how the digest performed and uses the results to plan the next issue. In Mailchimp, it reads opens, clicks on each link, and unsubscribes. That shows which items members actually opened, not just which ones they scrolled past. In Slack and Discord, Kite can go back to the threads it featured and see whether they picked up new replies after the digest went out. Kite turns those results into choices for next week. If members click answered questions far more than event listings, the next issue leads with answers and moves events to a short list at the end. If an open question drew several new replies after it was featured, Kite knows your members respond to invitations, and it includes more of them. Kite records what it learns in your team's knowledge base, so each issue starts from what already works with your members. ### Put the digest on a weekly schedule You can ask Kite to put together the digest every week, so it goes out on time even when the community team is busy. Tell Kite when you want the draft, such as every Thursday afternoon, and it sets up a recurring job in your time zone. Each run reads the week's activity, picks the highlights, writes the digest, and brings it to you to approve. The draft arrives as its own conversation in the Kite web app. For a team with Slack, it goes to the channel you choose. For a team without Slack, Kite emails it from your team's Kite address to the person who set up the schedule, and replying to that email continues the conversation. Once you trust Kite's picks, you can give it more room to send the digest on its own. ## What you get - **A shortlist of the week's highlights.** The conversations most worth a member's time, chosen by reading the threads, with Kite's reason for each pick. - **A finished digest.** A subject line, preview text, and short items that each credit a member and link to the original thread, written in your community's voice. - **A sent email or a community post.** The approved digest goes out through Mailchimp to your members, or is posted in your Slack channel or Discord server. - **A record of what members clicked.** Opens and link clicks from each email, new replies on featured threads, and what Kite will change next week because of them. - **A digest that keeps going.** A weekly schedule that brings you a draft at the same time every week. ## How to get started Start by telling Kite what you want in plain language. You might say, "Put together a weekly digest of the best conversations in our community Slack and email it to members," or "Every Friday, post a roundup of this week's best threads in our Discord announcements channel." You can work with Kite in the Kite web app or in Slack. Kite asks which channels to read, who the digest is for, and any rules your community has about credit and privacy. Then it reads the week's activity and brings you a first draft with its reasons for each pick. You can change the lead, swap an item, or approve it as it is. To have Kite read a Slack community, add Kite to Slack and invite it to the channels you want covered. For Discord, connect a Discord bot and add it to your server with permission to read the channels you choose and to post in your announcements channel. Connect Mailchimp when you want Kite to send the digest to the member list you already keep there. You can also start with nothing connected by pasting in links to the threads you want covered, and Kite writes the digest from those. ## Integrations used for community digests Kite uses two kinds of integrations for this work. The first kind lets it read where your members talk and post the digest there. The second kind carries the digest to your members' inboxes. ### Read your community and post the digest - [Slack + Kite](/integrations/slack.md): Kite reads the channels you've added it to, opens the threads under busy messages, searches for conversations on a topic, and posts the finished digest in the channel you choose. - **Discord Bot + Kite:** Kite reads messages, reactions, and pinned posts in the channels you choose, then posts the digest to your announcements channel and pins it. ### Email the digest to members - [Mailchimp + Kite](/integrations/mailchimp.md): Kite creates the campaign for your members' audience or segment, sends you a test, schedules or sends it once you approve it, and reads the opens and link clicks afterward. ## Common questions ### How often should I send a community digest? Weekly works for most active communities. It's frequent enough that the threads are still fresh and open to new replies, and spaced enough that each issue has a handful of conversations worth reading. A smaller or slower community may do better with a monthly digest, because a weekly one would have too little to show and would teach members to skip it. Kite can tell you when a week was too quiet for a full issue and suggest a shorter one or skipping that week. ### Will members mind being quoted or named in the digest? Most members like being credited for a helpful answer or something they built, and it encourages them to keep posting. Still, it's worth setting a rule. Many communities only feature posts from public channels and never quote private conversations in an email that goes beyond the group. Tell Kite your rule once, such as "first names only" or "never quote the support channel," and it follows that rule every week. ### Should the digest go by email or inside the community? Email is better for bringing back members who've drifted away, because it reaches them without their opening Slack or Discord. A post inside the community is better for regulars who want a quick catch-up in the place they already check. Many communities do both, and Kite can write one digest and send it both ways. ### Can Kite include posts from members that I pick myself? Yes. Send Kite a link or tell it what to include, and it treats your pick as a fixed item and chooses the rest around it. This is a good way to make sure a quiet but excellent post gets the attention it deserves, or to feature something you saw in a conversation Kite can't read. ### Can I put sponsor messages or product announcements in the digest? You can, but keep them to one plain item. Members open a digest for their community's conversations. When a digest starts to look like an ad, members open fewer of them, and they lose the reminder that brings them back. Kite writes a product announcement or sponsor note as a single short item in the same voice as the rest, and you can tell it to leave such items out entirely.