> ## Documentation Index > Fetch the complete documentation index at: https://docs.a2v2.ai/llms.txt > Use this file to discover all available pages before exploring further. # Automations > Decide automatically who owns each new contact and what pipeline stage they start in — so leads never sit unassigned. A lead comes in at 11pm. Who follows up — and when do they find out it's theirs? With **Automations**, that's already decided: the moment a contact is created, A2V2.ai assigns the right owner and drops them into the right pipeline stage, no manual triage required. Open your agent and choose **CRM → Automations** in the sidebar. The page is titled **CRM Automations**, with the subtitle "Configure what happens automatically when a contact is created." The Automations screen is **desktop only**. On a small screen you'll see a "Desktop Only" message asking you to switch to a larger display. ## Prerequisites * An agent (see [Create an agent](/building/create-agent)). * For assignment rules, the team members you want to assign should already be admins of your organization. ## The trigger Automations run on a single trigger — **Contact created**: "Runs the automations below every time a new contact enters this chatbot." Whether the contact was added by hand or captured by the agent, the rules below decide what happens next. The settings are configured **per agent**, split across two tabs: **Admin Assignment** and **Contact Stage**. CRM Automations page showing the Contact created trigger and the Admin Assignment and Contact Stage tabs ## Admin Assignment This tab decides who owns a new contact. A2V2.ai distinguishes **how** the contact was created, because the right owner is often different for each: * **Manually created contact** — "An admin adds the contact." * **Agent captured contact** — "Captured from the chatbot." For each method you set a **Primary Admin** and an optional **Secondary Admin** (a backup, assigned alongside the primary). Each is filled using one of these strategies: | Assign to | What it does | Available for | | -------------------------- | ----------------------------------------- | ----------------------------------------------------- | | **Creator of the contact** | The admin who created the contact | Manual only (a captured contact has no human creator) | | **Owner of the Org** | The organization owner | Manual and captured | | **Selected Admin** | A specific admin you choose | Manual and captured | | **Round Robin** | Rotate across a pool of admins you define | Manual and captured | | **None** | Leave the slot unassigned | Manual and captured | ### Round Robin Choose **Round Robin** to share leads fairly across a team. You define a **rotation order** of admins (add at least two), and each new contact advances to the next admin in the list. Primary and Secondary rotations are set independently, and an admin can't sit in the same slot twice — used admins are greyed out so a contact never gets the same person as both primary and secondary. When no owner is configured, new contacts are assigned to the organization owner by default, so a contact is never left with nobody responsible for it. ## Contact Stage This tab sets the **pipeline stage** a new contact starts in — "The pipeline stage a new contact is placed in." You can set a different default for manually added versus agent-captured contacts: * **Lead** — "Top-of-funnel, not yet qualified." * **Prospect** — "Qualified and being pursued." Whatever the starting stage, admins can move a contact along the pipeline manually at any time (see [stages on a contact](/crm/contacts#owner-stage-and-status)). ## Save your changes Automation changes are staged until you save — the page shows an **Unsaved** marker while you have pending edits. Select **Save changes** to apply them, or **Discard** to revert. Every change is recorded in your organization's audit log (what changed, who changed it, and when). ## Automation Logs To see automations in action, select **View logs**. The **Automation Logs** drawer shows "When automations ran, what changed, and how long they took." Each run records the contact, the **Process** (Admin Assignment or Contact Stage), the **Trigger** (Manual or Agent), a **Status** of **Success** or **Failed**, and the time taken. Filter by **Process**, **Trigger**, **Status**, and **Time range**, and open any run for full details of what changed. ## Use cases * **Fair lead distribution** — set captured contacts to **Round Robin** across your sales team so inbound leads rotate evenly. * **Owner-led manual entry** — set manually created contacts to **Creator of the contact**, so whoever adds a contact owns it. * **Clean pipeline** — start captured leads as **Lead** and manually added, pre-qualified contacts as **Prospect**. ## Troubleshooting Check the slot's strategy. If it's set to **None**, the slot is intentionally left empty. If an admin in a Round Robin or Selected rule was removed from the org, the run falls back — open the run in **Automation Logs** to see what happened. A rotation needs at least two admins, and the same admin can't appear in both the Primary and Secondary order on the same row. Adjust the orders so they differ. Automation edits stay in an **Unsaved** state until you select **Save changes**. Save before leaving the page. Automation configuration is available on desktop only. Open the agent on a larger screen. ## Related See owners and stages on the contact records automations create. Control what the agent captures on each new contact. Forms also create contacts — automations apply to them too. How automations fit into the wider CRM.