RX26 is a meaningful investment of your church's time and finances, but this is an event no leader in the fast-paced digital world can afford to miss. We've compiled three high-value takeaways executives will receive from Vision Day. When you're pitching RX26 to them, share this article to help steer the conversation and bridge the gap with them. 

1. The People in the Room are Digital Pioneers

RX is where the most innovative church technologists in the country connect and collaborate. Leaders will network with pastors from churches ranging in size from 80 to 80,000 who are navigating the same questions about AI, digital ministry, and stewardship.

The relationships developed at RX are ones that will last a lifetime. 

2. Stronger Cross-Departmental Alignment

The beauty of having all your ministry teams and nontechnical roles in one place together is that everyone hears the same keynote but applies the lesson to their own role creatively. Key decision makers and your entire team will walk away with inspiration and, more importantly, alignment of your ministry's shared mission and vision.

3. Clearer Prioritization and Better Resourcing

At each conference, we unveil the newest Rock features and share the direction for what’s ahead. Vision Day gives executives visibility into Rock, so they can better understand what your church truly needs to move ministry forward.

That clarity helps pastors separate mission-critical priorities, like work that directly supports ministry outcomes, staff effectiveness, and church health, from nice-to-have improvements, such as helpful, but not urgent enhancements. With clarity on what matters most, leaders can resource their team with time, budget, staffing, or training.

Why Save Your Seat at Vision Day?

Vision Day is built for those who want to grow, learn, and steward wisely in a digital world. If your church is serious about stewarding technology with purpose and building a healthier ministry foundation, Vision Day is worth the investment. Don't just take our word for it, read about the impact it had for Brent from LCBC church.

Jon and Emily are joined by a new voice on the show, Nicole Shibata, who handles marketing, fundraising, and conference planning here at Rock. 

Jon leads the team through the most consequential three months in AI since ChatGPT launched. They talk about what shipped in the industry, why the rapid pace matters, and what church leaders need to do about it now.

Emily then unpacks Will Guidara’s Unreasonable Hospitality to understand how service is different than hospitality. This is where churches have a unique opportunity to lead because Rock empowers churches with the tools they need to intentionally care for people. The real question is whether those tools are being used to create moments that are unexpected, meaningful, and unforgettable.

Nicole closes the conversation with a look at how this concept is ingrained into the Rock Community, highlighting the recent Ambassador Kickoff Meeting.

Rock Partners

We are thankful for our Rock Sponsors and their support of the Rock Community. Visit their websites through the link above to learn how they can help your ministry and confirm that those you work with are as invested in the success of Rock as you are!

Quick Links

• Join the brand-new Rock Cast Rocket Chat channel to see what others are saying about this episode!
• Read Unreasonable Hospitality by Will Guidara to be inspired.
• Stay updated on AI by listening to Nathaniel Whittemore's AI Daily Brief podcast on Apple and Spotify.
• Subscribe to our YouTube Channel to watch Rock Cast.

We built an entire day for your church leaders to join in on the conference fun, and we need your help inviting them. We’ve gathered a compelling list of reasons for what you'll gain when your leaders are involved. 

1. Faster Buy-In for the Roadmap Ahead

Right before the conference, we're unveiling new features that will change the way you interact with Rock. Churches with Early Access will be the first to experience these features in action.

When your leadership hears the heart and vision behind these innovations as well as the Kingdom impact, they'll see exactly where each cent of their financial contribution is going.

2. A Shared Language for Data Driven Decisions

One of the most valuable outcomes of bringing your leadership is that they come home speaking the same language. RX helps develop a common vocabulary so there's one less barrier in your communication. 

Vision Day is a high-leverage moment to help them connect the dots between tools, systems, and discipleship outcomes.

3. Multiplication of Impact

When executives champion for change, it multiplies impact throughout the entire church.  Your digital ministry strategy doesn't have to rest on the shoulders of a single team but can become a church-wide initiative. Bringing your leaders to RX26 naturally opens the door for these conversations creating traction for your ideas.

