<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Posts on Mass Request</title>
    <link>https://mass-request.pages.dev/posts/</link>
    <description>Recent content in Posts on Mass Request</description>
    <image>
      <title>Mass Request</title>
      <url>https://tse1.mm.bing.net/th?q=mass%20request</url>
      <link>https://tse1.mm.bing.net/th?q=mass%20request</link>
    </image>
    <generator>Hugo -- 0.151.1</generator>
    <language>en</language>
    <lastBuildDate>Fri, 27 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://mass-request.pages.dev/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Making the Most of a Mass Request Strategy</title>
      <link>https://mass-request.pages.dev/posts/mass-request/</link>
      <pubDate>Fri, 27 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://mass-request.pages.dev/posts/mass-request/</guid>
      <description>Sending out a mass request can feel such as a shot in the dark if you don&amp;#39;t have a solid plan in place to maintain things personal and organized. It&amp;#39;s one of those tasks that sounds incredibly simple on paper—you only require a bunch of people in</description>
    </item>
  </channel>
</rss>
