Notification preferences
Hilal Chatbot fires a lot of events — new conversations, escalations, quota alerts, billing events, action confirmations. The notifications page is where you decide which of those reach you, where, and how often.
In this guide:
- Open notification preferences
- Channels (in-app, email, Slack)
- Per-event toggles
- Quiet hours
- Connect Slack DMs
Step 1: Open notification preferences
Settings → Notifications.
Screenshot: The notification preferences with per-event toggles.
You’ll see a matrix:
- Rows = event types.
- Columns = channels (In-app, Email, Slack).
Toggle each cell on or off.
Step 2: Event categories
Common events:
| Event | When it fires | Default |
|---|---|---|
| New conversation assigned to me | An admin / round-robin assigns a conversation to you | All on |
| New unassigned conversation | A conversation lands in the unassigned queue | In-app on |
| Conversation reply | The customer replies in a conversation you’re handling | In-app on |
| Mention | A teammate @-mentions you in an internal note | All on |
| Quota threshold crossed | Message quota crosses 75%, 90%, 100% | Email on |
| Billing event | Subscription renews, charge fails, plan changes | Email on |
| Action confirmation pending | An AI Action requires human confirmation (and you’re a designated approver) | All on |
| Auto-retrain failed | A scheduled re-training failed | Email on |
| Webhook delivery failed | A webhook to Zapier / Make / custom failed multiple retries | In-app on |
| Weekly digest | Monday-morning rollup of last week’s activity | Email on |
Step 3: Pick a frequency
Some events support frequency control:
- Real-time — immediate notification.
- Hourly digest — batched into an hourly summary.
- Daily digest — once per day.
- Off — no notification.
For high-volume events (every conversation reply), digests prevent burnout.
Step 4: Quiet hours
Set a window where notifications are suppressed (or only urgent ones land):
- Quiet hours: 19:00–08:00 your local time.
- Days: pick weekdays only, or include weekends.
- Override for: only urgent events (e.g., quota at 100%, billing failure).
In-app notifications still queue during quiet hours; email and Slack are paused.
Step 5: Connect Slack DMs
If your org has Slack connected, you can opt in to Slack DMs:
- Settings → Notifications → Slack → Connect to Slack DMs.
- OAuth approves Hilal Chatbot to DM you.
- Slack column appears next to in-app and email.
Slack DMs are great for real-time events you want to act on immediately.
Step 6: Email recipient
By default, email notifications go to your account email. To use a different one (e.g., your team alias for billing):
- Notifications → Email recipient → Override.
- Add a specific email per category.
Useful when finance wants billing emails but you don’t.
Step 7: Bulk operations
- Mute all for 24 hours — useful when you’re in deep work.
- Reset to defaults — undo customizations.
Notification feed
The bell icon top-right of every page shows your in-app notifications:
- Unread count.
- Click to read; click row to jump to context.
- Mark all as read clears the badge.
Per-organization vs. per-account
These preferences are per-account, not per-organization. If you belong to multiple orgs, the same prefs apply to all (with org-specific filtering).
For different prefs per org, you’d need separate accounts — not common, but possible.
Tips
- Don’t enable everything. Notification fatigue is real. Pick the 3–5 events that genuinely require your attention.
- Use digests for high-frequency events. Daily-digest “Conversation reply” + real-time “Mention” is a common combo.
- Quiet hours actually work. Your team will respect them if you set them.
What’s next
You’ve reached the end of the operational sections. The last guide section covers the upcoming Unified Agentic Chatbot Beta.