Ready to Invite your Leadership?

RX26 is the best place to align strategy, build relationships and return home equipped to lead well. Our Early Bird pricing officially ends this Friday, April 10. If you're considering attending this event, now is the time to register and bring your decision makers. 

In episode 210 of Rock Cast, Jon, Emily, and Nick start with an exciting update that v19 is heading into pre-alpha. They discuss how Connections are getting a major rehaul and spend this episode diving deep into the underutilized feature, Following, that helps make Rock more than a ChMS, but a relational management system.

Following acts as a personalized digest to help you respond with care and track major life events. You can follow individuals or entire groups, creating a powerful way to ensure no one falls through the cracks. The more you use it, the more effective it becomes as a ministry presence tool.

The team then draws inspiration from Adam Grant’s book, Hidden Potential, and challenge the notion that churches lack volunteers with the reality that we simply lack the systems to develop the people before us into leaders.

This shift changes everything. It means noticing unlikely people and intentionally investing in their growth. They outline a simple framework to build a volunteer growth pathway which you can learn more about by listening to the full episode.

Rock Partners

We are thankful for our Rock Sponsors and their support of the Rock Community. Visit their websites through the link above to learn how they can help your ministry and confirm that those you work with are as invested in the success of Rock as you are!

Quick Links

• Read Adam Grant's Hidden Potential to understand the science behind finding greatness in people that others overlook.
• Get the best deal of the year with RX26 Early Bird pricing and bring your leadership to Vision Day.

• Take some time to learn about Rock's Following feature and configure it for your ministry.
• Listen to creative and powerful ways to empower your volunteers from our previous Rock Cast Episode 197.
• Sign your team up for our upcoming classes to level up their Rock skills.

In this episode of Rock Cast, Jon, Emily, and Nick describe some of the high-impact features coming to v19 and explore the challenge that every church faces. That challenge is how well-intentioned complexity creeps into systems and blocks ministry milestones.

They unpack what they call the complexity trap, the moment when tools meant to support ministry start creating friction instead. Whether it’s forms that collect unnecessary data or systems built for rare edge cases, complexity has a way of quietly growing until it overwhelms the people using it.

Jon introduces the first two steps of Elon Musk’s 5-Step Algorithm, which challenge teams to question requirements and even delete them entirely before trying to optimize or automate.

To bring the concept to life, they walk through real ministry examples, including baptism forms and children’s check-in systems, showing how removing unnecessary requirements can dramatically improve the experience for both volunteers and families.

One basic principle to keep in mind when building requirements is that every requirement needs an owner. If no one can clearly explain why something exists or what would break if it were removed, the requirement most likely shouldn’t exist at all.

Tune into this episode to learn how you can escape the trap of complexity.

Rock Partners

We are thankful for our Rock Sponsors and their support of the Rock Community. Visit their websites through the link above to learn how they can help your ministry and confirm that those you work with are as invested in the success of Rock as you are!

Quick Links

• Less than two weeks to save on RX26 before the Early Bird sale ends! Invite your leadership, local churches, and staff to experience Rock's biggest event of the year.
• Dive deep into Rock's templating language, Lava, and register for our upcoming class April 27-May 1.
• Missed our last Master Class? View the 2026 fall schedule to sign up for our upcoming classes.

Books Referenced in This Episode

• Don't Make Me Think by Steve Krug
• The Paradox of Choice by Barry Schwartz
• Cognitive Load Theory by John Sweller

As Rock continues to mature, we periodically groom the platform to ensure it remains secure, sustainable and focused on the tools churches actively use. This includes retiring legacy blocks, integrations and features that have modern replacements or are no longer widely adopted.

The items listed below outline planned deprecations and removals across upcoming releases. In most cases, these changes reflect long standing transitions that have been communicated over time, with extended opportunities for churches to migrate to newer and better options.

