WWJD Works · Famplified LLC

Your privacy choices

This release uses essential browser storage and an essential sign-in cookie for secure sign-in, invitations, and your session. Our public website pages also use Google Analytics cookies to count page views. Church workspaces, account pages, and prayer, connect, and unsubscribe pages are not measured. We do not load advertising cookies.

Essential storage — always active

Authentication and security storage are needed to provide the service you request. Signing out clears the app’s sign-in session.

Campaign labels

If you arrive through a link that carries campaign labels, such as one of our ads, those labels are kept for this visit and saved with a church workspace you create, so we can tell which campaigns help churches find us. They do not identify you and are not shared with advertisers.

Language preference

Choosing a language saves that preference on this device. You can remove the saved preference below. This does not change your account or ministry records.

You can block or delete cookies, including the page-view cookies, in your browser settings.

Privacy notice · Data policy

Learning library

Keep guest follow-up in view

Link a person, assign the next step and reopen the saved guest journey.

Guests offers a staff workflow when selected for your church. Access depends on your campus permissions and the linked People record. Visitors can send connect cards from your campus links, and your church can turn on a thank-you email for card senders. Follow-up reminders appear inside the workspace.

  1. 1. Start with a person

    Sign in, choose your church and open Guests. An administrator selects Guests in Explore apps within your plan and provides the required People and Guests campus access. Choose your Campus view, then Add guest journey. Enter Journey title and choose Campus. Use Find a person and Person to select an active person at that campus. If needed, add the person in People first; contact details and email choices stay on that profile.

  2. 2. Save the next step

    Enter Visit date and Follow-up date. Choose an eligible Follow-up owner, or leave Unassigned while preparing the journey. Set Journey status and Journey privacy, then enter Next step and Journey notes. Select Save guest journey. Reopen the saved record and confirm the person, dates, owner and next step. Choosing an owner does not grant access to the person or campus.

  3. 3. Follow the in-app reminder

    Keep the journey open, assigned and dated for follow-up. The daily morning check creates an in-app reminder for the assigned owner on or after the follow-up date, while they still have access. A date saved after that morning check is picked up the next morning. Open Notifications and the Guest follow-up due link to return to the saved journey. Editing the journey replaces the earlier reminder version; closing or unassigning it stops that reminder.

  4. 4. Update or close the journey

    Open the journey, update Next step and Journey status, then Save guest journey. When follow-up is finished, choose Closed and save; reopen the record to confirm it is closed. Use Reopen guest journey when follow-up resumes. If someone else changed the journey, copy your unsaved text before reloading the saved record. Each church sees its own journeys, within current campus, People and privacy access.

  5. 5. Find and download your working list

    Use Search guest journeys, Journey status, Assigned to me and Due follow-ups only to focus your list. Choose Download journeys CSV or Download journeys JSON for all matching journeys within your current access. Downloads include private notes: share them only with authorized staff. Keep the saved journey current so your team can reopen the next step in the workspace.

Open your church workspace
Watch tutorial — Guests

Report a problem

Tell us what happened and what you expected. Please do not include passwords or private ministry details.

Page:

Your report includes this page, product, language, and your account and church details when signed in. We do not attach page contents or screenshots.