Why I built a "don't text me about this, even if it's urgent" setting into an app whose whole point is texting you when things are urgent

SignalAI's entire premise is simple: AI reads your inbox, and texts you the moment something's genuinely urgent. That's the whole pitch.

So it felt almost contradictory when I sat down and built the opposite — a rule that lets you say "never text me about this sender or keyword, even if it's classified as urgent."

Here's the thing that changed my mind: "urgent" and "worth interrupting me for" aren't actually the same judgment, even when they look like it from the outside.

A concrete example: an accountant who wants every invoice-related email correctly flagged and categorized for their records, but genuinely doesn't want a text every time one lands — they'll check that category on their own schedule. The email is real, the classification is correct, the AI did its job right. They just don't want the interruption for that specific case.

Building this meant a decision I went back and forth on: should "don't text me" and "what category is this" be the same setting, or two independent ones? I landed on making them fully independent — you can force a category without suppressing texts, suppress texts without touching the category, or both. Someone can say "always flag this as urgent, never text me" just as easily as "don't touch the AI's classification, just never text me about this sender."

The part I didn't expect: this ended up making the "urgent → text" promise feel more trustworthy, not less. When someone knows they have real control over exactly when they get interrupted, they trust the system more, not less, when it does decide to interrupt them.

Curious if others building notification-heavy products have run into this same tension — the difference between "this is genuinely important" and "I want to be interrupted about this right now."