Ladna
Current version 0.120.0

What's new in Ladna

0.120.0

Individual lessons in studio Telegram bots

  • Customers can now book individual lessons directly through a studio-owned Telegram bot by choosing the location, direction, service, trainer, room, date, and time. Studios that use trainer availability timeframes get the same room-after-time selection as the Ladna schedule.
  • The bot respects studio opening hours, trainer and room availability, existing customer bookings, and published events. It books exactly one participant, reserves a suitable class pass when available, clearly warns when no pass is found, and checks availability again before creating the booking.
Release commit.
0.119.0

Safer Telegram customer access

  • Linked customers can now open their customer cabinet from the studio bot without signing in again. The bot uses a short-lived, single-use link that stops working after it expires, is used, or the Telegram connection is revoked.
  • The booking-history button now reliably shows previous and cancelled classes.
  • Telegram message, update, and customer-notification histories now follow the same automatic retention period configured for the activity log.
Release commit.
0.118.0

Studio-owned Telegram self-service bots

  • Each studio can now connect its own BotFather bot for customer self-service. The bot follows fixed Ladna scenarios without AI, asks customers to share their own Telegram phone number, links an existing studio profile, or creates a new profile only after name and phone confirmation.
  • Customers can book and cancel group classes, view upcoming and previous bookings, class passes, attendance, studio information, and their customer cabinet in Ukrainian or English. Eligible reminders use the studio bot first and automatically fall back to SMS when Telegram is unavailable.
  • Studio owners and authorized staff have a restricted connection manager with customer links, message and notification delivery histories, webhook update logs, session restart and unlink controls, plus live webhook status, registration, deletion, pending-update, error, and last-activity details.
Release commit.
0.117.0

Clearer trainer access rights

  • The trainer editor now separates profile information and class scope from system access rights in two focused tabs.
  • Trainer rights are grouped by schedule and classes, customers and class passes, payments and finance, team and settings, and events and connected tools. Every right has a detailed explanation of what it allows, which separate rights may still be required, and why its access level matters.
  • The bilingual tabs and detail dialogs work on desktop and mobile, support keyboard navigation, and automatically reveal the section containing a validation error.
Release commit.
0.116.0

Simpler studio finances and cashbox control

  • Daily finance work is now split into clear Payments, Cashbox, Operating expenses, and Payroll periods pages. Financial, earnings, and rental reports live together in the Reports section, while delegated permissions keep payment entry, cashflow management, financial reporting, and payroll separate.
  • Each location cashbox now shows how much cash should be present. Owners can start accounting from a confirmed actual amount or reconcile a later count through guarded confirmations; only expenses paid from a cashbox reduce its balance, and refunds, corrections, reversals, deposits, and withdrawals remain visible as separate history.
  • New financial, earnings, rental, and immutable payroll-period reports avoid counting class-pass sales twice as earned revenue. Ladna AI and MCP access follow the same report, cashflow, and payroll permissions, and the owner help now explains the complete workflow with current screenshots.
Release commit.
0.115.1

Clearer SMS account reports and complete help

  • SMS account credit activity, top-ups, and recent SMS are now organized into three accessible tabs. Each report is independently paginated by 25 records and keeps the selected tab while browsing its pages.
  • The owner help now covers the complete Ladna SMS service: choosing an SMS source, tariff readiness, manual and automatic top-ups, segment charging, insufficient-credit and OTP behavior, warnings, debt, delivery statuses, and report interpretation.
Release commit.
0.115.0

Ladna SMS service and simpler messaging settings

  • Studios now have one clear SMS mode for number confirmation and customer alerts: Disabled, SMS by Ladna, or their own SMS gateway. Existing gateway credentials stay saved when switching modes, and the studio Telegram bot now has its own notification-settings tab.
  • SMS by Ladna adds a separate prepaid SMS account with the current per-segment price, balance, manual top-ups, an optional threshold-based auto top-up, and understandable explanations for longer Cyrillic messages. Availability and funding controls appear only after the platform configures the service and tariff price.
  • The unified SMS delivery log now covers both number-confirmation codes and customer notifications, showing delivery state, provider, segment count, snapshotted rate, final charge, and provider message ID without exposing confirmation-code text.
Release commit.
0.114.0

Sortable class-pass catalog

  • Studio owners can now reorder class passes independently inside each price segment using drag handles or accessible move buttons. Changes save automatically, and the current display order is visible directly in the catalog.
  • The All segments view groups passes into separate sortable sections, including passes without a segment. The same saved order is used consistently on public price pages, embeds, and the public price API.
Release commit.
0.113.0

Percentage-based trainer salary models

  • Salary models now include a sixth formula that pays a percentage of the class value calculated from class-pass session coverage and net direct payments. Free coverage remains valid, while missing values or currency mismatches are clearly marked as not calculated.
  • The salary model editor keeps one shared default rule and groups concrete class-format overrides into Group, Individual, and Rent tabs. Trainer reports show the class value, percentage, and complete calculation formula.
  • This is an early version of the salary-model framework. It already covers common studio scenarios and will continue to gain more calculation options from founder feedback.
Release commit.
0.112.0

Shorter public class-pass price pages

  • Public class-pass price pages now use two tab levels: Group, Individual, and Rent first, followed by the studio-configured price segments for the selected category.
  • On mobile, clients see one focused category and segment at a time instead of one long combined list. The pass details and visible Buy actions stay unchanged.
Release commit.
0.111.0

