Yes. SleekAI reads your erg-type info from any WordPress page or custom field and answers equipment questions accurately. Competitive rowers and CrossFit athletes care about which monitor you run and whether the drag factor matches what they train on at home. Storing the erg model as a single custom field on the homepage means the answer stays consistent everywhere.

It collects the cohort, contact details, and any injury or experience notes, then hands off via webhook to Mindbody, Mariana Tek, Wodify, or your booking tool. The bot does not write into the booking system directly. It captures the intent and lets the integration or front desk confirm the slot, which is the safer pattern for cohort-based scheduling.

Yes. You configure the system prompt to flag knee, back, hip, shoulder, and post-surgery mentions and route them to a 1:1 form check instead of group class. The bot will not prescribe rehab, will not interpret imaging, and will not give programming for an undiagnosed condition. That posture is locked in the prompt and tested on edge prompts before launch.

Yes. SleekAI reads your pricing page at runtime so whatever Foundations + unlimited starter, 2-row intro, or new-rower pass you are running this month flows into the chatbot automatically. Update the price on the page and the bot reflects it on the next conversation. No retraining.

If the targets are published on your site, yes. SleekAI reads any post or page content. Most rowing studios publish stroke-rate targets per class type (steady-state, power, race-pace) on a coaching page, and the bot quotes them when prospects ask what to expect. The bot will not coach individual technique, that is the coach's job at the erg.

Yes. SleekAI multibot supports separate chatbots per page, post type, or URL pattern. A typical setup is one bot on the public schedule and pricing pages for new rowers, and a second bot on the team programme page for athletes asking about race prep, ergometer testing, and Crash-B prep. Each can have its own prompt and tone.

Yes. SleekAI is bring-your-own-key, so you control costs and data. OpenAI, Anthropic, Google, and OpenRouter all work. Most independent rowing studios run on their own OpenAI key with a $20-30 monthly cap, which more than covers new-rower chat volume. The cost is your conversation volume, not a SaaS subscription.

Every conversation is logged inside WordPress with model name, token usage, and page URL. You can filter by date, page, or visitor, and export to CSV. Most rowing studios spot the recurring objections (form anxiety, post-injury hesitation, erg-type curiosity) within two weeks and refine either the Foundations page or the system prompt to address them.