Editing and regenerating

Change a question, swap an avatar, update a CTA — without breaking your embedded widget.

Your widget is live but something needs to change. Pricing went up, a new product launched, you want to swap the welcome script. Wiqly handles edits without you ever touching the embed code on your site.

How edits work

Go to the widget detail page and click Edit. You can change:

  • The widget name (internal only — visitors don't see it)
  • The spokesperson
  • The backdrop
  • The welcome script and welcome CTA
  • Any FAQ's button label, script, or CTA
  • The order of questions (drag the handle on the left of each card)
  • Add new questions (up to your plan cap)
  • Delete questions

Click Save when you're done.

What re-generates

Wiqly only regenerates the videos that actually changed. If you edited the welcome script and added one new question, only those two videos get rebuilt. The rest stay live and untouched.

Your widget stays online the whole time. Visitors hitting your site during regeneration see the old version of the changed question (marked "Soon" if regeneration is still in progress) and the live version of everything else.

The embed code never changes

The embed <script> tag on your site is tied to a permanent token, not to any specific video. Edit anything in the dashboard and the live widget picks up the new version automatically. You don't need to re-copy or re-paste.

How long does it take?

About a minute per video. You'll get a toast notification in the dashboard when regeneration is queued, and an email when it's all finished.

Deleting questions with leads

If you delete a question that has captured leads, the leads stay in your dashboard — they're not lost. But the question goes away on the live widget immediately. The trash-icon delete warns you about lead counts so you know what you're doing.

What you can't edit

  • The widget's embed token (it's permanent — that's a feature, not a bug)
  • A video that's mid-generation (wait for it to finish, then edit)
  • Leads that have already been captured (they're append-only)

Tips

  • Test edits with Preview before saving. The widget detail page has a Preview button that loads the latest unsaved state.
  • Batch your edits. Each save triggers regeneration. Five edits in one save is cheaper (timewise) than five separate saves.
  • Use JSON import for big restructures. Faster than re-typing if you're rebuilding the whole question set. See Bulk import.