Bandeja de entrada
Donde viven las conversaciones con los usuarios: los hilos en una pestaña, las campañas en la otra. Cada hilo dice quién habló, un usuario final, un agente o el modelo, y los tres no se confunden.
Conversations
A thread is a person's messages from the Messenger, answered from here. Every turn carries who wrote it: the end user, a named agent, or the model, and the attribution is a database rule rather than a convention, so an assistant turn can never wear a person's name. Threads are open, snoozed or resolved; replying reopens what needs reopening, snooze parks a thread until a date, assignment names whose it is, and new turns stream in live while the thread is on screen.
Dónde se escribió un mensaje
Un mensaje de la persona lleva la página en la que lo escribió. Bajo el cuerpo, una línea tenue, con el mismo estilo que la hora del mensaje, da el host y la ruta, con el título de la página en su descripción emergente, y la línea abre esa página en una pestaña nueva. Solo un mensaje entrante la tiene: el agente y el modelo responden ambos desde la consola, así que una página en cualquiera de los dos nombraría la consola y no al visitante. Un mensaje enviado antes de que el mensajero llevara una página, o desde una superficie que no envía ninguna, sencillamente no tiene línea. Solo se guarda la ruta, nunca la consulta ni el fragmento, de modo que un token en un enlace de restablecimiento o de pago nunca llega a la bandeja.
Campaigns
A campaign is one message to many people: in-app, email or webhook, targeted at everyone, a cohort or named people. A sent campaign reports its deliveries by outcome, delivered, read, failed and pending, so a send that half-landed reads as exactly that rather than as done.
Proposals
The model's suggestions review where they point rather than on a tab of their own: a reply drafted for a thread waits in that conversation, a suggestion raised by an anomaly sits under that anomaly on Home, and one about a cohort sits on the cohort itself. Each proposal states its action in a sentence with its fields editable in place, plus its rationale; a person approves, adjusts or rejects it, and the decision is recorded with who made it. Nothing a proposal suggests happens without that approval.
Where this meets the API
The concept is the Messaging pillar. On the wire: threads are conversations and conversationThread, answered through replyToConversation, setConversationStatus and assignConversation, with live turns on the conversationTurns subscription; campaigns are messages and composeMessage; proposals are aiProposals with approveProposal, editProposal and rejectProposal (GraphQL reference). The user side of every thread is the Messenger, configured on its settings screen.