Short answer: for B2B SaaS event notifications, use an email and SMS API to create one durable delivery ledger, then sample the telemetry around it. Polling and retry belong to that ledger's operational layer. The integration question is effort: can the team explain a missed compliance notice without retaining every response?
1. How should event notifications use an email and SMS API for polling?
Start with the bytes that the bill actually stores. Use events x attempts x polls x response bytes as a working model. Fifty thousand notices, two retries, and six polls create 900,000 observations before indexing. I read log lines as bytes stored and labels as cardinality.
Keep notification ID, channel, attempt, request time, correlation ID, state, next check, and failure class in the ledger. Keep recipient identity there too, behind access control.…