Sales agent guideline and product knowledge changes reported as saved but not persisted

Configuring a sales agent in Frontier, several settings were confirmed by the agent as saved and active, but were absent on subsequent readback.

Observed over a single configuration session:

• Product knowledge was confirmed as added in detail on two occasions. A later full readback showed no stored product knowledge sources at all.
• The email signature was reported as updated four times. Each attempt returned a different malformed value: a stray literal "Text" prefix outside the paragraph tag, raw line breaks instead of <br>, and on one attempt a dropped ampersand.
• The Redirect stage was reported as existing, then as not existing, then appeared again in the playbook stage list with no guidelines attached.

Expected: settings confirmed as saved persist, and readback reflects stored state accurately.

Actual: the agent's own report of its configuration state could not be relied upon, so every change required manual verification. Where product knowledge was silently absent, generated output fell back to generic content.

Impact: there is no trustworthy way to confirm which configuration is in force at send time. For any customer-facing agent this is a blocker to go-live, since output cannot be assured against approved messaging.

Suggestion: expose a single authoritative configuration readback showing stored values verbatim, and surface provisioning state clearly where content is still being ingested. Or, enable manual editing of agent setup config rather than requiring agent to update it.