How to use Grok Bot to book a notary exam with payment approval
@SLNetworkz reports that Grok Bot found the Arizona Notary Public testing page, created an account, showed dates and paid the exam fee after she approved it. She chose 29 December.
x.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Find the correct registration page for my exam and show me available dates. Help set up the account, but wait for my date choice and explicit approval before paying any fee.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- @SLNetworkz
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- @SLNetworkz reports a booked Arizona Notary Public exam for 29 December, with payment made only after her approval. No receipt is attached.
- Human involvement
- The poster selected 29 December and explicitly approved proceeding before the bot paid. No fee amount, provider or account-security setup is disclosed.
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
- Grok Bot found the Arizona Notary Public testing page.
- It set up the poster's account and retrieved exam dates.
- The poster chose 29 December.
@SLNetworkz reports using Grok Bot to book an Arizona Notary Public exam. Her account describes a connected registration task rather than a recommendation about where to take the test: the bot found the right testing page, set up her account, retrieved available dates and paid the fee.
There was an explicit human checkpoint before payment. She says the bot paid only once she said to go ahead, and that her own choice was the 29 December date. The post does not give the fee amount, name the testing provider or explain how credentials and payment details were supplied. Those details should not be reconstructed from the fact that a booking was reported.
The outcome is her firsthand statement that the exam was booked. There is no attached booking receipt or payment confirmation in the post, so this entry does not independently verify the registration or imply that the exam has already happened.
For a similar task, the useful boundary is clear: let the agent handle finding the registration route and available slots, while the person chooses the date and authorises the payment.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: X · @SLNetworkz
Frequently asked questions
Who chose the exam date?
The poster says she chose 29 December from the dates the bot retrieved.
Was payment approved first?
Yes. The post says the bot paid the fee once she said to go ahead.
How much did the exam cost?
The source does not state the fee amount or name the testing provider.
More details
Remaining steps
- The bot paid the fee after the poster said to proceed, according to her account.
About this account
The bot handled finding the testing page, account setup, date retrieval and the reported payment, with the person supplying the date choice and payment approval.
Read the original X post, available replies and live profile on 2026-10-28; cross-checked full post text and timestamp via FxTwitter. The post has no attached media and no replies adding registration evidence. The payment approval gate is explicit in the original text. Results are self-reported, not independently reproduced. Prompt: Suggested by Agents In Use; no verbatim task prompt is shared for this workflow.
Credit: @SLNetworkz
Source published
Added to Agents In Use
Source checked
Tools and topics
Grok Bot
Exam booking · Payment approval · Registration
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.