Your records stay yours
The temple owns its devotees, its staff records, its connected accounts and its operating history.
Software for running a temple
36 workflows work on live production. We signed in to a real workspace and ran each one through its own checks. That proves the workflow itself. It does not say that temples have taken it up, that a message reached anyone, that money settled, or that the whole product is released.
The temple owns its devotees, its staff records, its connected accounts and its operating history.
BookMyMandir takes 0% of offerings. We record how the temple works. We never become the seller and we never hold the money.
When a workflow passes on live production, that proves the one workflow and the exact limits written into its check. Nothing beyond them.
Working today
Each one runs on live production today. The limits of its check are written into our release records before the check is run, and we hold ourselves to them. This is a list of what works. It is not a list of temples using it.
Run by Temple admin, relationship staff · People records, consent, and acquisition
Open in your workspace →Run by Temple admin, data operator · People records, consent, and acquisition
Run by Comms staff, relationship staff · People records, consent, and acquisition
Open in your workspace →Run by Trustee, fundraiser · People records, consent, and acquisition
Open in your workspace →Run by Temple claimant, BMM ops · People records, consent, and acquisition
Run by Comms staff, language editor · Communications and campaigns
Open in your workspace →Run by Temple admin, seva office · Listings, bookings, darshan, and sevas
Open in your workspace →Run by Seva office, devotee · Listings, bookings, darshan, and sevas
Open in your workspace →Run by Priest, seva office, devotee · Listings, bookings, darshan, and sevas
Open in your workspace →Run by Gate staff, operations · Listings, bookings, darshan, and sevas
Open in your workspace →Run by Trustee, devotee · Offerings, donations, hundi, and receipts
Open in your workspace →Run by Trustee, cashier, accountant · Offerings, donations, hundi, and receipts
Open in your workspace →Run by Cashier, accountant, trustee · Offerings, donations, hundi, and receipts
Open in your workspace →Run by Trustee, accountant · Offerings, donations, hundi, and receipts
Open in your workspace →Run by Store or kitchen manager · Prasad commerce, inventory, and logistics
Open in your workspace →Run by Temple admin, devotee · Presence, content, ads, and connected accounts
Run by Operations, security · Temple operations and ERP
Open in your workspace →Run by Trustee, estate manager · Temple operations and ERP
Open in your workspace →Run by Procurement staff, accountant · Temple operations and ERP
Open in your workspace →Run by Staff, approver, accountant · Xalen Books, finance, tax, and payroll
Open in your workspace →Run by Accountant, procurement · Xalen Books, finance, tax, and payroll
Open in your workspace →Run by Accountant · Xalen Books, finance, tax, and payroll
Open in your workspace →Run by HR admin, trustee · People, workforce, service desk, projects, and knowledge
Open in your workspace →Run by Staff, HR admin · People, workforce, service desk, projects, and knowledge
Open in your workspace →Run by Volunteer coordinator · People, workforce, service desk, projects, and knowledge
Open in your workspace →Run by Temple user, BMM ops · People, workforce, service desk, projects, and knowledge
Run by Owner, all staff · Tenant, governance, access, and platform
Open in your workspace →Run by Owner, auditor · Tenant, governance, access, and platform
Open in your workspace →Run by Board admin, samsthana · Tenant, governance, access, and platform
Open in your workspace →Run by Trustee, managers · Tenant, governance, access, and platform
Open in your workspace →Run by Data engineer, auditor · DPDP, privacy, and legal operations
Open in your workspace →Run by Devotee, data steward · DPDP, privacy, and legal operations
Run by Owner, manager · Analytics, reporting, and forms
Run by Trustee, fundraiser · Analytics, reporting, and forms
Open in your workspace →Run by Operations, security · Analytics, reporting, and forms
Open in your workspace →Run by Temple admin, seva desk · Analytics, reporting, and forms
Open in your workspace →Controlled beta · one workflow
Write a campaign, check consent for every name on the list, and keep control of who is allowed to receive it. Sending itself is held: nothing goes out until the temple owner connects a signed Resend sending account. We do not claim that a message left our side, reached an inbox, bounced or was marked as spam.
These are the workflows we mean to build. Your staff cannot open any of them today. The three groups below say how far each one has come.
The work is finished in our code. We have not yet run and proved it on live production, so we do not count it as working.
The plumbing underneath exists. There is no screen your staff can open for this.
We intend to build this. Nothing exists for your staff today.
Start with one job to be done