Sending notices to another address

Integrations sends this account’s emergency notices to an address that is not a Calchis login: a duty inbox, a watch-desk distribution list, a shared mailbox the whole shift can see.

What is sent

Two things: a CCIR met on one of your incidents, and a parametric trigger breached. Not "approaching" — an inbox that receives both stops being read. Each notice repeats what the email to your own users says, and links back into Calchis.

Adding an address

Press + Add an address, give it a name and the address. Calchis sends one confirmation email to it. Nothing else is sent until someone at that address confirms, so the row sits at Awaiting confirmation until then. Resend confirmation sends it again; once confirmed, the same button sends a test.

The address cannot be edited afterwards, because the confirmation belongs to that address. Remove the entry and add the new one, which confirms in its turn.

Stopping them

Every notice carries a link that stops them, and the RFC 8058 one-click header mail providers use, so the recipient never needs an account. A stopped row says Stopped by recipient; that is the mailbox’s decision, not an error. You can also Pause and Resume from this page, or Remove the address.

Slack, Teams and custom webhooks

They are named on the page and do not send. To reach Slack or Teams today, put an incoming-webhook URL on a trigger (Triggers → Edit) or use the account webhook under Settings → Webhooks. See API keys and webhooks.

Availability

Integrations are included from Analyst — see pricing.