Alerts tell you when a conversation needs your attention. The Alerts page (Manage menu) shows System alerts and Your alerts. Every trigger lands on the Notifications page (Main menu). System alerts are maintained by Desirely: you can assign them per model and silence them, but not edit them.
The catalog
Alert | What it flags | Effect |
Out of script | No script left to send in the conversation | Stops conversation (awaiting intervention) |
Sale | A purchase was confirmed in the conversation | Simple notification |
Offered services | The fan requests a specific service (custom content, cam, a named service) | Simple notification |
Out of funds | Your Desirely balance is empty: the bot stops until you top up | Notification. This alert is Always on: it cannot be unassigned or silenced, and goes to all your destinations |
"Stops conversation" means: the AI pauses on that conversation, which goes into awaiting human intervention. You turn its automation back on once the situation is handled. The other conversations are not affected.
A silenced alert is no longer sent to your destinations, but it still shows on Notifications and keeps its effect: Out of script still stops the conversation. To be warned when a fan asks to meet, makes a complaint or needs a human for anything else, create a custom alert with the Stop the conversation option (see "Create your own alerts").
Assign and silence per model
In Models → your model → Alerts tab, choose which alerts apply to this model and silence the ones you do not want to be notified about. The mandatory alert (Out of funds) stays always on.
Where alerts arrive
Every trigger appears on the Notifications page (alert, model, fan, reason, time and an Open conversation button) and goes to the destinations chosen for that alert (see "Choose where your alerts go" and "Get your alerts on Telegram").