Manual full and partial payment refunds

  • Authorized studio staff can now record a full or partial refund from any completed customer payment. The refund can be marked as cash or cashless, requires a reason, and is confirmed with the exact amount and method without initiating a bank or payment-provider transfer.
  • Every refund remains a separate audited row linked to the original payment. Multiple partial refunds cannot exceed the paid amount, payment totals show gross income, refunds, and net income separately, and a cash refund withdraws the amount from the selected location cashbox.
  • Refunds for class-pass payments recalculate the paid amount without cancelling the pass or its bookings. If the source payment already has a successful Checkbox receipt, Ladna also requests a matching return receipt; a receipt error is visible and retryable without undoing the recorded refund.
Release commit.
0.110.0

Studio notification delivery logs

  • Studio owners and authorized staff now have a dedicated Logs section that keeps the existing Activity log together with paginated Customer SMS and Trainer Telegram delivery histories.
  • Each notification log is restricted to the current studio and supports search plus delivery-status and notification-type filters. Owners can review the message, recipient, scheduled or delivered time, provider details, retry count, and delivery error without entering platform administration.
  • Trainer Telegram history includes only trainer alerts for the studio; platform, founder, and studio-owner announcements remain outside this tenant view.
Release commit.
0.109.0

Configurable safeguards and transparent usage for Ladna AI

  • Ladna AI now shares configurable user and studio usage limits across the dashboard and Telegram, including separate platform-admin allowances, paid-provider budgets, and a clear busy state that never spends another provider request.
  • Repeated requests outside the Ladna studio domain now lead to progressive automatic pauses with a specific explanation and unblock time. Valid Ladna answers clear the pending sequence, while provider failures, clarification requests, and limits do not count against the user.
  • Platform administrators have a dedicated AI limits and usage page with safe request and token statistics, provider, model, channel, status, studio, user, and period filters, active restriction details, and audited reset controls without exposing prompts, responses, phone numbers, or Telegram payloads.
Release commit.
0.108.0

A richer demo and real Ladna AI examples

  • The read-only demo studio now includes team-only closed classes plus five synthetic events that demonstrate paid and free registration, cancellation and refund attention, drafts, 2027 ticket sales, QR admission, and check-in history.
  • The Abilities page now explains the complete events workflow and the Ladna AI assistant in dedicated sections. Six genuine Ukrainian and English demo conversations show event analysis, customer and class-pass investigation, and screenshot recognition verified against Ladna data.
  • The main landing page now introduces the AI assistant directly. The wording remains explicit that an AI provider must be enabled and that any action which changes studio data requires the user’s confirmation.
Release commit.
0.107.0

Audited trial-pass exceptions

  • Authorized studio staff can now issue an otherwise ineligible trial class pass as an explicit exception when the customer has never had a class pass and has no successful payment history. A reason is required and permanently recorded with the issuer in the pass history.
  • The ordinary trial rule remains unchanged: online trial purchases cannot use the exception, regular class passes are unaffected, and any previous class pass or successful customer payment blocks the exception.
  • Ladna AI investigations now show ordinary trial eligibility and manual-exception availability separately, so an exception is always described as a human decision rather than normal eligibility.
Release commit.
0.106.0

Deterministic trial-pass investigations in Ladna AI

  • Studio owners can now ask Ladna AI in the dashboard or Telegram whether a named customer qualified for a trial or first-visit class pass at a specific moment. Ladna checks the customer’s complete booking history instead of relying on the visible timeline window.
  • The answer uses the same rule as real pass issuance: online purchase requires zero existing bookings, while manual issuance also permits one uncovered booking. Cancelled, attended, and future bookings all count, and the evidence includes prior attendance, current trial-plan price, pass payment state, and available payment chronology for staff with cashflow access.
  • External MCP investigations now accept an as-of timestamp and manual or online source, return structured eligibility and bounded evidence, and explicitly distinguish a provable rejection reason from unaudited failed clicks or actors.
Release commit.
0.105.0

Payment and event insights for Ladna AI

  • Studio owners and delegated staff can now ask Ladna AI for read-only payment overviews and bounded payment searches. Results group income, expenses, owner withdrawals, cash balances, and payment states by currency while masking customer contacts.
  • Ladna AI and external MCP automations can now summarize event lifecycle, capacity, ticket inventory, check-ins, revenue, and refund requirements without exposing buyer contacts.
  • MCP token abilities now follow the studio permission model when tokens are created or their secrets are managed. Sensitive abilities require the matching delegated permission, while authorized settings managers can still revoke a token.
Release commit.
0.104.0

Ladna AI understands images

  • Studio owners can now send a screenshot or photo to Ladna AI in the admin chat or Telegram. Ladna reads the visible interface, names, class-pass codes, dates, statuses, and other supported details, then answers questions about the image.
  • The conversation can continue after the image: Ladna remembers its details, can compare them with available studio data, and clearly separates what is visible in the image from what was verified in Ladna.
  • Answers now stay in the language of the current request even after topic and language changes, while misspelled help questions and detailed customer or class-pass investigations continue to use the available Ladna evidence.
Release commit.
0.102.0

Paid events with QR admission

  • Studios can now publish one-time events with a polished public page, studio-room or external venues, event-only ticket types, early-bird pricing, capacity controls, and paid or free guest checkout without creating customer records.
  • Every admission receives a secure QR ticket by email and on a private guest order page. Managers can review sales and refunds, while authorized door staff use an online mobile scanner and searchable door list with duplicate detection and an immutable check-in/check-out history.
  • Published studio events reserve only their selected rooms across class generation, manual scheduling, booking, rental, and restoration flows. Event payments reuse the configured Monopay, LiqPay, or WayForPay integration and are included in payment totals and fiscalization.
Release commit.
0.101.1

Safer and more reliable frontend updates

  • Ladna browser assets are now delivered in smaller, separately cached bundles so updated screens load reliably while repeat visits can reuse unchanged interface resources.
  • Frontend build dependencies received the latest security fixes.
Release commit.