Supercharge Contact Form 7 with instant Telegram & Bale notifications, per-form message templates, smart automation rules, and a full submission management dashboard.
CF7 Booster adds a native 🚀 CF7 Booster tab directly inside every Contact Form 7 form editor. From there you enable Telegram and Bale notifications for that specific form, write its own message template using real field placeholders, and point it to any chat ID or channel - all without leaving the CF7 editor. A global bot token is configured once. Everything else is per-form. An automation engine lets you write rules that route submissions by form, field name pattern, or field value using AND/OR logic with 13 operators including regex. Every delivery attempt is logged, retried automatically on failure, and visible in a management dashboard with CSV export.
Go to CF7 Booster → Telegram (or Bale) in the WordPress admin menu. Enter your bot token from @BotFather and optionally set default destination chat IDs. This is a one-time global configuration.
Every Contact Form 7 form editor now has a new CF7 Booster tab. Open it to enable Telegram and/or Bale for that form, enter the destination chat IDs or @channels specific to this form, and write a custom message template.
Click any placeholder chip to insert it into the template at the cursor position. Use {name}, {email}, {phone}, {message} as universal aliases. Use {radio} or {checkbox} to capture any radio/checkbox field regardless of its auto-generated ID. Use {all_fields} to automatically list every field and its value.
Go to CF7 Booster → Automation to build condition-based routing rules. Example: IF field name contains 'radio' AND value contains 'sale' THEN send to the Sales Telegram channel. Combine multiple conditions with AND/OR logic and send to multiple destinations from a single rule.
When a visitor submits any form, CF7 Booster intercepts the submission, stores it in the database, and dispatches notifications in the background via WP-Cron. Failed deliveries are retried automatically. View all submissions, filter, search, export to CSV, or manually resend from the Submissions dashboard.
A native 🚀 CF7 Booster tab appears inside every CF7 form editor. Enable Telegram/Bale, set destinations, and write a custom message template - all without leaving the CF7 editor. Settings are saved independently per form.
Send formatted notifications to any Telegram bot chat, channel, or group. Supports multiple destinations simultaneously. Bot token is configured once globally; destinations can be overridden per form.
Full support for Bale Messenger with independent bot configuration, destinations, and message templates. Same architecture as Telegram - completely separate settings and delivery logs.
Use {name}, {email}, {phone}, {message} as universal aliases. Use {radio}, {checkbox}, {select} to capture field values by type - works across all forms regardless of auto-generated IDs like radio-289. Use {all_fields} to dump every field automatically.
The message template editor shows chips for every system placeholder AND every actual field in that specific form. Click a chip to insert it at the cursor. No need to remember field names.
Build condition-based routing rules with AND/OR logic. Match by form, exact field name, or field name pattern (e.g. name contains 'radio'). 13 operators: equals, contains, starts with, ends with, regex, greater/less than, empty, not empty, and more.
Each automation rule can send to multiple channels and destinations simultaneously. Each destination in a rule can have its own custom message template override.
Every form submission is stored in a custom database table with form ID, field values, IP address, user agent, referrer, and delivery status. Data is never lost even if notification delivery fails.
Overview of total, today, weekly submissions and delivery success rates. Searchable, filterable submissions table with status badges, field preview, and one-click resend.
Export all submissions or filtered results to CSV with a single click directly from the submissions table.
Notifications are dispatched in the background via WP-Cron so form submissions return instantly to visitors. Failed deliveries are retried automatically with configurable intervals and maximum attempt counts.
Full per-channel delivery log with INFO, WARNING, and ERROR levels. Filter by channel or level. Sensitive fields (phone, email) are optionally masked in logs while full data is preserved in submissions.
Ships with complete Persian (fa_IR) and Arabic (ar) translations compiled and ready to use. A .pot template is included for any other language. All UI is RTL-compatible.
Nonce verification on all forms and AJAX endpoints, capability checks (manage_options), input sanitization on every field, and output escaping throughout. Bot tokens are never exposed in the frontend.
Uses WordPress-native functions exclusively: wp_remote_post for API calls, wp_schedule_single_event for the queue, and standard wpdb for storage. No Composer packages, no external SDKs.
Yes. CF7 Booster is an add-on for Contact Form 7. CF7 must be installed and active. The plugin will show an admin notice and will not boot if CF7 is not detected.
Open Telegram and search for @BotFather. Send /newbot, follow the instructions, and copy the token it gives you. Paste it into CF7 Booster → Telegram → Bot Token. Then add your bot to the target channel or group as an administrator, and use that channel's chat ID as the destination.
Forward any message from your channel or group to @userinfobot on Telegram - it will reply with the chat ID. Channel IDs are negative numbers starting with -100 (e.g. -100198234710). You can also use @username format for public channels (e.g. @mysaleschannel).
Async (recommended): after the visitor submits the form, WordPress immediately shows the success message. The notification is sent a few seconds later in the background via WP-Cron. The visitor never waits for the API call. Sync: the Telegram/Bale API call happens during the form submission itself. If the API is slow or unreachable, the visitor's browser waits. Use Sync only if WP-Cron is disabled on your server.
Contact Form 7 appends a unique number to field names (radio-289, radio-389) that changes per form. CF7 Booster solves this with base-type aliases: use {radio} to get the value of the first radio field on any form, or use {all_fields} to automatically include every field regardless of its name. For exact control, click the field chip in the per-form template editor - it shows the actual field name for that specific form.
Yes. In the per-form CF7 Booster tab, list multiple chat IDs (one per line) for Telegram and/or Bale. In Automation Rules, each rule can have unlimited action rows, each pointing to a different channel and destination with an optional custom template per destination.
The delivery is logged as failed and automatically retried. The number of retries and the interval between them are configurable in CF7 Booster → Settings. Default is 3 retries at 90-second intervals. If all retries are exhausted the submission is marked Failed and you can manually resend it from the Submissions table.
Yes. Every submission is stored in the database immediately when the form is submitted, before any delivery attempt. The stored submission includes all field values, IP address, user agent, and referrer. You never lose a lead due to an API failure.
No. CF7 Booster is built specifically for Contact Form 7 and hooks into CF7's native submission pipeline (wpcf7_mail_sent). It will not work with WPForms, Gravity Forms, or other form plugins.
Yes. A complete Persian (fa_IR) translation is included and compiled (.po and .mo files). Set your WordPress site language to Persian in Settings → General and the entire plugin admin interface will display in Persian automatically. An Arabic (ar) translation is also included.
The languages/ folder contains cf7-booster.pot - the master translation template with all strings. Open it in Poedit (free at poedit.net), translate all strings, and save as cf7-booster-{locale}.po (e.g. cf7-booster-de_DE.po for German). Poedit automatically generates the .mo binary file. Place both files in the languages/ folder and set your WordPress site language accordingly.
Yes. The admin UI is fully RTL-compatible and uses WordPress core RTL stylesheets. Both included translations (Persian and Arabic) are right-to-left languages and have been tested in RTL mode.
The plugin stores IP addresses, user agents, and form field values in the database. Sensitive fields (phone numbers and email addresses) can be masked in the Logs view via the Mask Sensitive Data setting. For full GDPR compliance you should document this data collection in your privacy policy and configure data retention according to your local requirements.
Exactly what CF7 was missing
We needed instant Telegram notifications for multiple forms routing to different team channels. CF7 Booster solved it completely - per-form templates, multiple destinations, automation rules, and a clean submission log. The placeholder chip system for the message editor is a genuinely nice touch.
wpcf7_mail_sentwpcf7_before_send_mailwpcf7_mail_failedwpcf7_save_contact_formwpcf7_editor_panelsadmin_menuadmin_enqueue_scriptscf7on_process_queuecf7on_retry_deliverywp_ajax_cf7on_save_telegramwp_ajax_cf7on_save_balewp_ajax_cf7on_save_settingswp_ajax_cf7on_save_ruleswp_ajax_cf7on_save_form_settingswp_ajax_cf7on_test_telegramwp_ajax_cf7on_test_balewp_ajax_cf7on_resendwp_ajax_cf7on_export_csvTelegram Bot API - sendMessage (https://core.telegram.org/bots/api)Bale Messenger Bot API - sendMessage (https://tapi.bale.ai)WordPress wp_remote_post - HTTP delivery layerWordPress wp_schedule_single_event - async queue via WP-CronWordPress wpdb - custom tables for submissions, deliveries, and logsAll notification delivery runs asynchronously via WP-Cron after the form submission response is returned to the visitor. No API calls are made during the HTTP request/response cycle in the default async mode. Database writes are minimal: one INSERT per submission, one per delivery attempt. Logging can be disabled on high-traffic sites to further reduce writes.
Community Reviews & Questions (2)