Inno Caller — know the customer before you answer

The name, the pinned note and the recent orders on the handset while it rings — and five different failures that used to share one sentence.

Knowing who is calling, before you answer

An agent who can see the customer before picking up starts the call somewhere useful. Inno Caller puts the customer’s name, their pinned note and their recent orders on the handset screen while it rings.

A separate app, on purpose

Call screening is a role Android gates on an app’s core purpose. Bolting it into a general staff app risks that app’s listing, so this is its own small install — and it deliberately does not become the default dialler, which would change the whole calling experience for nothing this feature needs.

No password on the handset

The phone is paired with a device secret, not an account. There is nobody to check a permission on, so the payload the phone receives is non-financial by construction rather than by stripping fields out of a bigger one — the version that strips misses a key eventually.

Every failure says which failure it was

“Could not reach the server” used to cover five different problems: no network, a rotated key, a deleted source, a switched-off source and a server error. Four of those are things somebody can fix, so each now has its own sentence in both languages, with the diagnostics reference the office can look up. A sixth was added because this project has shipped it — a 2xx that is not this API at all.

Recording the call is not the same as attributing it

A ring that ends with nobody speaking is a missed call, and it is recorded as one — never as a call with an invented talk time. A call the system cannot attribute to a person is logged against nobody rather than against a guess.