Feature
Send an issued receipt on WhatsApp or by email with the PDF attached, or download and print it. Whichever route a copy takes, it is recorded against the receipt — so “did this donor ever get their receipt?” has an answer.
Four routes, all recorded: WhatsApp, email, download and print. Email attaches the receipt PDF to a covering note carrying your organisation’s own name, address and 80G registration. WhatsApp sends the same PDF as a document from a number your trust links itself. Download and print produce that PDF for handing over in person or filing.
Every copy carries a QR code pointing at the receipt’s public verification page, so a donor can check any copy against the trust’s own record.
The message is composed by the person sending it, within limits the trust sets.
Delivery attempts sit on the receipt’s own timeline, beside the fact that it was created, approved and issued — because an auditor asks for one history, not two.
By WhatsApp or email with the PDF attached, or by being handed a printed or downloaded copy.
Emailing is a deliberate act by somebody holding the delivery capability: they choose the address, can add cc and bcc recipients and a reply-to that reaches the trust, and can write a note that goes with the receipt. WhatsApp can also be set to go out automatically as a receipt is issued, which is a decision the organisation makes once.
It is retried automatically after 1, 5 and 25 minutes, up to 4 attempts in total.
A hard bounce is never retried. Repeatedly sending to an address that is known to be bad is how a sending domain’s reputation is destroyed, and the receipts that would have reached real donors start landing in spam instead.
Every receipt has a delivery history showing each attempt, which channel it used, who asked for it, the address it went to and where it ended up.
What can be known depends on the channel. A send that has left the system is recorded as sent; confirmation of delivery, a read, or a bounce is recorded when the mail provider reports one back. The screen distinguishes “handed to the provider” from “confirmed delivered” rather than describing both as done.
Yes. Downloading or printing a receipt is written to the same history as anything that was emailed.
The question a trust actually asks is “did this donor ever get their receipt?”, and the answer should not depend on which route it took.
Yes. An issued receipt can go to a donor on WhatsApp with the PDF attached as a document and your own wording as its caption, sent from a number your organisation links itself.
It is recorded in the same delivery history as everything else. The gateway confirms it handed the message to WhatsApp and reports nothing afterwards, so the row settles there and never advances to “read”.
No. No SMS provider is connected, so SMS is not offered as a way of reaching donors and nothing here sends a text message.
Receipts reach donors by WhatsApp, email, download and print. Anything sent is recorded; nothing is described as sent that was not.
No. Email is never automatic: every message is a deliberate act by a person, recorded against their name together with the address it went to.
WhatsApp is the one channel that can be, and only because an organisation turned it on — the setting is off until somebody chooses it, and it applies to WhatsApp alone. There is no consent register in this product, so who a donor hears from stays a decision the trust makes rather than one a flag makes for it.
Register your organisation, issue a receipt, and email it with the PDF attached and a verification link the donor can open without an account.
