Because it isn’t one. Foldmetric does attendance and absence follow-up, properly, and nothing else — no giving, no rotas, no website builder, no children’s check-in labels. If you need all of that, buy a platform. If you bought a platform and nobody uses its attendance module, Foldmetric is the part you wanted.

No. Foldmetric is designed to sit alongside whatever you already run. Import your roster from a spreadsheet export, and take the absence list back out as CSV. On Growth you can sync through the API instead.

A record in your directory. Not a check-in, not an admin, not a visitor who registered once and never came back — you can archive those, and archived records don’t count. If you cross a tier boundary we’ll tell you before we bill you, not after.

No, and this is deliberate. Check-in is a web page — one field, no account, no download, about 80 kB. Members scan a QR code or type your address; it works on an eight-year-old Android on a saturated church wifi, which is the actual test. You can add it to a phone’s home screen if you want, but nobody has to.

One code, printed once, taped by the door — it never changes, so a sign lasts. A member scans it and gets one field: phone number or email. No app, no account, no password. The page is about 80 kB, which is the difference between working and not working on a saturated church wifi. Download the printable sheet from your dashboard; it comes with your church’s name and logo above the code.

They add themselves — a number the roster has never seen is asked for a name, and that is the whole form. No dead end, no queue at the welcome desk. Everyone who arrives that way is marked as self-registered, so your first-timers are a list you can filter rather than a face two people half-remember. From that first scan they are counted like anybody else, which is how you notice the visitor who came twice and stopped.

Attendance is one Sunday; engagement is the pattern across many. Foldmetric keeps the record per person and per service, so you see an x of y ratio over the period, a run of consecutive misses, how long since anyone last saw them, and turnout per service. That is what makes “three misses in a row” a different problem from “three scattered across a quarter” — one is drifting, the other is a busy season.

Not yet, and we would rather say so than let you find out. What ships today is the check-in, the directory, the absence list and the report — you choose who to contact and reach them however you already do. The settings for automated follow-up are in the dashboard (channel, and how many consecutive misses qualify somebody), and sending is what we are building next. It is included from Core when it lands; the messages themselves will be billed as credits at the rates above, because every send has a real cost. Nothing on your plan changes when it arrives.

Your admins, and nobody else. The directory is never readable from a browser, so the public check-in page can confirm that a number belongs to a member without ever being able to list the congregation. Failed lookups are throttled per connection to stop anyone probing it.

Yes. You choose which days count as services and, optionally, a time window for each. The schedule is evaluated in your own timezone on our servers — so someone changing the date on their phone can’t check in on a Tuesday.

Your rate is set by the country your church is in, not by where you happen to be browsing from. Africa, South and South-East Asia, and Latin America pay the regional rate in local currency, through local payment rails. Same product, same servers, same support.

You export it — every view, any time, on every plan including Free. There’s no export fee and no wind-down period where the data is held hostage. Delete the account and it’s gone from our systems.