Grok Bot corrects and emails a notary form remotely
@weiser86 reports that Grok Bot found and filled a state-licence form, then remotely corrected a first-name mismatch and emailed the PDF to the notary location.
x.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Find and complete [official form] using the exact legal details I provide. Save the PDF for review. If I request a correction remotely, update the saved copy and email only the approved recipient.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- @weiser86
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The poster reports receiving a corrected printed form in less than a minute after asking for the change, followed by notarisation. The human notary, not the agent, signed the document.
- Human involvement
- The poster printed the first version, attended the appointment, supplied the correction instruction and recipient, and obtained a human notary signature. The original name mismatch remained a real failure.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- The poster asked Grok Bot to find the state-licence form, fill it out and save it on the laptop desktop.
- After printing it, the poster took it to a notary appointment; the notary rejected a first-name mismatch with the licence.
- The poster asked the agent remotely to reopen the PDF, use the full legal name and email it to the shipping store.
@weiser86 describes needing a notarised document for a state licence. While at home, the poster asked Grok Bot to find the form online, complete it and save it to the laptop desktop. They later printed the document and took it to a notary appointment at a local shipping store.
The first version was not acceptable: the first name on the form did not match the full legal name on the licence. That mismatch matters because the account includes an agent-prepared document that initially failed an identity check. It should not be presented as flawless form automation.
At the appointment, the poster contacted the bot and asked it to reopen the PDF, correct the name and email it to the store. According to the account, the corrected email arrived in less than a minute, and another employee brought over a clean printed copy. The notary then signed it.
The supported workflow is remote retrieval, correction and delivery of an existing document. The poster supplied the correction and destination, and a human performed notarisation. The source does not identify the state, form number or email integration, and does not establish that the agent verified legal identity before creating the original form.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · @weiser86
Frequently asked questions
What went wrong with the first form?
The first name did not match the full legal name on the licence, so the notary would not notarise the initial copy.
What did the agent do remotely?
The poster says Grok Bot reopened the saved PDF, corrected the name and emailed it to the shipping store for printing.
Did Grok Bot notarise the document?
No. The source says a human notary signed the corrected form after it was printed at the store.
More details
Remaining steps
- The poster reports that an employee printed the corrected copy in less than a minute and the notary signed it.
About this account
The agent reportedly found and prepared a form, then reopened, corrected and emailed the saved PDF while the poster was away from the laptop.
Scout supplied verified public X API captures read live on 2026-10-29 and authorised their use instead of reopening X. This entry is based on that supplied capture, not an independent live retrieval or reproduction. Results are self-reported. Small account; included for a detailed firsthand sequence with an initial failure and a concrete recovery. Credit remains the handle; no surname inferred. No exact task prompt is shared in the retained source material; the prompt is editorially suggested.
Credit: @weiser86
Source published
Added to Agents In Use
Source checked
Tools and topics
Grok Bot · PDF · email
document correction · remote file access · notary form
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.