What to check before accepting a calendar proposal in Vithi AI
An AI suggestion can sound sensible while placing the right task on the wrong day. Before accepting a proposed calendar change, inspect the actual details rather than approving the wording alone. This guide is written by Vithi and explains a review process for the proposal and decision controls in Vithi AI.
Give the request a date and a bounded task
Describe the work you want to schedule and the time you genuinely have available. “Plan some revision tomorrow evening” leaves more room for interpretation than a request that names the calendar date, available interval and intended output.
For a hypothetical request: “Suggest a 30-minute block on 24 October 2026 between 18:00 and 19:00, Dubai time, to correct two chemistry questions. Do not move my existing appointments.” Use your own date and availability. Stating a constraint does not prove the proposal respected it; the next step is checking.
Read the proposal details before accepting
Vithi AI’s review dialog displays the proposal summary and available detail fields, with Accept and Decline controls. Inspect the information shown for the selected proposal. If a required detail is missing or unclear, request a clearer proposal rather than supplying your own assumption after approval.
Check the calendar date, start and end time, task title and the kind of change proposed. “Create a study block” and “change an existing event” are different operations. Identify which record would be affected before deciding.
For the example above, a proposal for 18:00 to 19:00 would allocate an hour, not the requested half-hour. A proposal for 18:00 to 18:30 on the wrong date still needs correction. Matching the topic alone is not enough.
Compare with commitments outside the conversation
Consult the calendar you actually rely on, including any school or family commitments that are not present in the chat. An empty interval in a proposal does not establish that the interval is free in your life.
Keep official deadlines and appointments distinct from flexible study blocks. A suggestion cannot change a teacher’s hand-in instructions or an external exam date. If the proposal touches one of those commitments, check the original source rather than treating an AI summary as authority.
Also consider practical time: travel, preparing the paper and checking answers. A 30-minute block may need a smaller task than a full practice paper. Change the scope or available interval explicitly instead of accepting an unrealistic plan.
Decline the wrong change and request a specific revision
Use Decline when the proposed action is not what you intend. Then state the mismatch plainly: “Keep the same task, but use 18:00 to 18:30 on 24 October; do not edit the existing appointment.” Review the revised details again.
If several proposals appear, evaluate each one. Approving a group should follow checking the whole set, not assuming that a correct first item makes the remaining items correct. Avoid approving overlapping alternatives that were intended as choices.
Verify the applied result in the calendar
An approval decision and a completed change are separate stages. Vithi AI’s action handling distinguishes applied results from errors. If an action reports a problem, inspect the calendar before retrying so you do not unintentionally create another copy.
After accepting, open the relevant calendar day and check the saved event’s title, date and times. Look for an unexpected duplicate or alteration to an existing commitment. The review is complete when the saved state matches your intention, not merely when you clicked Accept.
This process does not promise automatic conflict detection, a particular external-calendar connection or an undo feature. If the result is wrong, use the available calendar editing controls carefully, preserving the original details first.
Use a short approval record
Before deciding, ask: Is this the task I requested? Is the date explicit? Are the times and timezone understood? Does it fit my actual commitments? Does it create or change the intended event? After deciding, ask: Did the action report success, and does the calendar show the expected result?
Keep a brief note if the request is complicated: intended change; proposal checked; decision; saved result; discrepancy, if any. Do not copy unrelated private appointments into a chat just to explain one scheduling constraint. A simple unavailable interval may be enough.