Outreach Toolbox

The Outreach Toolbox helps the people in your church intentionally pray for and stay connected with the people God has placed in their lives: family, friends, neighbors, coworkers, and anyone they want to encourage or point toward Jesus. Each person builds a private list of contacts, chooses how often they want to pray for or connect with each one, and the app gives them a short, daily set of actions to follow through on. Relationships grow through consistency, and the toolbox keeps that rhythm so people can focus on the relationships themselves.

This page introduces the concepts shared across the toolbox and links to the documentation for each block. The blocks are designed to be used together, but can live on separate pages so you can shape the navigation that fits your app.

Key Concepts

A few shared terms make the individual block pages easier to follow.

1. Contact. A person someone is caring for. A contact is private to its owner and has its own profile: photo, key dates, social links, a personal note, and a focus for the relationship.
2. Touchpoint. A single prompt to take one small action for a contact, such as praying for them or reaching out. Touchpoints appear in a guided, one-at-a-time flow. Types include Prayer, Connection, Pulse, Reminder, and special-date touchpoints (birthday, wedding anniversary, baptism anniversary, and salvation anniversary).
3. Cadence. How often a contact should generate a touchpoint: for example Daily, Weekly, Every Other Week, Monthly, Every Other Month, or Quarterly. Cadence is set per contact, separately for prayer and connection, and can be changed or paused at any time.
4. Pulse. A periodic check-in touchpoint that invites the owner to update where a contact is in their faith journey (for example whether they have accepted Jesus or been baptized), keeping prayer and care current.

Blocks

Each block has its own page with full settings and linking details.

Building the Entry CTA (Onboarding vs Dashboard)

The toolbox has two entry blocks, and they are not interchangeable.

1. Outreach Onboarding is the on-ramp. Completing onboarding is the only thing that turns a person's touchpoint generation on, and it writes their weekly schedule and notification preferences. Send first-time users here.
2. Outreach Dashboard is the home. Once a person is set up, this is where they work day to day.

Your toolbox entry point (a launch button, tile, or routing page) should decide which block to show based on whether the person has finished onboarding. That state lives on the person's OutreachTouchpointGenerationEnabled flag, which is available in Lava. When it is true, show the Dashboard page; otherwise show the Onboarding page.

{% if CurrentPerson.OutreachTouchpointGenerationEnabled == true %}
    //- Person has onboarded: send them to the Outreach Dashboard page.
{% else %}
    //- Person has not onboarded yet: send them to the Outreach Onboarding page. 
{% endif %}

This single check also covers people who opt out: Stop All Touchpoints on the dashboard sets OutreachTouchpointGenerationEnabled back to false, so the same condition sends them through onboarding again the next time they enter. Set the Onboarding block's Completion Action to the Dashboard page so people land on their home the moment they finish.

How Touchpoints are Generated

People do not schedule touchpoints by hand. Based on each contact's cadence and the days of the week the person has chosen, Rock generates the right touchpoints automatically on a schedule and, when enabled, sends a reminder. People simply open the app and work through whatever is waiting.

For this to run, the Update Outreach Toolbox Touchpoints job must be active on the server. Schedule it to run at least hourly so that each time-of-day window can fire. The job also needs a push transport configured, and the mobile application must have its Outreach Toolbox touchpoint page set (this is the page a notification opens, and it should host the Touchpoint Detail block).

The job exposes these settings:

The three-hour settings are how you shift when morning, afternoon, and evening notifications go out. A person picks which of those windows they want; these settings decide the clock time of each window for everyone.

Notifications

From onboarding or the dashboard preferences, each person can choose:

1. The days of the week they want touchpoints added.
2. A daily reminder when touchpoints are waiting.
3. A special-events reminder for birthdays, anniversaries, and salvation and baptism dates.

Daily reminders are sent at the time of day the person selects (morning, afternoon, or evening). Special touchpoint notifications (birthdays and anniversaries) are always sent in the morning and cannot be changed.

Turning daily notifications off clears the saved time of day. People can also opt out entirely with Stop All Touchpoints and re-enable later by completing onboarding again.

Styling and Customization

The toolbox uses Rock's CSS utility classes, so it follows your app's palette and adapts to light and dark mode automatically. The illustrations (for example the welcome and schedule art) fall back to bundled defaults, but can be overridden with your own resources of the same name for a branded look.

Replacing the bundled illustrations

The toolbox ships with a fixed set of PNG illustrations baked into the app. At render time, each image checks whether a custom- prefixed copy of the same file exists in the app bundle and, if so, uses it instead. Because these resources are compiled into the shell, you cannot drop them in from Rock at runtime: send your replacement artwork to the app factory and they will bundle it into your next build.

Provide your override using the exact filename, prefixed with custom-. The full set of overrideable images is:

Tips for the handoff:

1. Match the original dimensions (1024x1024) and transparent background of the file you are replacing.
2. Use the same filename.
3. A single override file applies everywhere that image is used.