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

# Set up battle cards

> Write the answers you want reps to give to common objections, and put them where reps and Live Assist can use them during a call.

export const AiPrompt = ({children, label = "Prompt"}) => {
  const body = useRef(null);
  const [copied, setCopied] = useState(false);
  const copy = () => {
    const text = body.current ? body.current.innerText.trim() : "";
    if (!navigator.clipboard) return;
    navigator.clipboard.writeText(text).then(() => {
      setCopied(true);
      setTimeout(() => setCopied(false), 1600);
    }).catch(() => {});
  };
  return <div className="sf-prompt not-prose">
      <div className="sf-prompt-head">
        <span className="sf-prompt-label">
          <svg width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" aria-hidden="true">
            <path d="M12 3l1.9 5.1L19 10l-5.1 1.9L12 17l-1.9-5.1L5 10l5.1-1.9z" />
          </svg>
          {label}
        </span>
        <button type="button" className="sf-prompt-copy" onClick={copy} aria-label={copied ? "Copied" : "Copy prompt"}>
          {copied ? <svg width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2.2" strokeLinecap="round" strokeLinejoin="round" aria-hidden="true">
              <path d="M20 6L9 17l-5-5" />
            </svg> : <svg width="14" height="14" viewBox="0 0 24 24" fill="none" stroke="currentColor" strokeWidth="2" strokeLinecap="round" strokeLinejoin="round" aria-hidden="true">
              <rect x="9" y="9" width="12" height="12" rx="2" />
              <path d="M5 15H4a1 1 0 0 1-1-1V4a1 1 0 0 1 1-1h10a1 1 0 0 1 1 1v1" />
            </svg>}
          <span>{copied ? "Copied" : "Copy"}</span>
        </button>
      </div>
      <div className="sf-prompt-body" ref={body}>
        {children}
      </div>
    </div>;
};

A battle card is your team's best answer to something reps hear all the time: "we already have a
dialer", "no budget", "send me an email". Write it once, and it is in front of every rep when
they need it.

<Note>
  Battle cards are available on every plan. Anyone on your team can create, edit or delete a card,
  so agree on who looks after them.
</Note>

## Where battle cards show up

<CardGroup cols={2}>
  <Card title="In the dialer" icon="phone">
    Every contact has a **Battlecards** tab next to **Info and History**, so a rep can read a card
    while the phone is ringing.
  </Card>

  <Card title="On screen, during the call" icon="headset">
    [Live Assist](/live-assist/overview) takes its suggested lines from your cards and shows which
    card a line came from.
  </Card>

  <Card title="In the AI Copilot card" icon="sparkles">
    The **AI Copilot** card in the dialer pulls in battle cards, customer references and talking
    points as the call goes on.
  </Card>

  <Card title="In practice" icon="dumbbell">
    The [AI Training](/coaching/ai-training) practice screen has a **Battlecards** tab too, so reps
    can rehearse the answer before they need it.
  </Card>
</CardGroup>

## Create a battle card

<Steps>
  <Step title="Open Battlecards">
    In the sidebar, open **Analytics**, then **Battlecards**.
  </Step>

  <Step title="Click Create New">
    The **Create battlecard** window opens.
  </Step>

  <Step title="Name the card">
    In **Name**, write the objection or situation the card is for, such as "Budget" or "Already
    have a dialer". One objection per card works best.
  </Step>

  <Step title="Write the answer">
    In **Content**, write what you want the rep to say. You can add headings, lists, tables,
    quotes and checklists.
  </Step>

  <Step title="Click Create">
    The card is live for the whole team right away.
  </Step>
</Steps>

To change a card, click the pencil on it. To remove one, click the trash can.

<Warning>
  Deleting a card happens at once, with no confirmation and no undo.
</Warning>

## Write cards that work during a call

A rep has about two seconds to use a card. Write for that.

* **Put the line first.** Start with the one sentence you want the rep to say. Background and
  detail go underneath.
* **One objection per card.** Give it the name a rep would recognize. Live Assist shows that name
  next to the line, such as **Battle card · Already have a dialer**.
* **Follow with a question.** A good answer ends by handing the conversation back, such as "What
  would you improve about it?"
* **Use real proof only.** Name customers and numbers you can stand behind. Live Assist drops a
  line that quotes a number it can't find in your cards or the call.
* **Keep it short.** A few lines beat a page.

### What Live Assist reads

At the start of each call, Live Assist reads your battle cards, most recently updated first. It
reads up to 40 cards, the first 2,000 characters of each, and 24,000 characters in all. If you
have more than that, the cards you updated longest ago are the ones left out.

[Team plays](/live-assist/overview#set-it-up-for-your-team) come before battle cards. Use a team
play when you want exact words for one trigger, and a battle card for everything a rep should know
about an objection.

## How reps use them in the dialer

On a contact in the dialer, a rep clicks the **Battlecards** tab to see every card. To arrange
them, click **Edit layout**, drag the cards into the order you want or hide the ones you don't
use, then click **Done editing**. The layout is saved in that browser, for that rep only.

## Have Ari write your cards

If your plan includes [Ari](/ari/overview), it can read your past calls and write the cards for
you. Open Ari and ask:

<AiPrompt>
  Look at our last 30 scored calls. Find the objections that came up most, and what worked and what didn't when reps answered them. Create a battle card for each objection, with the answer that worked best written as one short line a rep can say.
</AiPrompt>

Ari creates the cards without asking for approval first, so read them on the **Battlecards** page
and edit anything that doesn't sound like your team. To keep them current on a schedule, see
[Set up a playbook that learns from your calls](/coaching/self-learning-battle-cards).

## Good to know

<AccordionGroup>
  <Accordion title="Who can edit battle cards?">
    Everyone on the team. There are no manager-only cards.
  </Accordion>

  <Accordion title="Is there a limit on cards?">
    Not on the page. Live Assist reads up to 40 cards on each call, most recently updated first.
  </Accordion>

  <Accordion title="A card isn't showing up in Live Assist. Why?">
    Check that the card has text in **Content**, and that it is among your 40 most recently
    updated cards. If a team play matches what the prospect said, the team play wins.
  </Accordion>

  <Accordion title="Is there an API for battle cards?">
    No. Battle cards are managed in the app, or by Ari.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Set up a playbook that learns from your calls" icon="arrows-rotate" href="/coaching/self-learning-battle-cards">
    Have Ari review calls on a schedule and keep your cards current.
  </Card>

  <Card title="Get help on live calls with Live Assist" icon="headset" href="/live-assist/overview">
    Put the right card's line on screen the moment a prospect pushes back.
  </Card>
</CardGroup>


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