Support

Something isn't behaving. Start here.

Most of what gets reported turns out to be one of four things, and three of them are Android settings rather than Doorman. If yours is a question about how the product works rather than something misbehaving, the questions page is the better one.

Setting it up

Doorman asks for two things, separately, and it works — less well — without either.

  1. The call screening role. Android only shows one app at a time the calls that are not from your contacts. Granting this is what lets Doorman hold a call rather than watch it ring.
  2. Notification access. This is what produces the log for texts and app notifications. Without it the door still shuts and you still get the quiet — you just lose the receipts. That is stated on the screen rather than being made a hard requirement.

Four things that are usually the cause

A call you expected was held

If the number is not in your contacts, that is the door working as written. Open the log, find the entry, and it will name the rule. Add the number to your list and it will ring next time. If you know a call is coming, add it before — that is what the expected call pass is for.

A verification code never arrived

Short codes are never saved contacts, so a shut door holds them. Use Let a code through on the Door screen: messages open to every sender for ten minutes and then shut on their own. Why it is a timer and not something cleverer.

An app you want is still being held

Per-app exceptions are not ours to grant. Android only lets the app that owns a notification channel exempt itself, so the switch lives in Android's own Do Not Disturb settings. Doorman will deep-link you there. The longer answer.

Your phone got quieter but voicemail got busier

Expected, and worth understanding rather than reporting. Taking the screening role takes it away from whatever your carrier or handset was doing before, and Doorman silences where that filter used to decline. A silenced call rings out and reaches voicemail; a declined one never rang at all. The Line is the half built for this.

Things to check before writing in

  • Android 10 or newer. Carrier attestation, which is one of the signals the log reports, needs Android 11 and a carrier that actually attests.
  • Doorman still holds the screening role — some OEM battery settings will quietly revoke it after a period of not being opened.
  • The decision budget is three and a half seconds. If it runs out, the call rings and the log records exactly that, rather than pretending it made a decision.

Getting your data out, or getting rid of it

The history is on your phone. You can clear it from Settings, set how long it is kept, or uninstall and it goes with the app. Deleting your data covers what is held on our side for the Line, and how to remove it.

Reaching a person

There is no ticket system and no chatbot. One address, answered by somebody who worked on it. Contact says what to include so the first reply is useful.

If something was held and you were not told, that's a bug.

Not a preference, not an edge case. Everything Doorman does is supposed to end up in the log with the reason attached, and a test fails the build if a path appears that could hide one. Tell us and we will treat it that way.