Proactive triggers
Reach out first when the signals say it's time.
Humane watches each user's state and fires an event when a threshold is crossed: mood dropping, energy running low, a user going quiet, trust passing a milestone. Each trigger has a cooldown and carries a suggested action, and your app decides how to reach out.
Proactive triggers
- mood_dropmood < 0.30cooldown 1h
- energy_lowenergy < 0.25cooldown 2h
- trust_milestonetrust > 0.70, 10+ turnscooldown 24h
- user_inactivesilent for 48hcooldown 24h
- engagement_dropquiet 24h, mood < 0.5cooldown 12h
→ proactive.mood_drop + proactive.triggered · suggested_action included
Five triggers, plus your own
mood_drop
Mood below 0.30. Cooldown one hour. Suggests an empathetic check-in.
energy_low
Energy below 0.25. Cooldown two hours. Suggests fewer, simpler messages.
user_inactive
No messages for 48 hours. Cooldown one day. Suggests re-engaging from the last conversation.
engagement_drop
An established user quiet for a day with mood below 0.5. Cooldown 12 hours. Suggests following up on the last topic.
trust_milestone
Trust above 0.70 after more than ten interactions. Once a day at most. Suggests more personal recommendations.
Your own
Policy rules fire proactive.<name> events on any condition they can match.
Learn moreTwo events per firing, so you can subscribe either way
Each firing sends a specific event, such as proactive.mood_drop, and the umbrella proactive.triggered with the trigger name at the top level. Cooldowns are claimed atomically in the database, so two workers can't fire the same trigger for the same user twice.
- Payload includes the user's state and a suggested action
- Cooldowns survive restarts and work across workers
- Proactive events also come back on process() responses
- Slack and Discord connectors can post them to a channel
Alerts · live
- safety.flaggedcriticaluser_88 · flags: self_harm→ Webhook · Slack
- safety.holdholduser_42 · reply held for review→ Webhook
- anomaly.detectedwarninguser_17 · engagement_drop→ Webhook
- proactive.mood_droptriggeruser_05 · mood below 0.30→ Discord
One handler for every trigger
event = json.loads(raw) # after verify_webhook_signature()
if event["event"] == "proactive.triggered":
d = event["data"]
print(d["trigger_name"], d["suggested_action"])
schedule_check_in(d["end_user_id"], reason=d["trigger_name"])Trigger questions
Something else? Ask us.
Works well with
Policy rules
Policy rules match on a user's state, their message or the time since they were last seen, then fire an event, adjust settings for that turn, set the safety action or skip the model. Rules are validated when they compile and can be tested before they go live.
ExploreTask detection and escalation
When a user writes “remind me to call the pharmacy at 6pm”, Humane extracts the task and its time without a separate API call. Open tasks climb a five-level ladder, firing reminder and escalation events until someone completes or snoozes them.
ExploreWebhooks and events
Humane posts events to your endpoints as things happen: safety flags, holds and blocks, proactive triggers, takeovers, anomalies and more. Every delivery is signed with HMAC-SHA256, retried on failure and parked in a dead-letter queue if it keeps failing.
ExploreEvery AI should know who it's talking to.
The safety and human-oversight layer for emotional AI: user state across sessions, risk alerts, safety gates and human takeover, with every decision explained.
