Give each message a useful job
An inbox full of ordinary traffic notifications quickly stops being useful. A weekly summary should help you review a period; a service alert should point to a condition that needs attention. Keeping these choices separate lets a store owner choose the right amount of email without turning everyday monitoring into another approval queue.
Blokk Bot separates optional weekly summaries from service alerts in Settings. Availability depends on email being enabled for the installation. If the controls are not available, the app remains the place to check activity and protection state. These preferences do not replace Shopify’s own account, order or billing messages.
Verify the inbox before subscribing it
When email setup is available, enter an address you control in Blokk Bot Settings and confirm the short-lived code sent to that inbox. Keep the code private. Verification demonstrates access to the address; it does not subscribe the recipient to summaries or alerts. Turn on each preference deliberately after verification succeeds.
Changing the recipient should not interrupt the existing address while the new one is still unconfirmed. Blokk Bot keeps the current recipient and choices until the replacement code is verified. Confirmation replaces the recipient and turns both email choices off, so the new address needs its own explicit opt-in. If a response is uncertain, check the displayed state before requesting another code.
Use the weekly summary to decide what to inspect
Read a summary as a view of supported activity received during its period. It is not a complete inventory of every request made to Shopify. The same collection, consent, marked-test and history limits that affect the app also matter when interpreting email. A quiet report cannot prove that the store had no automation.
Follow up in Dashboard when a finding needs context. Recorded events, observed sessions and restricted accounts answer different questions; they should not be added together into a single success count. Comparing representative periods is useful, but first check whether an allowance was reached or detailed history expired. Those changes can explain a difference without any change in visitor behaviour.
Use service alerts for conditions that need a check
Blokk Bot service alerts can describe a reached monitoring or account allowance, or an account-protection update or recovery that could not be confirmed. Open the app to see the current state and next step. An email describes the condition when it was generated; it is not a guarantee that the condition still exists when you read it.
If monitoring is limited, check the affected allowance and reset time in Plan. If recovery needs attention, inspect the affected account and the confirmed Shopify state. Existing restrictions may still apply while recovery is pending. Removing restrictions and turning protection off remain available without an upgrade.
Sending, delivery and reading are different events
An email provider accepting a send request does not prove arrival in the inbox. A delivery event reports acceptance by the receiving mail server; it does not prove that the recipient read or acted on the message. Failed delivery, spam filtering and mailbox rules can still affect what a store owner sees.
A provider delivery event cannot verify ownership of an email address; the code confirmation is a separate step. Blokk Bot treats failed verification-message delivery as a failure, rather than promoting it because a later response says the send was accepted. A delayed complaint for an old address must not disable a newly confirmed replacement.
For setup problems, check Settings and your inbox or spam folder, then contact support with the approximate time and status. Do not send passwords, verification codes, session files or customer records. Live email delivery and inbox arrival still need to be verified for a rollout; available controls and local tests alone do not establish that result.