In-app Alerts always work. Connect a chat tool if you want the same events in a channel or on your phone.
Integrations → Slack, Telegram, Microsoft Teams, WhatsApp, WeChat (WeCom), or Twilio SMS.
What gets posted
Depending on the provider, messages fire on share, view, and/or accept. They follow the same rules as in-app alerts: staff Preview and mailbox scanners should not look like a client open.
| Provider | Auth | Typical use |
|---|---|---|
| Slack | OAuth | Channel for views and shares |
| Microsoft Teams | Incoming webhook / API | Same idea in Teams |
| Telegram | Bot token | Personal or team bot alerts |
| Cloud API | Alerts to a number you control | |
| WeChat (WeCom) | API | Internal WeCom robot |
| Twilio SMS | Account SID + token | SMS for high-signal events |
You pay Slack/Twilio/etc. directly. Mute on a document still means “do not ping me about this link.”
Notification preferences
[Notifications-settings] Settings → Notifications (and your user prefs) choose in-app, email, and which integrations fan out. A teammate can keep Slack on and email off.
Outreach reminder emails (unopened / follow-up / balance due) are separate. They go to the creator. See Views, alerts, and reminders.
Chat agents that create clients
Telegram / Slack alerts are outbound only. To have a bot create a client or draft, use Incoming Webhooks (Team+). The chat app never talks to InProQu directly. The agent POSTs. Guide: WordPress and webhooks.