AI assistants
Example prompts
Questions to ask your AI assistant about your BLU agency, grouped by topic, with the tools each one uses and the permission the key needs.
Ask the way you would ask a colleague. The assistant picks BLU's tools, reads the numbers and answers. Each example shows which tools it uses, and which permission your key needs for them.
Revenue and sales
| You ask | Tools it uses | Permission |
|---|---|---|
| "Show Jane's last 20 transactions from this week." | list_ to find her, then list_ | Transactions |
| "Which sales were reassigned by hand this week?" | list_ | Reassigned sales log |
Fans
| You ask | Tools it uses | Permission |
|---|---|---|
| "How many new and renewed fans did each creator get last week?" | get_ | New and renewed fans |
| "Where do Jane's profile views come from?" | get_ | Profile views by country |
Links
| You ask | Tools it uses | Permission |
|---|---|---|
| "Which tracking links brought the most subscribers this month?" | get_ for each day's gains (recorded from 2026-09-12), list_ for the names | Tracking link daily clicks and subscribers and Tracking links, free trial links and profile promotions |
Team
| You ask | Tools it uses | Permission |
|---|---|---|
| "Who were our top 3 chatters by sales yesterday?" | get_, and list_ for their names | Sales statistics |
| "How fast did fans get replies on each creator yesterday?" | get_ | Messages sent statistics |
Your account
| You ask | Tools it uses | Permission |
|---|---|---|
| "What's our BLU bill for September?" | get_ | Invoice |
| "Which creators disconnected in the last 7 days?" | list_ | Creator status log |
| "What can this connection see?" | get_ | None — a good first question |
Listing your creators and employees is always allowed, so the assistant can always turn a name into the id the other tools need.
When the assistant says it is not allowed
The assistant tells you which permission is missing, using the same name as the app. The agency owner turns it on in BLU under API keys → Edit — no need to reconnect. See Troubleshooting.

