Assistant

Chat with AGO’s own agent from inside the admin interface.

The Assistant is an in-app chat that connects you to AGO’s own agent while you work in the admin interface. Ask it about your account, search your knowledge base, or get a quick summary of your conversations without leaving the page you’re on. It can also take you to the right admin page.

Open the Assistant

1. Sign in to the admin interface

   Open your AGO admin interface and sign in.

2. Open the Assistant

   Click Ask AGO at the bottom of the left sidebar, or press ⌘K (Mac) / Ctrl+K (Windows/Linux). A companion panel opens on the right, alongside the page — the rest of the admin interface stays usable while you chat.

3. Ask a question

   Type your question in the message box and press Enter to send, or Shift+Enter for a new line — the box grows with your message. Click the X in the panel header to close it — it reopens with your conversation, which is kept even after you refresh the page. Use New conversation to start fresh.

Reopen a past conversation

Click the history icon (the clock in the panel header) to see your past conversations, newest first, each showing its title and the day and time of its last message (for example 23/07/2026 15:03). Click one to reopen it — its title shows in the header and you can carry on where you left off. Use the back arrow to return without switching.

What you can ask

The Assistant answers from the same knowledge and tools your customer-facing agent uses. A few examples:

• “What changed in our knowledge base this week?”
• “Summarize my open tickets.”
• “How do I add a new agent?”

You can also attach a file to a message when your question refers to a document.

Let it take you there

The Assistant knows the admin pages. Ask it to “open the agents page”, “take me to tickets”, or “show the widget settings”, and it navigates you there. Useful when you are not sure where a setting lives.

It can also open the conversations list with filters already applied. Try “show me conversations handled by the Support agent that need review”, or “open conversations from [e-mail]”. You land on the chat history filtered to what you asked for.

On the dashboard, it can switch the view for you: ask it to “open the tickets tab” or “show the last 30 days”, and it changes the active tab and time range.

It can also filter list pages and switch tabs. On User Management, ask it to “search for john” or “show only staff users”; on the knowledge sync history, “show me the failed syncs”; on Agent Permissions, “open the JWT-based permissions tab”.

Two pages belong to a single record rather than to everyone: a user’s profile and a permission. Ask for “the profile of [e-mail]”, or “open the VIP permission”, and the Assistant reads the list first, then opens that record’s page — it needs to find it in the list before it can open it, so a search that returns nobody ends there.

Ask about what a page shows

On User Management, a user’s profile, Agent Permissions, the knowledge sync history and the dashboard, the Assistant reads the page back after it has filtered it, so it can answer about the results and not just apply the filter. Ask “is there a user called dupont?” and it searches, waits for the list to load, then tells you who it found. Ask “why did the SharePoint sync fail?” and it reads the error message off the failed run. On the dashboard, “how does last month compare to the previous one?” gets the conversation and user counts for the period you selected.

On a profile it reads the identity, role, organization, permissions, attached ticket form and the person’s conversation and ticket counts — so “does this user have the VIP permission?” is answered without you scrolling the page. On Agent Permissions it reads the permissions themselves — name, priority, whether they are active, selectable and public, and the agent each one falls back to — so “which permissions are public?” is answered from the list.

It reads what the page shows — the results on the page you are on, not every record you have. Narrow the filters if you want it to look at something further down the list.

See what it’s doing

As the Assistant works, it shows each step inline as it happens — “Navigating to Agents”, “Updating the page”, “Opening conversations” — in the order they occur, between the parts of its reply. A single answer reads as the sequence of what it did and what it wrote: it navigates, writes a line, changes something on the page, then finishes its reply. If you refresh the page, the conversation comes back with the Assistant’s replies (the step-by-step trace is shown live, as it works).

Once three or more steps in a row have finished, they fold into a single line — “3 steps” — so the answer isn’t buried under them. Click it to see the steps, and Hide steps to fold them back. Steps only fold once every one of them has finished.

