Planned/explored directions:

• AI-assisted content authoring — draft suggestions, summaries, and translations for Item content, reducing the time editors spend on first drafts and localization.
• Smarter automation triggers — moving beyond fixed schedules/rules toward automation that can reason about context (e.g., "this customer hasn't engaged in 60 days" rather than a rigid rule condition).
• Conversational CRM insight — asking natural-language questions about customer activity ("who are our most active volunteers this quarter?") instead of building custom reports.
• AI-assisted form/response triage — automatically categorizing and routing form submissions to the right staff member or team.

Why This Matters

As AI capability matures, the goal is to keep it grounded in the platform's existing data model (Item, Customer, Event, UserGroup) rather than bolting on a disconnected AI tool — every AI feature should make existing workflows faster, not add a new system to learn.

Technical Notes

Any AI expansion will build on the existing SearchService foundation and the platform's multi-tenant, Clean Architecture structure — new AI capability should be additive to existing services (e.g., extending CustomerService, AutomationBackgroundService) rather than introduced as a separate, parallel "AI service" disconnected from the data it acts on.