+ Unlike traditional OCR that relies on fixed zones and templates, Echo + uses multimodal vision AI to understand the entire card. It reads + handwritten text, identifies checked boxes, interprets context, and + extracts structured data — even from cards it has never seen before. +
++ This means you don’t need to redesign your cards or train the + system. Whether you use pre-printed forms, custom cards, or a mix of + both, Echo figures it out. +
++ Scan a full stack of double-sided cards through your office scanner. Echo + automatically pairs front and back pages, rotates them for readability, + and extracts data from both sides as a single record. +
++ Supports PDF (multi-page), JPEG, PNG, and WebP. Files up to 50 MB each. +
++ Every card is analyzed for all of the following fields. Echo only fills + in what it can confidently read — and flags the rest for human review. +
++ Every extraction includes a confidence score. High-confidence fields are + accepted automatically, while low-confidence results are highlighted so + your team can quickly verify and correct them. Nothing syncs to your CRM + until a human approves it. +
++ Echo intelligently assigns first-time guest dates and salvation dates + based on card context and your service schedule. A card scanned on Monday + morning? It knows it came from last Sunday’s service. +
++ Made changes to a card image? Want to try again with different AI + settings? Reprocess individual cards, entire batches, or specific jobs + with one click. The original images are always preserved. +
++ The moment you log in, you see the numbers that matter: total cards + processed, cards awaiting review, OCR success rate, and cards assigned + to you. Quick-action buttons let you jump straight to uploading, + reviewing, or managing your team. +
++ A getting-started guide walks new users through setup, then + dismisses itself so the dashboard stays clean. +
++ The response card grid is built on TanStack Table — the same engine + behind enterprise data tools. You get: +
++ Quick-filter chips at the top of the cards view let you jump between + views with one click: +
++ Each chip shows its count in real-time so you always know what’s + waiting for you. +
++ Every card captures rich context about your visitors: whether they’re + first-time or returning guests, what spiritual next steps they’re + considering, prayer requests, how they heard about your church, and + which service they attended. +
++ This data powers your follow-up strategy. Filter for all first-time + guests from last Sunday, see who requested prayer, and identify new + believers — then route them to the right team member. +
++ Click any card to see the complete record: front and back images, + every extracted field, confidence scores, assignment history, review + status, and a timestamped activity log. Edit any field directly, + add notes, and trigger reprocessing if needed. +
++ Export the current view — with all active filters applied — as a CSV + file. This means you can filter for “all first-time guests in + April” and export just that subset. The CSV includes all visible + columns, ready to import into Excel, Google Sheets, or any reporting + tool. +
++ Create collection days that repeat on a schedule: every Sunday at + 9 AM, the first Wednesday of the month, bi-weekly small groups — whatever + fits your church calendar. +
++ Echo uses the RFC 5545 recurrence standard (the same one Google Calendar + uses) so it can handle complex patterns like “every Sunday except + holidays” or “first and third Saturdays.” +
++ When cards are processed, Echo looks at the timestamp, your location, + and your event schedule to automatically assign each card to the most + recent matching service. A batch scanned Monday morning? Echo knows it + came from last Sunday’s service. +
++ Three assignment strategies, configurable per organization: +
++ Not everything is recurring. Create one-off collection days for special + events like Easter services, VBS, community outreach days, or + conferences. These work exactly like recurring events but with a single + fixed date. +
++ Each collection day belongs to a specific location. This means your + downtown campus can have different service times than your north campus, + and cards scanned at each location are assigned to the correct event + automatically. +
++ Browse all cards collected during a specific service. Filter your card + table by event to see exactly who visited on Easter Sunday at your + Main Street campus vs. your Northside campus. Great for targeted + follow-up. +
++ The auto-assignment engine looks backward in time for a matching event. + The default window is 48 hours, but you can adjust this per organization. + A 72-hour window works well for churches that scan cards on Monday or + Tuesday. +
++ {integration.description} +
+ + {integration.plan} plan & above + ++ Every integration fires on the events you choose. Configure each + connection to trigger on: +
++ Most churches trigger on “reviewed” so only human-verified + data enters their systems. +
++ Map Echo’s extracted fields to your destination’s fields + with a visual mapper. For Planning Center, Echo can even pull your + existing custom field definitions so everything lines up perfectly. +
++ Change your card layout? Just update the field mapping — no code required. +
++ The Planning Center integration goes beyond basic syncing: +
++ Every webhook payload is signed with your secret key using HMAC-SHA256. + Your receiving endpoint can verify the signature to ensure the data + came from Echo and wasn’t tampered with. Full payload includes + card data, event type, and timestamp. +
++ Use webhooks to connect Echo to Zapier, Make, n8n, or any platform + that accepts HTTP callbacks. Or reach out about a custom integration + on our Enterprise plan. +
+ + Request an integration ++ Each location in your organization has its own name, address, timezone + override, and set of collection days. Your downtown campus might have + services at 9 AM and 11 AM on Sundays, while your satellite campus + meets at 10 AM — Echo tracks both separately. +
++ Each campus can have its own scanner configuration. Northside emails + scans to one inbox, Downtown uses FTP, and the mobile campus uploads + from phones. All three feed into the same processing pipeline and + appear in the same dashboard. +
++ Assign team members to review cards from specific locations. Your + downtown volunteer coordinator only sees downtown cards, while the + executive pastor sees everything. Role-based permissions work + alongside location context. +
++ See aggregate stats across all locations or drill down by campus. + How many first-time guests did we have across all sites this month? + Which campus had the most prayer requests? The dashboard gives you + both the big picture and the details. +
++ Organization-level settings (AI provider, integration connections, + team permissions) apply everywhere. Location-specific settings + (timezone, scanner config, collection day schedules) can be + customized per campus. Change your Planning Center connection once + and it applies to all locations. +
++ Consultants, denominational leaders, or staff who serve multiple + churches can switch between organizations from the sidebar. Each + org is fully isolated — separate data, separate teams, separate + billing. +
++ Purpose-built for the way churches actually work — from the + welcome center to the pastor’s desk. +
++ {feature.description} +
++ Start free with 50 cards per month. No credit card required. +
++ The simplest path: open Echo on your phone, tablet, or computer, and + drag files onto the card grid. Or click the upload button in the + header. Supports PDF, JPEG, PNG, and WebP. +
++ Perfect for volunteers who snap photos of cards with their phone right + after the service. Multi-file upload means you can select an entire + folder at once. +
++ Configure your office multi-function printer to email scanned documents + to a dedicated inbox. Echo polls that inbox every two minutes, downloads + PDF and image attachments, and queues them for processing automatically. +
++ After processing, Echo can mark emails as read or move them to a + “processed” folder — so your inbox stays clean. +
++ Works with any IMAP-compatible email provider: Gmail, Outlook, + Dreamhost, Yahoo, or your church’s hosted email. +
++ For high-volume environments, configure your scanner to send batches to + an FTP server. Echo connects via FTP/FTPS, downloads new files from the + incoming directory, processes them, and moves them to a “processed” + folder. +
++ This is ideal for churches that run multiple scanners at different + campuses — each scanner sends to the same FTP endpoint and Echo handles + all of them. +
++ Ricoh, Xerox, Canon, HP, Brother, Epson — if your printer has a + “Scan to Email” or “Scan to FTP” option in its + address book (most do), it works with Echo. No special software, no + drivers, no plugins. +
++ Don’t have a dedicated scanner? A smartphone camera works too. + Take a photo, upload it, and Echo reads it just the same. +
++ Echo filters email attachments by type and size — it only processes + PDFs and images, ignoring signatures, logos, and other irrelevant + attachments. Multi-attachment emails are supported: each valid file + becomes its own processing job. +
++ Both email and FTP watchers run on a two-minute cron cycle. Cards + scanned and emailed during the Sunday service start appearing in your + dashboard within minutes — without anyone touching a computer. +
++ Every import is tracked as a processing job with source metadata: + where the file came from (upload, email, FTP), when it arrived, how + many cards were extracted, and the processing status. You always know + what happened and when. +
++ All data is encrypted in transit using TLS 1.3 and at rest using + AES-256 encryption. This applies to your database (Supabase + PostgreSQL), file storage (Supabase Storage), and every API + connection between Echo and third-party services. +
++ Passwords are hashed with bcrypt — they are never stored or + transmitted in plain text. +
++ Five distinct roles (Owner, Admin, Editor, Reviewer, Viewer) control + exactly what each team member can see and do. Permissions are enforced + on every API route — not just in the UI. Even if someone bookmarks a + URL, they can’t access data beyond their role. +
++ No public signup on your organization’s instance. New team members + must be invited by an Admin or Owner. Invitations include a pre-assigned + role and expire after 7 days. This prevents unauthorized access and + keeps your member data private. +
++ Every account requires a verified email address. Users who haven’t + verified see a persistent banner and can request a new verification + email at any time. This ensures that account recovery and + notifications reach the right person. +
++ Enterprise plans support OIDC/SSO integration with identity providers + like Authentik, Okta, Azure AD, and Google Workspace. This lets large + churches and denominations use their existing identity infrastructure + — single sign-on, centralized user management, and automatic + deprovisioning when staff leave. +
++ Every significant action is logged: who created a card, who reviewed + it, who changed a setting, when integrations fired, and what data was + synced. The activity log is timestamped and user-attributed, giving + you a complete chain of custody for sensitive data like prayer + requests and personal decisions. +
++ Echo runs on Vercel’s global edge network with Supabase (built + on AWS) for database and storage. Both platforms maintain SOC 2 + Type II compliance, regular security audits, and automatic backups. +
++ For organizations with strict data residency requirements, the + Enterprise plan includes self-hosted deployment via Docker — + your data never leaves your own infrastructure. +
++ All outbound webhooks are signed with HMAC-SHA256 using your secret + key. Receiving systems can verify that payloads originated from Echo + and were not modified in transit. This prevents spoofed data from + entering your CRM or other connected systems. +
+{role.description}
++ No self-registration on your instance. Admins send email invitations + with a pre-assigned role. The invitee clicks a link, creates their + account, and is immediately placed on your team with the right permissions. +
++ Invitations expire after 7 days and can be revoked at any time from + the team management page. +
++ After cards are scanned, assign them to specific team members for + review. Reviewers see only their assigned cards, verify the AI’s + extraction, make corrections, and mark them as reviewed. +
++ Once reviewed, cards can be synced to Planning Center or your CRM + with confidence that the data is accurate. The full assignment and + review history is tracked in the activity log. +
++ Team members receive notifications when cards are assigned to them, + when processing completes, and when errors need attention. A + notification center in the header keeps everyone informed without + email overload. +
++ Most churches have a mix of paid staff and volunteers on their guest + services team. Echo makes it easy to give volunteers limited access + (Reviewer or Viewer) while staff have broader control (Editor or Admin). +
++ The Owner role is reserved for the person who set up the account — + typically the executive pastor or admin director — ensuring there’s + always a single point of accountability. +
++ Start free. Upgrade when you’re ready. Every plan saves your team + hours of manual data entry every single week. +
++ {tier.description} +
++ All paid plans include a 14-day free trial. No credit card required to + start. Need more cards? Overage billed at $0.08/card. +
+| Feature | +Free | +Starter | +Growth | +Enterprise | +
|---|---|---|---|---|
| {row.feature} | +
{faq.a}
++ Start free. No credit card. No commitment. +
+ + Get Started Free ++ {subtitle} +
++ Start free with 50 cards per month. No credit card required. +
+