We know every organization uses Rock a little differently. If any of the items below would create an unexpected or significant impact for your ministry, we want to hear from you. While we cannot guarantee changes to the roadmap, we are open to feedback and committed to helping you identify alternative solutions where needed. These plans are informed by community usage research and ongoing conversations with churches across the Rock ecosystem.

If you want to hear directly from the team about how product grooming strengthens the ecosystem, listen to this Rock Cast episode:

Version 19 (Expected Release First Half of 2026)

The following features will be removed:

1. Removal of Event Registration Webforms Block - The legacy Event Registration Webforms block will be removed. As part of this transition, it will be automatically replaced with the new Obsidian block, implemented in v14, to ensure existing pages continue to function without disruption.
2. SignNow Integration - We recommend moving to Rock's built-in signature signing capability introduced in v14.
3. DotLiquid - We will be removing the code assemblies for DotLiquid. Support for DotLiquid was removed in v17. This change should only impact plugins that have yet to recompile or update.
4. Turnstile Captcha - Rock has a new built in captcha system that is replacing the CloudFlare Turnstile solution.
5. Dynamic Heat Map - The library used for this has been removed from Google Maps API.
6. System Email - This was replaced in v10 by the System Communications feature, which enables system SMS messaging. It was originally scheduled for removal in v17, but has been moved to v19.

We will be deprecating the following features:

1. Campus Service Times - This is a feature on campuses that allows you to provide a unstructured list of services times. We are encouraging organizations to move to the new Campus Schedules. Your currently configured service times will still work and be editable, but we are urging the community to move to the new solution.

Version 20 (Expected Release Second Half of 2026)

The following features will be removed:

1. Removal of the Old Rock Internal Theme - We will remove the old internal theme that was replaced in v18.
2. Delete v1 Profile Pages - We will delete the pages that were a part of the v1 person profile. These pages were replaced in v14. This will include deleting the related obsoleted blocks below:
   1. Person Profile
3. Removal of the Protect My Ministry (PMM) v1.0 Interface - PMM has released two newer versions as a plugin since it's original inclusion in core. This integration will now be fully implemented as a plugin.
4. Legacy Block Transitions - The following legacy blocks will be removed and replaced with their corresponding Obsidian blocks:
   1. Workflow Entry ⭐
   2. Contribution Statement Lava ⭐
   3. Communication Entry Wizard ⭐
   4. Group Attendance Detail
   5. Note
   6. Batch List
   7. Apple TV Page List
   8. Scheduled Transaction Edit
   9. Contribution Statement Lava ( Legacy )

Version 21 (Expected Release First Half of 2027)

1. Remove Campus Service Times - This feature was deprecated in v19 (see above).
2. Deprecate Lava Execute - We will be removing the undocumented Lava execute tag. We will be providing new Lava filters to print to ZPL and Base64 encode strings as this command was sometimes used for those activities.
3. Remove FontAwesome - Rock moved to the Tabler icon set in v18. We will be dropping core support for FontAwesome, but organizations are welcome to implement it themselves.
4. Webforms Check-in - We will be removing the legacy webforms/workflow based check-in. Organizations must use the new NextGen check-in that was introduced in v17.
5. Wi-Fi Captive Portal - Core features that are a part of the Wi-Fi Presence features will be removed. The Wi-Fi Presence service from Ministry Dynamics is no longer using these features.
6. Legacy Block Transitions - The following legacy blocks will be removed and replaced with their corresponding Obsidian blocks:
   1. Group Scheduler ⭐
   2. Dynamic Data ⭐
   3. Page Parameter Filter ⭐
   4. Group Placement
   5. Connection Request Detail - This will be replaced by the Connection Request List block that will auto-open to the request details.
