Using the inspector

Updated

Plan requirement

App pluscloud AI Agent Preview
Subscription Suite Team or higher, Support Team or higher
Access Client admin, Client editor, Client user

The inspector shows what the AI agent sent, what the channel receives and the IDs and session parameters of the test, next to the preview.

Open the inspector

Click Inspector in the toolbar, or hover over a message and click Inspect message. A badge on the toolbar button counts the messages with a warning. The inspector opens beside the preview. Drag its left edge to make it wider, or use the expand button at the top; it remembers the width. It has four tabs: Message, Conversation, Log and Events. The Log tab has its own article: Reading the conversation log. The inspector also works for a conversation you show from the conversation logs; see Viewing a logged conversation in the preview.

This inspector belongs to the preview in the AI agents dashboard. For the Web Widget on a website there is a separate Web Widget inspector; see Getting started with the Web Widget inspector. All raw data, with response times, is also in Chrome DevTools; see The AI Agent Inspector panel in Chrome DevTools.

Message

The Message tab shows the message you chose to inspect. Without one, it asks you to hover over a message and click the angle brackets.

  • Raw AI agent text: the output as the AI agent produced it, including the shorthand for buttons and images, with a Copy button.
  • Delivered by Sunshine Conversations: the message type, the text, each button with its type, and the image or the number of carousel cards. For a message from a dialogue, the node ID, with Locate in tests of a dialogue, branch or procedure. For a generative reply, its source.
  • Knowledge sources: the sources a generative reply cited. See Sources and the article viewer.
  • Help Center articles: in the Web Widget preview, each link to a Help Center article, with whether it opens in the widget or in a new tab, and why.
  • Checks: warnings about the AI agent's output and the limits of the channel. No issues found. when there are none. See Messages marked as not delivered.
  • On followed by the channel name: what that channel changes or leaves out. Not shown for the Web Widget.

Conversation

The inspector on the Conversation tab next to the preview. Under Identifiers are the dialogue name Order status, placeholder IDs for the AI agent, the conversation and the platform conversation, four visited nodes and the capture tags socket and test. Under Session parameters are a first name, a last name, an example email address and an order number, with a Copy button and a Session parameters button.

  • Identifiers: the dialogue you are testing, the ID of the AI agent (botId), of the conversation (conversationId) and of the conversation on the messaging platform (platformConvId), and the number of visited nodes.
  • Capture: socket when the preview follows the live test, dom when it rebuilt the conversation from what the test widget showed. test marks a test conversation.
  • Copy link to conversation log and a link to Open in conversation logs.
  • Ticket, with Open ticket: the Zendesk ticket of the conversation, when it has one. Test conversations get no ticket; a conversation you show from the conversation logs can have one.
  • Session parameters: the values the test runs with, which you can copy as JSON. In a dialogue test, the button under them opens the session parameters dialog; otherwise a line explains where to start such a test.

Session parameters can contain personal data such as a name or an email address. They stay in your browser, as described in What the extension can access and store.

Events

The raw events between the test widget and the AI agent, newest first, with the time and the direction of each event. This tab is meant for detailed debugging.

See also

Was this article helpful?

0

Still stuck?

Our support team will take a look with you.

Comments

0 comments

Please sign in to leave a comment.