What problem does it solve?
It solves the problem of not knowing how Omni CRM data is structured, which tables relate to which entities, and how to write correct, safe queries that match business concepts across domains.
Core Features & Use Cases
- Schema-aware database querying: Helps you translate a business question into PostgreSQL SELECT queries with correct joins and domain context across Tickets, Projects, CRM Inbox, CRM Sales, Campaigns, Workforce, and Network/Fiber.
- Cross-domain relationship guidance: Uses an entity relationship map (people/subscribers/tickets/projects/work_orders/crm_conversations) and PostGIS awareness to support analytics that span multiple functional areas.
- Production-safe query practices: Enforces read-only execution via the omni-db MCP server and provides safety rules (no writes, soft-delete filtering guidance, and LIMIT usage expectations).
Quick Start
Ask a question like: "What are the top 10 subscribers by ticket count for the last 30 days, including subscriber number and customer name?"