Skip to main content
Murph is the assistant built into the Scope3 platform for storefront operators. It works alongside you in chat to set up your storefront, connect inventory sources, compose products, and surface the analytics you need to negotiate and sell. Murph is available to every storefront account — open the Ask Murph panel from your storefront workspace to start a conversation.
Murph is the operator-facing assistant. Buyers interact with your storefront through the Buyer API and the Merchandising Agent, not with Murph directly.

​
What Murph helps with

AreaWhat Murph does
Storefront setupWalks you through onboarding, captures your business profile, and gets your storefront ready to sell.
Connecting inventorySends you to the secure forms for ad servers like Google Ad Manager, FreeWheel, and SpringServe, then verifies the connection.
Setup documentsReads uploaded brand books, media kits, rate cards, and operating instructions so you don’t have to paste them into chat.
MerchandisingHelps compose products and tune negotiation defaults using your recent storefront outcomes.
Seller analyticsSurfaces win rate, buyer asks, top products, and recommended negotiation posture so you can see what’s working.
Sandbox testingRuns and reports on sandbox test plans so you can validate behavior before going live.
DiagnosticsOpens source health, ADCP debug calls, test runs, and change history so product questions can be answered from live evidence.

​
Connecting your ad server

Murph guides you through connecting an upstream inventory source rather than asking you to hand over secrets in chat. For password- or token-based ad servers, Murph links you straight to the secure credential form, waits for you to submit, then runs a connection test to confirm the source can authenticate. For Google Ad Manager, no password is needed at all: Scope3 creates a per-customer service account, and you grant that service-account email access inside your GAM network. Before walking you through the grant, Murph explains what access Scope3 needs, what it will not do, and what the granted role allows — and asks for your explicit consent first.
Scope3 stores only non-secret display fields for a connection. The upstream ad server holds the encrypted secret and mints short-lived tokens as needed. See Storefront onboarding for the full connection flow.

​
Uploading setup documents

You can upload PDFs, decks, spreadsheets, images, and text documents during a conversation. Murph summarizes them into structured facts instead of copying the raw contents back, so it can reference your brand book, rate card, or do-not-air list in later turns without re-reading the whole file. For brand books, Murph can identify brand-manifest candidates — name, website, colors, fonts, tone, tagline, and disclaimers — and help you draft or compare the fields that map into a brand.json. When you upload or link to canonical brand artifacts, Murph compares what it learns against the current AAO brand.json state and calls out new information, changed values, conflicts, and assets that still need public URLs. For logo images, Murph can upload the asset to AAO for review; pending uploads are tracked but are not used in brand.json until AAO approves and lists the public /assets/brands/... URL. Murph can preview the exact brand.json update and, after you confirm it, publish it to AAO for your verified storefront operator domain.

​
Seller analytics and merchandising

Ask Murph for seller analytics and it can show your recent performance — win rate, buyer asks, top surfaced products, and the commercial outcomes attributed to your discovery runs. Murph turns that history into directional negotiation guidance and a recommended posture, and the same recent outcomes can tune the Merchandising Agent’s negotiation defaults when composing products. Your human operating instructions always remain authoritative over these historical defaults — Murph’s analytics inform the suggestion, they don’t override your rules.

​
Escalations

When Murph files an escalation, chat responses include an escalation artifact with the filed status and, when available, the linked Linear issue. Clients should check linearVisibility before rendering Linear references. 
{
  "escalated": true,
  "escalation": {
    "linearIdentifier": "MURPH-123",
    "linearUrl": "https://linear.app/scope3/issue/MURPH-123/example",
    "linearVisibility": "visible",
    "slackPosted": true,
    "severity": "medium"
  }
}
linearVisibility can be:
ValueMeaning
visiblelinearIdentifier and linearUrl may be shown to the caller.
hidden_for_roleLinear exists, but the current caller is not allowed to see the Linear reference. Treat linearIdentifier and linearUrl as hidden, not missing.
unavailableLinear was not configured, failed, or did not return a reference.

​
Working in the Dashboard

Beyond chat, Ask Murph includes a Dashboard view that swaps the chat column for a tabbed surface so you can review your state without leaving Murph. The conversation stays available in the sidebar the whole time. Sellers see their storefront tabs — Overview, Reporting, Activity, and Merchandising. Buyers see Overview, Reporting, Activity, Creatives (and Planning briefs when enabled), with an advertiser selector to scope each tab to a single advertiser. Buyers also get a Browse storefronts item in the sidebar that opens the full marketplace browse page inside the Murph shell.

​
Working in Diagnostics

Ask Murph also includes a Diagnostics view under the Help menu. Use it when you need the evidence behind a product or setup question, especially for third-party sales-agent inventory sources. The Debug calls tab shows recent ADCP protocol activity for connected sales agents. You can open it directly with: 
https://interchange.io/<customer-id>/murph?view=diagnostics&diagnosticsTab=debug-calls
To start a diagnostic conversation instead of just opening the panel, use: 
https://interchange.io/<customer-id>/murph?askMurph=third_party_sales_agent_diagnostics
For the full workflow, see Diagnose third-party sales agents.

Storefront onboarding

The end-to-end flow for standing up a storefront and connecting inventory.

Storefront object guide

The storefront resource, business profile, and seller analytics fields.

Sandbox

Test plans and diagnostics for validating your storefront before launch.

Third-party agent diagnostics

Find source health, recent ADCP debug calls, and missing diagnostic gaps.

Murph user preferences

Set Murph’s default language and read display preferences for the current user.

Conversation scope

Bind a Murph conversation to your account or a single advertiser.

Management UI

Navigate the platform dashboard for members, keys, and accounts.