When to use Wavo vs Help Center

Wavo is account-aware (sees your data + can take actions). Help Center (Pylon help.wevion.ai) is static documentation (feature reference, best practices). Use Wavo for "what's my X?"; use Help Center for "how does X work?". Wavo can also call create_support_ticket to open a Pylon ticket when human help is needed.

Who is this for

Anyone deciding "should I ask Wavo or look this up in the docs?"

The split

When Wavo is the right tool

Account-specific questions

• "What's my best-performing creative this week?"

• "Which audience converts at the lowest CPA?"

• "Why did my CTR drop on Reels?"

• "What's the difference between Campaign A and B in spend pacing?"

Wavo invokes tools, queries your data, answers with your numbers.

Taking actions

• "Pause every losing adset in account X."

• "Create a rule that scales winners."

• "Draft a new campaign for product Y."

• "Generate 3 image variants for this concept."

Wavo plans + presents approval card (for HIGH/MEDIUM risk) or executes (for LOW risk write tools). See ai-105.

Iterative refinement

• Start broad → narrow down → act

• Multi-turn conversation where each turn refines the previous

• Wavo holds last 20 messages of context

Help Center articles can't do this.

Decision support

• "Should I scale Campaign Z?" — Wavo analyzes + recommends

• "Is my budget pacing on target?" — Wavo computes + flags

• "Compare to last month — what changed?" — Wavo runs the comparison

Personalized analysis Help Center can't provide (it has no account context).

When Help Center is the right tool

Concept explanations

• "What is ROAS?" — definition + formula

• "What is postback attribution?" — explanation

• "How does the Rules Engine evaluate conditions?" — feature mechanics

These are universal facts. Wavo can answer them too (trained knowledge) but Help Center is canonical.

Feature reference

• Endpoint specs

• Schema fields

• Configuration options

• Hard limits + constraints

• Migration guides

Static, comprehensive, searchable. Wavo summarizes; Help Center is authoritative.

Walkthroughs

• "How do I set up Google Drive integration?"

• "How do I connect Meta?"

• "How do I configure a campaign template?"

Static step-by-step guides using location-based language (Pylon style — no visual captures). Better suited for sequential learning than chat.

Best practices

• "Best practices for ROAS targets by industry"

• "How to structure your account hierarchy"

• "When to use prospecting vs retargeting"

Universal advice. Help Center has authored, vetted content.

Wavo + Help Center workflow

A common pattern:

1. Help Center: learn the concept ("What is Cross-Channel analytics?")

2. Wavo: apply to your data ("Show my Cross-Channel KPI strip for last 7 days")

Or:

1. Wavo: get personalized recommendation ("Recommend budget allocation")

2. Help Center: deep dive on the recommended approach ("How does Budget Recommendation work?")

Wavo can open support tickets

When you need human help:

• "I think Wavo got this wrong — open a ticket"

• "I need an admin to look at this"

• "Escalate this question to support"

Wavo invokes create_support_ticket (LOW write mode):

• Creates a ticket in Pylon

• Attaches conversation context

• You + support team can follow up

No approval needed (LOW risk). Wavo confirms ticket ID after creation.

Help Center URL

Live at help.wevion.ai (per PRD-01 SSL fix).

Sections (per apps/backend/scripts/wiki-articles/TAXONOMY.yaml):

• Getting Started

• Account & Billing

• Team & Workspace

• Connect Meta / Google / TikTok / Taboola / Snap

• Commerce & Tracker

• Campaign Creator

• Ads Manager & Reports

• Rules Automation

• Creative Hub

• Analytics

• AI Chat (Wavo) — this section

• Notifications

• Troubleshooting & Glossary

Use Pylon's search (help.wevion.ai/search) to find articles fast.

Anti-patterns

❌ Asking Wavo to explain feature mechanics

"How does the Rules Engine work?" — Wavo can answer, but Help Center has the full reference. Faster for the canonical answer.

❌ Going to Help Center for account data

"What's my ROAS?" can't be answered in static docs. Ask Wavo.

❌ Treating Wavo as bug-tracker

If Wavo (or Wevion) malfunctions: use Help Center → Contact Support, OR ask Wavo to "open a ticket". Don't only post in chat hoping someone notices.

❌ Asking Wavo for company-internal info

"What's the Wevion roadmap?" — Wavo doesn't know company internals beyond product feature knowledge. Check public roadmap / contact CS.

Decision flowchart

Question contains "my" / "this account" / specific entity name?
  → Wavo

Question is "how does X work" / generic feature?
  → Help Center

Need to take an action?
  → Wavo (approval card handles safety)

Need a documented step-by-step setup walkthrough?
  → Help Center

Stuck and need human help?
  → Wavo: "open a support ticket"
  → OR Help Center → Contact Support

Common mistakes

• Asking Wavo where to find a Help Center article — Wavo can search but for fast canonical lookups, Pylon search is direct

• Reading 5 Help Center articles instead of asking Wavo to summarize for your case — Wavo can synthesize across your data + best practices

• Pasting Help Center content into chat — Wavo doesn't need it; it has the platform knowledge embedded

Related

• Meet Wavo — intro

• Credits + limits — Wavo billing

• Troubleshooting — when something goes wrong