The card is nearly right. It has the meeting and the person, but it misses the fact that you agreed to wait until the board discussion.
Dismissing the card removes the immediate interruption. Explaining the missing context gives future preparation something better to work from.
Put the correction beside the recommendation
Today feedback lets you add a plain-language explanation from a supported contact card. The feedback is saved as a note linked to that contact before subsequent processing tries to use it.
Be specific. “We agreed to speak after Tuesday’s board meeting” is more useful than “Bad suggestion”. Include the relevant date or condition when it changes what should happen next.
Separate saving from refreshing
For supported meeting cards, you can also request an updated brief. Saving the feedback and rebuilding the brief are separate steps. If the rebuild fails, the saved note remains and the app can offer a retry.
That distinction matters: you should not have to repeat your explanation because a later AI step did not finish.

Check the next piece of work
Read the refreshed brief or later recommendation to see whether the correction has been applied appropriately. A note about one meeting should not become a permanent rule that the person never wants contact.
The benefit is a shorter loop between your judgement and the system’s preparation. You can correct the context where you encounter the mistake, while retaining the original words as a record.
This is saved relationship feedback. It does not establish that every later answer will be correct, or that an AI-generated interpretation should outrank what you actually recorded.