Onboard your parish · QStone Network

1

Parish identity

Full parish name (English) *

Short name *

Name in native script

Tradition *

2

Location

Street address *

City *

State / Province *

ZIP / Postal code *

Country *

3

Public contact

Shown to parishioners on your portal + in the app

Phone *

Public email *

Website

Diocese / jurisdiction

4

Your main contact

Who we coordinate the setup with

Your name *

Role / title

Your email *

Your phone

5

Portal administrator

The first login we create for your parish

Administrator name *

Administrator email *

6

Your parish, at a glance

A few quick facts so we can size your setup. Everything below is optional — share what you can.

About how many families / households belong to your parish?

Languages used IN your services (spoken/sung)

Languages for printed materials (certificates, bulletin, email)

More detail (optional) — helps us tailor your setup

Roughly how many individual members would be in the directory?

Typical weekly Sunday Liturgy attendance?

7

Your member / family list

Usually the biggest piece to migrate — tell us where your people list lives today and we'll handle moving it in.

Where is your member / family list kept today?

Can you export that list to a CSV / Excel file?

More detail (optional) — helps us tailor your setup

Which info does your list include?

Do most members have email/mobile we can message — and have they opted in?

Most have email + phone, opted in Most have contact info, consent unclear Email only / few phones Very little contact info on file Not sure

8

Donations & giving

How you take donations now, and how much history to carry over so year-end tax letters stay accurate.

How do you accept giving today?

Where does your donation / giving history live today?

How far back should we import donation history?

What giving funds / categories do you use?

More detail (optional) — helps us tailor your setup

Do you issue year-end tax statements — should the portal take that over this year?

Yes — portal should issue them this year Yes — but our old system covers this year No — we don't issue them Not sure

Roughly how many recurring / auto-giving donors do you have?

9

Website, domain & email

Where your parish lives online today — this decides whether we use your own domain or a QStone subdomain, and who makes DNS changes.

Do you own a parish web domain (e.g. yourparish.org)?

Yes — we own a domain No — we'd use a QStone subdomain Not sure

Who controls your domain / DNS settings (where domain records are changed)?

How do you email parishioners today?

More detail (optional) — helps us tailor your setup

Do you have a website — on what platform?

What should we do about your current website?

Replace it — the portal becomes our main site Keep it — just add a link to the portal Keep it for now, revisit later No website — the portal will be our first Discuss on a call

Is there a parishioner email/contact list to import, and where does it live?

Do you have a parish logo and brand colors?

You can email logo/brand files to info@qstonenetwork.com after submitting.

10

Calendar, services & records

How you run your schedule and services now, and how your sacramental register books should move over.

How are your sacramental records (baptisms, weddings, funerals, slavas) kept today?

Carry historical records INTO the portal, or record new ones going forward only?

Carry over all historical records Carry over recent years only New records only from go-live; keep old books as-is Not sure

More detail (optional) — helps us tailor your setup

How do you manage your parish calendar / schedule today?

Which services do you actively schedule / track?

11

Who will use the portal

Your main contact and admin login were collected above — this is the rest of the team and who signs off.

Who should have full admin access (manage users, settings, finances)?

Who has final sign-off on going live? (name + role)

More detail (optional) — helps us tailor your setup

Anyone else who needs an account? (name, email, role)

How comfortable is the day-to-day person with new software?

Very comfortable — minimal help needed Comfortable with basic apps (email, Facebook) Needs step-by-step help and training A volunteer / family member handles tech No one identified yet

12

Launch plan

What to build first, when you need it, and anything that could hold us up.

Which features do you want LIVE at launch?

When would you like to be live?

Anything that might block go-live right now? (honesty helps us plan)

No website domain yet No bank account ready for Stripe yet No EIN / authority to set up our own Stripe yet Member data is on paper / not digital Need diocese or council approval first Limited staff time to help with setup No blockers — we're ready Other

More detail (optional) — helps us tailor your setup

Of those, which ONE matters most for go-live? We'll make sure it's solid first.

What's the #1 thing about your current setup you most want fixed?

Any event or date driving your timeline?

Which pricing tier are you expecting, based on size & support?

13

Preferences & agreement

Online payments (Stripe) *

We'll use our own Stripe account (recommended) Help us set it up later

Email sending *

Send from our own domain Use a qstonenetwork.com address (simplest)

Launch visibility *

Soft-launch — hidden until we verify together Public immediately on launch

Type your full name as signature *

Your role / title

Please review the QStone Master Services Agreement & Terms of Use (opens in a new tab) before accepting.

I am authorized to bind this church, and I have read and agree to the Master Services Agreement & Terms of Use and the Privacy Policy.