Forms are under development for release 1. The design separates two facts.
First, did Sitearc save the response? Second, did a notification provider accept an alert?
Those facts are related. They are not the same fact.
A receipt proves persistence.
Sitearc saves accepted form submissions before returning a receipt.
The saved response and its notification outbox row commit together.
HTTP 202 with saved true is evidence that the response was persisted.
A setup screen cannot prove that. A test receipt can.
A notification is a separate delivery attempt.
Notifications leave through a worker after the response is saved.
That keeps the response from depending on an email provider being perfect.
It also means the inbox matters. The inbox is where the saved response lives.
Saved in Sitearc and provider accepted should stay visually separate.
Provider accepted is a narrow claim.
Provider accepted means the provider returned success.
It does not prove that a person received or read an email.
An inbox rule, outage, typo, or provider policy can still affect arrival.
That is why the product should name the exact status it knows.
At least once means duplicates are possible.
At least once delivery sounds reassuring. It is also a warning.
A provider may receive a request before a worker loses its connection.
A retry can repeat the delivery. Webhook consumers should deduplicate events.
Good status language helps teams trust the saved response without overstating delivery.