Files
zeekay e981114824 chat: a signed-out reader asks the buying agent, and it routes them to pay
/chat signed out is the buying agent (components/sales/Guest, Agent): the
question the home composer carried in ?q= is asked of cloud's
POST /v1/ai/sales, the reply is drawn as text, and each next step the
server built is a control: a call (the lead is filed first, then the
calendar opens on it), the sign-up, a plan's card checkout, Add funds. A
quiet line says it is a limited preview and how many messages are left; at
the ceiling the sign-up takes the composer's place. A conversation's own
address still signs in, and a signed-in reader keeps the app.

/buying-specialist is the same agent; its keyword script, its typed prices
and its claims to see an account are gone. The model pages' no-key card is
the real lane, POST /v1/chat/public, not a guest key that answers 401.

Measured in the site's names: chat_started, cta_clicked {cta: kind, plan,
agent: sales}, sales_contacted. The floating privacy button is hidden as
room.css meant: the rule names its tag to outrank gui's atomic class.
2026-10-27 01:29:38 -07:00

16 lines
534 B
TypeScript

'use client'
/**
* /buying-specialist — the buying agent, for everyone: the pricing page's "Talk
* to our AI Buying Specialist" and /contact-sales send a reader here. The agent
* is cloud's (POST /v1/ai/sales); components/sales/Guest draws it. `?q=` is a
* first question, asked on arrival.
*/
import { Guest } from '@/components/sales/Guest'
import { useQuery } from '@/lib/auth/query'
export default function BuyingSpecialistPage() {
return <Guest seed={useQuery().get('q') ?? undefined} source="buying-specialist" />
}