# Setup directory

> Start with a business goal, see exactly what you need, follow the right guide, and verify that the feature is working before you go live.

Source: https://docs.amomic.in/start/setup-directory

---

Use this page when you know the outcome you want but not the Amomic-AI name for it. Every row tells you what must already exist, where the full instructions live, and what you can observe that proves the setup worked.

You don't need to configure everything. A website support agent needs an agent, knowledge and a web deployment. It doesn't need a phone number, Google Calendar or an API key.

Most rows need the **admin** or **owner** role. Rows that need a particular plan say so. [Plans & limits](/operate/limits) has the full table.

## Set up your workspace

| Goal | Have this ready | Follow this guide | You are done when |
|---|---|---|---|
| Get an account and a workspace | A work email or Google account; your country and billing currency (the currency is permanent) | [Create your account](/start/create-account) | **You're all set** appears and Home opens with the **Launch progress** card. |
| Bring your team in | The admin or owner role, and a free seat (pending invites count) | [Your team](/console/team#invite-a-teammate) | The teammate appears as active on **Settings → Members**, and **Invite your team** is ticked on Home. |
| Set the workspace clock | The admin or owner role | [Settings](/console/settings#organization) | **Time zone** in **Settings → Organization** shows your zone. Campaigns, live hours and call-backs follow it. |
| Choose a plan or add credits | The owner role | [Billing](/console/billing) and [Credits](/operate/credits) | **Billing** shows the new plan, or the **Prepaid credits** card shows the new balance. |
| Work in a second organization | An invitation, or a reason to keep billing and data separate | [Workspaces & roles](/concepts/workspace#more-than-one-workspace) | Both organizations are listed in the organization menu at the top left, each with your role. |

## Build the agent

| Goal | Have this ready | Follow this guide | You are done when |
|---|---|---|---|
| Create the first customer-facing agent | Your workspace and one useful source of business information | [Quickstart](/start/quickstart) | The **Test** tab answers from your source, and the agent is live on at least one channel. |
| Add business knowledge | A website, PDF, pasted text, live HTTPS endpoint or MCP server | [Knowledge bases](/build/knowledge) | The source shows ready, the knowledge base is attached to the agent, and a test answer lists the expected source. |
| Control what the agent may do | An agent; a booking calendar or connected WhatsApp sender for the tools that need them | [Tools and actions](/build/tools) | A test conversation uses the tool when it should, and the tool is off where you turned it off. |
| Change a live agent safely | An agent with at least one published version | [Agents](/build/agents#when-your-changes-reach-customers) and [Versions](/build/versions) | You tested the change right after saving it, published it as a new version, and know which version to roll back to. |
| Put the agent on a channel | A published agent (once) and the touchpoint: a website, a connected WhatsApp number or a phone number | [Deployments](/build/deployments) | The deployment shows `Live` and a real test message or call reaches the right agent. |

::: note Saved changes reach customers immediately
A deployment always serves the agent's saved settings. Publishing records a version you can roll back to; it doesn't hold changes back. See [When your changes reach customers](/build/agents#when-your-changes-reach-customers).
:::

## Connect customer channels

| Goal | Have this ready | Follow this guide | You are done when |
|---|---|---|---|
| Add the website chat widget | A published agent, access to your website's HTML, and its domains | [Web chat](/channels/web-chat) | A private browser window on an allowed domain opens the widget and gets an answer, and the conversation is in Inbox. |
| Build your own chat interface | A web deployment and a frontend where you can load the headless client | [Build a custom UI](/channels/web-chat-custom-ui) | A session starts, messages stream, and the conversation appears in Inbox. |
| Connect WhatsApp | Starter plan or above, a published agent, Meta business access, an eligible number, and the admin or owner role | [Set up WhatsApp](/channels/whatsapp) | A message from a personal phone reaches the number, gets an agent reply, and appears in Inbox. |
| Answer phone calls | Starter plan or above, business verification (India), a number, and a published agent | [Get a number](/channels/phone-numbers) and [How voice works](/channels/voice) | Calling the number plays your opening line, and the call appears on **Calls** with the right agent. |
| Learn why people call | A phone number with an agent on it | [Outcomes on incoming calls](/console/call-outcomes) | After a test call, the call's **Call outcome** card shows the answers and the number's **Outcomes** dashboard counts them. |
| Place calls from your backend | A number with an active voice deployment, an API key with `calls:write`, and a lawful reason to call | [Outbound calls](/channels/outbound-calls) | A test request rings the destination, and the outcome arrives by webhook or `GET /calls/{id}`. |

## Hand customers to people

| Goal | Have this ready | Follow this guide | You are done when |
|---|---|---|---|
| Let a person take over live | The admin or owner role to set it up; live hours and at least one responder | [Human handoff](/console/human-handoff) | A test customer asking for a person appears in **Live support**, and the responder can accept and reply. |
| Follow up asynchronously | An agent with the ticket tool on | [Tickets](/console/tickets) and [Ticket settings](/console/ticket-settings) | A test request creates a ticket with a reference such as `AM-4F91C2E0`, and a reply from the ticket reaches the customer. |

## Run campaigns and automations

| Goal | Have this ready | Follow this guide | You are done when |
|---|---|---|---|
| Send a WhatsApp broadcast | Growth plan or above, a connected WhatsApp number, an approved template, and tagged contacts or a CSV | [Create a campaign](/campaigns/create) | The campaign page shows recipients moving to delivered and read. |
| Have an agent call a list | Growth plan or above, a published agent, a number to call from, and a CSV or tagged contacts | [Create a campaign](/campaigns/create) and [Call scripts](/campaigns/call-scripts) | The campaign's report shows answered calls, and the outcome dashboard fills in. |
| Send recurring payment reminders | Growth plan or above, a connected WhatsApp number, an approved utility template, and how customers pay | [Duesly](/apps/duesly) | Both status chips read **Ready** and **Template selected**, and a test customer's due appears on **Today**. |

## Connect calendars and business systems

| Goal | Have this ready | Follow this guide | You are done when |
|---|---|---|---|
| Let an agent book appointments | A saved booking calendar and an agent | [Appointments and calendars](/console/appointments) | The agent offers only free slots, and a test booking appears on **Calendar**. |
| Block booked time with Google Calendar | A saved booking calendar, the admin or owner role, and a Google calendar you can edit | [Connect Google Calendar](/console/google-calendar) | A timed Google event blocks the matching slot, and a new booking appears in Google. |
| Look up live data from an agent | A public HTTPS endpoint or MCP server with scoped credentials | [Knowledge bases](/build/knowledge#api) and [Tools and actions](/build/tools) | A test answer uses the value your endpoint returned. |
| Let an agent change your system | A public HTTPS endpoint or MCP server, least-privilege credentials, and a safe test record | [Tools and actions](/build/tools#an-action-tool) | A deliberate test changes only the test record, and the action shows in the conversation's trail in [Inbox](/console/inbox#the-operational-trail). |

## Connect your own backend

| Goal | Have this ready | Follow this guide | You are done when |
|---|---|---|---|
| Authenticate to the REST API | The admin or owner role, to create a key on **Developers** | [Your first API call](/start/first-api-call) and [Authentication](/api/authentication) | `GET /api/v1/ping` returns your `workspace_id`, the key's name and the scopes you chose. |
| Send WhatsApp messages from code | A connected sender, an approved template for sends outside the 24-hour window, and a key with `messages:send` | [Sending messages](/api/messages) | The API returns a `message_id`, and the status webhook or Inbox shows delivery. |
| Place AI calls from code | A deployed voice number and a key with `calls:write` | [Placing calls](/api/calls) | The call reaches a final outcome. A `201` only means ringing started. |
| Receive events in your system | A public HTTPS endpoint and somewhere safe to keep the signing secret | [Getting events](/webhooks/overview) and [Verifying signatures](/webhooks/signatures) | A test event shows on **Developers → Webhooks** as delivered, and your code verified its signature. |
| Sync conversations to a warehouse | A key with only `conversations:read`, and a place to store a cursor | [Sync conversations](/recipes/sync-conversations) | Re-running the sync imports no duplicates and resumes after the saved cursor. |

## A reliable setup sequence

For any feature, use the same order:

1. **Check access.** Confirm your Amomic-AI role, your plan, and any permissions you need on the other side (Meta, Google, your own systems) before you start.
2. **Create prerequisites.** Publish the agent once, save the booking calendar, get the WhatsApp template approved, or get the number first.
3. **Connect or configure.** Follow the guide without skipping the choices that decide routing: agent, sender, calendar or number.
4. **Test both directions.** Test what comes in and what goes out. A green **Connected** badge proves authorization, not the whole customer journey.
5. **Test one failure.** Use a closed WhatsApp window, an occupied slot, or a revoked test permission, so your team knows what failure looks like.
6. **Record ownership.** Decide who watches reconnect warnings, failed sources, webhook deliveries, credits and calendar sync.

::: warning Test with non-production records first
Use a test contact, a test calendar event, your own phone and a reversible action. A successful test can send a real message, place a real call, take a real appointment slot or change a record in your system.
:::

## If the guide and console do not match

First check the organization name at the top left: each browser tab works in one organization. Then check your role. Controls that grant access to other services, spend money or change routing are for owners and admins, and **Campaigns**, **Channels** and **Developers** aren't in a member's sidebar at all. A feature your plan doesn't include shows a **Plan** chip in the sidebar.

If a button the guide describes is missing, the usual causes are a missing prerequisite, your role, or your plan. Before you write to support@amomic.in, note the page address, your **Organization ID** from **Settings → Organization**, exactly what the page shows, and when it happened. Those four details are more useful than "it didn't work".