Skip to main content

​
Platform Overview

The Woes platform is organized around the work a developer-support team does every day: answering conversations, tracking issues, managing customers, teaching AI agents, and measuring quality.

​
Core Areas

1

Set workspace data

Configure tags, statuses, priorities, custom fields, and macros in Data, Tags, Statuses, and Macros.
2

Invite users

Add operators and admins through Users and Permissions.
3

Create keys

Review widget keys and workspace API keys in Keys.
4

Define routing

Use Assignment to decide how work enters queues.
5

Review reporting

Use Analytics and usage visibility to check capacity and quality.

​
Configuration Boundaries

  • Workspace settings are permission-gated by section.
  • Widget public keys are safe for browser installs but do not grant account access.
  • REST API keys are private server-side credentials and should never be placed in client-side code.
  • API credentials used for live testing stay separate from source content and are not returned in plaintext.
  • Provider routing and model internals are not exposed as customer-facing settings.

​
Daily Operator Rhythm

  1. Open Inbox and clear urgent or assigned conversations.
  2. Take over AI-handled conversations when the customer needs a human.
  3. Convert durable work into issues.
  4. Update tags, priorities, and notes before closing work.
  5. Review analytics and knowledge-base gaps at the end of the day or week.
Last modified on July 3, 2026