The document is missing, not an explanation
A link is awkward to open on a phone. During a call, it may not help at all. The customer wants the invoice by email.
We developed a dedicated sending tool for this step in FRED. The intended workflow connects a request on WhatsApp or by phone to the associated invoices and the recorded recipient address.
Not to an arbitrary address
The tool is intended for verified customers. It uses the relevant contract relationship and recorded address. A free-form request must not simply override that association.
Illustrative example: during a conversation, someone requests a particular invoice. FRED can select the appropriate document for the intended sending process. This fictional example contains no customer records.

Found, sent and received
| State | What it establishes |
|---|---|
| Invoice found | The document is available |
| Sending confirmed | The sending tool reports a successful step |
| Customer received it | A separate outcome, not proven by retrieval alone |
FRED may say “sent” only after confirmation from the tool. Finding a document or preparing a message is not enough.

A small action with several connected steps
This AI-assisted development includes document selection, recipient binding and result handling. Each deployment needs appropriate configuration and activation.
Finding the relevant document starts with invoice information. Retrieval and sending belong together but solve different parts of the task.
Sources.
- SolvraONE: own development and technical source reviewOwn source · As of
- Stripe: invoice APIVendor / primary · As of


