> For the complete documentation index, see [llms.txt](https://docs.arcade.software/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcade.software/kb/ai-video/use-cases.md).

# Use Cases

Arcade's AI Video is built around several common jobs — here's what each looks like in practice.

## Product marketing

### How do teams use AI Video for product marketing?

Turn a new feature or product angle into a short, on-brand video without booking a camera crew or a designer. Describe the feature, attach an existing Arcade demo or a few screenshots, and AI Video drafts a complete first cut — script, scenes, voiceover, and your brand's look — in under a minute. Refine the pacing, copy, or visuals by chatting with the agent before publishing.

## Release announcements

### How do teams use AI Video for a release announcement?

Pair a changelog entry or release notes with a short video that shows the feature in action instead of just describing it. Attach the release notes or a relevant Arcade demo as source material, and AI Video builds a draft that highlights what changed — good for a launch email, an in-app announcement, or a social post.

## Sales follow-ups

### How do teams use AI Video for sales follow-ups?

Generate a short, personalized recap after a call — built from an existing demo or a brief you write — instead of sending a generic follow-up email. Swap in a prospect's name, logo, or screenshots directly in the editor to personalize each one without spending credits — save chat-driven rewrites for the bigger changes.

## Paid ads

### How do teams use AI Video for paid ad creative?

Produce multiple on-brand video variants quickly for testing across channels — different hooks, lengths, or calls-to-action — using the same brand kit and source material each time, so creative stays consistent even when you're iterating fast. [Create Variation](https://docs.arcade.software/kb/ai-video/ai-video/create-variation.md) makes this faster once you have one version you like: reformat it, translate it, or swap the opening instead of starting over for every variant.

## Social media

### How do teams use AI Video for social media?

Post straight from Arcade instead of exporting a file and re-uploading it somewhere else: generate the video, then post it directly to a connected LinkedIn, YouTube, X, or TikTok account from the Share panel's `Socials` tab. See how each post is doing — views, likes, comments, and other platform-specific engagement — on your video library's `Channels` page, without leaving Arcade. See [Sharing & Exporting](https://docs.arcade.software/kb/ai-video/ai-video/sharing-and-exporting.md) for the full breakdown.

## Customer enablement

### How do teams use AI Video for customer enablement?

Turn a new-feature rollout into a short explainer customers can watch before a call or find in your help center, instead of writing another doc nobody reads. For something you do on a recurring cadence — a monthly release recap, a weekly enablement update — save the version that nails your format as a [Template](https://docs.arcade.software/kb/ai-video/ai-video/templates.md), then reuse it: swap in new screenshots and a new talk track each time instead of rebuilding from scratch, and get a pre-approved video ready to send to customers or post publicly.

***

Have a use case that's not listed here? Let us know through our support channel.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.arcade.software/kb/ai-video/use-cases.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
