Content Management

Upload, process, and manage your sermon content to power HolyQA's AI responses.

Getting Started

Upload Process

  1. Access the Content Management tab in your dashboard
  2. Upload files, add YouTube content, or connect your website
  3. Complete your Church Profile for logistics information
  4. Monitor processing status until items show "Processed"
  5. Test by asking questions in the Ask tab

Start Uploading

Access your content management dashboard to begin uploading sermons and materials.

Go to Dashboard →

Supported Content Types

Audio Files

Formats: MP3, WAV, M4A, AAC, OGG, FLAC, WMA, OPUS

Best for: Sermon recordings, podcasts

Video Files

Formats: MP4, MOV, MKV, WebM, M4V, AVI

Best for: Recorded services, teaching sessions

Documents

Formats: PDF, DOCX, TXT

Best for: Sermon notes, study guides, bulletins

YouTube Content

Available: All tiers (Scale includes channel automation)

Best for: Sermon videos, conferences

Website Indexing

Connect your church website for automatic daily syncing of pages. Auto-syncs run daily at 3:00 AM UTC.

Best for: Service times, ministries, contact information

Church Profile

Your Church Profile stores service times, address, contact details, and ministries. This information is prioritized over website content for logistics questions.

YouTube Integration

Plan Requirements

  • Starter: File uploads only (no YouTube processing)
  • Growth: Individual YouTube video processing
  • Scale: YouTube automation with auto-sync

Individual Videos (Growth Tier)

Paste individual video URLs:

https://www.youtube.com/watch?v=VIDEO_ID

YouTube Automation (Scale Tier)

How It Works

  1. Discover: Use the Discovery tab to add a YouTube channel or playlist URL. HolyQA scans it for matching videos.
  2. Review Inbox: New videos appear in your YouTube Inbox. Review and import selected videos, or enable auto-import for automatic processing.
  3. Auto-Sync Settings: Toggle auto-sync per channel/playlist in the Discovery Settings. Configure filters (duration, keywords, date) to control which videos are discovered.
  4. Processing: Enabled channels with auto-import are checked weekly. New videos are automatically queued for processing.

Auto-Sync Frequency

YouTube automation checks for new videos every 7 days (weekly) for channels with auto-sync enabled.

Processing Status

After uploading content, HolyQA processes it to make it searchable. Status updates appear in real-time without needing to refresh the page.

Pending

Queued and waiting to be processed

Processing

Being analyzed and prepared for AI responses

Processed

Ready and available for AI responses

Error

Processing encountered an error

Managing & Optimizing Your Content

Use the Content Management tab to keep uploads and YouTube automation in sync, review processing status, and clear space when needed.

Actions

  • Delete individual items or use bulk delete for large batches.
  • Filter & Search by type, processing status, or source so you only see the items you need.
  • Sort by upload date, title, or processing status to keep fresh content surfaced.

Editing content isn’t supported yet—delete and re-upload if you need to refresh a file.

Library Tools

Easily find and organize your materials.

  • Live status updates show you exactly when a file is ready
  • Select multiple items for quick cleanup or imports
  • Use search and filters to find specific sermons in seconds

Content Quality

Upload complete, high-quality sermons and name them clearly. Fresh uploads deliver more immediate value to your congregation.

Capacity & Testing

Keep an eye on your processing capacity. Remove duplicates or outdated files to stay under the limit and test AI responses after new uploads.

Need Help?

If you're experiencing issues or have questions, we're here to help.

Email Support

Send us a detailed message at hello@holyqa.com

Response within 24 hours

Documentation

Check our troubleshooting guide for common solutions

Immediate answers to common questions

When contacting support, please include your church name and a detailed description of the issue.

Was this page helpful?