Conversation History
The quality of every draft depends on the history behind it. A reply written against three months of context is a different product from one written against the last two lines.
The platform keeps that history complete for you.
How history stays current
Section titled “How history stays current”Three things happen automatically, with no action from your team:
Live sync. While a conversation is open, every new message is captured as it arrives — the fan’s messages and anything your chatter types directly on the platform. Your CRM is never behind the conversation on screen.
Automatic catch-up. When a chatter opens a conversation, anything that arrived while it was closed is brought in immediately. Only the new material is fetched, so returning to a familiar conversation is close to instant.
Write-back. Every reply sent through the panel is written into the history straight away, so the next draft is built on a complete record.
The result: from the moment you install, your history stays current by itself.
The panel says so plainly, and tells you when it last looked:
Importing your existing history
Section titled “Importing your existing history”Everything that happened before you installed needs one import. This is the one history task that requires a decision from you.
To run an import
- Open your creator’s inbox on the platform and leave the tab open.
- In the side panel, open Settings (the gear icon) → Chat history.
- Choose a depth — how many messages per conversation to bring in.
- Choose your mode:
- Collect everything — reads each conversation from its beginning. Use this for your first import.
- Only what’s new — picks up from where the last run finished. Much faster; use it for periodic top-ups.
- Press start.
You can close the panel while it runs — the work continues and the panel picks it back up when you reopen it. Stop ends the run cleanly at any point.
Agency tip. Run your first full import overnight, per creator, before your team’s first shift on the platform. Chatters arriving to complete history get a materially better first impression of draft quality than chatters arriving to empty profiles.
Importing a single conversation
Section titled “Importing a single conversation”Any individual conversation can be imported on demand from the Draft tab, without running a full sweep. Use this when you open a high-value relationship and want its entire history in place before you reply.
Reading the results
Section titled “Reading the results”An import reports four numbers:
| Result | Meaning |
|---|---|
| New | Messages added to your CRM |
| Already on record | Messages that matched what was already stored. A high number here on a repeat run is exactly what you want to see |
| Skipped | Conversations passed over untouched because nothing had changed since the last run. Only Only what’s new skips — a full run opens every conversation |
| Problems | Conversations that need another look, with the reason |
Running an import twice never duplicates anything. The platform reconciles what it reads against what it already holds and adds only the difference, so you can re-run a sweep whenever you like.
Deleted messages
Section titled “Deleted messages”If a message that was on record is removed from the platform — by the fan, or by a member of your team — it is marked as removed rather than erased. It stops being used in drafts, but the record of the relationship stays intact.
If it reappears, it is restored automatically.
Best practice for interface language
Section titled “Best practice for interface language”Set the platform interface for your creator accounts to English. Date headings are read directly from the platform’s own interface, and English gives the most complete date detail on imported history.
This affects historical imports only. Live conversation capture is unaffected by interface language.
How often to run an import
Section titled “How often to run an import”| Situation | Recommendation |
|---|---|
| First install | Collect everything, once, per creator |
| Normal operation | Nothing. Automatic catch-up covers it |
| After a period with the extension uninstalled | Collect everything on affected creators |
| Onboarding a creator account you just took over | Collect everything, maximum depth |
| Monthly hygiene | Collect everything on your top creators |
Privacy
Section titled “Privacy”Conversation history is stored inside your account and is visible only to team members whose role grants them access to that creator. A chatter assigned to two creators can never see the history of a third.
Conversation history has no automatic expiry — it is kept until you delete it, because it is what the assistant works from.
Draft text is cleared after 180 days. This is separate from the conversation history above, and it happens on its own. Six months after a draft was generated, its wording — the fan message it answered, the draft, and the translation if there was one — is erased. What survives is the measurement: which model wrote it, how long it took and how you rated it, so nothing in Analytics changes.
In practice this only matters if you go looking for the exact wording of something written more than half a year ago. If you need it kept, export the fan record before then (Export on the fan’s page).