Lead-platform alert logger for Bark-style emails
Gmail alerts from lead platforms logged per message, including forwarded and same-thread alerts, with no double-logging.
The goal
Make sure an owner notices every lead-platform alert quickly, even when alerts are forwarded or bunched into one Gmail thread.
What was built
- A Gmail search for Bark, Checkatrade and MyBuilder alerts, including forwarded copies
- Per-message logging with remembered message IDs, instead of a thread label that hid later alerts
- A sheet tab: arrived, platform, from, subject, forwarded?, logged at, minutes to log
What we learned
Two real-world gaps showed up: owners often forward alerts from another inbox, and Gmail threads repeated alerts together. Both are now handled.
Limits, stated plainly
Tested with fictional, Bark-style emails in a simplified Gmail search mock. Checkatrade and MyBuilder sender formats are confirmed on the first real alert. It does not reply to customers.
How it was tested: real results
| Check | Result |
|---|---|
| Direct alert | Logged |
| Alert forwarded by the owner | Logged (the first draft missed it) |
| Second alert in the same thread | Logged (the first draft missed it) |
| Newsletter mentioning nothing relevant | Ignored |
| Second run | No duplicate rows |
Tell me what you need done
Describe the job in a few lines. You get a fixed-price scope, or an honest “not for me”.
Is this a client project?
No. DEMO – not a client project. It was built and tested with fictional data.
Are the numbers real?
Yes: they come from the actual tests and files of this build. Anything simulated is labelled as simulated.