# Temple Church Management — AI Skill **Last updated: 4 September 2026.** Download the current version any time from templeadmin.com/temple-skill.md, or from the **Download AI Skill** button on the user guide at templeadmin.com/guide. ## How to use this file Give it to any AI assistant so that it knows Temple as well as our support team does. Then ask it anything: "how do I track first-time visitors?", "write a broadcast telling members about our campaign", "why can't my accountant see the giving page?". - **Claude (claude.ai):** create a Project, add this file under *Project knowledge*, and ask your questions in that project. Or paste the whole file into a chat and ask. - **ChatGPT:** attach the file to a conversation, or add it to a custom GPT's knowledge. Or paste it in. - **Gemini, Copilot and others:** paste the file into the conversation before your first question. Ask in your own words. The assistant can answer "where do I find…", give step-by-step instructions, explain what each plan includes, draft emails and SMS in Temple's voice, and tell you when something is on a higher plan than yours. **Inside Temple** there is also a built-in assistant (Growth and Enterprise): press **Cmd/Ctrl + K** anywhere in the dashboard, type a question, and choose *Ask*. It knows your church's context and can jump you to the right page. --- ## What is Temple? Temple is a cloud church management platform (ChMS) at **templeadmin.com**, built by SyntaxReady. It covers people and pastoral care, attendance and check-in, giving and finance, events and forms, communication (email and SMS), automations, discipleship, training, announcements and a member portal — for one church or a multi-campus organisation. - Sign in with email and password, or **Continue with Google** (sign-in, sign-up, accepting an invitation and claiming a record all support it). - Each church has its own address, `
.templeadmin.com`, which starts as its name with no hyphens (`dominioncitymississauga.templeadmin.com`). An admin can change it in Settings, under Organization. The public page is at `/`, the dashboard at `/admin/…`, and the member portal at `/portal/…`. Each church also has a fixed **slug**. The older `templeadmin.com/c//…`, `/portal/` and `/p/` links, `.templeadmin.com` and any earlier address keep working and forward to the current one. Signing in happens at `templeadmin.com`, and a church's links show its logo and name when shared. - Every church sets its own **timezone**, **currency** and **country** (Settings → Organization). Dates such as service dates, birthdays and tax years are always in the church's own timezone. --- ## Plans and pricing | Plan | USD / month | CAD / month | NGN / month (Nigeria, via Paystack) | Best for | |------|-------------|-------------|-------------------------------------|----------| | **Free** | $0 | $0 | ₦0 | Getting started | | **Starter** | $29 | $39 | ₦5,000 | Small churches up to 250 members | | **Growth** | $69 | $89 | ₦12,000 | Growing churches up to 1,000 members; AI, automations, integrations | | **Enterprise** | $179 | $249 | ₦30,000 | Large or multi-campus organisations | Billing is monthly by card through Stripe (USD or CAD) or Paystack (Naira). A church can upgrade, downgrade or cancel from **Settings → Finance & Credits**. Platform admins can also extend a trial or set a plan by hand. ### Limits by plan | Limit | Free | Starter | Growth | Enterprise | |-------|------|---------|--------|-----------| | Members | 100 | 250 | 1,000 | Unlimited | | Team members (staff logins) | 2 | 5 | 15 | Unlimited | | Storage | 50 MB | 2 GB | 10 GB | 10 GB | | Giving transactions / year | 100 | Unlimited | Unlimited | Unlimited | | Active forms | 2 | Unlimited | Unlimited | Unlimited | | Form responses (total) | 200 | Unlimited | Unlimited | Unlimited | | Active events | 3 | Unlimited | Unlimited | Unlimited | | Attendance records / year | 500 | Unlimited | Unlimited | Unlimited | | Tax receipts / year | 25 | Unlimited | Unlimited | Unlimited | Limits are enforced at the moment you try to exceed them, with an upgrade prompt. Existing data is never removed when a limit is reached. Team **invitations and roles work on every plan** — only the number of active team members is limited. ### Included monthly communication credits | Plan | SMS / month | Email / month | |------|-------------|---------------| | Free | 0 | 0 | | Starter | 200 | 2,000 | | Growth | 500 | 5,000 | | Enterprise | 1,500 | 10,000 | - Every new church receives **50 SMS + 200 email credits once**, at sign-up, on any plan. - Included monthly credits are granted at the start of each billing month and **do not roll over**. - **Naira (Nigeria) plans are pay-as-you-go**: they carry no monthly allotment, and messages come from Naira-priced credit packs. - Inbound SMS replies are free. Top-up packs (below) stay usable for 12 months after purchase. ### Support | Plan | Support | Response | |------|---------|----------| | Free | Community and documentation | Best effort | | Starter | Email | 48 hours | | Growth | Priority email, video tutorials | 24 hours | | Enterprise | Dedicated support, phone, email, Slack | 4 hours, with SLA | Contact: **contact@syntaxready.com**. --- ## Feature availability by plan | Feature | Free | Starter | Growth | Enterprise | |---------|------|---------|--------|-----------| | People directory, households, care notes | ✓ | ✓ | ✓ | ✓ | | Attendance, live check-in, QR and public self check-in | ✓ | ✓ | ✓ | ✓ | | Giving records, funds, pledges, expenses | ✓ | ✓ | ✓ | ✓ | | Online giving (Stripe or Paystack) | ✓ | ✓ | ✓ | ✓ | | Events (including paid events, waitlists, discount codes), forms, resources | ✓ | ✓ | ✓ | ✓ | | Teams, rota, rosters, service plans, songs, blockouts, background checks | ✓ | ✓ | ✓ | ✓ | | Workflows, rule-based lists, custom fields, tags, group finder | ✓ | ✓ | ✓ | ✓ | | Reports, including scheduled report emails | ✓ | ✓ | ✓ | ✓ | | SMS broadcasts (credit-based) | ✓ | ✓ | ✓ | ✓ | | Discipleship (Reach 12) | ✓ | ✓ | ✓ | ✓ | | First-timer tracking and follow-up | ✓ | ✓ | ✓ | ✓ | | Weekly celebrations digest, admin reminders | ✓ | ✓ | ✓ | ✓ | | Community Marketplace (Converge) | ✓ | ✓ | ✓ | ✓ | | Bulk email broadcasts | — | ✓ | ✓ | ✓ | | Scheduled broadcasts | — | ✓ | ✓ | ✓ | | Recurring giving | — | ✓ | ✓ | ✓ | | Digital kids registration and pickup codes | — | ✓ | ✓ | ✓ | | First-timer assignment (staff owner + emails) | — | ✓ | ✓ | ✓ | | Data export (CSV/Excel) | — | ✓ | ✓ | ✓ | | Typed signatures on tax receipts | — | ✓ | ✓ | ✓ | | Announcements (posts with photos, website embed) | — | — | ✓ | ✓ | | Attendance insights and per-person report | — | — | ✓ | ✓ | | Public API, MCP, webhooks and forms API | — | — | ✓ | ✓ | | Your own app in the stores | — | — | ✓ | ✓ | | Giving campaigns (crowdfunding-style) | — | — | ✓ | ✓ | | Academy (courses, exams, badges) | — | — | ✓ | ✓ | | Program / convention check-in | — | — | ✓ | ✓ | | Future service scheduling | — | — | ✓ | ✓ | | Automations: birthday, welcome sequence, attendance follow-up | — | — | ✓ | ✓ | | Two-way SMS inbox and delivery reports | — | — | ✓ | ✓ | | AI Chat Assistant, Dexter growth advisor (chat over your church data), AI message refinement, AI CSV mapping | — | — | ✓ | ✓ | | QuickBooks Online and Xero sync | — | — | ✓ | ✓ | | Google Drive | — | — | ✓ | ✓ | | Outbound webhooks | — | — | ✓ | ✓ | | Email Donation AI Agent (inbox crawler) | — | — | — | ✓ | | Multi-campus, campus-scoped receipts | — | — | — | ✓ | --- ## How the dashboard is organised The sidebar groups pages like this (tabs in brackets): - **Overview** — the dashboard: giving and attendance trends, quick actions, who needs a call, upcoming birthdays. - **Community** - **People** [Directory, Lists, Fields & tags, First timers, Workflows, Households, Care, Kids] - **Attendance** [Live check-in, Follow-up, Insights, Report] - **Groups & serving** [Groups, Teams, Rota, Rosters, Plans, Songs, Blockouts] - **Growth** [Overview, Tree] (optional module) - **Ministry** - **Events** [Upcoming, Past, Calendar] - **Forms** - **Communicate** [Compose (Email, SMS), Audiences, Announcements, Automated, Activity (Sent, SMS replies)] - **Academy** [Courses, Cohorts, Grading, Learners] (optional module, Growth+) - **Resources** [Assets, Bookings, Calendar, Google Drive] (optional module) - **Finance** — **Giving** [Gifts, Approvals, Funds, Campaigns (Campaigns, Pledges), Recurring, Receipts], **Expenses**, **Reports** [Giving analysis, Financial statements, Chart of accounts, Scheduled] - **Settings** [Organization, Finance & credits, System, My account] - **Help** — Ask Dexter, User guide, Video tutorials, the product tour, Explain this page. Kids check-in, Growth, Resources and Academy stay out of the sidebar until a church turns them on under Settings → Organization → Sidebar modules. **Cmd/Ctrl + K** opens the command palette: jump to any page or tab by name, or type a question ("how can I start a campaign") and it answers with the right destination. **Notifications bell** (top bar): new first-timers, pending donations, expense approvals, attendance alerts, and a warning when the church's outbound email or SMS has started failing. --- ## Core modules ### 1. People & pastoral care - **Member profiles**: contact details, status (Active / Inactive / Visitor / Archived / Child), household, home campus, birthday and anniversary, photo, profile details (employer, school…), pastoral care notes with priority, and a timeline of every email and SMS sent to them. - **Source**: every record shows where it came from. Importing a list asks *"Where is this list from?"* (for example "Easter outreach sign-up sheet" or "Planning Center export") and stamps it on each record; a **Source** column in the file can set it per row. Records the app creates itself carry a fixed label — *Self check-in*, *Kids registration*, *Feedback form*, *Form: *, *Added manually*. The directory has a **Source** filter, the CSV export includes it, and the First Timers view shows it so a follow-up call can start with "you signed up at the fair". - **Directory**: search by name, email or phone; filter by status, gender, group or source; sort; select many for bulk archive; export to CSV (Starter+). - **Import** (People → Directory → Import): CSV or Excel, with a downloadable template. Columns are auto-mapped; a mapping dialog lets you correct them. Duplicates are matched on email, then phone, then full name, and a re-import updates the existing record instead of creating a second one. **AI CSV mapping** (Growth+) can fix messy files. - **Your own app** (Settings → Integrations): your church's name and icon in the stores, on Growth ($299 setup, then $49 a month) and Enterprise ($299 setup, app included). The church holds its own Apple and Google accounts. - **Automations and AI tools**: the API (Settings → Integrations → API tokens) also serves AI tools over MCP at `/v1/mcp`, and Zapier through Webhooks by Zapier. See `/developers/api`. - **Lists** (People → Lists): saved lists built from rules on status, tags, custom fields and groups, which keep themselves up to date, plus audiences a church fills by hand. Use them to message people or feed a workflow. - **Fields & tags** (People → Fields & tags): custom fields (text, number, date, yes or no, pick one, pick several) shown on every profile, and tags added one at a time or in bulk. - **Workflows** (People → Workflows): a church sets out its own steps, like a membership class, and moves people through them by hand or from a saved list. Each step can have a deadline in days and a person it is assigned to; Edit steps sets both, and the board filters to Assigned to me or Overdue. First timers and care keep their own pipelines. - **Households**: group members into families. - **Duplicate finder** and **merge** (Starter+) keep giving, attendance and notes when two records are combined. - **Feedback**: visitors and members can be asked for feedback by email; responses appear under People → Care. - **Claim a record**: someone already in the directory can prove they own their email address at `templeadmin.com/claim` (one-time code) and get portal access to that record — and only that record. - **Member self-join** (optional, Settings → Organization): lets congregants create their own portal account and link to their record. ### 2. First timers and follow-up - A visitor's first check-in, form submission or kids registration creates a **follow-up** automatically under People → First timers. - Each follow-up has a status (Pending → Called → Visited → Completed), notes, the visitor's source, and badges showing whether they **returned** and whether they were **connected** (joined a group or became active). - **Assignment** (Starter+): assign a staff member; both the staff member and the visitor receive an email, with a deep link to the record. - **Reminders**: staff are reminded about follow-ups that are still open; a follow-up more than a week old raises the `first_timer.followup_overdue` webhook event and appears in the admin morning digest. - **Outcomes**: Attendance → Insights and the First timers stats show conversion over time. ### 3. Attendance and check-in - **Services**: create services (name, date, time, campus). **Future service scheduling** (Growth+, from Live Check-In) lets you create them ahead of time so the QR codes exist early; upcoming services also show on the public profile. - **Live Check-In** (Attendance → Live check-in): staff search and check people in, add visitors on the spot, and see counts live. **Program check-in** (Growth+) handles conferences and multi-session programs — each session is checked in separately, inside the same tab. - **QR self check-in**: every service has a QR code; members scan and check themselves in on their phone. Codes can be regenerated at any time, and Settings → System → Self check-in search sets whether old codes keep working or stop after their service. - **Public self check-in search**: a public page where people find themselves by name, phone or email — no code needed. Which fields are searchable is configured in the same settings section; matches show masked hints only. - **Follow-up**: members who have broken their usual pattern; contact them directly, add anyone by hand and name an owner. - **Insights** (Growth+): trends, service comparisons, how newcomers settle in. - **Offline desk**: if the connection drops, the check-in desk keeps a local list and sends it when back online. - **Household check-in**: someone checking in can tick the others with them. - **Headcount**: count a room rather than each person. - **Attendance reports** (Growth+): per-member history by date range, program and campus, with the details captured at check-in; export to CSV. - **Attendance follow-up** (Growth+): after a configurable number of missed weeks, Temple drafts a message for each member; nothing sends until staff review it. ### 4. Digital kids registration (Starter+) Turn on the Kids check-in module under Settings → Organization → Sidebar modules, then enable registration under People → Kids → Settings. 1. A parent opens `templeadmin.com/c//kids-register`, enters their email and confirms a one-time 6-digit code. 2. They register each child (name, birthday, allergies, medical notes, photo consent) and receive a permanent QR **Kids Card** by email. 3. At the station, staff scan the card; Temple records attendance and issues a unique **two-half pickup code** printed on the child's label. At pickup, staff enter the matching half; a code can only be used once. **Rooms** (Kids → Rooms): set rooms by age, with a capacity and kids per adult. A checked-in child is suggested a room from their age, and the Rooms tab shows who needs attention; volunteers count from a team's rota. **Pickup list**: each child can list who may collect them and who must not, and staff see it before releasing. Labels can show or hide the room and service, and carry a note. Labels print from the browser on any printer, including DYMO label printers (2×4", 4×6" or Letter 2-up). Kids' medical notes and pickup codes are never sent to webhooks or exports. ### 5. Announcements - **Announcements** (Growth+): publish an announcement by **uploading the flyer you already made** (JPG, PNG or PDF), **uploading a PowerPoint** (converted to poster slides), or building slides in the editor (layouts, themes, drag reordering, call-to-action buttons). Published announcements appear as a carousel on the public profile; slide decks export to PDF or PowerPoint (PPTX). ### 6. Giving and finance **Recording gifts** - Giving → New entry, with deposit batches that count toward nothing until committed: single gifts and batch entry for cash, cheque, e-Transfer/Interac and online; import from CSV. - **Bank Import**: upload a bank statement, match lines to members (AI-assisted, Growth+), review, commit — with undo. - **Approvals**: gifts recorded by non-finance roles, self-reported campaign and pledge payments, and inbox-detected donations wait here for a finance role to verify. - **Funds**: keep designations separate; mark which funds are **tax-deductible** (that flag flows to campaigns and gifts and decides what appears on receipts; refunds are de-receipted automatically). - **Gifts**: every contribution, with edit history. **Online giving** - **Stripe**: each church connects its **own** Stripe account from Settings → System → Integrations → Stripe (Express onboarding, a few minutes). Once Stripe has enabled charges, a **Give Now** button appears on the public profile and at `templeadmin.com/donate`, and card gifts settle directly to the church. Recurring gifts (weekly / monthly) are Starter+. - **Paystack** (Nigeria): the same, in Naira, from Settings → System → Integrations → Paystack. - **Recurring** tab (Giving → Recurring): staff see every standing gift and can cancel one on a member's behalf. Donors change the amount or card, pause or stop in the portal; paused givers can ask for at most two reminders (30 and 90 days). - Donors can choose to cover the card fee, and online gifts can be refunded in full or in part from Temple. - Failed payments email the donor; a church is told when its payment setup is missing (dashboard checklist and a banner on the Giving page). **Pledges and campaigns** - **Pledges**: standalone or tied to a campaign; progress tracking; daily reminder emails link straight to the member's own pledge in the portal, where they can report a payment. - **Public scan-to-pledge**: a QR / link (Giving → Pledges → Get Pledge QR Code, or per campaign) lets anyone commit with no login; an existing member is matched by email or phone. - **Campaigns** (Growth+): goal, suggested amounts, optional fund, public page and QR, member commitments, self-reported payments verified by staff, milestone emails at 25/50/75/100 %, weekly reminders to members who have not committed. Closing a campaign really stops the giving — recurring Stripe gifts tied to it are cancelled, and a pause only pauses. **Expenses**: requests with receipts, an approval workflow with comments, disbursement tracking, and budget reporting. **Background checks** (all plans): staff record a person's check on their profile, with an expiry date. A team marked *Background check required* refuses anyone without a clear, unexpired check, on the team and on the rota. **Tax receipts**: per-member PDF receipts with wording for **Canada (CRA)** and the **United States (IRS)**; every other country gets neutral wording that makes no tax claim (UK Gift Aid and Australian ATO wording are not offered yet). Receipts are emailed in bulk or one at a time. Free plans get 25 per year; Starter+ unlimited. Enterprise can scope receipts by campus. **Accounting sync** (Growth+): **QuickBooks Online** and **Xero** — donors as customers, donations as income, disbursed expenses as bills, idempotent (nothing posts twice), in the church's timezone. **Reports**: Giving Analysis, Financial Statements, Chart of Accounts, and **Scheduled Reports** (Starter+) that email themselves weekly or monthly. **Currencies**: CAD, USD, GBP, EUR, AUD, NGN. Amounts everywhere respect the church's currency, and a **Conceal** toggle in the user menu (top right) masks every amount on screen for presenting in public. ### 7. Events Events with public pages, a price charged through the church's own Stripe or Paystack, capacity limits with a waitlist (Offer free places moves people up), discount codes, linked registration forms, RSVP confirmations, repeating dates (every week, 2 weeks or month), add-to-calendar links, a subscribable calendar feed, a Calendar tab with services, events, room bookings and holidays, and a Past tab. Mark paid records cash, check, transfer or a waived fee. Free plans can have 3 active events. ### 8. Forms Fully self-hosted (no third-party form service). - Drag-and-drop builder with text, email, phone, date/time, number, link, dropdown, multiple choice, checkboxes, file upload, rating, structured address and **e-signature** fields (generated signatures Starter+). - Multi-page forms with conditional logic, scheduled close dates, response caps, custom thank-you pages and redirects. - **Automations**: any answer can create a member, a pledge or a care note, start a first-timer follow-up, or email a notification list. - Submission notifications, respondent copies, per-form collaborator access, and public embedding. - Free: 2 active forms and 200 responses in total; Starter+ unlimited. ### 9. Scheduling, service teams and resources - **Teams**: worship, ushers, tech, kids… with members and leaders. - **Service plans** (Groups & serving → Plans): the order of a service from a template or empty, with songs, items, headings, lengths and who leads. Link a plan to a service and share it with the team in the app. - **Songs**: a library with key, BPM, CCLI number, themes and chord charts, imported from and exported to EasyWorship, ProPresenter, FreeShow and OpenLyrics. Exports hold words and sections only. - **Blockouts**: dates people can't serve, added by staff or by volunteers in the app; the rota warns before scheduling over them. - **Rosters**: daily, weekly, monthly or quarterly series with auto-rotation, per-service overrides, CSV roster import, and reminders (email 24 hours before, SMS 6 hours before — SMS uses credits). - **Resources**: rooms, vehicles and equipment with bookings, conflict detection and a resource calendar. - **Google Drive** (Growth+): an administrator connects a church Google account in Settings. Staff browse, upload, rename, move and trash files from Resources, and attach files and folders to assets. Temple only sees files it created or that someone added with Google's picker. Selecting a folder's name opens it in Google Drive, where everything is visible. Adding a folder doesn't add its files: choose Open in Temple from the folder's menu and use Add from Google Drive there, up to 100 at a time. Remove from Temple takes a file or folder off the list and leaves it untouched in Drive, along with what was added from inside it; the Removed view brings it back, and so does picking it again. Move to Drive's trash takes it out of Drive, and is restorable for 30 days. Share gives church staff, a serving team or anyone by email access to a file or folder, up to 50 people at a time, and lists who has access; Google emails each person a link, and a folder shares everything in it. Only named people can be added: Temple never makes a file public. **Filling the rota**: each team has a number needed. **Auto-fill** adds the people who are free, whoever served longest ago first, and skips anyone away, already serving that day (on a rota or leading a roster turn) or without a required background check. A team can let its own people sign up for open places, and a volunteer can ask a free teammate to cover their slot. ### 10. Communication - **Communicate**: broadcast **email** (Starter+) and **SMS** (all plans) to the people you choose (member status, group, data source, first timers, at-risk members, a saved audience, or people you pick); attachments; scheduling (Starter+); a full history with delivery stats; **AI refine** (Growth+, counted against the plan's AI allowance) to polish tone before sending. - **WhatsApp**: the SMS composer can send through WhatsApp instead, using the same recipients and credits. - **SMS replies** (Communicate → Activity, Growth+): a two-way SMS inbox; inbound replies are free. - **Credits**: 1 SMS credit = 1 segment (160 characters, or 70 if the message contains an emoji or special character); 1 email credit = 1 email. - **Safeguards**: every email carries an unsubscribe link; members can opt out of email or SMS separately; one person receives at most **10 automated emails from a church per day** (receipts, codes and confirmations are exempt); scheduled sends more than two hours late are marked *missed* rather than sent stale; and if a church's sends start failing, its admins get a bell notification. ### 11. Automations (Settings → System → Integrations → Member Communication) | Automation | What it does | Plan | |-----------|--------------|------| | Automated birthday messages | Birthday email and/or SMS to the member; optional admin notification | Growth+ | | New member welcome | A welcome email and SMS with editable templates when someone becomes a member; first-time visitors also get a fixed 3-step email sequence on days 1, 3 and 14 | Growth+ | | Attendance follow-up | Draft a message after N missed weeks, for staff to review | Growth+ | | Year-end giving reminders | Sundays at 4pm in November and December, a summary of gifts still to record, link or approve | All plans, opt-in | | Weekly celebrations digest | Every Monday at 9 am church time, one email to each member naming that week's birthdays and anniversaries, with a link to sign a shared card | All plans, opt-in | | Admin reminders | A nudge a few hours after a service nobody recorded attendance for, and an 8 am digest of overdue follow-ups and expense approvals (admins only, only when there is something in it) | All plans, opt-in | | Feedback requests | Ask visitors for feedback after their first visit | All plans | | Donation update reminders | Remind finance managers to keep donation records current | All plans | | Pledge and campaign reminders | Pledge-due emails; weekly campaign commitment reminders | with the feature | ### 12. Discipleship — Reach 12 (all plans) - One active **program** per church with a target (default 12) and a reminder cadence. - Members accept the assignment in the **portal** and add the people they are reaching, moving each through six stages: Praying For → Invited → Attending → New Believer → Church Member → Multiplying. Admins do not enrol members; members join themselves. - Eleven **milestone badges** awarded automatically, each with a KJV scripture and an instant celebration email; encouragement reminders on the cadence (members can opt out). - Admin view: stats, journey funnel, optional leaderboard, per-discipler drill-down, an 8-year multiplication projection, and a **Tree** tab drawing the whole multiplication tree. Members see their own tree. ### 13. Academy (Growth+) Training for a church's own workforce, modelled on a real church academy. - **Courses** with a code, track, reading sections and one exam; audiences are *open* (anyone in the church) or *assigned*; delivery is *self-paced* or *cohort* (a scheduled intake, optionally with an instructor). - **Exams** are graded on the server: multiple-choice automatically, written answers by staff on the **Grading** tab. Answer keys never reach the browser. - **Learners** shows enrolments, progress and passes. Passing awards a **badge** that appears on the member's profile. - Members take courses from the **Academy** tab in their portal. ### 14. Groups Cells, departments and ministries are all groups (Groups & serving → Groups), with leaders and members. Each group sets who can find it (hidden, members in the app, or anyone on the public page) and who can join (straight away, a leader approves, or closed), with an optional limit. The public group finder is at `/p//groups`. Leaders manage their group's people, join requests and attendance (date, topic, visitors) from the app or portal. ### 14a. Dexter and AI tools **Dexter** (Growth 25 questions a day, Enterprise 75): press Ask Dexter on any page. It reads the church's people, first-timers, attendance, groups, events, messages and giving, answers with figures, tables, charts, links and draft messages, and can create an event, add a person, update a first-timer or open a care follow-up once a person confirms. Other tools: the assistant in Cmd/Ctrl + K search, Refine with AI, import help, donor matching and the email donation agent. A church can turn all of them off under Settings → Organization → Security & access → AI features. ### 14b. Importing from Planning Center Settings → System → Integrations → Import from Planning Center: paste an App ID and Secret (Temple doesn't keep them), then choose people, custom fields, groups and songs. Nobody is messaged, existing people are matched by email with only blanks filled in, and giving history isn't included. It can run again. ### 14c. Community Marketplace (Converge) An optional marketplace where the congregation can buy from and support one another, powered by Converge (useconvergeapp.com). An admin links the church's Converge community under Settings → Organization; until then nothing shows. Once linked, **Marketplace** appears in the sidebar and as a card in the member portal. Converge is a separate service with its own sign-in; Temple does not process marketplace orders. ### 15. Outbound webhooks (Growth+) Settings → System → Integrations → Webhooks, shown only to the church's owner. Up to five `https://` endpoints per church, each with the events it wants and a signing secret shown once. Events: `service.completed`, `first_timer.created`, `first_timer.followup_overdue`, `member.absence_threshold_reached`, `discipleship.stage_changed`, `automation.failed`. By default only identifiers, counts and dates are sent; names, giving totals, form answers and message content each need a scope ticked. Kids' medical details, pickup codes, passwords, payment credentials and pastoral notes are never sent. Delivery is at-least-once with retries over 48 hours, a delivery log, manual replay, and 24-hour secret rotation. Developer docs: `docs/webhooks.md` in the repository. ### 16. Member portal (`
.templeadmin.com/portal`) Members sign in (or claim their record) and see Home (next gathering, one-tap check-in, announcements, events, serving, groups), Calendar, My giving (history, pledges with *Make a Payment*, recurring gifts, a yearly statement), Prayer, their discipleship assignment and tree, academy courses, campaigns (web only) and the marketplace card. They can confirm or decline a serving slot, find a replacement, sign up for open places, add dates they're away, see the service plan with chord charts, find and join groups (leaders manage their group's people, requests and attendance), and choose notifications in the app. Every email and SMS carries its own unsubscribe link. Portal access never grants access to the church directory. ### 17. Public pages - `/p/` — church profile: upcoming services, Give Now, kids registration link, announcement carousel, brand colour, and an embeddable `