ChatGPT Voice can now act on your email, calendar, and Slack
Illustration, not documentary evidence of the event.
ChatGPT Voice can now use email, calendar and Slack plugins, The Decoder reports. The report describes looking up events, sending emails and using connected apps through spoken requests. It also describes creating documents, presentations and spreadsheets in ChatGPT Work on web and mobile.
Evaluate a workflow, not just a conversation
For a team considering voice access, the useful distinction is between retrieving information and changing it. Reading a calendar entry and sending an email have different consequences even when both begin with a spoken sentence. Assess them separately before enabling a broader workflow.
- Start with a read-only task involving non-sensitive information. Check whether the answer refers to the intended account, date and event.
- For an email action, use a test recipient. Check the recipient, message and attachments before sending. If the workflow does not let you inspect those details, keep that task in the email application.
- For a calendar change, use a disposable event. Confirm the date, time zone and attendees in the calendar itself after the action. An assistant's spoken confirmation alone is not evidence that the intended change was saved.
- Before connecting a work account, review the permissions being requested and how access can be revoked. Follow the organization's existing rules for connecting third-party tools.
These are evaluation criteria, not results of a Seedwire test. The report does not establish how confirmation, permissions or audit records behave in each connected application. That does not mean those safeguards are absent. Check the current product documentation and the actual account configuration before relying on a consequential action.
A successful read-only trial supports using that specific workflow. It does not establish that financial actions, external messages or other connected tools are equally reliable.