What Happens After Someone Hits Submit

It’s easy to describe software in terms of features — a form, a moderation queue, a wall — without ever saying what it’s actually like to watch a single request move through the system from start to finish. So here’s that, in order.

Someone fills out the form. It’s short on purpose: what they’d like held in prayer, who should see it, and, optionally, enough contact information that your team can follow up if they’ve asked for that. There’s no account to create and no required field that doesn’t need to be there. The moment they submit, the request lands in a queue — not on any public page, not in anyone’s inbox, just in the plugin’s own moderation view inside WordPress.

That’s where a person comes in. Someone on your care team — however you’ve assigned that role — opens the queue and reads the request. This is the step that can’t be automated and shouldn’t be: they’re deciding whether it’s ready to be shared at the level the person asked for, whether it needs a private conversation before anything else happens, or whether it’s something the whole team should be aware of quietly, without it ever becoming public. Most requests move through this step in minutes once someone’s looking at the queue; how often that happens depends entirely on how often your team checks it; nothing about the plugin sets that rhythm for you.

Once approved, a request that was marked shareable appears on the prayer wall — anonymously or by name, exactly as the person chose. People can pray for it there, and that act is logged quietly rather than displayed as a running counter; we didn’t want a prayer wall that felt like a leaderboard. Requests that were kept team-only never reach this page at all; they stay exactly where the person asked them to stay, visible only to the people caring for them directly.

The story doesn’t have to end at approval. If the person opted into follow-up, your team has a way to circle back — a private note, a check-in, a “how are you doing” that doesn’t get lost the way it would in a shared inbox three weeks later. That’s the piece most systems don’t have at all, because most systems were never built to hold a request past the moment it was received.

Nothing here happens automatically end to end, and that’s deliberate. A person decides what’s shared. A person reviews it. A person follows up. The software’s job is only to make sure the request survives long enough, and clearly enough, for those people to actually do that.