Asking questions — best practices

Open /chat or click the Wavo sidebar. Type your question + Enter. Wavo streams the answer. Best questions are specific (campaign name + date range + platform), goal-oriented ("which adset is losing money?" vs vague "show me data"), and context-aware (refer to previous answers). Voice input via Whisper (25 MB max, BCP-47 lang); file upload via paperclip (10 MB max, MIME whitelist).

Who is this for

Anyone new to chat-based AI tools, or anyone whose Wavo questions get vague follow-up requests instead of direct answers.

How to ask

Method 1: Type

1. Open /chat

2. (Optional) Pick / create a project

3. Type in the input box

4. Enter to send (Shift+Enter for newline)

Method 2: Voice

1. Tap the mic icon

2. Speak your question

3. Whisper transcribes (POST /api/v1/chat-voice/transcribe, 25 MB max, BCP-47 language code — default it)

4. Transcribed text appears in input → edit if needed → send

Note: Wavo transcribes your voice (input only). It doesn't speak back. See ai-102.

Method 3: File upload

1. Tap the paperclip icon

2. Pick a file (10 MB max)

3. Wavo receives the file as context for your next message

Allowed file types (POST /api/v1/chat-upload MIME whitelist):

• Images: JPEG, PNG, WebP, GIF

• Documents: PDF, CSV, plain text, DOCX, XLSX

Larger files or other formats: rejected with clear error.

What makes a good question

Specific > vague

Specific questions get direct answers. Vague questions get follow-up requests for context.

Goal-oriented

State why you're asking, not just what. Helps Wavo pick the right tool + frame the answer.

• "Why did Campaign Y's CPA spike yesterday?" (diagnostic)

• "Which audience converts best for product X?" (optimization)

• "Should I scale Campaign Z?" (decision-support — Wavo will analyze + recommend)

Context-aware

Refer to prior messages:

• "From those 5 campaigns you just listed, which has the worst frequency?"

• "Apply the same filter as my previous query but for last month."

Wavo holds last 20 messages in context (MAX_HISTORY=20). Beyond that: restate or rely on project memory.

State constraints up front

If you have non-negotiables: say them. Examples:

• "Budget is fixed at €1000 — don't suggest increases."

• "Currency = EUR; don't show USD."

• "Only consider campaigns active in last 30 days."

Examples by use case

Performance review

What are my top 10 adsets by ROAS for last 7 days on Meta, 
sorted descending, excluding any with spend below €50?

Diagnostic

Campaign 'Spring Sale Prospecting' had ROAS 3.2 last week 
but dropped to 1.5 this week. What changed?

Action with approval

Pause every adset in account act_123 with CPA > 30 over last 7 days, 
spend > €50, status active.

(Wavo will present an approval card listing matched adsets before executing.)

Comparison

Compare Meta vs Google CPA for prospecting campaigns this month.

Creative

Draft 3 short Reels ad scripts (30 seconds) for product X 
targeting Italian users 25-45 interested in fitness.

Cross-tool

First check which audience has best ROAS this month, 
then draft a new campaign targeting that audience.

(Wavo will chain 2 tool calls: get_audience_insights → create_campaign_draft.)

When Wavo asks back

If your prompt lacks essential info (budget, target country, product, objective), Wavo asks. Don't try to make Wavo guess — provide the missing piece. Saves multiple back-and-forth turns.

Mandatory info Wavo will ask if missing:

• Campaign / adset / ad name or ID (for actions on entities)

• Date range (for analytics queries)

• Platform (when ambiguous)

• Currency (for budget actions)

• Target audience / country (for new campaigns / creatives)

Follow-up chips

After most answers, Wavo suggests up to 3 follow-up questions (chips, max 80 chars each). Click to send instantly. Useful for quick drill-downs.

Generated by Wavo per-context. Disable in /settings → AI preferences if you find them noisy.

What NOT to do

Don't ask "yes / no" questions

"Is this campaign good?" — too subjective. Try "Compare this campaign's ROAS to my account average."

Don't ask for unsupported actions

"Switch to dark mode" — Wavo can't change UI settings. Use the settings menu directly.

Don't paste secrets

Don't paste API keys / passwords / tokens into chat. Wavo's sanitization redacts known patterns, but the safest path is not to share them at all.

Don't expect cross-team queries

"What's the other team's ROAS?" — won't work. Strict team isolation.

Don't ask Wavo to ignore approval

"Just do it without asking me" — approval cards are mandatory for HIGH/MEDIUM risk. Cannot be disabled.

Common issues

• Wavo asks too many follow-ups: your prompts are too vague. Be specific.

• Voice transcription wrong language: pass language param BCP-47 (e.g. en, es).

• File upload rejected: check size (10 MB max) + MIME whitelist.

• Wavo replies in wrong language: set user_ai_preferences.preferred_language (default auto — Wavo matches your input language).

Related

• Prompt tips — patterns for mediabuyers

• Data grounded — what Wavo can see

• Actions Wavo takes — approval flow