Troubleshooting: look for the underlying record
Start with the original request or billing record, not the inbox alone. ManyRequests documents several notification types, and email delivery is a separate event from the work being recorded. Note the client, approximate time and action you expected. If the original record exists, use it rather than submitting a duplicate. A missing notification can inconvenience a customer without meaning that the underlying work or payment process failed.
Check the intended recipient
Confirm which person should have received the message and whether they are using the expected account. A forwarded email or a shared business address can obscure who actually has portal access. Review the current notification preferences and the relevant request participants where supported. Do not broaden permissions or add every teammate merely to make an email arrive. Keep the investigation limited to the information needed for the affected work.
Separate preferences from delivery problems
A preference that suppresses a type of email differs from a message delayed or filtered by the mailbox. Check the documented settings before changing them, and inspect only the relevant mail when authorized. Avoid asserting that a provider outage caused the problem without evidence. Record what you observed: the request exists, the intended email is absent and the recipient’s relevant preference is enabled, for example. That is more useful than a generic failure label.
Use a safe interim update
If work is safely recorded, send an agreed manual update through the normal channel rather than asking the client to repeat a potentially consequential action. Keep the original identity and state visible. For an uncertain payment or submission, reconcile the actual result before retrying. This procedure is our operational recommendation; it does not claim that the product guarantees email delivery or that every action can be repeated without creating another record.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- ManyRequests notification email types — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests notification preferences — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19
- ManyRequests managing requests and exporting data — Merchant documentation · help.manyrequests.com · Merchant-controlled · checked 2026-09-19