Free tools

Free Tools

Small utilities that do one job. No signup, no email gate, no limits - everything runs in your browser. When a tool tells you something is wrong, the error code directory and the platform limits reference explain why.

10tools
0signups required
100%browser-only

WhatsApp Template Checker

Paste a WhatsApp Business message template and find out why Meta will reject it - before you submit it for review.

WhatsAppOpen tool

WhatsApp QR Code Generator

Turn your number into a scannable click-to-chat QR code with a pre-filled message. Print-resolution PNG, drawn in your browser.

WhatsAppOpen tool

WhatsApp Link Generator

Build a wa.me click-to-chat link with an optional pre-filled message. Runs in your browser - nothing is stored.

WhatsAppOpen tool

WhatsApp API Cost Calculator

Estimate monthly and annual WhatsApp Business API costs by recipient country and template category, with editable Meta rates.

WhatsAppOpen tool

Telegram Link Generator

Build t.me links for bots and channels, including start payloads that tell your bot where the user came from.

TelegramOpen tool

Telegram Bot Token Checker

Validate a bot token, call getMe and getWebhookInfo from your browser, and get a plain-English read on webhook and privacy-mode problems.

TelegramOpen tool

Messenger Link Generator

Build m.me click-to-Messenger links with a ref parameter your bot receives as campaign attribution.

MessengerOpen tool

Chatbot Cost Calculator

Work out what a chatbot costs and saves at your ticket volume. No email wall - the formula and every benchmark are on the page.

ChatbotOpen tool

UTM Campaign Builder

Build tagged campaign URLs, and see why UTM parameters never survive the jump into a chat thread.

AnalyticsOpen tool

Chatbot Name Generator

Generate bot names by tone and industry, plus what to weigh before naming a bot after a person.

NamingOpen tool

Which tool do I need?

The tools split along one question: are you trying to start conversations, send into them, or measure them? The three link generators start conversations - each builds the deep link its platform actually documents, with the platform's own attribution parameter where one exists. The WhatsApp pair in the middle of the table deals with sending at scale, where Meta's template review and per-message billing decide what reaches anyone and what it costs. The last group is diagnosis and housekeeping: a silent Telegram bot, an untagged campaign, an unnamed bot. Every tool runs entirely in your browser, and each one pairs with a reference page that explains the rules the tool is applying.

You want to...UsePairs with
Let customers open a WhatsApp chat from a bio, ad or QRWhatsApp link generatorWhatsApp limits
Get a message template past Meta review first timeTemplate checkerWhy templates get rejected
Budget WhatsApp sending by market and categoryAPI cost calculatorOctober 2026 billing changes
Carry a campaign tag into a Telegram botTelegram link generatorWebhook
Attribute Messenger conversations to an ad or QR codeMessenger link generatorMessenger + Facebook ads
Work out why a Telegram bot is silentBot token checkerTelegram bot not responding
Tag ads and landing pages so GA4 sees the campaignUTM campaign builderChatbot analytics metrics
Name the bot before it goes liveChatbot name generatorChatbot persona

Looking for the ROI calculators? They were retired on 19 August 2026 - nobody searched for them, and their estimates were not something we could stand behind. The WhatsApp API cost calculator uses published rates instead, and the free plan lets you measure your own results.

What these tools are for, and what they are not

Every one of these does a single job that is otherwise a twenty-minute detour through documentation. None of them requires an account, none stores what you type, and each runs in the browser tab rather than on our servers - which is the only honest way to handle a bot token or a customer's phone number.

What they are not is a substitute for reading the platform rules. A link generator cannot tell you that a WhatsApp template will be rejected for its category, and a cost calculator cannot tell you that Meta is changing service-message billing on 1 October 2026. Each tool therefore points at the reference page behind it, and those pages are where the actual rules live.

The mistakes these tools exist to catch

Each tool was built after watching the same avoidable failure happen repeatedly. The failures are worth knowing even if you never open the tool.

A phone number written the way humans write it. wa.me links need the full international number with no plus sign, no spaces, no brackets and no leading zero. A number that looks correct to you produces a “phone number shared via url is invalid” error for everyone outside your country. The link generator strips the formatting as you type.

A template rejected for its category, not its wording. Every source that studies Meta rejections puts category misclassification at the top - a marketing message submitted as utility. Rewriting the copy will not fix it. The template checker runs 28 of Meta's rules before you spend a review cycle finding out.

