#21 — Messaging: 2-way email sync + shared team inbox
Gmail/Outlook 2-way email sync + a shared team inbox — the recurring competitor strength (Karbon's signature capability) Firmary has none of. Includes the inbound email bridge + saved replies milestone from the 2026-07-05 market audit, bulk email blasts (4/6 competitors), and email-to-task conversion. New email capability behind an adapter. Size: L. Source: product-roadmap.md §4 (scope widened by the 2026-07-09 comparison fold-in).
3 Comments
Sign in to comment
·about 2 months agoAgent B — saved-replies slice complete & verified (PR #30, commit 77a8126). Firm-shared canned replies: manage at /staff/messages/saved-replies (write roles CRUD, readers read-only, duplicate titles rejected), inserted via the composer's new "Insert saved reply" picker (appends for editing, never auto-sends; portal composer never sees the list). Migration 0070; messaging.write/read authz; audited; 4 new integration tests (CRUD/order, conflicts, authz reach incl. contacts, tenant isolation); live Playwright drive of the whole flow. Epic status: the sync/OAuth core of this card remains GATED on §10.8 — see the new DECIDE card on Needs-Daniel (also asks firm-level vs per-staff mailbox). Releasing my claim on this card; it stays In Progress with the saved-replies slice shipped and the terrain map for the sync build captured in tonight's session transcript.
·about 2 months agoAgent B claiming a bounded slice of this epic until completion or block. Scope: SAVED REPLIES only — the decision-independent named milestone (market audit #3): per-firm canned replies (schema + migration), manage surface, insert-into-composer in the staff messaging composer, validators, authz (staff-only manage, any staff use), tests, contract update. NOT touching the sync/OAuth layer: §10.8 is explicitly undecided and the roadmap gates the build on it — DECIDE card posted on Needs-Daniel just now (also asks firm-level vs per-staff mailbox). Started: 2026-07-09 07:05 America/Chicago.
Migrated to https://github.com/Firmary/firmary-os/issues/356 during the 2026-08-23 GitHub migration (status corrections and full history carried over). Quackback is now the public user-feedback portal; internal tracking for this item continues on GitHub.