Get owner alerts from your apps
Owner alerts tell you the moment something happens in your apps that you may want to know about: a supplier answered an order, an expense claim is waiting, a project went over budget, a deal is stuck. You read them in Kluvan, and can also get them by e-mail or Telegram. They sit in the Owner workspace, beside the attention list.
Before you start
- Only the owner can change these settings. Every change is kept in the activity log.
- For Telegram: your plan must include it, and your organisation's Telegram bot must be set in Settings → Integrations (see Telegram).
Steps
- Open Settings → Owner alerts.
- Tick Switch on owner alerts. Nothing is shown or sent until this is on.
- Under Which events alert, tick the events you want, for example Failed sign-ins, Slow and dead stock or Requests waiting too long.
- Under Quiet hours, set From and To. Nothing is sent in these hours; the digest after them carries what happened.
- Under How alerts are sent, pick one:
- Serious ones at once, the rest in an hourly digest (the default);
- Every alert at once;
- Everything in an hourly digest.
- Set Most messages per hour (the rest wait for the digest).
- Under Where, tick Telegram and E-mail to your address if you want them. Alerts in Kluvan (the bell and the alerts page) are always on.
- Tick Managers see the alerts too (within their branches) if your managers should see them.
- Select Save.
[SHOT workspace-owner-alerts-settings 1440x900]Screenshot to come: Settings → Owner alerts: Switch on owner alerts ticked, Which events alert with several events ticked, Quiet hours from 22:00 to 08:00, How alerts are sent with the first choice selected, Most messages per hour 10, and Where with the in-app line always on, Telegram and E-mail ticked
Review alerts
- Select the bell (Alerts) at the top of any page. It counts the alerts of the last 7 days not yet reviewed.
- Or open Owner workspace → Owner alerts.
- Filter by days (From, To), Alert, Branch or Status, and select Apply.
- Open an alert, type a Note if you like, and select Mark as reviewed. Select Mark as not reviewed to undo.
- To keep a copy, select CSV or Excel next to Export:.
[SHOT workspace-owner-alerts-page 1440x900]Screenshot to come: The Owner alerts page: filters From, To, Alert, Branch, Status with Apply; a timeline of alerts such as 'Supplier answered an order', 'Expense claim waiting' and 'Deal stuck', one marked 'Reviewed by Mona', and the Export: CSV / Excel links
Alerts from your apps
These come whenever owner alerts and the app are on:
| App | Alerts |
|---|---|
| CRM | Campaign finished, High-value customer gone quiet, Deal stuck |
| Collections | Promises to pay missed, Money crossing into the oldest age, Bank payments not matched, Disputes past their day |
| Procurement | Supplier answered an order, Purchase requests waiting, Supplier invoice not matching, Orders late |
| Projects | Project past due, Project over budget, Time not invoiced, Retention due |
| Subscriptions | Subscriptions past due, Subscriptions cancelled, Deliveries not scheduled |
| Expenses | Expense claim waiting, Petty cash low, Expense claim outside policy |
| Fixed assets | Warranty ending, Depreciation waiting, Asset count still open |
| HR & Payroll | Requests waiting too long, Weekly hours cap near, Labour cost over the target |
Good to know
- Alerts or the attention list? An alert tells you once that something happened. The attention list keeps an item open until the records show it is dealt with, says what happens if it is ignored, and can be given to someone. Many events appear in both.
- E-mail goes to the owner's address. An address that bounced or marked our mail as spam gets nothing.
- WhatsApp is not a channel for owner alerts.
- Desk, Workflows and Connections raise no owner alerts; their items are on the attention list.
- For one message a day with the top items, set up the daily brief.
- The same Telegram bot can answer questions. See Ask.
Was this page helpful?
Thank you. Your answer helps us improve this page.
Still need help?
Chat with us on WhatsApp. Tell us what you were doing and, for an error, the code after the # in the link.