The NewWave agent has two different kinds of knowledge. Keeping them separate is what makes its answers useful and checkable. For an account-specific question, a good answer usually needs both: the documented rule and the live record it applies to. Wavie sits in a panel beside your brand pages, so you can ask a question while keeping the page open. When Wavie is on for your workspace, that panel is your team’s shared chat with Wavie, so teammates see what you ask. On Campaigns, selecting New campaign opens a Wavie chat for campaign setup.

​
The answer flow

1

Identify the question

The assistant separates a general product question from a request about a specific workspace, campaign, creator, submission, or payment.
2

Find the product rule

For “how,” “why,” and policy questions, it searches the canonical brand, creator, and platform-reference guides in this site.
3

Read live state when needed

For account-specific questions, it reads the relevant NewWave record using your permissions. The docs cannot see your account, and live data alone does not define the product rule.
4

Use analytics for calculated numbers

Views, spend, CPM, engagement, and earnings should come from NewWave analytics. The assistant should not recreate totals by adding rows from unrelated screens.
5

Explain and cite

A strong answer states what is happening, gives the documented rule, connects it to the live state, and links the relevant guide when one exists.

​
What the agent should not do

  • Guess a policy when the docs do not cover it.
  • Claim it checked your account when it only read a general guide.
  • Treat a published video as automatically settled or paid.
  • Hand-calculate money when a NewWave analytics result is available.
  • Perform a creator-facing, destructive, or irreversible action without making the action clear and getting your confirmation. In the team chat, Wavie proposes each change and runs it when a teammate taps yes; asking for an exact change counts as your yes. Your team can let Wavie do some routine tasks on its own and tell you after, such as nudging a quiet creator. Money and contracts always wait for a tap.
If the docs and your live state appear to disagree, the right response is to show both and escalate the mismatch. It should not silently choose whichever answer sounds more reassuring.

​
Ask questions that expose both sources

Instead of:
Try:
Instead of:
Try:

​
Canonical knowledge map

Brand operations

Workspace setup, funding, campaigns, creators, reviews, analytics, and settlement.

Creator experience

Accounts, applications, contracts, submissions, publishing, earnings, and withdrawals.

Core concepts

Canonical vocabulary and lifecycle states shared across the platform.

Tracking & payouts

The shared rules behind views, payout calculation, accrual, and settlement.