Twill Brain

#773 Merchant Chat & Activity Log

2 min read

#773 — Merchant Chat & Activity Log

Repo: Twill-AI/twill-ai-ui State: closed | Status: done Assignee: meliascosta

Created: 2025-10-27 · Updated: 2026-03-04

Description

Merchant Chat / Activity Log will be a functional, real-time communication and tasking system. It is intended to become:

  • The primary communication surface between Merchant ↔ Partner ↔ Master

  • A live activity feed (messages, status changes, document events)

  • A lightweight internal tasking system tightly coupled to merchant conversations

  • Partner, Rep, and Master operate in a fully transparent internal system

  • Merchant visibility is explicit and intentional — nothing is shown implicitly

  • All activity visibility filtering must be enforced at the Facade layer (not the UI).

Acceptance Criteria:

  • Master ↔ Partner ↔ Rep messages default to Internal Only
  • Internal users must explicitly choose to send a message to the Merchant
  • Internal messages cannot be retroactively shared with the Merchant
  • AI-generated notes and suggestions are hidden from the Merchant in V1
  • Internal-only metadata (Fireflies, AI notes) is never included in Merchant payloads
  • Merchant-visible activities are deterministically filtered server-side
  • All the endpoints needed for this functionality accept the role MERCHANT

Merchant Incoming Messages (New type MERCHANT_MESSAGE_SENT)

  • Created whenever a Merchant sends a message
  • Visible immediately to the Merchant
  • Visible immediately to all internal users (Master / Partner / Rep)
  • Delivered via WebSocket (notification + in-chat update)
  • Outgoing replies to Merchant messages are human-only
  • AI may observe and sugge

Notes

Add implementation notes, blockers, and context here

Add wikilinks to related people, meetings, or other tickets

Graph View