7. Blocks Removed With No Replacement - The following blocks will be fully removed from Rock with no replacement. This cleanup supports our ongoing transition to Obsidian and helps reduce long term maintenance of legacy functionality. Community surveys and usage research indicate these blocks are rarely used. To help you validate impact in your own environment, we have included a SQL statement below that you can run to identify whether any of these blocks are currently in use.
   1. Group Member Link
   2. Package Detail Lava
   3. Groups Context Setter
   4. Person Transaction Links
   5. Related Entity Connect
   6. Related Entity List
   7. Rock Modal Gallery
   8. ViewState Viewer
   9. Sample Linq Report
   10. RSS Feed
   11. RSS Feed Item
   12. Person Context Setter
   13. Account Detail (Security)
   14. Date Range Context Setter
   15. Defined Value List Lava
   16. Connection Request List Lava
   17. Prayer Request List Lava
   18. Link List Lava
   19. Tags (not the feature, this is a specific very rarely used block)
   20. Content Channel Item Personal List Lava
   21. Dashboard Blocks - These blocks were created in the early days of Rock. We recommend transitioning to Lava using the Chart shortcode.
       1. PieChartDashboardWidget
       2. BarChartDashboardWidget
       3. LineChartDashboardWidget
       4. LiquidDashboardWidget
       5. Dynamic Chart
   22. Campus Schedule Context Setter
   23. Package Rating
   24. Person Attribute Forms
   25. Check-in Manager Person Location
   26. Activate Workflow
   27. Stark Detail
   28. Stark List
   29. Captive Portal
   30. Giving Type Context Setter (functionality moved into the Transaction Report block)

Below is a SQL statement that we formulated to help you know if you're using any of the proposed blocks to be removed. It will tell you if the block is on a page in your instance and if so how many times that page has been visited in the last 30 and 90 days.

SELECT
    CASE WHEN [PageCount] = 0 THEN 'GREEN'
        WHEN [PageViewsInLast90Days] = 0 THEN 'GREEN'
        WHEN [PageViewsInLast30Days] < 50 THEN 'YELLOW'
        ELSE 'RED'
        END AS [Status]
    , [Name] AS [BlockName]
    , [Category]
    , CASE WHEN [PageCount] = 0 THEN 'You are not using this block.'
        WHEN [PageViewsInLast90Days] = 0 THEN 'This block is on a page, but there are no page views in the last 90 days.'
        WHEN [PageViewsInLast30Days] < 50 THEN 'This block is on a page, but has less than 50 page views in the last 30 days.'
        ELSE 'This block is on a page and is getting more than 50 page views in the last 30 days.'
        END AS [Message]
    , [PageCount] AS [Number of Pages With This Block Type]
    , [PageViewsInLast30Days]
    , [PageViewsInLast90Days]
