Offers
An offer is built from a template — role, compensation, start date, terms — and sent to the candidate, who can read and respond to it from a link.
Templates are editable and reusable, and the placeholders fill from the position and the candidate rather than being retyped. Responses are recorded against the candidate, so the state of an offer is visible without anybody chasing a mailbox.
Rejections
Rejecting a candidate in the pipeline and telling them are separate actions, deliberately. Recording the decision closes your process; sending the message is something you choose to do and choose the words for.
Where you do send one, a template with a genuine sentence about the stage they reached is worth writing once. The default is short and neutral because a generic rejection is better than a falsely warm one.
What a rejected candidate can see
Nothing about the reasoning. Your internal decision and its rationale are never shown to a candidate, whatever your result-visibility settings — those govern their performance report, which is a different document.
If you have released reports for the stage, they can still see how they did. Many organisations do exactly this: the outcome by email, the performance report on the platform.
Reopening
A rejected candidate can be restored to the pipeline if a role reopens. Nothing was deleted.