AI chatbot for Ortto: journey, message & contact answers
SleekAI's chatbot reads the Ortto plugin's tracking key and project settings stored in wp_options, plus the WordPress user and WooCommerce order data Ortto syncs from. Bring your own OpenAI, Anthropic, Google, or OpenRouter key.
♾️ Lifetime License available
A chatbot that fits inside your Ortto journeys
The Ortto plugin, still installed in many sites under the legacy autopilothq slug, stores the tracking pixel ID and project configuration under autopilot_settings in wp_options. It loads the Capture tracking script on the front end so journeys can fire from page views and form submissions. Customer identity comes from wp_users, and the order events Ortto reacts to live in wp_postmeta or the HPOS wp_wc_orders table.
SleekAI maps those plugin settings and your declared journey vocabulary into the prompt at request time. When a contact asks why they received a specific Ortto email or what a particular Capture event tracks, the bot can describe the journey by name, reference the underlying user action, and explain the trigger conditions without needing a private Ortto API call.
Generic chatbots have no idea which Ortto journey is live and what each one expects. SleekAI reads the real plugin configuration plus a small set of journey names you pass in, so the answer about a journey trigger or a Capture event lines up with what an Ortto admin would say in the dashboard.
Workflow
How SleekAI plugs into Ortto
Map plugin settings
autopilot_settings in wp_options plus the WordPress user and WooCommerce order data Ortto reacts to into named prompt variables. The bot reads the same context the journey did.
Declare your journeys
Scope where it runs
Tune over time
Try it now
A typical Ortto contact conversation
Comparison
Generic chatbot vs SleekAI for Ortto
Generic chatbot
- Doesn't recognise Ortto journey names or trigger conditions
- Has no view of the Capture tracking on the visitor's session
- Confuses journeys, campaigns, and broadcasts in its answers
- Can't reference the underlying user actions in WordPress
- Treats Ortto as a generic ESP rather than a journey platform
SleekAI chatbot
-
Reads Ortto plugin settings from
autopilot_settings - Maps WordPress user and order history into prompt variables
- Uses real journey names and trigger conditions you pass in
- Explains Capture pixel events in plain language
- Logs each Ortto question so you can tune the system prompt
Features
What SleekAI gives you for Ortto (formerly Autopilot)
Journey-aware
Pass in your active Ortto journey names and trigger logic. The bot answers about Webinar Nurture, Onboarding, or Product Tour Follow-up by name, with the right reasons for why each one fired.
Capture event vocabulary
Ortto's Capture pixel fires events from the page. The bot explains what each tracked event means in plain language, so a contact understands that visiting a pricing page twice put them on a sales nurture journey.
Handoff between journeys
Ortto contacts often move between journeys. The bot explains that a contact who finishes one journey is being handed off to another, with the timing and number of follow-ups they can expect.
Use cases
Where Ortto users put SleekAI to work
Journey explanations
Contact asks why they got a specific email. The bot reads the WordPress action that triggered the journey and explains the timing in their own words.
Webinar funnels
Help visitors register for a webinar tied to an Ortto journey, with accurate session times, room links, and what follow-up communication they'll see.
Contact preferences
Walk a contact through how to opt out of one journey without going off the global Ortto contact list, and which emails they'll still receive.
The bigger picture
Why Ortto users want context-aware AI
Ortto's value comes from the journeys it orchestrates, and journeys generate questions. A contact gets a follow-up email two days after a webinar registration and asks why. A prospect lands on a pricing page twice in a week and finds themselves on a nurture sequence they don't remember opting into.
A generic chatbot dropped on the marketing site has no idea what Ortto is doing in the background and will invent answers that contradict the email the contact is reading. SleekAI reads the Ortto plugin's configuration and a journey vocabulary you supply, so it explains the timing and the trigger of a real journey instead of pretending one exists. The Capture pixel does its work on the Ortto side, but the underlying action that fired the event lives in WordPress, and that's enough context for the bot to answer most contact questions without ever calling the Ortto API.
Combine that with display conditions that scope the bot to help and account pages, and a small marketing team can offload journey support without losing the trust that long marketing automation cycles depend on.
Questions
Common questions about SleekAI for Ortto (formerly Autopilot)
No. The bot only needs the plugin's WordPress-side metadata, plus the journey vocabulary you list in the system prompt. The Ortto private API key isn't exposed to the model. If you later want write actions like adding a contact to a journey from chat, wire it as a tool call against an Ortto-side endpoint you control.
It infers from a small set of journeys you define. If you give it the names of your top three to five customer-facing journeys plus their triggers, the bot can match a contact's described email to the most likely journey with high accuracy. That's enough to handle the bulk of inbound questions.
Capture events go to Ortto, not to your WordPress database, so the bot doesn't read them directly. It does read the WordPress action that caused the Capture event in the first place, like a form submission or a logged-in page view, and explains the journey trigger from that angle without inventing missing data.
Yes. The plugin slug on the WordPress.org repository is still autopilothq for many existing installs, and its option keys are stable. SleekAI reads the same configuration regardless of whether you migrated branding to Ortto or are still on an older Autopilot install.
Yes. Multibot mode runs several chatbots side by side with their own system prompts and display conditions. A common setup is a webinar bot scoped to webinar landing pages and a general support bot on My Account, each with a tighter journey vocabulary.
Yes. The public wrapper enforces per-IP rate limits and runs a guideline filter that blocks prompt-injection attempts and topic drift. The Ortto API key and other sensitive options are excluded from the variable map by default, so curious visitors can't coax credentials out of the model.
If you use Ortto SMS, you can pass the SMS journey names into the system prompt and the bot will answer questions about SMS opt-in, timing, and how to leave specific SMS journeys. The bot itself doesn't send SMS, since that stays with Ortto.
Yes. For logged-in admin users you can scope a separate marketer-focused bot that reveals trigger conditions and recent contact activity in plain language. It's a useful complement to the Ortto dashboard when you want a quick answer about why a specific contact is in a specific journey.
Pricing
More than 1000+
happy customers
Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.
Lifetime ♾️
Most popular
EUR
once
- Unlimited websites
- Lifetime updates
- Lifetime support
...or get the Bundle Deal
and save €250 🎁
The Bundle (unlimited sites)
Pay once, own it forever
Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.
What’s included
-
SleekAI
-
SleekByte
-
SleekMotion
-
SleekPixel
-
SleekRank
-
SleekView
€749
Continue to checkoutBrowse more
- Conversational Wishlist Building
- Warranty Claim Intake
- Policy Explainer Chatbot
- Privacy policy pages
- Address Change Chatbot
- Event RSVP Chatbot
- Donation Collection Chatbot
- testimonial pages
- Internal IT Helpdesk Chatbot
- Scholarship Eligibility Chatbot
- Recruiting
- Developer Pages
- Service Area Checker Chatbot
- Employee FAQ Chatbot
- Energy Audit Chatbot
- Carpet cleaning services
- Private investigators
- Lead generation agencies
- Lead Generation Services
- Ecommerce agencies
- Long-distance movers
- Airbnb cleaning services
- Consultants
- Downsizing Services
- Nail Salons
- HVAC Companies
- Wedding Photographers
- Resume writers
- Branding agencies
- Live Stream Production Services