One simple price
The €14 plan includes 25,000 transactional chat messages a month. That is enough for most contact forms, codes, and alerts.
Turn WhatsApp into your website inbox.
- Use cases
- Auth, forms, bookings
- Included
- 25k transactional messages
- Fallback
- €5 SMS fallback credit
send via .chat
online
Today
Thanks, I am in.
15:55
✓✓
Message
Why teams switch to send via .chat
- Instant delivery
- ~98% read rate
- Included chat message allowance
- EU hosted
- Setup in 5 minutes
How a message travels
Messages arrive where your customers already answer.
Connect your WhatsApp or Telegram account and keep auth delivery covered with SMS fallback when chat delivery is unavailable.
Your app
send via .chat
scope · render · log
Your device
WhatsApp / Telegram
Delivered
What you get
Your device. Your delivery rules.
send via .chat sends through the WhatsApp or Telegram account you connect, so you stay in control of the channel, the recipients, fallback, and the delivery history.
Delivered in seconds
Messages leave from your own device. Most codes arrive before the user has time to switch apps.
Setup in 5 minutes
Scan a WhatsApp QR code or sign in to Telegram. Create an API key. Add one HTTP call to your app.
Safe by default
Ready templates in 7 languages: English, Italian, German, French, Spanish, Polish, and Chinese. Keys are locked to one channel and can be revoked anytime. A login code key can only send login codes.
Automatic SMS fallback
If a login code does not reach WhatsApp, we retry by SMS with €5 SMS fallback credit included, usually around 100 SMS in the EU.
Full delivery logs
Every send has a time, status, scope, and destination in your dashboard. Useful for support and debugging.
Responsible use
Built for expected transactional messages.
send via .chat is built for messages your users already expect: login codes, booking updates, appointment reminders, support notices, and contact form requests.
Not spam software
Cold outreach, bulk blasts, scraped lists, and unrequested messages are not supported by the product design: there is no list upload, campaign builder, or prospecting workflow.
Not lead generation
We do not sell contacts, build prospect lists, enrich databases, or help you find new people to message.
Not an SMS provider
SMS is only an optional fallback for critical delivery, such as login codes, when chat delivery is unavailable.
Not marketing automation
Campaigns, promotional sequences, newsletter pushes, and marketing opt-out management are not product features; the service only exposes scoped transactional flows.
Message types
Use the right message flow for your business.
Auth, contact, booking, and appointment messages should not look or behave the same. Each flow has its own template, destination rule, and delivery policy.
Auth message
Login codes that feel native in chat.
Best for SaaS apps, marketplaces, memberships, customer portals, and any product where users need a fast code or magic link.
send via .chat
online
Today
Your login code is
482931
This code expires in 10 minutes.
09:14
Message
Booking desk
available
Today
Booking confirmed
Table for 4
Friday at 20:30
10:07
Message
Booking message
Booking updates without extra admin work.
Best for restaurants, rentals, classes, events, ticketed experiences, local shops, and service bookings that need confirmations or status changes.
Appointment reminder
Reduce no-shows with simple reminders.
Best for clinics, salons, consultants, repair visits, coaching calls, and service teams that need people to arrive on time.
Appointment
online
Tomorrow
Appointment reminder
Your visit is tomorrow at 15:30.
18:00
Message
Contact request
online
Today
New contact request
Marta asked for pricing from your homepage form.
Contact
Marta +39 347 123 4567
11:42
Message
Contact alert
Contact requests land where you answer.
Best for agencies, freelancers, B2B sites, real estate pages, and service businesses that want form requests in WhatsApp or Telegram.
Contact Alerts
Website forms sent to a destination you control.
Contact forms, support requests, and contact request alerts go to the owner or group locked to the API key. If the channel is offline, the contact request is held in Undelivered so you can recover it instead of losing the conversation.
How it works
Three steps. No more.
-
Step 01
Connect WhatsApp or Telegram
Scan a QR code from your phone or sign in to Telegram. Your session stays linked so messages always send from your own number.
-
Step 02
Create a scoped API key
Bind the key to the messages it is allowed to send, the channel it should use, and the default language for templates.
-
Step 03
Call the API from your app
One JSON request. Templates render on the server. Logs land in your dashboard immediately.
Use cases
Start with the message flows that already matter.
Each guide shows a focused implementation path for sending expected business messages through WhatsApp or Telegram.
WordPress contact form alerts
Route Contact Form 7, WPForms, or Gravity Forms submissions to WhatsApp or Telegram.
Read the guideLaravel OTP verification
Deliver login codes over chat, track delivery, and keep SMS fallback for auth.
Read the guideZapier booking notifications
Connect booking triggers to simple WhatsApp or Telegram confirmations.
Read the guideAPI
Simple API. Easy to ship.
Send login codes, magic links, and contact alerts with one small API call. Your app keeps the flow; send via .chat handles templates with translations, delivery, fallback, and the trace you need to debug.
POST
chat first, SMS fallback
curl example
$ curl -X POST https://sendvia.chat/api/send/auth \
-H "Authorization: Bearer sendvia_••••••••" \
-H "Content-Type: application/json" \
-d '{
"phone": "+39333111222",
"code": "123456",
"language": "en"
}'
Drop it behind your signup, checkout, booking flow, or support form. The same API shape covers the boring production details without making your team babysit delivery.
Simple and private
send via .chat keeps the API simple, predictable, and OpenAPI-friendly. After delivery, it does not keep your clients' private information like phone numbers or message text.
Messaging API alternatives
A lighter way to send business messages through WhatsApp or Telegram.
If your team only needs reliable alerts, codes, and handoffs, you should not have to spend weeks wiring up a heavy messaging stack.
Looking for a simpler WhatsApp API alternative?
send via .chat is built for developers, SaaS apps, and small teams that want to send important messages without a long WhatsApp Business API setup.
Use it for contact form alerts, login codes, booking updates, internal notifications, and customer messages through WhatsApp or Telegram. If you have compared WAPI, Twilio WhatsApp alternatives, WATI alternatives, WhatsApp Cloud API pricing, or other WhatsApp Business API alternatives, this is the calmer path: connect your device, create an API key, and start with the flows you actually need.
Need your AI agent to send a WhatsApp message?
Some automations do not need a full chatbot. They just need a dependable way to let a human know something happened.
Your Claude workflow, GPT assistant, n8n automation, backend job, or internal AI agent can call sendvia.chat to send WhatsApp or Telegram messages for lead alerts, form submissions, booking requests, failed payments, login codes, and human handoffs.
send via .chat is a messaging layer for expected business notifications, not a general-purpose AI chatbot platform.
Common ways people use sendvia.chat
Teams use sendvia.chat when they need a simple WhatsApp API, Telegram API, WhatsApp OTP API, contact form to WhatsApp integration, SMS fallback for login codes, a WAPI alternative, a WATI alternative, a Twilio WhatsApp alternative, or a WhatsApp Cloud API alternative that is easier to reason about.
It also fits small Claude WhatsApp notification flows, GPT WhatsApp alert flows, and n8n WhatsApp message automation where the goal is a clear business notification, not a new marketing channel.
FAQ
Frequently asked questions
Do I need the official WhatsApp Business API to use sendvia.chat?
No. sendvia.chat sends through the WhatsApp or Telegram account you connect, so you can start without a complex WhatsApp Business API setup, Meta Cloud API configuration, or enterprise onboarding.
It is designed for simple transactional messages: login codes, magic links, contact form alerts, booking updates, appointment reminders, and internal notifications.
Is this for marketing campaigns or cold outreach?
No. sendvia.chat is not built for cold outreach, scraped lists, bulk blasts, newsletters, or promotional campaigns.
There is no list upload, no campaign builder, and no prospecting workflow. The product is for expected business messages that the recipient should reasonably receive, such as OTP codes, contact replies, booking confirmations, and service reminders.
What happens if my WhatsApp or Telegram device is offline?
For auth messages, sendvia.chat can use SMS fallback when chat delivery is unavailable and you have SMS credit available.
For contact form alerts and other non-auth flows, undelivered messages are kept in the Undelivered queue so you can recover the request instead of silently losing it.
Can I use it only for contact forms, without login codes?
Yes. You can use sendvia.chat only for contact form alerts, support forms, pricing requests, booking requests, or website lead notifications.
Each API key can be configured for the scopes you need, so you can keep one key for a specific form or create broader keys for multiple flows.
Can my Claude, GPT, or n8n workflow use sendvia.chat?
Yes, as a notification layer. Your Claude workflow, GPT assistant, n8n automation, backend job, or internal AI agent can call the API to send WhatsApp or Telegram notifications for lead alerts, form submissions, failed payments, booking requests, human handoffs, or login codes.
sendvia.chat is not a general-purpose AI chatbot platform. It simply gives your workflow a controlled way to send expected business messages.
Pricing
€14 / month. Predictable chat delivery.
One predictable plan for teams that need transactional chat delivery with an included chat message allowance, SMS fallback credit.
25k
Transactional chats
€5
SMS credit
30
Days free
Relying on SMS for login codes? send via .chat keeps the plan at €14 when typical SMS-provider pricing would climb quickly.
Pro
€14
/ month
IVA not included
First 30 days free · cancel anytime · no commitment
- 25,000 transactional chat messages per month
- €5 SMS fallback credit included
- One connected WhatsApp and Telegram
- Auth, contact, booking & appointment messages
- 30 day delivery logs & email support
Enterprise
Custom
For large teams and regulated industries.
- Custom monthly volume, no caps
- Multiple connected devices & numbers
- Private, isolated infrastructure
- Bring your own SMS fallback provider
- Dedicated Android App
- Priority & phone support, SLA on request
All prices are in € and exclude IVA/VAT, so tax is added where applicable. Cancel anytime from your account. No phone calls.
send via .chat is built for transactional and operational messages to recipients who expect them. Customers are responsible for having proper consent/opt-in before sending WhatsApp messages. It does not include list upload, campaign, newsletter, or prospecting workflows.
Send expected messages. Start sending via chat.
A practical messaging layer for small and medium teams that need reliable codes and alerts without enterprise setup, carrier contracts, or months of configuration.
send via .chat · 30 days free · €14 / month before tax · cancel anytime