Every Lyra tool, one chat.
AI Advisor is the chat surface of the Lyra Agent. The Agent reads your real account data, answers strategy questions, and when you ask for an action it dispatches the matching Lyra tool — bid optimisation, campaign creation, health analysis, change-history alerts. Read-only by default; nothing writes to your account without you saying yes.
Your account, in scope. Every registered tool, ready to call.
AI Advisor reads your account data, your diary and your onboarding settings, and can dispatch any of the registered functions. It never invents context; everything in its responses is grounded in something you've configured or written.
What it looks like in chat.
Illustrative example: three scenarios on a fictional account. The advisor reads your account, reasons about the question, dispatches the matching Lyra tool, and waits for your approval before anything writes. Click a chip to switch.
What the advisor reads, every turn.
The advisor's responses are grounded in what's stored in your Lyra workspace. No third-party benchmarks, no scraped competitive intel — what you've stored is what the advisor reads.
The same data your dashboard shows.
The advisor reads the same account data your dashboard shows — connected customers, campaigns, conversion data, last-sync timestamps — so the numbers it cites are the numbers you see.
Source · account data · refreshed by data-sync engineEvery decision you've logged is in scope.
Your diary holds the running record of decisions and rationale — what you paused, why, when. The advisor reads these for context, so questions like "remember when we restructured Brand · Search?" land somewhere real.
Source · account diary · per customerYour settings, in scope.
What you told us at setup — goals and targets. The advisor reads it before answering.
Source · onboarding settingsA chat, on a short leash.
Every response is text plus an optional dispatch suggestion. Tool execution requires your explicit yes. Read-only at the model level — the Agent can't bypass the approval gate.
Your account data, your diary and your settings. No third-party benchmarks, no scraped competitive intel, no synthesised numbers. What's in your workspace is what the advisor knows.
Bid optimisation, campaign creation, health analysis, change-history activation, search-terms management, and more. The function table is the agent's tool surface — if a capability isn't there, the advisor can't run it.
Every chat is saved. Resume it later. Nothing is shared across customers or accounts.
The honest answers about the chat.
Can the advisor change my Google Ads account on its own?
No. Every action that mutates Google Ads — bid changes, campaign creation, applied recommendations — runs through an explicit approval step. The model cannot bypass it; the gate is enforced in the dispatch layer, not the prompt. Whatever the advisor proposes, you approve before it ships.
What's actually powering the chat?
The Lyra Agent — our name for the AI layer across the product. Today it runs on Claude Sonnet from Anthropic, via the function-calling pattern. The Agent receives your message, decides whether to read more from your DB, optionally proposes a function call, and returns text plus an optional dispatch suggestion. The orchestration code is ours; we may change the underlying model as the field evolves — the contract with you is the Agent's behaviour, not the model behind it.
What can the advisor not do?
Anything that doesn't have a registered function. The function table is the boundary — if a Lyra capability isn't there, the advisor can't run it. New functions get added as we ship new tools.
Does the advisor remember our last conversation?
Yes — every conversation is saved. The advisor reads recent history alongside your diary to answer follow-ups in context.
Why use the advisor instead of running the tools directly?
Speed and synthesis. The advisor reads your account before answering, so you skip the pull-metrics → form-question → find-the-right-tool cycle. For an experienced operator, going direct to a tool can still be faster — both paths exist.
Run the audit.
Keep the findings.
Connect your account and let Lyra run its 8 tools for 14 days. If the projected waste recovery isn't worth at least 10× the $49, don't pay. You keep every insight either way.
Read-only connect · write access opt-in per tool · GDPR compliant