@@structuredData
Right message. Right time. Right channel. KriyaX keeps members and teams in sync with in-app notifications, WhatsApp, and email summaries across every module—so nothing slips.
Multi-channel communications that drive timely actions—renew, attend, pay, engage.
Automated nudges for expiring packages with smart follow-ups and payment links.
Class reminders, waitlist pings, and geofenced check-in prompts at the right time.
Dues reminders, one-tap pay links, aging escalations, and payment confirmations.
Daily/weekly email digests for owners & managers: KPIs, risks, and next best actions.
Event-driven alerts with smart routing and measurable outcomes.
Triggers from every module—renewals, dues, low attendance, no-shows, AMC due, stock low.
Score by impact & urgency (e.g., high-value members, aging invoices, class capacity).
Choose channel per user preference & cost—In-app, WhatsApp, Email (fallback & escalation).
Auto-retries, quiet hours, and branch-aware routing to managers when needed.
Track opens, clicks, attendance, payments—optimize templates and timing.
End-to-end alerts for Members, Classes, Finance, Ops, and Teams.
Renewals due, churn risk, birthdays/anniversaries, visit-frequency nudges, upsell suggestions.
Class reminders, no-show recovery, top/bottom classes, instructor schedule changes, waitlist pings.
Payment due/overdue, partial payments, refunds/credit notes, reconciliations, tax filings windows.
AMC & warranty expiries, ticket SLAs, stock low, geo-fenced attendance compliance.
Lead follow-ups due, SLA breaches, campaign ROAS updates, online vs offline performance.
Quiet hours, opt-in/opt-out, frequency caps, templates with personalization tokens, multi-language.
Track how communication moves the needle. (Illustrative figures.)
On-time Renewals
With renewal playbooks
Message Response Rate
Across WhatsApp + In-app
No-Shows
With reminder + fallback
Collections Cycle
Dues reminders + links
Everything about channels, controls, and delivery.
In-app notifications, WhatsApp (via your connected provider/BSP), and email. You can enable one or all and set priority & fallback per audience.
Use quiet hours, frequency caps, deduplication, and contact-policy rules. Members can opt-in/out per channel; staff alerts route branch-wise.
Yes—use tokens like {{member_name}}, {{branch_name}}, {{class_time}}, {{due_amount}} and multi-language templates per audience.
Channel costs (e.g., WhatsApp) are visible in reports; we track delivery, reads, clicks, and downstream actions like check-ins and payments.
Absolutely—branch-aware playbooks, manager escalations, and region/city filters for digests keep multi-location teams coordinated.
From renewals to no-shows to AMC—KriyaX keeps everyone informed and on track.