# Quickstart > From sign-up to an agent answering on your website — create your organization, build an agent, give it knowledge, test it, deploy the web widget, then add WhatsApp or a phone number. Source: https://docs.amomic.in/start/quickstart --- This page takes you from nothing to an agent answering real questions on your website. It takes about twenty minutes, most of it spent on knowledge and testing. Nothing needs installing except one line on your site. **Who can do this:** whoever creates the organization becomes its **owner** and can do every step. If you are joining a colleague's workspace instead, you need the **admin** or **owner** role for steps 2 to 6. **Plan:** everything on this page works on the Free plan (one agent, one knowledge base, web chat, 100 AI conversations a month). WhatsApp and phone numbers need [Starter or above](/operate/limits#plans). Building from your own backend? Do this page first anyway. The API sends messages and places calls *through* an agent and a connected channel, so you need both before [Your first API call](/start/first-api-call) is useful. ::: steps ::: step Sign up and create your organization Go to `https://console.amomic.in/signup`. Enter your name, work email and a password, or choose **Continue with Google**, then click the link in the verification email. On **Create your organization**, enter your **Organization name**, your country (**Where is your business based?**), your **Time zone** and your **Billing currency**. The currency can't be changed later. Click **Create organization**, then **Go to console**. ![The Create your organization form filled in for Veloria Home, with India, Asia/Kolkata and ₹ INR selected and a warning that the currency can't be changed later](https://docs.amomic.in/screens/account/create-organization.light.webp) Every field, and what to do if the email doesn't arrive, is in [Create your account](/start/create-account). ::: ::: step Create an agent Open **Agents** and choose **New agent** (in an empty workspace, **Create your first AI agent** shows the same button). Fill in: - **Agent name**: what customers see on the widget and hear on the phone. `Veloria Support` is fine. `Test bot 2` is not. - **Purpose**: the outcome this agent owns. Describe the job, not the channel. *"Answer warranty, AMC and service-visit questions from our published policy, and hand off anything about refunds"* works. *"Help customers"* does not. - **Business knowledge**: leave it on **Require a ready knowledge base before publishing**. It stops the agent being published with nothing to look up. Choose **Create agent**. The agent opens in its studio. Nothing customer-facing exists yet. ![The Create an agent form with Agent name, Purpose, Additional instructions and Business knowledge filled in](https://docs.amomic.in/screens/agents/new.light.webp) [Agents](/build/agents) explains every field and how to write a purpose that produces a good agent. ::: ::: step Give it something to know An agent with no knowledge can only be polite. Open **Knowledge**, choose **New knowledge base**, give it a **Name** such as `Help centre`, and click **Create**. Inside the knowledge base, click **Add source**. The fastest useful source is your own website: on the **Website** tab, paste your help or FAQ address and add it. The crawler reads up to 60 pages. You can also upload **Files** (a warranty PDF, a price sheet) or paste **Text** (the exceptions your team knows by heart). Most workspaces end up with all three. ![The Add source dialog on the Website tab with a website address filled in and Keep it fresh set to Every week](https://docs.amomic.in/screens/knowledge/add-website.light.webp) ::: tip Start narrower than feels right Start the crawl from your help centre, not your marketing homepage. A crawl reads the sitemap after the start page, so on a large site the 60 pages can be spent on careers and press pages. See [Website sources](/build/knowledge#website). ::: When the source shows ready, go back to the agent, open its **Knowledge** tab, pick the knowledge base under **Choose a knowledge base** and click **Attach**. An agent only answers from knowledge bases attached to it. ![The agent's Knowledge tab with two attached knowledge bases marked ready and the Attach existing knowledge picker](https://docs.amomic.in/screens/agents/knowledge-tab.light.webp) ::: ::: step Test it before anyone else does Open the agent's **Test** tab and ask the five questions your customers actually ask. Not the easy ones: the ones your team gets wrong. Ask a follow-up, too. That is where most agents break. Under each answer you see which sources it used, or **No knowledge used**. Watch for two failures: - **It answers from nowhere.** It states a policy that isn't in your sources. Add the missing source. - **It refuses something it should know.** The passage exists but wasn't found, often because it sits in a table or an image. Rewrite it as a sentence in a **Text** source. Mark good answers **Pass**. A passed test ticks **Test your agent** on Home's launch checklist. ![The Test tab with a threaded conversation: answers showing their sources, one marked pass, and an out-of-scope question showing No knowledge used](https://docs.amomic.in/screens/agents/testing-conversation.light.webp) [Testing](/build/testing) covers what to test and how to read the results. ::: ::: step Publish the first version An agent must be published once before it can be deployed. On the **Overview** tab, choose **Publish first version**. Add a **Version heading** if you like, then **Publish**. Publishing records the agent's setup as Version 1, a point you can compare against and roll back to. It does not freeze what customers get. ::: warning Saved changes are live straight away Once the agent is deployed, every change you **save** (instructions, tools, attached knowledge) reaches customers from their next message. You don't publish or redeploy for it. Test a risky change in the **Test** tab right after saving, and [roll back](/build/versions#roll-back-to-an-earlier-version) if it goes wrong. See [When your changes reach customers](/build/agents#when-your-changes-reach-customers). ::: ::: ::: step Deploy it to your website On the agent, choose **Deploy** and then **Web widget**. This opens **Deploy to the web**, a five-step wizard: | Step | What you do | |---|---| | **Website** | Enter your site's address. The console reads its brand colour and font to pre-fill the next steps. | | **Knowledge** | Check the knowledge bases the agent answers from. | | **Identity** | The bot name, company name, welcome message, suggested questions and picture. | | **Appearance** | Colour, font, theme, position, launcher, greeting bubble and the lead form. | | **Install** | List your **Allowed websites**, pick your platform, copy the snippet and click **Set live**. | The **Live preview** on the right is the real widget answering from your agent. ![The Install step of Deploy to the web: Allowed websites lists three domains, Shopify is selected, the snippet is shown, and the live widget preview is on the right](https://docs.amomic.in/screens/webchat/deploy-install.light.webp) Paste the snippet before your site's closing `` tag: ```html title="One line, before " ``` Your `data-bot` value is your own widget's id, shown in the wizard. The widget only loads on the sites in **Allowed websites**. Open your site in a private window and ask it a question. The conversation appears in [Inbox](/console/inbox). [Web chat](/channels/web-chat) has the platform-specific install steps and troubleshooting. Building your own interface? The [headless client](/channels/web-chat-custom-ui) uses the same deployment. ::: ::: step Add your other channels The same agent can answer everywhere, with the same knowledge. On the agent's **Deployments** tab, each channel has a tile: - **WhatsApp** (Starter and above): connect your WhatsApp Business number through Meta, then deploy the agent to it. See [Set up WhatsApp](/channels/whatsapp). - **Phone** (Starter and above): in India, verify your business once, then request a number and deploy the agent to it. See [Get a number](/channels/phone-numbers) and [How voice works](/channels/voice). [Channels hub](/channels/overview) shows every channel's state in one place, and [Deployments](/build/deployments) covers editing, disabling and moving a deployment. ::: ::: ## You now have - An organization, with you as owner - An agent with a defined job, grounded in your own content and tested - Version 1 recorded, to compare against and roll back to - The agent live on your website, with every conversation in your Inbox Home's **Launch progress** card ticks itself off as you go. Its last item, **Invite your team**, is on [Your team](/console/team#invite-a-teammate). ## Troubleshooting | What you see | What to do | |---|---| | **Publish first version** is disabled | Open **Overview** and resolve the **Required before publishing** items, usually *Attach at least one ready knowledge base.* See [Readiness checks](/build/testing#readiness-checks). | | The wizard shows *Publish the agent first* | Publish from **Overview** or **Versions**, then choose **Deploy** again. | | The widget doesn't appear on your site | Your domain isn't in **Allowed websites**, or the snippet isn't on the page. See [When the widget refuses to load](/channels/web-chat#when-the-widget-refuses-to-load). | | The agent says it doesn't know something that's on your site | The page wasn't crawled, or the answer sits in a table or image. See [When the agent says it doesn't know](/build/knowledge-retrieval#when-the-agent-says-it-doesn-t-know). | | *Agent limit reached* or *Your plan includes 1 agent(s)* | The Free plan has one agent. See [Plans & limits](/operate/limits). | ## Where to go next ::: cards ::: card Find your way around [Using the console](/console/overview): every page in the sidebar and what it's for. ::: ::: card Understand the model [How it fits together](/concepts/architecture): agents, knowledge, deployments and channels on one page. ::: ::: card Find any setup path [Setup directory](/start/setup-directory) starts from the outcome you want and names the test that proves it works. ::: ::: card Drive it from your backend [Your first API call](/start/first-api-call): send a message from your own systems. ::: :::