Safety and control
Get notified when Otto needs you
Notifications bring important events from Otto to your attention without asking you to keep the conversation open. Use them for decisions and problems that would otherwise leave an agent or automation waiting; keep routine results in their conversation or chosen delivery destination.
When notifications help
Otto may notify you when:
- an agent needs your approval before it takes an action;
- an agent or automation finishes work that needs your review; or
- an automation fails or reaches a condition that needs attention.
A notification is not a replacement for the result itself. Open the relevant conversation or automation run to read the request, result, or error before you act.
Turn notifications on
- During setup, allow notifications when Otto asks.
- If you skipped that step, open Otto's device settings and select Notifications.
- Allow notifications for Otto in your operating system's notification settings.
- If you want notifications while you are away from the app, keep the Otto device online and follow the platform's guidance for allowing the app to run or launch in the background.
Notification settings can differ between desktop and mobile. If a setting is not available in your app, use the operating system's notification settings for Otto instead.
Respond to a notification
- Open the notification and return to the indicated conversation or run.
- For an approval request, read the action, target, and reason. Choose Approve or Deny, or return to the conversation with a correction.
- For a completed result, review the output and any next step Otto describes.
- For a failed automation, open the run details and use the error to decide whether to reconnect an app, adjust access or limits, revise the instruction, or retry the run.
An approval notification does not grant access by itself. The agent or automation still needs the connected app and the appropriate access level.
If notifications do not arrive
Work through these checks in order:
- Open Otto and inspect the conversation or automation's run history. The event may have occurred without a system notification.
- Check that notifications are enabled for Otto in its device settings and in your operating system. Also check that a focus, do-not-disturb, or battery setting is not suppressing them.
- Confirm that Otto is online. An offline device cannot deliver fresh results or notification events.
- For an automation, open its settings and confirm the task's result and notification behavior. A delivery destination and a notification are separate choices.
- On desktop, confirm Otto is running or configured to launch as required by your platform.
If a notification is still missing, record the approximate time, the agent or automation involved, and any visible run status before contacting support. Never include passwords, recovery codes, or other credentials in a support request.