Review chat changes before you apply them

When chat wants to change your data, it drafts a proposed write first. The card that appears is a decision, not a notification, and nothing is written until you answer it.

This page has no screenshot. The card exists only in the moment after the assistant has proposed a particular change to your own records, and that state cannot be arranged for a capture without inventing a change that was never proposed. The labels below are quoted instead.

The two ways to answer it

The card carries two controls:

• Apply performs the write.
• Discard rejects it, and nothing is written.

It also carries a badge showing where the proposal stands: Proposed while it is still waiting on you, and Decided once you have answered it either way. A card you have already applied or discarded stays visible in the conversation with its badge changed, so the thread keeps a record of what you agreed to.

Before you decide, the card names what the change is and where it would land — the section of ATSReady it writes into, such as Professional Journey, a resume or a saved job, or that it writes nowhere and stays in the conversation.

What the safety model is

• The proposal is stored as a proposed card.
• Your own authenticated apply request is the only writer that can approve it.
• ATSReady rechecks whether the target record is still writable.

Why apply can refuse

Apply can stop instead of writing when:

• the record changed after the card was drafted,
• the target record is no longer available,
• or the requested address inside the record is no longer valid.

That prevents a stale card from silently writing to the wrong state. If it refuses, ask again in the conversation — the assistant drafts a fresh card against the record as it now stands.

Related

• What ATSReady chat can do
• Chat limits
• Professional Journey
• You have an interview on Thursday, which ends at this card