WordPress plugin · Hamranik TelePress
Hamranik TelePress — Messenger-to-WordPress publishing
Open the demo inbox, convert a queued messenger row into a local draft, then sign in as viewer to see convert locked. Live Telegram/Bale/Rubika webhooks are not connected. Order alerts belong to NotifyHub.
Introduction
Why publishing only from wp-admin slows teams down
Content and store teams often work in Telegram/Bale but still re-enter everything in wp-admin. TelePress connects bots, links users, and enables allowed actions for posts and products.
The public demo seeds a messenger inbox and writes local drafts. Tokens and live webhooks are connected after consultation.
Publishing content is TelePress; order notifications belong to NotifyHub.
Problem
Double publishing means more errors
When drafts live in chat and publishing lives in admin, versions drift and bot permissions stay unclear.
Without roles and capabilities, accidental publishes and over-broad access become likely.
- Repeated work across messenger and wp-admin
- No per-action bot controls
- Weak Chat ID ↔ WP user linking
- Messy product gallery/price publishing
- Multiple messengers without one settings model
Solution
How TelePress structures publishing
In the demo you open the inbox, convert a Telegram/Bale/Rubika row to a draft, and see that the viewer cannot. After consultation, real tokens and webhooks are wired for production.
Telegram, Bale and Rubika in one plugin.
- Bot and action management
- Chat ID to WP user linking
- Post and product publishing
- Product gallery and price flows
- Multi-messenger settings tabs
Capabilities
Hamranik TelePress capabilities
From bot connection to controlled publishing.
Multi-messenger
Telegram, Bale and Rubika in dedicated settings tabs.
Bot action controls
Toggle post, product, gallery, prices and more per bot.
User linking
Map Chat IDs to WordPress users or approve /link requests.
Role-aware menus
Wizard steps respect WP / WooCommerce / Dokan capabilities.
Product gallery
First image featured; remaining images in the Woo gallery.
Dokan-aware
Products can be authored as the linked seller.
Honest demo mode
Public demo is clearly display-only without a live webhook.
Hamranik UI
Aligned with the rest of the plugin family.
How it works
From queued message to draft
A ten-minute demo path; live tokens are a separate deployment step.
Inbox
Read a seeded Telegram, Bale or Rubika row labeled queued (demo).
Convert
The publisher turns it into a post or product draft; the viewer cannot.
Permissions
Open bot management and see which actions this role may run.
Review
Open the WordPress draft. Nothing is sent to a live messenger.
Best fit
A good fit for
If messenger publishing is part of daily operations.
- WooCommerce stores with messenger-based content teams
- Dokan marketplaces
- Brands using Iranian messengers
- Teams that need per-action bot control
Not a fit
Not the right fit for
If you only need order notifications, see NotifyHub.
- A full social media suite replacement
- Order notification hub (NotifyHub)
- Sites not on WordPress
Differentiation
Why teams choose it
Messenger publishing for the Iranian market with role control.
Three messengers, one plugin
Telegram + Bale + Rubika.
Action control
Each bot only performs allowed work.
Transparent demo
Display mode without fake live-webhook promises.
Hamranik family
Shared consultation path and UI language.
Pricing
Annual license
Annual license
$22 / year
An annual license covers standard deployment and minor updates. Deep integrations, custom training and bespoke work are scoped separately.
Related services
When you need deeper customization
From the blog
Read more about this domain
FAQ
FAQ about Hamranik TelePress
Does the demo use a live webhook?
No. The inbox shows queued rows and convert writes a local WordPress draft. Live tokens and webhooks are connected after consultation.
Which messengers are supported?
Telegram, Bale and Rubika via multi-tab settings.
Does it work with Dokan?
Yes — products can be authored as the linked seller.
How is this different from NotifyHub?
TelePress publishes content/products; NotifyHub notifies on store events. An optional bridge is possible, not a hard dependency.
Software environment
Hamranik TelePress in practice
Version history
-
Version 0.4.3
- WordPress.org Plugin Check hardening: translator comments, input sanitization, Tested up to WordPress 7.0
- About screen reworded as author credit without a premium upsell
-
Version 0.4.2
- Admin section headers now show the product name and a short capability list instead of the Hamranik logo
- Dismissible About page keeps the Hamranik credit, logo, and website CTA
-
Version 0.4.1
- Alpine.js unminified source shipped beside alpine.min.js; standard gettext .po/.mo
- Admin Hamranik credit limited to the dismissible About screen
- Removed TelePress Pro upgrade card from the dashboard
-
Version 0.4.0
- No fake Telegram/Bale/Rubika seeding on activate
- Optional Load sample data button; default off
- wordpress.org readme, GPL license, dismissible About credit
-
Version 0.3.4
- Demo messenger inbox with convert-to-draft for posts and products
- Viewer role that can read the inbox but cannot convert
- Clear split from NotifyHub; no live webhook claimed
-
Version 0.3.3
- 12-locale demo sync
- Bot management polish
- Final package prep
-
Version 0.3.0
- Bot actions and Chat ID linking
- Woo product gallery
- Dokan support
-
Version 0.2.0
- Telegram/Bale/Rubika tabs
- Role-aware wizard
-
Version 0.1.0
- Basic post publishing from bot
Convert a queued message in the demo
Publisher and viewer roles, a seeded inbox, and local drafts — no live webhook. Deployment scope is set in consultation.