Quickstart Overview
Use this guide to move from an empty workspace to a support-ready Woes setup.Setup Checklist
Create or open your workspace
Confirm the workspace name, support URL, timezone, and company details in Settings.
Add source context
Add at least one source in Context. Woes works best when the source includes endpoint paths, auth rules, examples, request bodies, response shapes, and error cases.
Create or tune an agent
Use Agents to attach source context to an agent. Each agent can have its own context, behavior, guardrails, and widget key.
Install a customer channel
Install the live chat widget, connect an email domain, or connect Discord.
Workspace Surfaces
| Surface | Use it for |
|---|---|
| Inbox | Live customer conversations across live chat, email, and Discord. |
| Issues | Durable support work, standalone tickets, linked conversation issues, notes, tags, and workflow state. |
| Context | API docs, repositories, specs, endpoint Markdown, auth configuration, and test readiness. |
| Agents | Multi-agent setup, context attachments, prompts, guardrails, learning, and widget keys. |
| Automations | Triggered workflows for assignment, status, priority, tags, notes, SLA, snooze, CSAT, and auto-replies. |
| Analytics | Operational reporting for conversations, agents, workforce, SLA, surveys, live chat, sources, clients, and feedback. |
| Settings | Workspace configuration, channels, keys, users, roles, surveys, notifications, tags, macros, statuses, and install snippets. |
What To Avoid
- Do not paste production credentials into API source content.
- Do not expose provider or model routing to customers.
- Do not expect the agent to answer from memory when source context is missing.
- Do not use public widget keys as account-level API credentials.