No second messenger — communication on the change request
Questions and clarifications where scope and confirmation already live. Why MEMNO does not build a Slack replacement — and still needs communication.
“Can we do two logo variants instead of three?” — questions like that land in WhatsApp or email today. Later you hunt for the thread where the client agreed. MEMNO solves this on the change request, not in a general chat.
Scope
Thread per change request. Owner ↔ client. Email digest on new messages. System events (“client confirmed”, “payment received”) in the thread. No Slack, no WhatsApp import.
What is in — and what is not
- Yes: messages on the specific change request, both sides reply, read via magic link
- Yes: email “New message in MEMNO” with link back
- No: general project chat, group chats, @mentions, video/voice
- No: WhatsApp integration — deliberately excluded
Why this makes sense
Questions before confirmation reduce “that is not what I understood”. In disputes, thread + PDF + confirmation live in one place. For Easy Pay: clarify first → confirm → pay in the same flow.
Fits the MEMNO story
“Check MEMNO, project X, change request from June 12.” — not “search WhatsApp for last week’s message”.
Technical concept
Table `requestMessages` with `authorRole: owner | client | system`. Realtime via Convex subscription on `changeRequestId`. Rate limit: max one email per thread per hour — no spam.
Prerequisite: phases A–C of the two-sided platform so both sides can optionally be on the platform. Phase D (email notifications) can go live without D+.