# Campaign Toolkit (/docs/guides/campaign-toolkit)



Some configuration in careCycle does not belong to any single campaign. Routing
groups, calendars, scripts, and sources are **shared
building blocks**: you configure them once, and every campaign (and Cora, your
Receptionist) can use them.

You manage these from **Configure** in the sidebar, which has a tab for each
building block: **Routing**, **Scripts**, **Calendars**, and **Sources**.

<Callout type="warn">
  Because these building blocks are shared, editing one changes it everywhere it
  is used. careCycle shows you which campaigns use each item before you edit, so
  check that list before making changes during business hours.
</Callout>

The Building Blocks [#the-building-blocks]

Start with [Campaign Types and Configuration](/docs/guides/campaign-toolkit/campaigns)
to choose **Voice AI**, **Inbound Agent Queue**, or **Outbound Agent Queue** and
understand the settings each uses. Your organization Receptionist has a dedicated
[setup guide](/docs/guides/getting-set-up/configure-your-receptionist).

<Cards>
  <Card title="Campaign Types and Configuration" href="/docs/guides/campaign-toolkit/campaigns">
    Choose the right campaign, configure its handler and follow-up, and review it before activation.
  </Card>

  <Card title="Routing" href="/docs/guides/campaign-toolkit/routing">
    Where live calls go when the AI or an agent transfers: your team's
    softphones, an external number, or a dynamic destination.
  </Card>

  <Card title="Scripts" href="/docs/guides/campaign-toolkit/scripts">
    Conversation guides with questions and fields for live calls.
  </Card>

  <Card title="Calendars" href="/docs/guides/campaign-toolkit/calendars">
    Availability, appointment lengths and limits, routing, and reminder
    workflows for AI-booked appointments.
  </Card>

  <Card title="Pulse" href="/docs/guides/campaign-toolkit/pulse">
    The workflow builder that decides when each campaign calls, texts, waits,
    and retries.
  </Card>
</Cards>

Sources (where your leads and calls come from) also have a tab in Configure;
they get their own section covering [source
tracking](/docs/guides/sources/source-tracking) and
[ping-post](/docs/guides/sources/ping-post).

How They Connect [#how-they-connect]

A typical escalation shows why these are shared: Cora takes a call, an
Assistant Behavior says "transfer plan complaints live," the **routing
group** routes the call to your service team's softphones, and the
agent who answers sees the **script** attached to that routing group. If
nobody is available, a configured booking fallback can offer a future appointment
using your **calendar**. Review the actual fallback rather than assuming booking
is enabled. **Pulse** is a campaign-owned outreach sequence, while routing groups,
calendars, scripts, and source definitions are reusable shared resources.