FROM (

    SELECT
        bt.[Name]
        , bt.[Guid]
        , bt.[Path]
        , bt.[Category]
        , (SELECT COUNT(*) 
            FROM [Page] p 
                INNER JOIN [Block] b ON b.[PageId] = p.[Id] 
            WHERE b.[BlockTypeId] = bt.[Id] 
            ) AS [PageCount]
        , (SELECT COUNT(*) 
            FROM [Page] p 
                INNER JOIN [Block] b ON b.[PageId] = p.[Id] 
                INNER JOIN [InteractionComponent] ic ON ic.[EntityId] = p.[Id]
                INNER JOIN [Interaction] i ON i.[InteractionComponentId] = ic.[Id]
                INNER JOIN [InteractionChannel] ich ON ich.[Id] = ic.[InteractionChannelId]
                INNER JOIN [DefinedValue] mdv ON mdv.[Id] = ich.[ChannelTypeMediumValueId]
            WHERE 
                b.[BlockTypeId] = bt.[Id] 
                AND mdv.[Guid] = 'e503e77d-cf35-e09f-41a2-b213184f48e8'
                AND i.[InteractionDateTime] >= DATEADD( day, -30, GETDATE())
                ) AS [PageViewsInLast30Days]
        , (SELECT COUNT(*) 
            FROM [Page] p 
                INNER JOIN [Block] b ON b.[PageId] = p.[Id] 
                INNER JOIN [InteractionComponent] ic ON ic.[EntityId] = p.[Id]
                INNER JOIN [Interaction] i ON i.[InteractionComponentId] = ic.[Id]
                INNER JOIN [InteractionChannel] ich ON ich.[Id] = ic.[InteractionChannelId]
                INNER JOIN [DefinedValue] mdv ON mdv.[Id] = ich.[ChannelTypeMediumValueId]
            WHERE 
                b.[BlockTypeId] = bt.[Id] 
                AND mdv.[Guid] = 'e503e77d-cf35-e09f-41a2-b213184f48e8'
                AND i.[InteractionDateTime] >= DATEADD( day, -90, GETDATE())
                ) AS [PageViewsInLast90Days]
    FROM
        [BlockType] bt
        LEFT OUTER JOIN [Block] b ON b.[BlockTypeId] = bt.[Id]
    WHERE
        bt.[Guid] IN (
        'FAFBB883-D0B4-498E-91EE-CAC5652E5095',
        '9AAA967C-D0B0-4E42-89DE-2AE6AAFC17EF',
        '62F749F7-67DF-4A84-B7DD-84CA8E10E205',
        '9EC29D0F-7EE7-434B-A30F-6C36A81B0DEB',
        '62F749F7-67DF-4A84-B7DD-84CA8E10E205',
        '2BB707AC-F29A-44DF-A103-7454077509B4',
        '5F40F4FD-338A-4711-87F7-980ED1FAE615',
        '28516B18-7423-4A97-9223-B97537BD0F79',
        'CDDE32B6-CDC2-4869-AA39-35DB97D3A59F',
        '268F9F11-BC74-4E86-A72D-6AA668BF470D',
        'E98E0584-0D87-4DC6-9085-DC93F17AFB7F',
        '2760F435-3E89-4016-85D9-13C019D0C58F',
        'F7898E47-8496-4D70-9594-4D1F616928F5',
        'EA33088D-7B18-46A7-ADFA-B9DA9512B4A4',
        'B37DC24D-9DE4-4E94-B8E1-9BCB03A835F1',
        'ABC4A04E-6FA8-4817-8113-A653251A16B3',
        'C4ADDDFA-DF16-467E-9285-B1FF0FC066ED',
        'E6BAA42C-D799-4189-ABC9-4A8CA1B91D5A',
        '341AAD88-47E0-4F25-B4F2-0EBCE5A96A1D',
        '4E3A95C6-AB63-4920-9EA6-FA5F882B13AD',
        '0ADBF632-D54D-42D5-A8A1-517E95DDFDB1',
        'AC19A4F3-2E88-487E-8E88-377C1C20DBD5',
        '7BCCBFB0-26A5-4376-B1F3-DC6ADD7C3723',
        'A0405364-C722-495B-879C-C57B5BC5E213',
        '9EC29D0F-7EE7-434B-A30F-6C36A81B0DEB',
        '5A7C11C2-4E9F-4AF6-8149-CB2093CE9727',
        '5464f6b3-e0e4-4f9f-8fba-44a18db83f44',
        '00fc1dea-fe34-41e3-bc0a-2ee9138091ec',
        '83cb0c72-4f0a-44a7-98d0-260ce33788e9',
        'a7961c9c-2ef5-44df-bea5-c334b42a90e2',
        'af0b20c3-b969-4246-81cd-76cc443cfdeb',
        'bba9210e-80e1-486a-822d-f8842fe09f99',
        '13e4d4b5-0929-4ed6-9e59-05a6d511fa06',
        '351004ff-c2d6-4169-978f-5888beff982f',
        'ccfcd227-c8f9-4952-8ac5-e427d519ee47',
        '57b00d03-1cdc-4492-95cf-7bd127ce61f0'
        )
    GROUP BY 
        bt.[Name], bt.[Guid], bt.[Path], bt.[Category], bt.[Id]
) x

