Enabling the form

The visitor form is on by default the moment your church signs up — there's no master switch to flip. What you actually need to do is grab the URL, decide where to print or link to it, and make sure your welcome team knows what to do when it pings on Sunday morning.

This page walks through finding the link, sharing it, and the handful of small decisions that matter before you send a single visitor to it.

Open the configuration page

From the admin sidebar, go to Settings → Visitor Form. You'll land on a two-card layout — the top card is the access and link section, the bottom card is the field editor we cover in Customizing fields.

Find the shareable URL

In the Access & link card, the Shareable link field shows the exact URL to send visitors to. The format depends on how your tenant is configured:

• If you've set up a custom domain and verified it, the link reads https://yourchurch.org/visitor.
• If you're using your free org subdomain, it reads https://yourchurch.geniuschurchmanager.com/visitor.
• If neither is configured yet, you'll see the bare app.geniuschurchmanager.com/visitor URL — that one works too, but visitors will see the generic GCM domain instead of your church's name in the browser bar.

Click the copy icon to the right of the link to push it to your clipboard.

TIP

A custom domain is worth the fifteen minutes of DNS work — visitors trust firstbaptist.org/visitor far more than they trust an unfamiliar SaaS URL. Custom domains are set up under Settings → Branding → Domains.

Where to share the link

The link is just a URL — anywhere you can put a URL, you can put this. The patterns that work best in practice:

• QR code on the back of the bulletin. Generate it with any free QR tool, print it large enough to scan from a chair. Label it "First time? Tell us about yourself."
• QR code at the welcome desk. A laminated card next to the visitor mug. Visitors scan it on their own phone instead of borrowing a clipboard.
• Linked from your church website. If you've built your site with the website builder, there's a VisitorFormEmbed block you can drop into any page and the form renders inline.
• Sent by text from your greeters. If a greeter takes a visitor's phone number on Sunday morning, your follow-up workflow can text them the link Monday morning. See Messaging for the send-link flow.

What visitors see

When someone opens the link on their phone, they see a single-page form with your church's logo and primary brand colour at the top — pulled live from your Branding settings. The form is responsive, works offline (it queues the submission until the browser reconnects), and supports both English and Spanish based on the visitor's browser language. They can switch languages manually at the top right.

If your church has Hierarchy & attendance turned on, the form will also ask which branch or campus they visited, and whether to mark them present at this morning's service. Both can be off by default — see that page for the toggles.

Quick checks before you send the link

Before you start distributing the URL, open it yourself on a phone and step through it end to end. Specifically check:

1. Your church logo and colour show up at the top. If not, finish setting up Branding.
2. The fields are what you expect. If you've removed optional fields or renamed any, this is your last chance to catch typos.
3. The submission works — fill it out as a fake visitor and confirm the record lands in Members → All members with member type Visitor.
4. Your welcome workflow fires if you've set one up. See What happens after submission for the trigger details.

Turning the form off temporarily

There's no global off switch, but you have two soft options if you need to pause submissions for a season:

• Set a passcode and don't share it. The URL still loads, but no one can submit without the code.
• Remove the QR codes and links from your bulletin and welcome desk. The URL still works for anyone with it, but you stop driving traffic to it.

For most churches the form just lives — on quietly, year round, ready for the next first-time guest.

Where to go next

• Customizing fields — pick what you ask for.
• Passcode protection — lock the form when you need to.
• What happens after submission — wire up the follow-up.
• First-time visitor recipe — a worked example tying everything together.
• Back to Visitor form overview.