Docs

Build customer rooms from brand-approved context.

BexBrand docs stay on bexbrand.ai while account access is managed in the consolidated app.

Data model

Brand, customer, room, asset

The workflow separates reusable brand sources from customer-specific delivery.

Brand system

Core

Tokens, tone, source notes and reference assets define the creative boundary.

Customer record

Core

A named account stores context, contacts and domain rules.

Customer room

Core

A private mini-site packages the assets and tracks access.

Review

Governed generation

AI drafts are useful only when they stay tied to source material and approval.

Budget gate

Required

Generation should respect account-level weekly and monthly limits.

Human approval

Required

Customer-facing rooms and assets need approval before publishing.

Event trail

Required

Views, access requests and asset opens become customer-room events.

Dashboard

Manage Bex access centrally.

Signed-in users see Bex beside the other AI robots their account can use.

Open dashboard