Intelligence built for operations

AI that works inside the operation.

RidgeHQ is the operations platform for dive centers, surf schools, and other activity businesses. Its AI Copilot isn’t a chatbot answering FAQs — it reads your live bookings, staff schedule, and capacity, and confirms with you before it changes anything.

Context-Aware Assistance

Because RidgeHQ connects all your data, the Copilot can inspect bookings, staff schedules, and resource availability across the entire business. It uses the exact same permission model as your team.

AI Copilot summarizing what needs attention today

Create and verify, in one flow

Ask the Copilot to add a session and it drafts the full change — program, time, staff, capacity — then shows you exactly what it will do. Nothing is written until you confirm, and the result is checked back against your live schedule.

Controlled Actions

The Copilot can suggest and stage actions, but medium and high-risk operations require your explicit confirmation before execution.

  • Safe tool boundary
  • Operator-first confirmation

Audit & Undo

Every non-read action the AI takes is recorded in the operational audit log. Selected schedule and assignment actions have explicit undo support.

  • Full mutation history
  • Reversible planning tools

Provider Choice

The RidgeHQ AI layer is provider-agnostic. Depending on your configuration, it supports major models to balance intelligence with privacy.

  • Anthropic
  • OpenAI
  • Ollama support

What it can look at

Ask in plain language and the Copilot reads the same live records your team works from, so its answers reflect today rather than a summary from last week.

  • A morning brief of what needs attention today, with a suggested next step for each alert
  • Who on a trip still has an unsigned or expired waiver
  • Which divers need gear from you, and in what sizes
  • Why a trip's gear prep list is short — out for service, on another trip, or not in stock
  • Recent bookings, including unpaid or outstanding orders
  • How the season is going: slow days, under-used boats, returning-customer trends

What it can change — after you confirm

When you ask for a change, the Copilot prepares it and shows you exactly what it will do. Nothing is written until you confirm, and the confirmation applies to every role, including the Owner.

  • Create a session, or reschedule one, from a sentence like “add a dive tomorrow at 10:00 for 10”
  • Take a piece of gear out of service with a maintenance record
  • Draft a gear-return reminder — drafted only, never sent without a person
  • Bookings, cancellations, and refunds are high-risk actions: always confirmed, and limited to senior roles

What it deliberately won't do

The Copilot is built to reduce coordination work, not to replace your judgement. Its limits are part of the design.

  • Act beyond the role of the person using it
  • Skip the confirmation step on a medium- or high-risk change
  • Offer booking, cancellation, or refund actions to outside AI assistants
  • Send a drafted message on its own

Your choice of AI provider

The Copilot isn't tied to one model vendor. A manager chooses the provider in Settings, and the change applies on the next question — no restart.

  • Anthropic by default, or OpenAI
  • Your own API key, or a self-hosted Ollama model
  • Every recorded action notes which provider and model carried it out

Prefer to use it from Claude or ChatGPT directly?

The same tools are available over MCP, so you can ask Claude, ChatGPT, or Claude Code to work with your RidgeHQ account from the assistant you already use — same permissions, same confirmation step, same audit log.

Connect an AI assistant →

Frequently asked questions

No. It can answer questions straight away, but any change rated medium or high risk is shown to you first and only runs after you confirm. Creating, cancelling, or refunding a booking is high risk and limited to senior roles.

Some can. Reversible scheduling actions — such as rescheduling a session — can be undone from the Copilot panel within one hour. Money-moving actions such as refunds are not reversible this way, which is why they always need confirmation first.

No. It works within the role of the person using it, and revenue figures follow the same per-business visibility rule as the rest of RidgeHQ.

Anthropic by default. A manager can switch to OpenAI or to a self-hosted Ollama model, and can supply the business's own API key.

A completed change the AI makes on your behalf. Questions, searches, previews, failed attempts, and undoing an action are not counted as actions.

Yes. The same tools are available over MCP using an access token you create and can revoke. The token carries a staff role no higher than Manager, and booking, cancellation, and refund actions are never available that way.

Ready to test the Copilot?

Join our Design Partner program to help shape AI workflows for activity operations.