> ## Documentation Index > Fetch the complete documentation index at: https://docs.tied.com/llms.txt > Use this file to discover all available pages before exploring further. # Quickstart > Ten minutes from an empty account to watching an AI agent resolve a real conversation. By the end of this you will have connected a channel, given an agent something to know, sent a real message, and seen exactly what it cost. That last part matters — it makes pricing concrete before you've committed to anything. **What you need:** a Tied account and about ten minutes. No card, no DNS changes, and nothing to install. We'll use web chat because it's the only channel that needs no verification or carrier approval — you'll be live in under a minute. Sign up and name your workspace. You'll land on the home dashboard with an empty inbox. The Tied dashboard home screen.

Go to **AI agents** and create one. Before touching channels, give it a knowledge source — an agent with nothing to draw on can only escalate, which makes for a dull first test. The fastest option is to point it at a URL: your existing help centre, your FAQ page, even your marketing site. Tied will crawl and index it. If you have no content anywhere yet, paste in three or four of your most-asked questions and their answers. It's enough to see the whole loop work, and you can replace it properly later. Go to **Channels → Web chat** and create an inbox. Attach the agent you just made. The inbox settings page gives you a script tag with your own website token and base URL already filled in. **Copy it from there** rather than from here — the token in it is yours. It looks like this: ```html theme={null} ``` Drop it in before the closing `` tag on any page you control. No website handy? The inbox settings page has a live preview you can talk to directly. The inbox list in settings, with the web chat inbox connected.

The inbox list in settings, with the web chat inbox connected.

Open your page — or the preview — and ask the agent something your knowledge source covers. Something a real customer would ask, not "hello". The agent should answer from knowledge within a few seconds. Switch to **Inbox**. The conversation is there, with the agent's reply already in the thread and an activity entry showing it handled things. This is the view your team will live in. Everything from every channel arrives here. A conversation open in the shared inbox, with the reply composer below it.

A conversation open in the shared inbox, with the reply composer below it.

As the customer, reply *"perfect, thanks"* — or whatever a satisfied person actually says. That's a **Tier 1 explicit confirmation**, the strongest resolution signal there is. Without some positive signal, nothing would be billed at all: [silence never bills](/pricing/resolutions). Open the conversation's receipt. You'll see a `knowledge` resolution — the agent answered from what it knew without touching any external system — at **\$0.35**, plus the model tokens at whatever the provider charged, with no markup. Typically a fraction of a cent. The receipt names which signal tier was relied on, which discriminator assigned the class, and the itemized token cost. That is the whole bill for that conversation. ## What just happened You ran the entire [message lifecycle](/message-lifecycle) end to end: a message arrived on a channel, landed in an inbox, was picked up by an AI agent, got answered from knowledge, and produced a positive signal that turned into exactly one billable resolution. Everything else in Tied is that same path with more capability at each step. ## Next Apple Messages, RCS, SMS, WhatsApp and the rest — capabilities and setup effort compared. Connect an app so it can look things up and fix them, not just answer. The five things to do first, in the order that avoids rework. Two numbers per resolution, and why most conversations produce none. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.