Quickstart Overview

Use this guide to move from an empty workspace to a support-ready Woes setup.

Before You Start

Have these ready:

One source of truth for your API support context: docs URL, OpenAPI file, Postman documenter link, GitHub repository, or Markdown runbook.
A few real customer questions your team receives today.
Access to the site where the live chat widget will be installed.
An operator account with permission to manage Context, Agents, Channels, and Settings.

Most teams can complete the first working setup in 15 to 30 minutes. Start with one strong context source, test the agent, then add channels and automation.

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. Live chat is the fastest first channel because you can test it immediately from your own site.

Invite operators

Add team members in Settings → Users and assign the right role.

Review analytics

Use Analytics after the first conversations to inspect answer rate, skip reasons, confidence, surveys, and feedback.

A Good First Test

After the first source and agent are ready, ask the agent three questions:

Question type	Example	What success looks like
Exact endpoint	”How do I create a customer?”	The agent names the right endpoint, method, required fields, and auth expectations.
Troubleshooting	”Why am I getting a 401?”	The agent explains the relevant auth rule and asks for missing details instead of guessing.
Out-of-scope	”Can you change my billing plan?”	The agent hands off or clarifies because the answer depends on account-specific data.

If the answer is weak, open the source detail in Context and check whether the missing endpoint, schema, or behavior was actually indexed. Fixing source coverage usually improves the agent faster than rewriting prompts.

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, assignment, keys, users, roles, surveys, notifications, tags, macros, statuses, and install snippets.

Daily Operator Tools

Tool	Use it for
Command search	Find pages, issues, clients, contacts, sources, and workspace commands.
Keyboard shortcuts	Jump to major pages, issue views, docs, and workspace actions.
Assignment	Route issues by team, capacity, status, schedule, and skills.
Notifications	Tune in-app, sound, browser, email, and push delivery per event.

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.

For best results, add one high-quality source first, test the agent with exact endpoint questions, then expand context coverage.

​Quickstart Overview

​Before You Start

​Setup Checklist

​A Good First Test

​Workspace Surfaces

​Daily Operator Tools

​What To Avoid

Quickstart Overview

Before You Start

Setup Checklist

A Good First Test

Workspace Surfaces

Daily Operator Tools

What To Avoid