Skip to main content

Chips (Guided Prompts)

Chips are Boa’s structured, guided workflows. They’re designed to guarantee consistent, high-quality insights — every time, for everyone on your team.
Think of Chips as expert templates. They ask you the right questions, guide you through proven workflows, and deliver outputs you can trust and share.

Why use Chips

Chips solve a critical challenge for creative and performance teams: consistency. When everyone uses Chips, your team gets: Reliable structure — Same workflow, same quality, every time
Clear inputs — No guessing what context to provide
Consistent outputs — Easy to compare, share, and act on
Faster onboarding — New team members get value from day one
Chips are Boa’s “king” feature for enterprise teams. If you need repeatable workflows and guaranteed results, Chips are your best friend.

How Chips work

Using a Chip is simple:
1

Pick a Chip by goal

Browse the Chip Library and choose a Chip that matches your current goal:
  • Discover — Find what’s working
  • Diagnose — Understand why something performs
  • Generate — Create reports and briefs
  • Forecast — Spot emerging trends
  • Monitor — Track competitors and breakouts
2

Provide the minimum inputs

Each Chip asks for specific context to ensure quality results. Common inputs include:
  • Genre — e.g., “fantasy RPG,” “cozy puzzle,” “action shooter”
  • Theme — e.g., “epic battles,” “social gameplay,” “relaxation”
  • Time window — e.g., “last 30 days,” “Q3 2024”
  • Market or region — e.g., “US mobile games,” “global”
Don’t worry — Chips only ask for what they need. You won’t be overwhelmed with fields.
3

Optionally add follow-up questions

After the initial result, you can refine or expand:
  • Ask clarifying questions
  • Request deeper analysis
  • Change the context and re-run
Your Chip result is ready — complete, structured, and shareable.
Chip workflow example

Using a Chip in Boa


Best practices for using Chips

Keep prompts concise

Chips are designed to handle the heavy lifting. You don’t need to write long, detailed prompts — just provide the context fields and let the Chip do the rest. Good example:
  • Genre: “Fantasy RPG”
  • Theme: “Hero’s journey”
  • Time: “Last 60 days”
Over-complicated example:
  • ❌ “I want to understand all fantasy RPG creatives that use hero’s journey narratives, especially those with epic music and cinematic pacing, over the last 60 days, focusing on top-tier performance…”
Keep it simple. Chips are structured to ask for what they need — extra detail can sometimes confuse the flow.

Provide context items when available

If you have specific creatives, competitors, or benchmarks in mind, include them:
  • Reference a specific creative you want to analyze
  • Mention competitors you’re tracking
  • Cite themes or tones you’re exploring

Save to a Report or Creative Brief

Every Chip result can be saved as a Report (for strategy) or Creative Brief (for production). Take advantage of this to build a library of insights over time.
Pro teams create a “Chip Routine” — running the same 2-3 Chips weekly to track changes and spot trends early.

When to use Chips vs Conversational Mode

Use Chips when…Use Conversational Mode when…
You need consistent, repeatable resultsYou’re exploring and don’t have a set structure
You’re onboarding new team membersYou want to ask “why” and iterate deeply
You’re creating deliverables to shareYou’re ideating or brainstorming
You want guaranteed qualityYou’re comfortable with flexible outputs
Many teams start with Chips to build their creative intelligence muscle, then graduate to Conversational Mode for advanced exploration.

Explore the Chip Library

Ready to see what’s available?

Browse the Chip Library

See all available Chips organized by goal