Yes. Configure which states you are commissioned for and which RON platforms you use (Notarize, NotaryCam, OneNotary, BlueNotary, or your state's approved platform). The bot surfaces the right answer based on the signer's state, declines politely for states or document types where RON is not allowed, and routes to in-person if RON is unavailable. Signers rarely know the rules - the bot does.

Yes. Add your travel zones with mileage caps and surcharges - typically a base fee plus mileage tiers, with weekend or after-hours bumps - and the bot quotes from those tiers based on the destination ZIP. For practices that operate across multiple metros, you can configure separate zone structures per region and the bot picks the right one based on the appointment location.

Yes, and this is one of the most underrated pieces of value. The system prompt instructs the bot to confirm ID status (valid government-issued, unexpired) and remind signers to bring acceptable identification before the appointment. Missing or expired ID is the single most common cause of failed signings; the bot catches it upfront so the signing actually happens when the notary shows up.

Not directly. SleekAI captures the conversation in WordPress and you forward signing details to whichever platform you use - Snapdocs for loan signings, NotaryGadget for record-keeping, or your own spreadsheet. Most mobile notaries use a webhook to push the booking summary into their preferred tool so the chatbot intake flows into the same record system as the rest of the practice.

Yes. GPT-4o and Claude both handle Spanish natively, and many notaries run a bilingual bot to capture Spanish-speaking signers who prefer to discuss the appointment in Spanish even when they are comfortable signing in English. The bot detects the signer's language from the first message and responds in the same language. For markets with significant Mandarin, Vietnamese, or Tagalog speakers, the same multilingual capability extends naturally.

Yes. Multibot lets you run a loan-signing bot on your loan-signing pages and an apostille bot on apostille pages, each with its own intake flow - apostilles ask about the destination country and document type, loan signings ask about the lender and package format. The two flows are different enough that splitting them is cleaner than running one general-purpose bot.

Yes. The bot asks whether the lender has sent the package and whether the signer has a printer, and quotes the print/scan surcharge if needed. For loan signings, the print question is the second-most-common cause of failed appointments after ID issues, so the bot is configured to surface it explicitly during booking and again in the confirmation message the day before. That single check saves a meaningful percentage of weekend signings.

It uses your commission state(s) as the canonical list and declines politely for states where you are not commissioned. For practices that operate near a state line and serve clients on both sides, you can configure multiple commissions and the bot routes by the appointment location's state. RON adds another wrinkle - some states allow RON for in-state signers regardless of where the notary is, others do not - and the bot reads from your configured platform list to answer correctly.