WhatsApp support automation
Green API and Meta API workflows for private chats, customer groups, linked users, admin identities, and safe customer replies.
Feature system
Support automation features built for SMM panel operations.
Manage customer commands, WhatsApp and Telegram webhooks, ticket workflows, linked users, provider routes, templates, broadcasts, billing, and logs from one workspace.
Feature map
Customer command2274209 refill
ParsedPanel APIOwnership verified
SafeProvider routeexternal_id refill
SentLogsCommand result saved
Stored
Main bot features
Customer commands, ownership checks, and provider dispatch.
These features control the main customer-facing support automation flow.
Telegram support automation
Webhook-based Telegram support with automatic chat detection, linked users, provider groups, and workspace-level controls.
Ticket workflow automation
Ticket subject rules can trigger speed, cancel, refill, and details workflows while keeping platform support tickets separate.
Command parser
Detects speed, cancel, refill, balance, details, help, bulk IDs, aliases, and custom commands.
Order ownership checks
Uses panel API data to verify linked username ownership before sensitive order actions are processed.
External ID dispatch
Provider groups receive clean commands like external_id speed, external_id cancel, or external_id refill.
Automation logic
Rules that stop wrong requests before they reach providers.
The system checks order state, service rules, cooldowns, and route configuration first.
Provider route manager
Map provider domains, keys, aliases, WhatsApp groups, and Telegram groups with custom command templates.
Cooldown protection
Prevent repeated requests for the same order and action during the configured cooldown period.
Dedupe protection
Avoid duplicate processing of repeated webhook events using message keys and update identifiers.
Service rule engine
Use service-name parsing or cached service rules for start-time and refill eligibility decisions.
Refill logic
Check completed status, refill coverage, lifetime refill settings, refill windows, and service metadata before dispatch.
Speed logic
Check order status, remains, start timing, and cooldown before forwarding speed requests.
Workspace controls
Everything customers need to manage the bot.
Each workspace includes setup, routing, communication, logs, templates, and support tools.
Linked users
Link WhatsApp, Meta wa_id, Green API identifiers, and Telegram chat IDs to panel usernames.
Admin chats
Mark trusted WhatsApp, Meta, or Telegram identities as admin chats for controlled support-side operations.
Broadcasts
Send service notices, downtime alerts, and important announcements to linked users with plan-based medium control.
Response templates
Customize replies for success, failure, route missing, provider missing, help, verification, and custom commands.
Logs and history
Review webhook logs, outbound logs, conversations, command logs, dispatches, cooldowns, and ticket activity.
Runtime health
Monitor webhook status, connection validation, channel configuration, plan access, and runtime module state.
Security and safety
Designed to keep sensitive data and customer actions controlled.
The system separates tenants, avoids exposing technical errors to customers, and protects sensitive configuration data.
Protected settings
Sensitive API tokens, app secrets, bot tokens, and connection credentials are stored away from public pages.
Tenant isolation
Each workspace has separate settings, routes, linked users, commands, cooldowns, logs, subscriptions, and runtime state.
Safe replies
Technical errors are translated into customer-safe messages while full details remain available in logs.
Panel API verification
The system checks users, orders, services, and ticket data before provider dispatch.
Cron and webhook safety
Background processing is designed with dedupe and lock-style protection where supported.
Plan restrictions
Allowed mediums and modules are enforced in setup pages, routes, broadcasts, and runtime processing.
SaaS and business layer
Built for customers, subscriptions, plans, billing, and platform control.
The product is structured as a SaaS platform for multiple workspaces and support teams.
Billing and invoices
Customers can choose a plan, select panel type, submit payment reference, and wait for approval.
Subscription control
Plan status, expiry, active modules, and allowed mediums are managed per workspace.
Platform controls
Master admin can manage customers, plans, invoices, subscriptions, support queue, templates, and runtime health.
Panel backend support
The workspace supports panel adapter logic so customers can connect their preferred backend panel type.
Background automation
Runners handle ticket processing, broadcast dispatch, service cache refresh, and runtime maintenance.
Multi-tenant SaaS model
Designed for multiple customers, separate workspaces, individual billing, and controlled automation modules.
Command lifecycle
From customer message to provider route.
Customer sends command
Example: 2274209 refill or multiple IDs separated by commas.
Bot verifies order
Panel API fetches order details and checks linked username ownership.
Rules are checked
Status, start time, refill coverage, cooldown, external ID, and provider route are checked.
Provider receives ID
The provider group receives clean text like external_id refill.
Logs are saved
Command result, provider dispatch, cooldown, and customer reply are saved.
Configuration modes
Use quick parsing or advanced cached service rules.
Service name parsing
Read start-time and refill wording directly from service names for a faster launch.
- Fast setup
- Good for smaller catalogs
- No manual service cache required
- Depends on clean service naming
Cached service rules
Fetch services from panel API, cache service data, then define start-time and refill rules from the workspace.
- Better for larger panels
- More controlled refill logic
- Manual service-level decisions
- Cleaner long-term automation
Ready to launch
Turn repetitive support into a controlled workspace.
Start with one channel, map providers, link users, test the panel API, and enable advanced service rules when ready.