Yes, the state-by-state RON rules sit in the chatbot's system instruction and you can edit them in the SleekAI admin whenever a legislature updates the rules. The bot refuses to book a session it can't legally complete and offers an in-person referral instead, so the signer never pays for an appointment that has to be cancelled.

SleekAI exposes your services page postmeta to the chatbot through mapped variables. The first-seal fee, additional-seal fee, after-hours rate, and apostille fee are read live from the page when the bot needs to answer a price question. Edit the fee on your services page and the next conversation reflects the new number.

If you use LatePoint, Amelia, or another booking plugin with a documented custom table, SleekAI can read availability and create the booking through the plugin's API. The bot collects signer email and document type, then writes a confirmed booking record. If the plugin only supports a hosted link, the bot can also drop the calendar URL into chat.

Conversations are stored in your own WordPress database in the SleekAI logs table. Nothing leaves your site except the prompt sent to whichever LLM provider key you brought (OpenAI, Anthropic, Google, or OpenRouter). You can configure log retention and you can redact the signer's date of birth or SSN before storage.

Tell the bot in its instruction which document types you don't notarize via RON (typical exclusions include wills, codicils, and recorded real estate in certain states) and it will detect those document types from the conversation and route the signer elsewhere. The instruction is the source of truth, so you don't fight the bot's training defaults.

The bot can verify that the signer understands the ID requirement and has acceptable identification on hand, but the actual KBA quiz and credential analysis happen in your RON platform (Notarize, Pavaso, or BlueNotary). The bot's job is to set expectations and refuse bookings where the signer cannot pass KBA, like signers without a US credit history when KBA is required.

Yes, your system instruction can list known agencies that have historically rejected RON (some county recorders, certain foreign consulates, some title companies) and the bot will warn the signer before booking. It will also recommend an apostille or hybrid in-person session if the receiving agency requires it.

SleekAI display conditions let you show the bot only on pages with a specific tag, custom post type, or URL pattern. So you can scope it to /online-notary/ and your services post type, and exclude blog posts and contact pages. You can also vary the system instruction by page so a healthcare POA page gets a more specific bot than the homepage.