A copy of an inbound message written into the agency's own client-message table so it appears in the Conversation tab of the opportunity card it is a reply to. The canonical row stays exactly where every other inbound consumer expects it.
Also called: reply didn't route back to the opportunity · agency conversation tab
- 1Applies only to the reserved platform account and only when the sender matched a contact
- 2The message is MIRRORED, not rerouted
- 3A mirroring failure is swallowed with a warning: the reply is already stored, so failing to mirror costs a card view, not the message
Replies to our own outbound email were being stored correctly and still not appearing on the opportunity card we actually work from, so a prospect's answer looked like silence and got followed up as though they had never written back. An inbound reply for our own pipeline is now mirrored into the place that card reads, without moving the canonical record. It applies only to our own board — a builder's replies belong in their own thread and never appear on it.
- Inbound replies stored correctly but invisible on the surface reading a different table
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →