Your AI employee's claims are checked against what it did
When your AI employee tells you in its chat that it did something or that it will do something later, that statement is checked against what it actually did. A check that is busy now runs again a few minutes later instead of leaving the reply unchecked.
What you get
- In your chat with your AI employee, a statement that it did something, such as sending an email, or that it will do something later, such as reminding you, is checked against what it actually did while answering: the actions it took, the tasks it set up and the mail it handled.
- If a statement does not hold, a short note is added at the end of the reply, in the language of the reply, saying what it can and cannot confirm. When a promised follow-up is not set up, the note says so and offers to set it up.
- The check runs right after the reply arrives, so a note can appear a little later.
- When the check is busy or cannot finish, it runs again a few minutes later instead of leaving the reply unchecked. Before, a busy check could leave a reply unchecked.
- Each check now gets more time, the same for short and long answers, and each thing it reads about what your AI employee did is whole rather than shortened, so a cut-down record no longer misleads it.
- A check that runs later uses the record of your AI employee's tasks saved when the reply was written, so a change made afterwards does not make a kept promise look broken or a broken one look kept. If that record is missing, it leaves promises unjudged rather than risk a wrong note.