Full transcript reply instead of message-by-message replay
Import the thread as one created record plus one full transcript reply when the buyer mainly needs readable history, not a perfect recreation of every old event.
Why this can grow a startup
Teams often overpay in complexity because they assume historical fidelity means rebuilding every message as a separate action. In many migrations, the useful job is simpler: preserve context, make the thread readable, and let agents understand what happened before the switch. A full transcript reply keeps that context visible while avoiding the scripting sprawl and notification hazards of replaying the entire past.
Company example
Intercom's migration guide recommends posting the full Zendesk transcript as a reply on the imported conversation or ticket rather than recreating each message one by one.
Source and metric
Source: Intercom Help · Browse Intercom Help tactics
Use one reply to carry the full historical transcript
Source discovered: May 26, 2026
When to use it
Use this when Support, Docs, Operations is relevant to migration, support ops, reporting continuity and you can run a bounded test with a low budget.
When not to use it
Do not use it as a substitute for customer evidence, a clear owner, or a measurable stop condition. Local platform rules and market behavior still need checking.
Founder checklist
- Read Intercom Help and identify what is directly supported.
- Choose one channel context: Support, Docs, Operations.
- Define the test around Use one reply to carry the full historical transcript.
- Set an owner, evidence window, and stop condition before launch.
Explore the context
Apply this with an operator
Choose product surfaces that compound distribution without hiding weak activation or retention.