Webhooks that close the loop
Send a message, receive delivery updates, and sync accepted, sent, failed, and undelivered states back into your own app.
send via .chat
online
Thanks, I am in.
ChatGPT integration
Connect ChatGPT to sendvia.chat so an authenticated assistant can read active chats, find contacts, choose the right WhatsApp or Telegram device, and prepare customer replies from one controlled workflow.
OAuth login
Users authorize ChatGPT without sharing passwords, dashboard sessions, or API keys.
MCP tools
Expose focused tools for devices, active chats, contacts, and approved message sending.
Assistant workspace
Ask ChatGPT
Find the active WhatsApp chat for Marta, summarize the latest context, and send a polite follow-up from my connected number.
Tool calls
sendvia_list_active_devices
whatsapp · connected · +39••••1122
sendvia_list_contacts
Marta Rossi · customer lead
sendvia_create_contact
verifies number · requires confirmation
sendvia_send_message_to_phone
direct E.164 recipient · requires confirmation
sendvia_send_message
requires user confirmation
Why teams switch to send via .chat
How a message travels
Connect WhatsApp or Telegram, trigger messages from your product, receive delivery webhooks, and add SMS fallback through your own provider when you need it.
Your app
send via .chat
send · deliver · log
Your device
WhatsApp / Telegram
Delivered
What you get
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.
Send a message, receive delivery updates, and sync accepted, sent, failed, and undelivered states back into your own app.
Messages leave from your own device. Most codes arrive before the user has time to switch apps.
Scan a WhatsApp QR code or sign in to Telegram. Create an API key. Add one HTTP call to your app.
Bearer keys can be revoked anytime, defensive rate limiting stays on, and delivery logs help you understand every important customer notification.
Add SMS fallback with your own provider for critical flows such as login codes, booking confirmations, and time-sensitive alerts.
Every send has a time, status, channel, and destination in your dashboard. Useful for support and debugging.
Customer messaging
send via .chat helps teams turn product events, website forms, bookings, and customer moments into WhatsApp, Telegram, and SMS-backed conversations.
Send demo forms, support messages, and landing-page leads straight to the team member or group that can answer fastest.
Deliver OTP codes, magic links, onboarding nudges, payment notices, and account updates where customers already look.
Bring your own SMS provider for fallback or special delivery rules, while keeping the operational dashboard in one place.
Trigger renewal reminders, booking follow-ups, review requests, internal escalations, and handoff messages from your existing tools.
Message examples
Use the same messaging layer for login codes, booking updates, reminders, form alerts, internal notifications, and customer follow-ups.
Best for SaaS apps, marketplaces, memberships, customer portals, and any product where users need a fast code or magic link.
send via .chat
online
Your login code is
482931
This code expires in 10 minutes.
Booking desk
available
Booking confirmed
Table for 4
Friday at 20:30
Best for restaurants, rentals, classes, events, ticketed experiences, local shops, and service bookings that need confirmations or status changes.
Best for clinics, salons, consultants, repair visits, coaching calls, and service teams that need people to arrive on time.
Appointment
online
Appointment reminder
Your visit is tomorrow at 15:30.
Contact request
online
New contact request
Marta sent a request from your homepage form.
Contact
Marta +39 347 123 4567
Best for agencies, freelancers, B2B sites, real estate pages, and service businesses that want form requests in WhatsApp or Telegram.
Contact Alerts
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
Scan a QR code from your phone or sign in to Telegram. Your session stays linked so messages always send from your own number.
Use one bearer credential from your backend. Choose the channel, recipient, message, and metadata in each request.
One JSON request. Templates render on the server. Logs land in your dashboard immediately.
Use cases
Each guide shows a focused implementation path for sending expected business messages through WhatsApp or Telegram.
Route Contact Form 7, WPForms, or Gravity Forms submissions to WhatsApp or Telegram.
Read the guideDeliver login codes over chat, track delivery, and keep SMS fallback for auth.
Read the guideConnect booking triggers to simple WhatsApp or Telegram confirmations.
Read the guideAPI
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.
curl example
$ curl -X POST https://sendvia.chat/api/send \
-H "Authorization: Bearer sendvia_••••••••" \
-H "Content-Type: application/json" \
-d '{
"channel": "whatsapp",
"phone": "+39333111222",
"message": "Your login code is 123456",
"metadata": {"kind": "login_code"}
}'
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
If your team only needs reliable alerts, codes, and handoffs, you should not have to spend weeks wiring up a heavy messaging stack.
send via .chat is built for developers, SaaS apps, agencies, and local businesses 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, customer follow-ups, and WhatsApp or Telegram messages from your own tools. If you have compared WAPI, Twilio WhatsApp alternatives, WATI alternatives, 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.
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 business notifications, lead alerts, and human handoffs from the workflows you already run.
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 Claude WhatsApp notification flows, GPT WhatsApp alert flows, and n8n WhatsApp message automation where the goal is fast communication with customers or your own team.
FAQ
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.
Yes. Use sendvia.chat for permission-based marketing follow-ups, lead replies, booking updates, review requests, payment reminders, and campaign handoffs.
It is not for mass spamming, scraped lists, or cold outreach. The strongest workflows start from your own product, CRM, form, booking tool, or automation platform, then send the right WhatsApp, Telegram, or SMS-backed message at the right moment.
For critical messages, sendvia.chat can use SMS fallback when chat delivery is unavailable.
You can also bring your own SMS provider integration for custom fallback rules, while failed chat deliveries remain visible in the Undelivered queue.
Yes. You can use sendvia.chat only for contact form alerts, support forms, demo requests, booking requests, or website lead notifications.
Use metadata in each request to identify the form, booking, customer journey, or workflow that triggered the message.
Yes. 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 gives your workflow a controlled way to send business messages and track what happened after the message was accepted.
Access
Access starts from a direct conversation. Contact us, we review the setup together, enable the account manually, and connect the right WhatsApp, Telegram, and optional SMS fallback workflow.
Manual setup
contact first
Unlimited messages
WhatsApp and Telegram
SMS fallback
with your provider
Need something custom? send via .chat can also support multiple numbers, private infrastructure, and your own SMS provider integration.
Start
manual approval and setup
Unlimited messages
WhatsApp and Telegram delivery for the flows your business runs every day.
Enterprise
For large teams and regulated industries.
All access starts from the contact form, then we activate the account manually.
send via .chat helps you send customer messages, alerts, codes, reminders, and permission-based marketing follow-ups from the systems you already use. It is not for mass spam.
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 · Unlimited messages · delivery webhooks · SMS provider integration
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect