Closure
Request access

Assistants

Meet Alex.Chat · Talk — goal configurable.

Closure Assistant — Chat and Talk on the Organization graph, configured with a goal such as sales or support. This site runs a sales goal (Alex). Same chrome; your Knowledge and Workflows set the job.

Request access

Two surfaces

Surfaces and goals.

Chat and Talk are projectors. The goal — sales, support, or yours — is configuration on the graph: Knowledge packs, Workflows, and tone.

Text

Chat

Streaming replies — Knowledge-grounded answers, chips for next steps, and MicroForms when structure is required. Goal (sales, support, …) sets the brain.

Face-to-face

Talk

Closure Talk — play the intro, then continue on the same configured brain. Live mic + lip sync is next; Chat stays available anytime.

Goals

Configure the job.

Convert

Sales

Qualify, capture leads, Request Access, and route to Sign in. This dogfood (Alex) runs a sales goal — Knowledge + MicroForms aimed at closing the next step.

Resolve

Support

Same Chat · Talk chrome — different goal. Point Knowledge packs and Workflows at tickets, status, and handoff. One assistant contract, configured for help.

Live demo

Sales goal · live here.

This dogfood runs a sales goal — same panel as the corner FAB. Chat · Talk, streaming tokens, sealed forms. Signed in? Alex already knows you.

Alex· Closure

Online · sales

Request Access →

Session loop

Goal → surface → identity → seal

Goal

Sales · support · or yours

Surface

Chat or Talk — same chrome

Identity

Session · Sign in · or seal email

Seal

MicroForm → act on the graph

What ships today

One contract. Goal on the graph.

  • Configurable goals

    Set the assistant’s job — sales, support, or your own — via Knowledge packs and Workflows on the graph. Same surfaces; different intent.

  • Identity first

    Signed-in members are recognized from their Closure session — no “are you a member?” loop. Guests get Sign in or Request Access so email seals out of chat.

  • Live streaming

    SSE token stream, headshots, relative timestamps. Same panel in the sitewide FAB and on this page.

  • MicroForms on the graph

    When structure is required, chat pauses. One field at a time. Submit seals — same Workflow Graph as Forms (request access, qualify, contact, tickets).

  • Knowledge-grounded

    Answers from your org Knowledge — not a free-floating chatbot. Swap packs when you change the goal from sales to support.

  • Attributed when you’re in

    Signed-in turns can land as org events on your graph so the conversation isn’t anonymous noise.

In Games, the same assistant brain can ride a Character — embodied, goal-driven, still sealing through MicroForms. One graph. Platform overview →

Configure the goal. Ship Chat · Talk.

Sales on this site; support (or your own goal) with different Knowledge and Workflows. Open the assistant above, or the FAB on any page.

Request access