Limitations & Recommendations

What M91 does not guarantee, and what to do about it. Each point has four short lines: True, Why, Do, Don’t. Delivery limits are in the API.

Reaching people

Only HIGH and CRITICAL make phone calls

True
LOW and MEDIUM ring loudly and stop there. HIGH and CRITICAL call after 45 seconds of no response, in small rounds, and the call only says to open the app.
Why
the default is MEDIUM so a careless alert can never phone anyone.
Do
pick severity on purpose, and put everything people need in title and description.
Don’t
plan on “everyone will get a call”.

A send link alerts a channel, not a person

True
there is no recipient field. The channel is the list, and people only get alerts after they install M91 and accept. An empty channel returns 409.
Why
it keeps phone numbers out of your code, and nobody is added without agreeing.
Do
use narrow channels, and test with Send a test alert from each member’s phone. For one person, use the Platform API.
Don’t
assume a new channel works, or send unrelated alerts through one channel.

The link is a secret in a URL

True
anyone who has it can alert that channel. Revoking deletes it right away, and there is no rotation.
Why
no headers means any tool with a “URL to call” field can use it, and that is also why it is easy to leak.
Do
keep it in a secret store, call it from your server, never log the request path, and use one link per integration.
Don’t
commit it, put it in frontend code, or share one link everywhere.

A link can read a decision but never make one

True
it can raise, close and read alerts. Neither a link nor an API key can answer. Only a person can.
Why
links leak, and a leaked link must not be able to approve for someone else.
Do
if code can decide, decide in code and skip the alert.
Don’t
build a flow where a machine answers for a person.

Alerts over time

Alerts stay open, and repeats are absorbed

True
an alert stays open until somebody closes it. While it is open, repeats with the same customId do nothing. There is no expiry. Closed alerts are deleted after 30 days.
Why
only your system knows what “too long” means.
Do
close the alert when the problem clears, set your own timeout, and treat silence as “no”. Send pure notices with [] and isAutoClose: true.
Don’t
use a timestamp as customId, or open an alert you never close.

Answers are final, and limits apply

True
one answer per person, and it cannot be changed. You can send 60 alerts a minute per link. Identical sends within 5 seconds are merged.
Why
a SHARED answer means someone owns it, and that must stay clear.
Do
offer two or three clear buttons, add a customId, and back off on 429.
Don’t
retry in a tight loop, or use buttons to collect long answers.

API keys, SDKs and agents

An API key is powerful, so guard it

True
it is shown once and has no scopes. It can create and staff channels but cannot alert them, and a person must accept before a direct alert reaches them.
Why
a leaked key must not be able to ring a team.
Do
keep it on the server, rotate by creating a new key and revoking the old one, and invite first and alert only after accepted.
Don’t
put it in client code, or expect an alert to invite anyone.

An SDK or agent follows the same rules

True
an SDK only wraps the send link. An agent waiting on a person may never get an answer.
Why
nothing a wrapper does changes what the link can do.
Do
continue only on the exact approving answer, treat rejection, timeout and errors as “do not proceed”, and close the alert.
Don’t
let an agent do something irreversible just because an alert went out.

The people on the other end

Too many alerts break alerting

True
every severity rings through silent mode, and that permission disappears when people mute the app or leave the channel.
Why
systems rarely fail by not delivering. They fail by delivering so much that people stop reacting.
Do
keep alerts rare, name each problem with a customId, and review what a channel sends each week.
Don’t
escalate severity out of worry, or send an alert whose answer is “look at it tomorrow”.