Asori · Church & community operations
Asori is a church operations platform built by SomaMe. Members use the Asori app; administrators and pastors use Asori Admin. Behind both is one backend that keeps every church’s people, roles and records separate.
Asori Admin · admins & pastors
The problem
A growing congregation is run by dozens of volunteers: ushers at the gate, department heads planning Sunday, care teams calling people who missed service, a media team publishing updates, a pastor who needs the whole picture.
Most of that work happens in spreadsheets, shared accounts and personal phone contact lists. Attendance is counted on paper and typed up later. Nobody is sure who followed up with whom. Leaders see far more personal data than their role requires — or none at all.
Asori replaces that patchwork with one system where every role has its own view, its own tools and its own limits.
Who it serves
Asori models 28 church roles. They group into six kinds of work — each with its own tools and its own limits.
Join a church, keep a profile, check in, read the Bible and notes, send prayer requests and testimonies, follow church news.
Mark attendance at the gate — even when the network drops — without being able to open members’ profiles.
See the people in their care, follow up absentees, plan services and assign volunteers within their scope.
Work shared queues: prayer requests, testimonies to review, souls to verify, people to call.
Publish feeds and events, create services, manage resources and run Face Attendance enrolment.
Oversee everything in Asori Admin: membership, roles, reports, exports, dashboards and bulk SMS.
One platform, two surfaces
They are not separate products: both apps read and write the same church data, under the same permissions.
For everyone in the church
The member app is where almost all church work happens. What a person sees depends on their role in that church: a member sees their own profile and church life; an usher gets gate attendance; a department head gets their people, planning and messaging.
For administrators and pastors
Asori Admin only admits a church’s administrators and pastors. It is the oversight console: membership approvals, roles and scopes, attendance analytics, report review, custom reports and exports, and the church’s bulk SMS wallet.
How Asori is organised
Authority in Asori comes from a person’s membership in a specific church, not from their account. That is what lets many churches share one platform safely.
Illustrative example · one person, two churches
Membership lifecycle
Visitor
Browses public church life or is added at the gate or through Visitor Connect.
Request
Asks to join, or claims an existing church record.
Approved member
An administrator or pastor approves; role and scope are set.
Retired
People who leave are retired — their history is kept.
Restored
A retired member can be restored without losing the past.
What Asori does
Grouped the way a church thinks about its work. Features are normally available to the roles shown; a church can always restrict them further.
People find their church, join it and get exactly the experience their role in that church allows.
Pick a church from the list or open it from the church’s QR code or app link.
Visitors browse public church life; members request membership and an administrator or pastor approves it.
People already on the church register claim their record through identity matching, on their own or with a leader’s help.
First-time guests scan a QR code at the entrance and share their details on a web page — no app install needed.
Administrators set each person’s role and department, group or age-band scope. Members who leave are retired with their history kept.
Normally available to: Administrators and pastors
Several ways to record who was there — designed for a busy entrance and an unreliable network.
Members check themselves in from Home when they are at church (location-aware) or by scanning the church QR code; online attendance comes through Online Church.
Ushers pick the active service, search, and tap to mark members and visitors present — or switch to batch mode at a crowded door.
Normally available to: Ushers, presbytery, pastors, admins; other leaders within scope
When the connection drops, marks queue on the device with a visible pending count, then sync when it returns — with permissions rechecked first.
Opt-in, face-assisted check-in with active liveness checks, confidence-aware matching and fast fallback to the operator.
After each service Asori works out who was absent — automatically once services end — and administrators can make audited corrections.
Simulation · usher at the gate
Online — marks save immediately
Pending on device: 0
Nobody slips through the cracks — and nobody sees people outside their care.
Each leader sees only the people in their care — by department, group level or age band. An empty scope means no access.
Pick a completed service and see the absentees in your care. Call or open WhatsApp in one tap, then record the outcome so the whole care team sees it.
A list of members celebrating birthdays, with call, share and greeting shortcuts.
One service record connects planning, people, attendance and follow-up.
Public and member views of upcoming services and events.
Create one-off or recurring services and edit a single date or the whole series.
Normally available to: Media team, presbytery, pastors, admins
A structured running order built by the people responsible for the service content.
Workers answer “I’ll be there”, “Not sure” or “I can’t make it” for each upcoming service.
Leaders assign roles from the people who are available in their teams and send readiness reminders.
Live and upcoming streams, reminders and a prayer mode.
Ministry teams get shared queues instead of scattered messages.
Members submit requests; the prayer team reviews, reaches out and marks them attended in the Prayer Ward.
Members submit testimonies; the ministry reviews them in the Testimony Ward and publishes approved ones to the church feed.
Members record people they have reached; authorised leaders verify each record, which updates church totals and awards points.
The right channel for the message: feeds, targeted app messages and paid bulk SMS.
Church posts with images and video, push notifications with deep links, and system sharing.
Targeted in-app messages. Department heads can reach their own departments; church-wide sends are reserved for broader roles.
Personalised SMS to absentees, birthday celebrants, all active members or a custom list — with the exact cost shown before sending.
Normally available to: Administrators and pastors, in Asori Admin
Leaders report from their phones; leadership sees the whole church.
Period reports submitted from the phone — membership sections, souls won, converts and baptisms, transfers, Communion Sunday and custom statistics.
Pastors and administrators review submissions in one place.
Choose sections, fields and filters, preview detail rows or summary counts, and generate in the background.
Membership, demographic and service exports as CSV or XLSX.
Membership, visitors, pending approvals, recent attendance and ministry activity at a glance.
Everyday tools that make the app worth opening between Sundays.
A Bible reader with search, bookmarks and text settings.
Personal notes that work on the device, with explicit cloud sync.
Church files organised in folders for members to browse and download.
Points for timely attendance, verified evangelism and leader recognition.
How it works
One service record connects planning, participation and follow-up. Creation, content planning, attendance and reporting are separate permissions, even when they share one service.
Authorised leader
Create
A one-off or recurring service with its details and flyer.
Members
Calendar
The service appears in the Church Calendar for everyone to discover.
Workers
Availability
People answer whether they can serve.
Leaders
Assign & outline
Roles are assigned from available people; the running order is planned.
Ushers & members
Attendance
Gate, offline, self and face-assisted check-in record who came.
Care leaders
Follow-Up
Absentees become scoped follow-up queues.
Leadership
Report
Outcomes flow into dashboards and reports.
From a QR code at the door to the right experience for your role.
The entrance is the worst place for Wi-Fi. Attendance keeps going anyway.
Absence becomes a task for the right person, not a number in a report.
Face Attendance (FAM)
Status: PilotAsori’s Face Attendance pilot supports confidence-aware matching with active liveness checks, fast operator fallback, and a configurable path for high-confidence automatic marking. It is opt-in and consent-first.
High confidence
Configurable automatic marking
The pilot includes a path for recording a high-confidence match automatically — only if the church’s configuration enables it on both the app and the server, and only when the match is stable, exactly one face is in view and the active liveness challenge has passed. It comes with a short Undo and an audit entry. Otherwise the operator confirms.
Medium confidence
The operator decides
Asori shows candidates and the usher confirms the right person, rejects the suggestion or searches manually.
Low confidence
Manual attendance
Asori steps aside and the usher marks attendance the ordinary way.
Recognition runs on the operator’s phone. Camera frames are not stored, uploaded or logged.
Every mark passes the same attendance permission check as a manual mark.
The server can switch every device back to operator confirmation without an app release.
Liveness checks (turn, blink, frame continuity) are designed to stop printed photos and replayed screens.
FAM is a pilot. Whether automatic marking is switched on is a per-church configuration controlled from the server. We do not publish accuracy figures.
Photo Discovery
Status: NewMembers can choose to receive event photographs of themselves. Nothing reaches a member until a church reviewer has confirmed the match.
Member opts in
A separate consent from FAM. It can be turned off at any time.
Church connects a private folder
Event photos stay in the church’s own private storage; public “anyone with the link” folders are refused.
Processing
Photos are processed in the cloud; originals remain in the church’s storage.
A reviewer confirms
Confirm, reject, choose another member or mark unmatched. There is no automatic publishing.
Human review gate — no automatic publishing
Your Images
The member sees confirmed photos, can download or share them — or tap “Not me” to hide one and flag it.
Bulk SMS & wallet
Churches top up a shared SMS wallet and see the exact cost of every campaign before it goes.
Security & privacy architecture
Described at a public level. We do not claim certifications we do not hold.
Every church is a separate tenant. Requests are authorised against the active church and membership on the server; cross-church access is denied and tested.
28 church roles with scopes by department, group level or age band. An explicit deny overrides everything — even a pastor’s default access.
Sensitive actions are checked on the server, not just hidden in the interface. Secrets never ship in the apps.
Membership changes, attendance corrections, face-attendance decisions, photo matches, rewards and SMS money movements are recorded.
Release builds detect debuggers, rooted or jailbroken devices and instrumentation, and lock sensitive features.
Regular managed database backups; payment and SMS settlement are idempotent so retries never double-charge.
The actual product
Captured with a synthetic training identity. Church-identifying details have been cropped or masked in these marketing copies.
Evidence
Live in production with its first church partner. Every number below shows its source and date.
FAQ
Already using Asori and need help?
Asori supportAsori for your church
We will walk you through membership, attendance, follow-up and planning using your departments and roles. Every church is verified before onboarding.