The idea for this article emerged from a simple question: What actually happens after someone clicks the "Request Prayer" button on a church website?
Behind that single click often lies a complex story—one that wasn't easy to commit to paper or a screen. We wanted to walk this entire journey through the user’s eyes: What helps them make the decision? How can they express their pain? Will they know that someone actually prayed for them? And can a simple form become the start of genuine human connection?
That is how the Prayer Space concept was born. In this edition of the One Voice 27 Lab digital laboratory, we will guide you from the very first screen to the personal prayer response: sharing our design mockups, explaining the solutions we feel confident about, and raising the questions we are still seeking answers to.
We are opening up this work to the community because these ideas are applicable far beyond a single project. Perhaps you will take an individual concept for your own church website, suggest a solution we missed, or even help us develop Prayer Space together.
So, step one: a person comes with a request for the very first time.
Before Requesting: Removing the Barriers
Imagine someone going through a tough time or caring for a sick loved one. They see an invitation to share a prayer request—under a video, on social media, or on a church website. They want to write, but hesitation sets in: Who will read this? Will I be judged? What will they do with my story?
Most websites hit visitors head-on with a blank input box. In Prayer Space, we decided to address these unspoken fears first:
Who will see my request?
Can I remain anonymous?
Will I know when someone prays for me?
The first screen explains the rules of engagement before asking for trust. We state clearly: behind this button is a real prayer team. Users choose their own privacy level and, if they wish, receive a notification once their request has been prayed over.
The main challenge here is avoiding text overload. You need literally 2–3 simple sentences that convey clarity and safety.

A question for you: If your ministry website has a prayer form, does a first-time visitor clearly understand what happens after they hit "Submit"?
Helping Formulate What Hurts
Even after deciding to reach out, people often freeze in front of a blank text box. Some prefer a single sentence ("Please pray for my family"), while others need to pour their heart out.
To ease that first step, we offer a gentle entry point:
Topic Selection: Family, Health, Relationships, Seeking God, or "Other."
Details: An optional field to add written specifics.
Voice Input: For those who find it easier to speak their pain aloud rather than type it on a keyboard.
These options are meant to act as supportive scaffolding, not a rigid survey. If someone knows exactly what they came for, they can skip the categories and jump straight to writing in their own words.
Open question: Does selecting a topic genuinely help people start, or does it add an unnecessary hurdle for someone under emotional stress? We plan to test both scenarios.
Public or Private: Giving Control Back to the User
While studying how different churches handle prayer requests, we noticed a powerful feature: some publish requests (with permission) on a public "Prayer Wall."
There is strong theological and practical reasoning behind this:
For the community: A chance to pray for one another during the week and see the real needs of a "living body."
For the newcomer: A visible sign that the church is active and that their request won't vanish into a digital black hole.
However, public exposure isn't for everyone. A request might involve deeply personal details, medical diagnoses, or third parties who never consented to public sharing.
That’s why in Prayer Space, publishing is always a conscious toggle: "Post on the Prayer Wall so the community can join in." Right beside it sits an equally clear private mode: "For the Prayer Team only."
A question for you: Which option do people choose more often in your ministry? What key information is crucial to highlight before someone clicks "Publish"?
How Would They Like to Receive a Response?
This is where the interaction logic gets truly compelling. We designed three potential response pathways:
No direct response: "I just want to know you prayed for me; I'm not ready for direct contact."
Text response: A letter or message containing a written prayer that can be revisited at any time.
Voice prayer: An audio recording where the person hears a living voice, tone, and genuine warmth from a minister.
If the user wishes to receive a response, we only ask for their email address (or preferred messaging app). If they choose total anonymity, the form submits without collecting any personal data.

A question for you: Does the impact of a prayer change when you can listen to a recorded audio message instead of simply reading text on a screen?
Behind the Screen: The Prayer Team Experience
Now let’s flip the interface and look at the process from a prayer volunteer's perspective.
The team member receives a request card containing clear context: whether it is private, whether a response was requested, and in what format. They pray right then and there—recording a brief audio prayer or typing a personalized message.
The user receives a notification. Clicking the link reveals a personal, living prayer from an actual human being—not a cold system auto-reply like "Ticket #4512 has been processed."

Design cannot replace authenticity. For this chain to work, you need trained volunteers, clear privacy guidelines, and dedicated human time. But good UI allows team members to focus on what matters most—prayer, not administration.
Can the Conversation Continue?
When someone receives a prayer response, we leave an open door. They can:
Click a "Thank You" button or send a quick reply.
Share an update on how the situation develops.
Ask a follow-up spiritual question.
...or simply close the page. And that is a completely valid outcome, too.
If a dialogue naturally begins, the interface can gently suggest next steps: Bible reading resources, a simple guide on prayer, or an introduction to a local community.
Local Context: If a request comes through a specific local church's website, a volunteer from that exact congregation responds. In time, that digital connection can naturally transition into a real-life conversation over a cup of coffee after a weekend service.
Where Can the Prayer Space Concept Be Applied?
Local Churches: Integrated into the main website or social channels.
Media Ministries: Placed directly beneath articles or videos addressing difficult life topics.
Online Courses: Offered at the end of lessons when students may be navigating personal crises.
The user journey adapts to the context: in some places, the focus will lean toward an anonymous form, while in others, it will center around a shared Prayer Wall.
Let’s Build Prayer Space Together
The mockups in this article are not a finished product—they are an invitation to collaborate and design together.
If you already run a prayer ministry: Share in the comments how your process is structured.
If you see an idea you'd like to implement: Feel free to take it and use it.
If you'd like to test Prayer Hub with us or join development within the One Voice 27 initiative: Get in touch with our team.
To close, we return to the question that started this entire journey:
If someone entrusts their pain to the church in the form of a prayer request, what experience on the other side of the screen will prove to them that they were truly heard?

Alex Kurenchuk
Editor, OneVoice27 Lab DeepVision Innovation
Helping ministries navigate AI, technology, and digital mission.
Missed our previous issues? Catch up here: |
