> ## 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. # Setup checklist > Five things to do first, in the order that avoids rework. You can do these in any order, but this one avoids rework. Each step assumes the one before it. Start here, not with channels. The agent is what everything else gets pointed at, and building it first means your first real conversation already has something to handle it. Give it a knowledge source — your Help Center is the obvious one, and if you don't have content yet, a handful of your most-asked questions beats nothing. An agent with no knowledge can only escalate. Creating an agent, knowledge sources, and how to specify its behaviour. **One.** The instinct is to connect everything on day one; resist it. Pick the channel your customers already use most, get it genuinely working, then add the rest. Web chat is the fastest to stand up — a script tag and you're live. Apple Messages for Business and RCS are the highest-value but need brand verification, which takes days, so start those applications now and let them run in the background while you use something else. Every channel compared: capabilities, cost model, plan availability and setup effort. This is the step that changes what your agent is capable of, and the one most often skipped. An agent with no integrations can only answer from knowledge. Connect your order system, CRM or payment processor and it can look things up — and, on Advanced, actually fix things. The difference between *"let me check on that"* and *"I've refunded it, you'll see it in three days"* is entirely this step. Authorise, grant scopes, verify. Optional, and genuinely optional — plenty of accounts run well without one. Build a flow where you need a path handled identically every time: an onboarding sequence, a returns process with strict eligibility rules, anything with a compliance script. Let the agent handle everything else freely. The canvas, node types, branching and versioning. Last, deliberately. Invite people once there is something for them to walk into — a working channel, an agent that handles the easy volume, and integrations that make the hard ones tractable. Set up teams and business hours at the same time. Routing rules with no teams to route to is the most common reason a first week goes badly. Inviting people, assigning roles, and setting up teams. ## Then what Once those five are done, the useful next moves are all measurement and tightening: The strongest resolution signal there is — and negative feedback automatically voids a billed resolution, so it protects you as well as informing you. First-response and resolution targets, and what happens on breach. Doubles as your public knowledge base and your agent's knowledge source. What a resolution is, what it costs, and what never bills. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.