Zum Hauptinhalt springen

Posteingang

Wo die Unterhaltungen mit Nutzern leben: Threads in einem Tab, Kampagnen im anderen. Jeder Thread sagt, wer sprach, ein Endnutzer, ein Agent oder das Modell, und die drei sind nicht zu verwechseln.

The inbox in the Live environment
The inbox, Live environment.
The inbox in the Live environment, dark theme
The inbox, Live environment.

Conversations

A conversation opened to its turns
A conversation open: every turn attributed.
A conversation opened to its turns, dark theme
A conversation open: every turn attributed.

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.

Working the inbox

Saved views keep a filter over status, priority, assignee and the company's own attributes, each with a count of what it selects now. Macros are saved replies with actions: picking one fills the reply and stages its actions, which run when the reply is sent, or alone with Apply without replying. Undo send holds a reply for the delay a member picks (off, 5, 10, 20 or 30 seconds) so it can be taken back, and Away stops new conversations reaching a member, with the choice to hand back the open ones. A reply a member has started is kept as they type and waits in the same thread on any tab or device until it is sent. The Live tab shows each member's load as it changes.

Details, in the thread's header line, opens a side panel with the conversation's priority, its assignee and the company's own attributes, saved together. A high or urgent conversation says so in words beside the name in the list. Merge moves this conversation's messages, files and ticket links into another conversation with the same person and resolves this one, which stays readable. When the person shares an email with someone else in the project, a Possible duplicate chip names who and offers the People merge, or Not the same person so the pair is never offered again. How new conversations reach the team (manual, round robin or balanced) and each member's assignment limit live on the Assignment tab of Messenger settings.

AI writes a summary of a thread when asked, and translates on demand: Translate under a visitor's message shows the translation inside the same bubble, captioned with the language it came from, and once the visitor's language is known, Translate to that language beside Send turns the reply into it before it goes. A reply sent translated keeps what the member wrote, which the thread shows under it; the visitor sees only the translation.

Wo eine Nachricht geschrieben wurde

Ein Beitrag von der Person trägt die Seite mit, auf der er geschrieben wurde. Unter dem Text gibt eine gedämpfte Zeile im Stil der Uhrzeit des Beitrags den Host und den Pfadnamen an, der Seitentitel steht in ihrem Tooltip, und die Zeile öffnet diese Seite in einem neuen Tab. Nur ein eingehender Beitrag hat eine: Agent und Modell antworten beide aus der Konsole, eine Seite an einem von beiden würde also die Konsole benennen statt den Besucher. Eine Nachricht, die gesendet wurde, bevor der Messenger eine Seite mitführte, oder von einer Oberfläche, die keine sendet, hat schlicht keine Zeile. Bewahrt wird nur der Pfadname, nie die Abfrage und nie das Fragment, sodass ein Token in einem Zurücksetzen- oder Kassenlink nie den Posteingang erreicht.

Sent

The sent tab
The sent tab: every message sent, with its status.
The sent tab, dark theme
The sent tab: every message sent, with its status.

A message sent from here goes to many people at once: in-app, email or webhook, targeted at everyone, a cohort or named people. Each one 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; sent messages 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.