Oppy, in your Slack. Ask, approve and get alerts where your team talks.

One Slack thread is one conversation with Oppy. It also shows in the app's Chat, marked with Slack's logo, so you can carry on at your desk. Each answer ends with Open in Optizads and a thumbs up or down.

A channel can follow one ad account. An admin picks the account from Oppy's menu in that channel, then chooses whether Oppy answers when mentioned or answers every message.

In any message's menu, Ask Oppy about this hands that message to Oppy. A link to a page of the app shows as a card. /oppy report makes the report of the month you pick, in its own thread.

Each person decides what reaches them in direct messages: their notifications, such as mentions and changes made, and a morning briefing of their own.

A change Oppy proposes comes as a card, the change written on it, with Confirm. Confirm runs that change, with the same checks as in the app.

Each morning, the channel that follows an account gets a briefing. It gives yesterday's spend and conversions against a usual day, and the open alerts. The changes waiting follow, each with Approve and Decline.

Once someone presses Approve or Decline, the card says who did. The task moves the same way on the Tasks page.

Slack sends Oppy the messages of the channels it is in. Oppy keeps only what is meant for it: direct messages, mentions, /oppy, the messages you hand it, and every message of a channel where an admin turned that on. It reads no channel it is not in.

Nobody acts through Slack before connecting their Optizads login. Every message and every button checks again that the person may open the account.

Oppy can make mistakes, like any AI. Check a figure in the app before you act on it, and read a change before you confirm it.

Your Slack messages never train an AI model. The privacy policy says what is kept and for how long.