Operation completed
When an operation ends and the weather data is fetched, the configured recipient receives an email with the PDF service proof attached.
Feature · Notifications
PDF in the inbox, when the operation ends
Customers can have the PDF service proof in their inbox minutes after the operation ends — no phone call required, no "did you come?" email chain. Every send is logged.
Three triggers
Updated service proof
If weather data becomes available retroactively (e.g. after a provider delay), an updated proof is sent automatically.
Portal access credentials
When a customer portal account is created, login details are sent automatically to the customer.
Per customer, per location
Notifications can be enabled or disabled per customer and per service location. Different recipients can be set per location — useful when one customer owns multiple sites with different property managers.
Duplicate sends are detected and suppressed automatically — for example, when a service proof is regenerated after a weather data fix, the same address is not notified twice for the same operation.
Plain SMTP
No third-party transactional email service is required.
Notifications send through any SMTP server the operator configures — the same provider that powers the operator's existing business email is usually fine. No SendGrid, Postmark, or Mailgun integration is required (though any of them can be used if preferred).
This keeps the data path consistent: customer addresses and PDF attachments do not pass through a third-party transactional cloud unless the operator explicitly chooses one.
Audit log
Every email is recorded.
- · Recipient address
- · Sent timestamp
- · Notification type
- · Delivery status (sent / failed / skipped)
- · Failure reason (if applicable)
Filterable by status, type, and time range. When a customer claims they never received a notification, the log answers definitively.