Keep old help center links and sign-ins after switching

After moving from Intercom, Crisp, Chatwoot or others, keep old article links working and signed-in users verified with the old identity secret.

Updated
On this page

After you switch, two things need a little care: your old help center links, and your site's calls to the old chat.

Swap the chat snippet

Remove the old tool's snippet and add Opskeet's from Settings → Install. Nothing else is needed: your site's existing calls drive Opskeet instead, unless the old chat is still on the page. These work: Intercom('boot'), Intercom('show'), $crisp.push(...), Tawk_API, $chatwoot.setUser, Beacon('identify'), FrontChat('init') and Gleap.identify.

Keep signed-in users verified

If your server signs users for the old chat (Intercom user_hash, Crisp, Chatwoot and so on), paste the old secret so those users stay verified and see their imported history.

  1. Go to Settings → Import & export and find Switch the chat.
  2. Choose the old tool and paste its identity secret.
  3. Click Save.

Later, move to Opskeet's own signing. Then click Remove on the old secret. You confirm "Remove tool's secret?": people your site still signs the old way stop being verified, and can't sign in if identity is required. Do it once your site signs the Opskeet way.

Imported articles remember their old addresses. To make old links work:

  1. Put your help center on your own domain, the same one your old help center used.
  2. Click Publish N articles on the import.

Old article links then lead to the same articles. Addresses on the old tool's own domain, like intercom.help/acme, can't be redirected.

Did this help?

Related articles