A sponsored Blog Post by 9 Embers

Strong onboarding doesn’t happen by accident. Whether you’re coordinating dozens of volunteers or equipping those who serve vulnerable populations, a thoughtful process ensures safety, consistency, and confidence. When expectations are clear and each step is defined, volunteers feel equipped, staff stay supported, and ministry teams function smoothly.

Some volunteer roles require only a few steps, while others—especially those serving children or vulnerable populations—require a more detailed, multi-tiered approach. The flowchart below shows an example of what a full process can look like when mapped out.

Step-by-Step Overview

From initial engagement to serving, several Rock tools work together to guide volunteers through each stage. Below is a high-level walkthrough of the process. Each step corresponds to the flowchart and can be explored in more detail in our full article.

Step 1: Initial Engagement

A potential volunteer selects a role on the Serve page and submits a simple form. This automatically creates a Connection Request. Configured statuses and badges help connectors quickly see membership status and determine next steps.

If the individual isn’t a member, the request is routed appropriately for follow-up before progressing further.

Step 2: Application & Requirements

The connector sends a pre-filled email linking to the correct volunteer application (adult or minor) via a workflow. Automated reminders ensure follow-up after 7 and 14 days. When the application is complete, a badge updates on the Connection Request. 

Next, the connector manually launches a background-check workflow. After clearance, another workflow sends training videos, quizzes, and reference-request links. Quiz scores and reference submissions automatically notify the connector without generating extra Rock records or clutter.

Step 3: Group Scheduling & Serving

The connector invites the volunteer to an orientation or training event using a workflow that links directly to available dates. Attendance is tracked through check-in and stored on a person attribute, which updates the badge and moves the volunteer to a “Ready” status.

A final workflow then adds them to the appropriate scheduling team—officially completing the onboarding cycle.

Where to Start

If building or refining your onboarding process feels overwhelming, start small. You can read in-depth about the process in the flowchart or download a PDF from our article. Begin by:

• Building volunteer applications in Registrations
• Creating Serve Opportunities that open Connection Requests
• Enabling Group Scheduling

Each small improvement builds toward a scalable, safe, and effective process—one that ensures your volunteers are prepared and your vulnerable populations are protected.

In episode 208 of Rock Cast, Jon and Emily tackle a hot topic in tech right now, vibe coding, and explore what it means for church software and digital ministry. They also share updates on v18.2, give an early preview of what’s coming in v19, and revisit the importance of Rock’s Early Access program and generosity‑based funding model.

Jon defines vibe coding as the rapid iteration with AI that prioritizes experimentation over planning, and speed over structure. Inspired by the AI Daily Brief Podcast, they spend this episode discussing whether software is dead and if our churches should stop buying software, and instead, start vibe coding.

They make an important distinction: you can vibe code features, but you cannot vibe code systems. Systems require planning, constraints, and engineering foresight that cannot be hurried or improvised without risk.

For example, you might experiment with a new UI for event sign up but you should never vibe code areas that require critical logic like care, confidentiality, and money.

Tune in to this interesting discussion to hear what vibe coding means for Rock churches, how to use it safely, and Rock's future plans for AI.

Quick Links

• Check out the AI Daily Brief Podcast to hear why vibe coding is panicking the market.
• Update your Annual Commitment from your Community profile to enjoy Early Access.
• Not able to give at the recommended rate? Apply for a grant today.
• Purchase your RX26 tickets before early bird pricing expires!

In episode 207 of Rock Cast, Jon, Emily, and Nick dive into a blend of technical updates and visionary strategy. From the v17.7 bug fix and new features in v19 to updates on Short Links and AI agents, there’s a lot to unpack. They also offer fresh insight into the Essentials model and talk about what the most successful churches on Rock have in common.

