Ask about the subscription you are already looking at

The most annoying thing about product chatbots is the re-explaining. You are staring at a subscription's detail page, and the assistant asks you which subscription you mean. Subscriber Bot's assistant does not, because grounding happens before the question is sent.

The assistant is mounted in the app shell itself, so it is available on every screen — the Overview, Relationships, the Providers registry, the Universal Inbox, Invoices, AI Agents, Workflows, Insights, and the Asset Vault — rather than being a feature of one page. Opening it does not navigate you away or lose your place.

When you send a prompt, the assistant gathers page context first. It matches your current path against an explicit list of entity routes and resolves a typed entity — a Subscriber Bot relationship, provider, agent, invoice, or workflow — together with its identifier. On list and dashboard screens where there is no single entity, it falls back to the active tab instead of guessing. Only the fields on the shared context contract survive the trip to the model; environment details the browser knows about are filtered out on the receiving side rather than trusted to be harmless.

Because grounding is derived from where you are rather than from what you remember to type, the useful questions get short. On a relationship you can ask what it costs, when it renews, and which card pays it. On a provider you can ask which of your relationships point at it. On an agent you can ask which policies bound it. The assistant runs operations against the same workspace API your screens use, with your identity and your permissions, so it can only see and do what you can see and do.

Two honest limits. First, the assistant is a general product operator, not the AI Subscription Brain described in the product vision — it does not yet reason across your whole portfolio to tell you which two services overlap and which one to drop; that reasoning layer is designed and ticketed, not built. Second, the per-product content guide that would teach the assistant Subscriber Bot's domain vocabulary in depth has not been written yet, so answers today lean on the live API and the generic platform guidance rather than a hand-authored subscription playbook.