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

# Plays

> Monitor customer outcomes with AI, surface recommendations when something needs attention, and prepare actions for the account owner to review.

A Play watches your customers for an outcome you care about: keeping onboarding moving, preparing for renewals, or following up on commitments. It uses a [skill](/product/skills) to read customer context, decide whether something needs attention, and surface a recommendation in [Actions](/product/actions).

Manage Plays from the **Agents** page. Use the **Plays** filter to find them.

## Creating a Play

Choose **Start from scratch → Play → Create Play**, or **Create from template** to start with a configured Play and its skill. Templates cover renewal preparation, touchpoint follow-up, growth and expansion, onboarding, collections, account monitoring, and project updates.

Before publishing, connect the [data sources](/integrations/introduction) your skill needs. If you want to target a particular group, create a customer segment under **Settings → Customer Segments** first.

In the **Builder** tab:

<Steps>
  <Step title="Define the successful outcome">
    Describe what the Play should help achieve. For example, *"Keep onboarding on track by identifying blocked tasks and commitments that need a follow-up."* This guides which changes are worth turning into Actions. You can rename the Play and edit its description in **Play settings**.
  </Step>

  <Step title="Choose the audience and cadence">
    Target **All customers** or a **Specific segment**. A customer can belong to multiple Plays.

    Choose **When customer data changes**, **Every day**, **Every week**, or **Every month**. Event-driven Plays evaluate the affected customer after relevant data is processed. Scheduled Plays re-check the audience at a time Quivly chooses automatically.
  </Step>

  <Step title="Select a skill">
    Choose a published skill that defines what to investigate and which data to read. Use the preview icon to inspect it, or **Create** to describe a new skill with AI. Publish the skill before using it in a live Play.
  </Step>

  <Step title="Choose actions">
    In the **Actions** panel, enable the Quivly actions or connected app actions the Play may propose. Open a group's details to see its supported operations, or use **Suggest actions** for recommendations based on your Play. Suggestions take effect only after you accept them.

    A blank Play starts with no actions enabled; templates keep their configured choices. You can leave actions off to surface findings without proposing changes.
  </Step>

  <Step title="Configure delivery">
    Choose where new Action alerts go: Slack, email, or both. Actions also appear in the Actions inbox. Delivery settings are explained below.
  </Step>
</Steps>

The customer owner must approve proposed changes before they run. Enabling an action gives the Play permission to prepare it for review.

## Delivery

| Destination | Options |
| - | - |
| **Slack** | Send to the **Owner DM** or a **Channel**. Owner DMs require a fallback channel if the DM cannot be opened. Invite your workspace's Quivly app to private channels before selecting them. |
| **Email** | Send to the **Account owner**, a workspace user, or **Custom** email address. Changing the recipient does not change who can approve actions. |

**Send test Slack message** and **Send test email** send a sample alert without running the Play or creating Actions. For owner delivery, the test goes to your own DM or email; live alerts go to each account owner.

<Note>
  A custom email address can be outside your workspace. The email includes Action details, but opening the Action still requires workspace access.
</Note>

## Previewing and publishing

Open **Preview**, choose a customer in the audience, and inspect the output in the **Quivly** and **Slack** views. Preview uses real customer data without creating Actions, approving changes, or sending messages. If there is no useful recommendation, it explains why.

If your skill requests a combined digest, you can preview a report across the audience. Automatic digests require a scheduled cadence and a Slack channel; owner DMs deliver customer-specific Actions.

Click **Save draft**, then **Publish Play**. Publishing requires a published skill that identifies the data the Play needs, plus a valid destination for each enabled delivery channel. The Play evaluates matching customers when the required data is ready.

Edits stay in a draft while the published version keeps running. Save and publish again to make changes live. Use the **Active** toggle or **Play settings** to pause the Play.

## Reviewing results

Open **Action History** to search and filter the Actions generated by this Play across its published versions. Select an Action to read the finding and review its proposed next steps. The same items are available in the [Actions inbox](/product/actions).

For example, **Automate project updates** reads calls and Slack conversations and proposes changes to projects, tasks, and milestones. The customer owner reviews the proposed changes before they are applied.

## FAQ

<AccordionGroup>
  <Accordion title="How is a Play different from a workflow?">
    A [workflow](/product/agents) follows a defined sequence of steps on a visual canvas. A Play uses a skill to assess customer context against your desired outcome and decide which findings and next steps to surface.
  </Accordion>

  <Accordion title="Why hasn't my Play created an Action?">
    Check that the Play is published and active, the customer is in its audience, and the required data sources are connected and ready. Preview the customer to see whether data is missing, the issue has already been surfaced, or there is no new action worth taking. A scheduled evaluation does not guarantee a new Action.
  </Accordion>

  <Accordion title="Does connecting an app make it trigger the Play?">
    No. Connecting an app for actions lets the Play propose supported operations in that app. It does not automatically add the app's incoming events as triggers.
  </Accordion>

  <Accordion title="Can a Play change data or send a drafted message without approval?">
    Proposed changes and messages require the customer owner's approval. Slack and email alerts about those Actions are delivered automatically according to your delivery settings.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.