If you scroll up while the Assistant is still writing, the panel stops following along and a Latest button appears at the bottom to jump back to the end.

Change settings on the page you’re on

On the builder pages for agents, tools, knowledge sources, conversation starters, incident banners, prompt templates, business hours and permissions, the Assistant can fill in the form for you. Describe the change in plain language and it updates the fields — you review, then save.

• Agent builder: name, display name, active/inactive status, instructions (the prompt), model, temperature, top-p, reasoning iterations, background-agent mode, selected tools, number of documents retrieved and shown, public access, and which knowledge sources the agent can search. Try “write the instructions for a polite order-status agent”, “set the temperature to 0.2 and switch the model to GPT-5”, “make this agent public”, “make it a background agent with the Order Lookup tool”, or “let it search all the SharePoint sources” (name a source, or a source type to pick every source of that type).
• Tool builder: name, display name, description, tool type, additional info JSON, input schema JSON, prompt, strict mode, forwarding the user’s authentication, and requiring approval in background runs. Try “create an HTTP request tool for order lookup and turn on strict mode”, or “mark this tool as requiring approval in background runs”.
• Knowledge source builder: name, source type (the connector, e.g. SharePoint or Notion), domain, breadcrumbs, public display, external document links, and automatic sync. Try “create a SharePoint source called HR Portal”, or “enable auto-sync and hide these documents from public display”.
• Conversation starter builder: title, description, initial message, additional prompt, active status, widget auto-starter, and show-on-home. Try “create a starter titled Onboarding feedback that asks how the setup went, and show it on the home screen”.
• Incident banner builder: title, message, banner content for the agent, active status, and the background and text colors. Try “draft a maintenance banner in red and activate it”.
• Prompt template builder: name and prompt content. Try “create a template named Support that tells the agent to keep answers short”.
• Business hours builder: name, timezone, and default status. Try “name it Support hours and set the timezone to Europe/Paris”.
• Permission builder: name, display name, description, priority, color, active/selectable/public status, ticket-creation messages and instructions, and the home page title and subtitle. Try “create a permission named VIP, make it public and set priority 10”.

You can start from scratch and combine it with navigation in one request: “create an agent that searches all our SharePoint sources” opens a blank agent builder and pre-fills it, and “open the tool builder and turn on strict mode” takes you there and applies the change. The Assistant only changes the fields you ask about.

When you ask for a tool or knowledge source that is not available, the Assistant keeps the current selection and tells you which name it could not match. A request that mixes available and unavailable names is refused as a whole, so it cannot replace a working selection with a partial one. If the available choices are still loading, it asks you to retry instead of reporting a change it could not check.

The Assistant also reports when a requested value is already set. It refuses values that the page does not allow, such as an unavailable model or background-agent mode on a router agent. To remove text from an optional field, ask it to clear that field; required names, titles, modes, and prompt content are left intact when no replacement value is provided.

Let it save the page

On those same builder pages, ask it to save and it clicks Save for you: “create a permission named VIP, make it public and set priority 10, then save it” ends on a saved permission instead of a filled-in form. It still only fills the fields you named, so read the page before asking for the save if you want to check its work.

If the page refuses the save, the Assistant tells you why rather than claiming it worked — “the agent cannot be saved, it is missing the agent name” — and you can answer with the missing value in the same conversation.

Deleting needs your approval

Saving happens on your word alone. Deleting does not: on Agent Permissions, ask it to “delete the VIP permission” and it stops and asks first, naming the permission it is about to delete. Nothing is removed until you click Yes in the panel; No cancels and the Assistant carries on without it. If the name it shows you isn’t the one that permission actually has, the deletion is refused even after you approve it.

Troubleshooting

The Assistant can't reach the server

The Assistant connects to AGO’s support service. If messages fail to send, check your network connection and try again, or reload the page.

Replies come back empty

Reload the page and ask again. If empty replies continue, contact AGO support.