Navigate

Quick find

Find what you need

Esc

Discord community AI / In development

Fewer repeat questions.
More conversation.

Your moderators shouldn’t have to explain the same rules and guides every day. We’re building a bot to help members find the answer in the conversation.

A conversation pilot has been built. Ask us about a demonstration and current availability. Owner-approved knowledge and customer setup are still in development.

For community owners

Make the answers easier to find.

We want members to find the right guide without waiting for a moderator to reply.

The planned owner controls let you choose the information and channels it uses, and review the answers.

Conversation pilot

Join the conversation

The pilot is designed to respond to mentions and direct replies through the shared model service. Ask about a demonstration using questions your community asks.

In development

Use your knowledge

Choose the rules and FAQs it may use. Update or remove a source when the information changes.

In development

Add game context

We’re working on game, wiki and mod information, with checks for the version and source behind an answer.

Start with a real question

See whether it
fits your community.

  1. Tell us about your server.One recurring question and a public example are enough to start.
  2. Discuss a demonstration.We’ll check availability and discuss where the pilot could help or fall short.
  3. Identify the information it needs.Discuss the rules, FAQs and sources your moderators would approve.
  4. Work out the next step.We’ll explain what a trial on your server would need before access can be arranged.

What exists today

A conversation pilot.
Customer setup comes next.

The model adapter has returned a test response. Signed Discord delivery still needs its own acceptance check.

Approved-fact storage is implemented separately and still needs to be connected to the pilot.

The source checks cover approval, version and expiry. Customer installation and owner controls—including removing sources—still need a full test.

See the model cutover and remaining release checks

The recorded cutover selected the native model for the public API and Discord adapters. It does not establish signed Discord acceptance, answer quality or paid-customer readiness. Before paid access opens, installation, permissions, payment verification, source removal, cancellation and expiry must pass the commissioning gate.

Customer setup / In development

Your server.
Your approved sources.

The setup needs to confirm who owns the server, where the bot can help and which sources it may use.

See the setup and access checks

These are the checks being connected to the existing authority. They are not a running self-service installation.

  1. Sign in as the server owner.Verify current Discord management authority and the actual installation grant before choosing an eligible server.
  2. Choose where it can help.Review the permitted channels, roles and settings, then accept the demonstrated configuration.
  3. Approve and maintain the sources.Add, update or remove the rules and FAQs it may use. Changed or expired sources must stop granting access to old answers.
  4. Verify activation and revocation.A commissioned worker and current payment status must match. Cancellation, expiry or revoked server permissions must stop access.

A typed server ID, a checkout redirect or an earlier payment cannot grant access. Paid activation remains unavailable while these checks are incomplete.

Demo and early-access enquiries

What do your moderators keep answering?

Tell us about your community and one question you would like the bot to help with.

Discuss a Discord demo