Nick kicks things off with a preview of what’s coming in v19, including performance improvements to Group Scheduler, helpful new Person Merge features like email notifications, and more.

Jon then turns the conversation toward a recurring theme in the Community: technology complexity. He shares that historically, cost has been the biggest barrier for churches adopting enterprise‑level software. Now that Rock's donation‑based model removes that barrier, perceived complexity is what hinders churches from adopting Rock. He shares three main sources of complexity and why Spark's transition towards the Essentials model can help resolve this issue.

Emily also shares details about the upcoming Ambassador program, a new initiative to train Community members to help cast vision for Essentials churches and guide new adopters with clarity and care.

Rock Partners

We are thankful for our Rock Sponsors and their support of the Rock Community. Visit their websites through the link above to learn how they can help your ministry and confirm that those you work with are as invested in the success of Rock as you are!

Quick Links

• 20% of the Renaissance Hotel filled up in just one month! Don't wait to register for RX26 and book your stay now for the most affordable pricing!
• Visit rockrms.com to browse our new website.
• Learn more about the changes to Short Links and best practices.

A Sponsored Blog Post by Triumph Tech

Traditional digital strategy is no longer the answer. With the emergence of AI agents, churches will be left behind unless they make a radical shift in their digital spaces. Just as predicted at RX25 by Jon Edmiston, Dwell Community Church has already been experiencing the negative impact of AI on their online traffic. What has happened to them is not unique, but what they did about it is.   

Keep reading to learn how this church successfully pivoted their strategy and how you can do the same.

Why Clicks Are Vanishing

In May 2024, Google rolled out a game-changing feature, Gemini AI Summaries, which altered how people interact with websites. Instead of clicking through to search results, visitors are served AI-summarized responses directly at the top of the page.

Dwell Community Church soon felt the harsh reality of this change.

• Click-throughs tanked 40% year-over-year
• Impressions dropped by 17%
• On-site searches declined by 21%

Less people are seeing a link to their site and it's clear they aren't navigating digital forums the way they used to. Unfortunately, visitors are no longer landing where their church faithfully created resources to meet them.

You can learn more about the full extent of the impact they experienced in the post The Digital Ministry Blind Spot That AI Just Exposed.   

How Dwell Pivoted Their Digital Ministry

Dwell Community Church didn't lose heart though and didn't panic. Instead, they saw a new vision for their ministry and reimagined an engagement strategy that worked.

They moved away from a disconnected non-native mobile to a Rock-powered native experience that far outperformed AI. Within a year, these are the results of their strategy. 

• Page views surged by 1,040%
• App downloads tripled
• Unique active devices more than doubled
• Unique active people grew by 80%

People aren't just finding their app; they're also engaging with it taking church beyond the walls of their sanctuary and into their daily lives.

• Unique sessions increased by 416%
• Interactions skyrocketed by 751%
• Their teaching library gained momentum with 40,000 taps and 70,000+ views

Learn more about Dwell Community Church's win by reading the blog, 8.5x More Interactions: What Happens When Ministry Meets Rock Mobile.

The Moral of the Story

The reality is that even the most thoughtful, truth-filled content is being bypassed when AI owns the interaction.  ChatGPT, Gemini, and other AI tools scrape your content without sending seekers to your site, your resources, or your community. These AI agents don’t point people toward the Church or even your website. 

Relying solely on website traffic or search visibility isn't a sustainable strategy. Let a Rock Mobile app be the next investment you make for your ministry. From Starter Apps to custom apps, you can find a mobile solution  designed to fit your budget.   

Dwell Community Church established a digital outpost they control. Their mobile app is a stable, branded space where their teaching isn’t diluted or displaced; where their people are engaging like never before.  

Now is the time for you to evaluate your digital outreach and build a ministry platform that is immune to the impact of AI changes.