Swifty Knowledge Base

How to switch chatbot providers without breaking anything

Updated Nov 21, 2026

A checklist for moving from one leasing chat provider to another without ending up with two chat bubbles or losing phone call tracking.

Moving from one chat or leasing-assistant provider to another (for example Knock to EliseAI) usually goes wrong in one of three ways: the old script is never removed, the wrong property's script gets pasted, or the old provider's call-tracking number quietly stops working. This checklist avoids all three.

  1. Confirm with your new vendor exactly which script or integration card applies, and for which property if you manage more than one.
  2. Remove or disable the old provider first: if it was added as an integration, deactivate it under Settings > Integrations; if it was added as a tracking code, disable or delete that code under Settings > Tracking Codes.
  3. Add the new provider following the steps in the chat widget article.
  4. Decide whether to keep the old provider's call-tracking (DNI) number active during the transition, and tell support if you want to keep it.
  5. If Emily, the built-in Swifty assistant, is on, turn it off so visitors do not see two chat bubbles.
  6. Click SAVE/UPDATE, clear cache, and check the live site in a private window.
Heads up: if you remove the old provider's script without arranging for its call-tracking number to be replaced, phone calls attributed to that source can stop being tracked. Confirm with your ad or marketing team before removing it.
Tip: switching several properties at once? Send one spreadsheet listing property name, site URL, old vendor, new script, and whether to keep the old call-tracking number, so the whole batch can be handled together.

Still stuck?

If the new chat bubble does not appear after saving, clear cache and check in a private window before contacting support.

Related:

Was this article helpful?