Ask for the right destination
Say “Help me report a bug” or “Make a feature request.” A bug report is not a journal entry. If you only say “Save this,” Eli should ask which destination you mean.
Describe it
Explain what you were doing, what went wrong, and what you expected. If details are missing, Eli asks for them. He can prepare the existing feedback form using your stated description, but must not invent symptoms.
Review before sending
The draft shows its originating app page. A ready Bible reader can include its displayed book and chapter. This is page metadata, not a screenshot or permission to inspect private screen content. The originating page stays with the draft even if you navigate elsewhere.
You can edit the description and report type. User edits take priority over later tool calls. Add screenshots yourself if useful; none are captured automatically.
Send or cancel
Preparing a draft sends nothing. Review it and press Send report or Share idea yourself. Close the form to cancel. If sending fails, the form keeps your description and shows an error; Eli must not claim delivery.
The normal feedback form also supports signed-out visitors and an optional reply email. Personal Bible saving and journals still require sign-in.