An email and calendar assistant is most useful when it can reconcile a conversation with an actual event. The difficult part is not finding a free rectangle in the calendar. It is understanding whether the people involved agreed to that time and making only the change you authorized.
A rescheduling request makes the problem concrete. You need the latest email, the existing event, the relevant time zones and your availability. Then you need to distinguish a proposed reply from a sent message, and a planned calendar change from a saved update.
The workflow below uses an entirely fictional conversation. It is a practical review method, not a demonstration that every assistant or connection supports every action.
One Request, Two Different Sources of Truth
Imagine you organize a 30-minute project review with Priya. Your calendar contains the review on Thursday, October 8, at 15:00 Europe/London. Priya emails: “Could we move to Friday at the same time?” An earlier message in the thread says “15:00 London time,” and the invitation agrees.
Your calendar shows an existing event from 15:00 to 16:00 on Friday. You would be available at 16:30, but you do not have access to Priya's calendar.
The email establishes that Priya wants a change. It does not establish a new agreement. The calendar establishes a conflict in your own schedule. It does not establish Priya's availability at 16:30. If the assistant merges those facts into “Meeting moved to Friday at 16:30,” it has skipped the most important step.
The first useful output is therefore a reconciliation, not an action:
Existing review: Thursday, October 8, 15:00–15:30 Europe/London. Priya proposed Friday at the same time. Your Friday 15:00 slot is occupied. A possible alternative is 16:30–17:00, but Priya has not accepted it. No email has been sent and the original event is unchanged.
Read the Whole Relevant Exchange
Ask the assistant to find the current event and the latest relevant messages, including any response that supersedes an earlier proposal. A quoted sentence in a reply is not necessarily the newest position, and a familiar subject line does not prove that two messages concern the same event.
Check the identity of the event: organizer, attendees, duration and topic. If there are two similarly named reviews, stop and identify the right one. A correct time applied to the wrong event is still a failed task.
Use explicit time zones and dates in the proposed change. “Friday afternoon” is insufficient when participants travel or work in different locations. Preserve the intended duration unless a participant has agreed to change it. If the source only says “same time” and the earlier time cannot be established, the next step is a clarification question.
Your request might be:
Review this scheduling thread and the existing project-review event. Identify the latest proposal, what has been accepted and any conflict in my calendar. Use explicit dates and time zones. Suggest a reply, but do not send it or modify the event. If the event or intended time is ambiguous, ask me before proceeding.
Offer an Alternative Without Claiming an Agreement
In the fictional case, a draft could say:
Friday at 15:00 London time conflicts with another appointment. Would Friday, October 9, 16:30–17:00 Europe/London work instead? I'll keep Thursday's invitation unchanged until we confirm a new time.
Before sending, check that the alternative fits your full schedule, including any calendars the assistant could not access. Available time is not always usable time: you may need travel, preparation or a buffer. Those constraints should be supplied rather than assumed.
The draft should also say what happens to the original invitation. Here, it remains unchanged. In another situation, you might agree to cancel first and arrange a replacement later. That is a user decision, not a scheduling convention the assistant should invent.
Sending requires its own approval. Review the recipient and exact message; “this looks good” should not be treated as broad permission to alter other events or contact additional attendees.
Change the Event After the New Time Is Accepted
Suppose Priya replies, “Yes, Friday October 9 at 16:30 London time works.” Now there is evidence of agreement. Recheck your availability because it may have changed since the proposal was drafted.
Then inspect the intended update before authorizing it:
| Detail | Expected change in this example |
|---|---|
| Event | Existing 30-minute project review with Priya |
| Old time | October 8, 15:00–15:30 Europe/London |
| New time | October 9, 16:30–17:00 Europe/London |
| Attendees | Unchanged |
| Location or meeting link | Preserve unless a change is required and approved |
| Scope | This event only; no recurring-series changes |
Changing an event and notifying attendees are related but distinct outcomes. Ask the assistant to explain what its available tool will do about invitations or update notices before it acts. If it cannot establish that behavior, complete the change in the calendar interface where you can inspect the options.
This example assumes you control the event. If someone else is the organizer or the connection cannot edit it, prepare a reply asking the organizer to update the invitation. Do not create a second event simply to make the workflow appear finished.
Verify the Result and Handle Partial Completion
After an approved update, check the saved event's date, time zone, duration and attendees. If the assistant can return a link to the event, use it. If not, inspect the event directly. The correct end state is one updated review, not an old event plus an accidental duplicate.
A sent message and a saved calendar event can fail independently. If the email succeeds but the event update fails, report both states and leave the calendar work visibly unfinished. If the tool times out, inspect the destination before retrying: the action may already have taken effect even though its confirmation did not return.
A useful final report for the example would identify the updated event and its new time, then state whether an attendee update was confirmed. It should not claim that Priya read the notice or will attend merely because the event was saved.
Applying the Workflow in Today
Today supports Gmail and Google Calendar actions through authorized connections, including email preparation and calendar work. The Today product overview explains how connected work fits into the personal agent; the actions available to you still depend on the connection, permissions and confirmation flow.
Begin with the read-and-draft portion of this example. Ask Today to reconcile one scheduling thread with one event, inspect its proposed reply and only then authorize a supported external action. This does not require granting the assistant responsibility for your entire inbox or making it a universal task manager.
Treat account permission and task instructions separately. A narrow request does not necessarily narrow the technical permission granted to a connector. Check the available access before connecting, and do not use a work account this way if your organization does not allow it.
Email explains what people are asking for; the calendar records what is scheduled. A reliable assistant helps you bring the two into agreement while leaving the proposal, approval and completed change visible at every step.