> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ringingo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Configure Ringingo Inbound Campaigns

> Route customer-initiated calls in Ringingo. Configure inbound campaigns with call queues, transfer rules, recording, and number masking.

An Inbound Campaign in Ringingo manages customer-initiated call routing. It defines which outgoing rules are applied for callbacks, whether calls are recorded, and which advanced routing destinations agents can transfer to. Each campaign must be linked to an active Outgoing Rule before it can be saved and activated.

## Manage inbound campaigns

Navigate to **Contact Center → Inbound Campaign** to see the list. From here you can enable or disable via the Status toggle, edit with the pencil icon, delete with the trash icon, or create a new campaign.

| Field          | Description                                                                      |
| -------------- | -------------------------------------------------------------------------------- |
| Name           | Unique identifier for the campaign.                                              |
| Outgoing Rules | SIP trunk routing rule applied to callbacks and outbound transfers.              |
| Status         | Toggle to enable or disable. Only enabled campaigns accept live inbound traffic. |
| Actions        | Edit or delete the campaign.                                                     |

## Create an inbound campaign

<Steps>
  <Step title="Open the form">
    Click **+ Create Inbound Campaign**.
  </Step>

  <Step title="Fill in the basic fields">
    Enter Name, Outgoing Rules, an optional Description, and Status.
  </Step>

  <Step title="Configure advance fields">
    Scroll to **Advance Fields** and choose which queues, ring groups, and IVR destinations agents can transfer to. Toggle recording and number masking as needed.
  </Step>

  <Step title="Save and enable">
    Save the campaign. Enable Status to accept live traffic.
  </Step>
</Steps>

### Basic fields

| Field          | Required | Description                                                 |
| -------------- | -------- | ----------------------------------------------------------- |
| Name           | Yes      | Unique campaign label used across reports.                  |
| Outgoing Rules | Yes      | Outbound SIP trunk routing rule for callbacks or transfers. |
| Description    | No       | Free-text field for internal documentation.                 |
| Status         | Yes      | Enable to activate immediately.                             |

### Advance fields

| Field                       | Description                                                    |
| --------------------------- | -------------------------------------------------------------- |
| Allowed Call Queue          | Restricts agents to specific call queues for inbound handling. |
| Allowed Transfer Ring Group | Ring Groups agents can transfer callers to.                    |
| Allowed Transfer Call Queue | Call Queues agents can transfer callers to.                    |
| Allowed Transfer IVR        | IVR menus agents can transfer callers to.                      |
| Recording                   | Record all inbound calls handled under this campaign.          |
| Number Masking              | Mask the caller's phone number from the agent's view.          |
| Wrap Up Time                | Seconds after a call for agents to complete notes.             |
| Auto Answer                 | Calls connect automatically without pressing Answer.           |
| Agent Script                | Pre-configured script popup appears during calls.              |

<Info>
  Always verify the Outgoing Rule is active and correctly routed to the intended SIP trunk before enabling an Inbound Campaign. A misconfigured rule prevents agents from making outbound transfers or callbacks.
</Info>

## Related

<CardGroup cols={3}>
  <Card title="Call Queues" icon="list" href="/routing/call-queues">
    Waiting queues for inbound callers.
  </Card>

  <Card title="IVR" icon="phone" href="/routing/ivr">
    Menu-driven routing.
  </Card>

  <Card title="Ring Groups" icon="users" href="/routing/ring-groups">
    Simultaneous or sequential ringing.
  </Card>
</CardGroup>