Fix it once, at the source

Yes. Any reply drawn from that entry uses the new version from the moment you publish. The re-check confirms the question you flagged, and later visitors who ask related questions get the updated wording and its cite.

Past conversations keep what was said at the time. Only new questions use the published fix. If you need to undo the change, roll back to an earlier version in one step.

Yes. Roll back to any earlier version in one step. Your history keeps prior versions of each entry, including who changed them and when, so a bad edit does not lock you in.

After a rollback, new conversations use the restored version and its cite. You can still keep the later draft in your workspace if you want to rework it and publish again later. The assistant never fills the gap with made-up wording while you decide.

Yes. Flag, fix, preview, publish, and re-check come with every plan, including Free. The correction loop is part of how Kuuba protects your firm, not an upgrade.

Plans differ in allowances and features, not in the ability to correct a reply. See Pricing for a full comparison, and Corrections for how the loop works.

Anyone on your team who can read conversations can flag a reply. That way a wrong answer can be marked as soon as someone notices it, without waiting for a specific role.

Only the people you allow to approve and publish can publish the fix. Drafts still cannot reach visitors by mistake, and publishing remains an explicit step after the entry has been corrected and previewed. Until then, the assistant stays limited to what is already published, or hands the question to your team when nothing published covers it.

Flag it from the conversation with a note, fix the entry it came from, preview the new reply, and republish. Anyone on your team who can read conversations can raise the flag so problems do not wait for a single owner.

After you publish the fix, Kuuba asks the flagged question again and shows you the result, so you can check the correction before visitors see it. Until the fix is live, related questions can be handed to your team rather than repeating the wrong published answer. The old version stays in history if you need to compare or roll back.

Yes. Every version of every entry stays in your history, with who changed it and when. You can compare what was live before, and roll back to an earlier version in one step if you need to.

Past conversations keep what was said at the time. New questions use the version that is published when the visitor asks. The assistant never fills a gap with made-up wording while you decide.

Yes. Edit the entry yourself whenever fees, hours, or wording change, then preview and republish. You do not need a visitor flag to keep your knowledge current.

After you publish, new conversations use the updated entry and its cite. Earlier versions stay in your history, and you can roll back in one step if you need to.

No. Past conversations keep what was said at the time, including the entry version that was live then. That record stays available for your team to review.

New questions get the updated entry once you publish. The re-check after a flagged fix confirms the question you corrected before visitors see the new wording.

Yes. We can help prepare and review your first entries and add the snippet. A one-off setup fee may apply, and we agree it before you start. Contact sales to arrange a guided start.

Many firms set up on their own in an afternoon: create an account, publish a few entries, and paste the snippet. Help is there if you want a hand with knowledge packs, branding, or connections into Slack and your inbox.

Yes. Edit it, preview the reply, and republish, or archive it so it is no longer used. Changes take effect for new conversations once you publish. Visitors who start a chat after you republish see the updated entry and its cite.

Every earlier version stays in your history, so you can see what was live before, who changed it, and when. If you need to undo a change, you can roll back to an earlier version in one step. Until a replacement is published, related questions that no longer have a live entry are handed to your team.