Customer 360: an account page built from your own content

One page per account — status, risks, and a drill-in chat — assembled from whatever your instance already knows about that customer. No CRM export, no separate index.

~1 hrIntermediate

Problem

Account executives jump between CRM notes, renewal docs, and security packets to prep a single customer conversation. This puts those sources in one account workspace with evidence coverage, compact source sections, and an above-the-fold assistant thread — so the next call needs one tab, not nine.

Everything displayed comes from what your instance already knows about that account. The overview uses only the supplied account name and deterministic Search result counts; assistant claims remain cited rather than turning loose search matches into unsupported CRM facts.

This recipe builds the page two ways: Platform Search plus Client Chat for an open-ended dashboard, or Agents createRun for a prescriptive QBR-ready brief.

Architecture

Account pageEvidence overview + sources + assistant thread

Path A: Search + Chatglean.search.query + Client Chat

Path B: Agentsglean.agents.createRun

Glean Platform APIpermission-aware retrieval + synthesis

Prerequisites

A work email for tenant discovery and OAuth sign-in; a scoped Glean API token is the fallback

X_GLEAN_INCLUDE_EXPERIMENTAL=true for Platform Search and Agents

Path B: an Account Brief agent in Agent Builder; set GLEAN_AGENT_ID server-side

Node 20+

An account name your own content covers — the page is built around whichever you pick (GLEAN_ACCOUNT_NAME)

Steps

Pick a path

Path A combines parallel Platform Search tiles with Client Chat synthesis. Path B keeps the same page UX but uses a template Account Brief agent.

Platform Search Chat
Platform Agents

Scaffold the project

npx -y tiged@2.12.8 --mode=git gleanwork/glean-cookbook/recipes/customer-360/platform-search-chat customer-360

Install dependencies

cd customer-360 && npm install

Set credentials

The shipped command discovers the tenant and completes OAuth, with a scoped API token fallback. Set GLEAN_ACCOUNT_NAME in the resulting ignored .env to the account the user supplied. Do not search for a different account.

cd customer-360 && npm run login -- --email "<work-email>"

Verify

Allow 1–3 minutes. It starts its own server, runs the demo queries against the supplied account, and asserts cited answers plus deterministic evidence coverage.

cd customer-360 && npm run verify

Run it

cd customer-360 && npm start

Scaffold the project

npx -y tiged@2.12.8 --mode=git gleanwork/glean-cookbook/recipes/customer-360/platform-agents customer-360

Install dependencies

cd customer-360 && npm install

Set credentials

The shipped command discovers the tenant and completes OAuth, with a scoped API token fallback. Set GLEAN_ACCOUNT_NAME and GLEAN_AGENT_ID in the resulting ignored .env from the answers already supplied.

cd customer-360 && npm run login -- --email "<work-email>"

Verify

Allow 1–3 minutes. It starts its own server and verifies the supplied account and Account Brief agent before the app is left running.

cd customer-360 && npm run verify

Run it

cd customer-360 && npm start

Take it further

Add a portfolio dashboard across a rep's whole book of business, with health and renewal countdown tiles per account.
Schedule a weekly headless job that re-runs the account's queries, diffs against the last run, and posts only what changed to Slack.
Wire push-to-CRM / push-to-Slack actions from the journey panel once you have a governed custom tool.

Try it

What's the status of our renewal with that account?

Returns a non-empty answer citing real documents about the account you built the page around. Substitute the name when you ask — there is no fixed query text for a page built around whichever account you pick.

Give me a customer summary

Synthesizes across more than one source with a citation per claim, rather than restating a single document.

What are the renewal risks?

Either names risks grounded in cited content, or says it has none to report. It must not infer risk the sources don't support, and the account overview must show only the supplied account name and deterministic Search result counts.

Choose your tool
Install the plugin
1
```
claude plugin marketplace add gleanwork/glean-cookbook
```
2
```
claude plugin install cookbook@glean-cookbook
```
Run the recipe
```
/cookbook:customer-360
```
Run /reload-plugins to pick it up without restarting.

View source

Runs the recipe through the Glean cookbook plugin.

At a glance

SurfacesPlatform API, Client API

StatusShowcase

Time~1 hr

Required scopes

SEARCHCHATAGENTS