Test Poppy agents with Ari

Status: Current | Last reviewed: 2026-10-20

Use Ari to try an assistant experience with your Poppy agents, inspect the Company's original responses and compare protocol checks after an update. Ari is a separate web app with its own address.

On Vanguard, open https://assistant.vanguard.dev.trueserve.deloitte.com.

Sign in

Choose Continue with Studio, sign in through your existing Studio account and authorize Ari. Your existing tenant and Run Agents permissions apply. You do not need a separate demo account.

Each user has a private workspace within their tenant. Connections, chats, approvals, test runs and appearance are saved there. To use another tenant, sign out of Ari, select that tenant in Studio and sign in to Ari again.

Studio sign-in gives you access to the test app. Connecting a Company's customer account is a separate consent step.

Add a connection

  1. Open Connections.
  2. Choose Add a connection.
  3. Select a company under Available connections, or enter its website or connection link and choose Connect.
  4. Watch Ari find the company and set up the connection.
  5. When the app confirms the company is added, choose Talk to Ari to start a conversation, or Done to return to your connections.

The available list comes from your current Studio tenant and refreshes while you use it. Use its refresh button to check for newly published agents. If setup fails, check the address and choose Try again. Retrying a completed setup reuses that connection.

In desktop view, Advanced settings lets you choose an Assistant profile before connecting. Discovery, versions and extension details are also available there. Phone view uses the default profile and presents the connection as an app feature.

Your administrator must first expose a reviewed published Chat Agent through the Poppy publication API. Publishing an ordinary Studio agent alone does not expose it publicly. The desktop list shows the exact version reviewed for guest access. Ask your administrator to update that exposure after reviewing a newer published version.

For example, ask the included Ari Test Company for its support hours. This sandbox has no customer accounts, business tools or real transactions.

For an external Company offering account sign-in, choose Connect account in phone view, or expand Connect your company account in desktop view. Select its permissions and continue to the Company's own sign-in. You return to Connections in the same desktop or phone view. Use Disconnect account to revoke that connection. Ari never asks you to paste the Company's password or access token into chat.

Read and join a conversation

Conversations lists your saved chats with Ari. Search by title or company, open a chat to continue, or use New conversation. Back returns to the list. The selected screen and conversation are retained when you reload or change between desktop and phone view.

Company conversations shows original user and Company messages. Assistant-authored messages and You, directly messages are labelled separately. A working conversation refreshes while you keep it open. In phone view, open Conversations → Company messages for the same messages.

Choose Speak directly to open a direct child conversation. Your next message is sent in your own words. The assistant can read that conversation but cannot write in it. The parent becomes read-only until you close the direct conversation.

Request a human asks the Company for a representative. Availability depends on that endpoint. The initial TrueServe gateway explains that no representative is available and keeps the Company agent as the responder.

Choose Close to end a conversation. Closing a conversation does not cancel a separate business operation.

If delivery is interrupted, Messages awaiting acceptance shows the original message; phone view calls this Messages to check. Retry delivery uses the same message ID. If earlier Company history is no longer available, Ari shows a history-gap notice.

Approve an operation

For Companies supporting Operations v1, Approvals displays the Company's summary, structured terms, revision, expiry and eventual result.

Read the terms before choosing Approve revision … or Decline. The assistant cannot press the approval button, and consent written in chat does not confirm an operation.

If terms change, Ari requests review of the new revision. If a Company changes terms without issuing a revision, approval stays blocked. If a confirmation response is lost, the card shows that its outcome needs checking. Use Check status to learn what happened before taking another action. An accepted operation can remain in progress; acceptance is not a completed result. An in-progress operation offers Request cancellation. The Company decides whether it can stop the action and reports its outcome.

To validate an operation you created elsewhere, switch to desktop view and expand Inspect a test operation, select its Company and enter the operation ID. Use a sandbox Company when testing; approval on a live endpoint can have real effects.

The initial TrueServe guest gateway does not yet expose Operations. These controls are for connected Companies that advertise that extension.

Run and compare checks

The protocol lab and technical activity inspector are available in desktop view. From the phone app, choose Settings → Desktop view first.

  1. Open Protocol lab and choose Company under test.
  2. Choose Run protocol checks.
  3. Inspect individual results. The lab creates and closes its own conversations.
  4. Choose Export to save the run, profile and discovery snapshot as JSON.
  5. After updating an agent, choose Rediscover in Connections and run again.
  6. Choose an earlier run in Compare with to compare the results.

The automatic suite checks sessions, proof/key binding, event replay, message retry behavior, direct-conversation locking and close behavior.

Not exercised means that scenario was not validated. Account consent, Operations approvals, staffed handoff and OpenAPI/MCP execution are not included in the automatic run. “Automated checks passed” applies only to the checks listed as passed; it is not full Poppy certification.

Use Assistant profiles in the lab to create a Core-only or Operations-enabled identity, then select it when adding a connection. This lets you test extension negotiation without changing an existing client's published identity.

Activity shows HTTP status, timings and redacted request/response payloads. It still includes your test messages. Use synthetic data for shared test reports.

Set appearance and phone view

Open Appearance to set the assistant name, welcome line, HTTPS portrait URL, accent color and default display. Choose Save appearance. Reset to Ari restores the form's Ari defaults; save to apply them.

Choose Phone view from any screen to open the full Ari app inside the shared phone emulator. It has its own Conversations, Connections, Approvals and Settings tabs. All navigation stays inside the phone.

Choose Settings → Desktop view inside the app to return to the full workspace. On a small browser screen, phone view fills the available screen without an extra handset frame. You can change the assistant name, welcome message and accent color in phone Settings.

Appearance and display preferences are saved for your workspace; they are not a tenant-wide branding policy.

Current limits

The app uses OpenMuse's agent engine with an Ari interface. It does not include all upstream OpenMuse features. Device Sign-In, Company SSE, browser continuity, automatic OpenAPI/MCP tool execution and standing permissions are future work. Voice calling is not part of this app.

If the model cannot start, check that your Studio tenant has an active OpenAI integration with LLM capability. Protocol checks and direct Company messages remain available without a model call.

See also