GuildPilot
Product documentation

How GuildPilot is meant to be used

Discord-first auth, server operations, tickets, automation, AI, and paid onboarding in one place.

1. Login and identity

  • GuildPilot uses Discord authentication because the product is Discord-native.
  • We do not force email/password sign-in for core access.
  • Billing contact details are captured separately when a workspace upgrades to a paid plan.

2. Bot install and server linking

  • Invite the bot into the target Discord server.
  • Register the guild in the Servers page so GuildPilot knows which workspace owns it.
  • Once linked, that server becomes available for support and automation workflows.

3. Ticket operations

  • Post a ticket panel in Discord using the bot command flow.
  • When a user opens a ticket, GuildPilot records the ticket and the Discord channel.
  • When the ticket closes, transcripts are tracked so the web app has an audit trail.

4. Automations

  • Automations are modeled as trigger, condition, action.
  • Examples: ticket escalation, member onboarding, button-driven partner workflows.
  • Start small. Bad automations scale stupidity faster than good ones scale help.

5. AI assistant

  • AI should answer known questions, not invent policy.
  • Use confidence thresholds and support-role escalation when the bot is uncertain.
  • Knowledgebase quality matters more than raw model enthusiasm.

6. Billing and paid onboarding

  • Billing contact and address details live in the Billing page.
  • Those details are meant for paid-plan onboarding, not base sign-in.
  • This keeps the Discord login path clean while still supporting real business customers.
Current API surface

Useful endpoints in the current MVP

These are the endpoints currently wired on the web side.

Auth

  • /api/auth.php?action=discord_start
  • /api/auth.php?action=discord_callback
  • /api/auth.php?action=discord_implicit_complete
  • /api/auth.php?action=logout

Servers

  • /api/servers.php?action=list
  • /api/servers.php?action=link

Tickets

  • /api/tickets.php?action=create
  • /api/tickets.php?action=close
  • /api/tickets.php?action=transcript
  • /api/tickets.php?action=list

AI and automations

  • /api/automations.php?action=list
  • /api/automations.php?action=save
  • /api/ai.php?action=settings