Notifications and alerts

PoultryDesk can tell you when something needs your attention - a mortality spike, an overdue invoice, or a missing daily entry - on the channel you prefer, at a volume you can live with. The goal is to be useful, not noisy.

Alert rules

An alert rule decides what you get told about. A manager or owner sets rules under Settings then Alerts. Each rule has:

• A trigger - what to watch for. It might be a number crossing a threshold (mortality above a rate), a particular kind of entry happening, a schedule, or a daily record that was expected but missing.
• Recipients - who is told.
• A message template - what the notification says.
• A cooldown - the least time between repeats, so one situation does not fire over and over.

When you build a rule, PoultryDesk previews how many times it would have fired over the last month, so you can judge whether it is too sensitive before you save it.

Where notifications arrive

A notification can reach you on more than one channel:

• In-app - the bell in the header shows a count; open it to see recent notifications, and tap one to jump to what it is about.
• Email - the rendered message to your inbox.
• SMS - a short version to your phone.
• Web push - a pop-up from the installed app that opens the relevant screen when tapped.
• Webhook - for connecting another system. A rule on the webhook channel POSTs the notification to an HTTPS address you register, so your own software can react to it.

Connecting another system with webhooks

If you want a notification to reach software rather than a person, an owner or manager can register a webhook endpoint under Settings then Notifications then Webhooks. First set a notification template's channel to Webhook, then add the HTTPS address and a secret that signs each delivery.

Before pointing it at your real system, test it against a free sandbox receiver such as webhook.site or requestbin.com: paste the sandbox address as the endpoint, then use the Test button to send a signed sample delivery and watch it arrive. The result shows the event id so you can match it in the sandbox.

Keeping the bell tidy

In-app notifications can be marked read, snoozed for a few hours, or dismissed. Dismissing clears it from the bell but keeps it in your list, so nothing is lost. Each person tunes their own preferences per organization - which channels they want and when to stay quiet - so the same rule can reach different people in different ways.

See also

• Health and withdrawals
• Invoices and payments
• Members and roles