A bot that is silent because two processes are listening. A webhook and a polling process cannot both consume the same Telegram bot. The symptom is a 409 conflict and a bot that answers intermittently or not at all; the token checker calls getMe and getWebhookInfo and tells you which. If the queue is climbing, pending_update_count explains what the number means.

A campaign that arrives untagged. UTM parameters do not survive the jump into a chat thread - the click opens WhatsApp, and the query string stays behind in the browser. Attribution has to move into the message itself, which is what the campaign builder and the platform ref parameters are for.

A budget built on the wrong unit. Since July 2025 Meta bills WhatsApp per message rather than per 24-hour conversation, and rates follow the recipient's country and the template category. Modelling your own mix in the cost calculator is the only way to a number that survives contact with a real send.

Where each platform breaks, and what to read

WhatsApp fails at two points: template review before you send, and per-message cost once you do. Both are Meta's rules rather than your platform's, so they apply identically whichever provider you use. The WhatsApp error codes list the literal API responses with fixes, and WhatsApp limits covers messaging windows and throughput tiers. If you are still deciding whether the API costs anything at all, is the WhatsApp API free answers it without the vendor spin.

Telegram is the friendliest of the three to build on and the least forgiving about webhooks. Almost every “my bot stopped working” report traces to a webhook that returns the wrong status, a certificate Telegram will not accept, or a second consumer. The Telegram error codes and bot not responding guide cover the causes in the order they actually occur.

Messenger is constrained less by errors than by Meta's 24-hour messaging window and message tags, which decide what you may send and when. The Instagram and Messenger error codes and Messenger setup guide are the two pages worth having open.

Across all three, the deep links these tools build are only the entry point. What happens after someone taps is a conversation you have to design - which is what the template library exists for, and why the free plan is a plan rather than a trial: you can wire the link to a real flow and watch what people do with it before paying anyone.

Reference

Free tools FAQ

Are these tools really free, with no signup?

Yes. None of them asks for an email, an account or a card, and none has a usage limit. They run as JavaScript in your browser tab, so what you type - a phone number, a bot token, a message template - is processed on your own machine and never reaches our servers. That is a deliberate design constraint rather than a policy promise: a tool that has to send your bot token somewhere to validate it is a tool you should not use.

Is it safe to paste my Telegram bot token into the token checker?

The check runs entirely in your browser: it calls api.telegram.org directly from the page, so the token goes from you to Telegram and nowhere else. Nothing is logged and nothing is stored. That said, the correct instinct is caution - a bot token is a password. If you have pasted one into any tool you are unsure about, revoke it with /revoke in BotFather and issue a new one.

Why does my WhatsApp link work for me but not for customers abroad?

Almost always the number format. A wa.me link needs the full international number with the country code, no plus sign, no spaces, no brackets and no leading zero - so a UK number written 07700 900123 has to become 447700900123. It works for you because your phone fills in your own country code; it fails for everyone else because theirs does not. The link generator strips the formatting as you type.

Which tool should I use to work out what WhatsApp will cost?

The WhatsApp API cost calculator, because Meta bills per message and the rate depends on the recipient's country and the template category. A single blended figure will be wrong for any real audience. If you also want to know what Meta charges nothing for, the free WhatsApp API guide covers what is genuinely free and what changes on 1 October 2026 when service messages become billable.

Why did my message template get rejected when the wording looks fine?

The most common cause is not the wording at all - it is the category. A promotional message submitted as Utility gets rejected regardless of how it is written, and rewriting the copy will not help. Other frequent causes are a variable placed at the very start or end of the body, two placeholders with no text between them, and formatting that is invalid in a template. The template checker runs 28 of these rules before you spend a review cycle.

Do UTM parameters work for WhatsApp and Messenger campaigns?

Not through the click itself. A UTM-tagged link to wa.me opens WhatsApp, and the query string stays behind in the browser - the conversation arrives with no campaign attached. Attribution has to move into the message or the platform's own parameter instead: WhatsApp uses the pre-filled message text, Messenger has a ref parameter, and Telegram has a start payload. The campaign builder produces both halves so the analytics link and the chat link agree.

Can I use these tools with a chatbot platform other than Conferbot?

Yes. Everything here operates on the platforms' own formats - wa.me and t.me links, m.me ref parameters, Meta's template rules, Telegram's getMe and getWebhookInfo responses. None of it is specific to our product, and the reference pages behind each tool document the platform rule rather than our implementation. We built them because our own users kept hitting these problems, not to gate anything.

Turn These Links Into a Working Chatbot

Free plan, no credit card required.