Kotak masuk

Tempat percakapan dengan pengguna berada: thread di satu tab, kampanye di tab lainnya. Setiap thread menyebut siapa yang berbicara, pengguna akhir, agen, atau model, dan ketiganya tidak dapat tertukar.

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.

Di mana sebuah pesan ditulis

Giliran dari orang itu membawa halaman tempat ia menulisnya. Di bawah badan pesan, satu baris redup bergaya sama dengan waktu giliran memberikan host dan pathname, dengan judul halaman pada tooltipnya, dan baris itu membuka halaman tersebut di tab baru. Hanya giliran masuk yang memilikinya: agen dan model sama-sama menjawab dari konsol, jadi halaman pada salah satunya akan menyebut konsol, bukan pengunjung. Pesan yang dikirim sebelum messenger membawa halaman, atau dari permukaan yang tidak mengirim apa pun, memang tidak punya baris itu. Hanya pathname yang disimpan, tidak pernah kueri atau fragmen, sehingga token dalam tautan reset atau checkout tidak pernah sampai ke kotak masuk.

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.