PromptQL

What is PromptQL?

PromptQL, built by Hasura, is a multiplayer AI platform designed to give teams a shared brain rather than isolated chat sessions. It pulls context from Slack, docs, tickets, CRM, and warehouse tables, then turns corrections made during real work into reusable team knowledge stored in a Wikipedia-style wiki. Instead of asking people to update documentation separately, PromptQL captures institutional knowledge directly from the flow of work, so accuracy and context compound over time rather than decaying.

Key Features

• Shared Threads & Context

  Team members work inside shared AI conversation threads, so decisions, corrections, and reasoning stay visible to everyone instead of trapped in individual chats.

• Self-Building Wiki

  Automatically generates and updates a Wikipedia-like knowledge base from Slack, Google Docs, Snowflake, CRM, and product analytics, complete with citations and revision history.

• Learn-by-Correction Model

  When a teammate corrects an answer or clarifies a data source, PromptQL converts that correction into a scoped, reusable skill or semantic-model update for future queries.

• Governed Access Scopes

  Grants different visibility into the shared wiki for internal teams, customers, or external collaborators, with granular view and edit permissions.

• AI Analyst Agents

  Answers complex business questions in plain English by reasoning across data silos, validating conclusions, and flagging uncertainty like a skilled analyst.

• Data Access & Query Planning

  Connects to structured, unstructured, and API-based data sources, building inspectable query plans that retry and self-correct to reduce hallucinated results.

Use Cases

• Churn Risk Analysis : Customer success teams can quickly assess renewal risk by combining usage trends, support ticket sentiment, and prior team knowledge in one thread.
• Business Reporting : Analysts and operators pull accurate, up-to-date figures like revenue by region, automatically correcting for stale data sources based on prior team edits.
• Onboarding Account Context : New team members can seed a full account wiki in seconds by pulling from Slack, CRM, and product analytics tied to a specific customer.
• Cross-Team Knowledge Sharing : Support, engineering, and customer success teams collaborate in the same thread, preventing duplicated investigation and repeated explanations.
• Real-Time Operational Decisions : Category managers and sales reps get instant, trusted answers to urgent business questions without waiting in an analytics team's ticket queue.

FAQs