Guide · 12 minute read

How to get SMS notifications from your contact form

Five working ways to make your website's contact form text you the moment a lead arrives. Comparing cost, setup time, and ongoing effort, with a real Twilio tutorial you can follow.

Published 2026-04-14 · By localbot

The short answer

Most leads go cold because the business replied too late. Thirty minutes of silence and your conversion rate collapses by roughly 80%. The single highest-leverage fix is to move lead notifications off email and onto SMS, where messages are read in under three minutes on average.

There are five honest ways to wire this up. Here they are, from most to least work.

At a glance

MethodSetupMonthly costSkillsBest for
Twilio + custom backend4 to 8 hours€10 to €30DeveloperFull control
Zapier + Twilio30 minutes€40 to €70NoneQuick no-code
Make.com + Twilio45 minutes€15 to €40Some technicalCheaper than Zapier
WordPress + WPForms + Twilio1 hour€25 to €50WordPress adminExisting WP sites
localbot5 minutes€99NoneAnyone who wants it to just work

Method 1: Twilio with a custom backend

This is the classic developer path. You get full control, the lowest per-message cost, and the ability to layer in any custom logic later. It takes real time up front: expect four to eight hours to get something production-ready, plus ongoing maintenance when things break.

1. Sign up for Twilio and buy a number

Create a Twilio account at twilio.com. The free trial gives you €15 in credit, enough for about 100 test SMS. Inside the console, go to Phone Numbers and buy one. For a Finnish number, filter by country and SMS capability. Expect to pay around €1 per month for the number itself.

Finnish regulatory note: Finnish carriers require an alias registration through Traficom before they deliver SMS from your number. Twilio handles the paperwork but the process takes 3 to 5 business days. Skip this and your messages silently fail on Finnish mobile networks.

2. Grab your API credentials

In the Twilio console, go to Account and copy your Account SID and Auth Token. Store them in environment variables, never in your repo:

TWILIO_ACCOUNT_SID=ACxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
TWILIO_AUTH_TOKEN=your-auth-token
TWILIO_PHONE_NUMBER=+358XXXXXXXX
OWNER_PHONE_NUMBER=+358YYYYYYYY

3. Build the endpoint

Install the Twilio SDK and create a route that accepts form submissions and texts you. In Next.js (App Router):

// app/api/contact/route.ts
import { NextResponse } from 'next/server';
import twilio from 'twilio';

const client = twilio(
  process.env.TWILIO_ACCOUNT_SID!,
  process.env.TWILIO_AUTH_TOKEN!,
);

export async function POST(request: Request) {
  const { name, phone, message } = await request.json();

  if (!name || !phone) {
    return NextResponse.json(
      { error: 'Missing fields' },
      { status: 400 },
    );
  }

  const body = `New lead from ${name} (${phone})\n\n${message}`;

  await client.messages.create({
    body,
    from: process.env.TWILIO_PHONE_NUMBER!,
    to: process.env.OWNER_PHONE_NUMBER!,
  });

  return NextResponse.json({ ok: true });
}

4. Wire up the form

Your form posts to that endpoint. Here is the minimum client code:

const form = document.querySelector('#contact');
form?.addEventListener('submit', async (e) => {
  e.preventDefault();
  const data = Object.fromEntries(new FormData(form).entries());
  const res = await fetch('/api/contact', {
    method: 'POST',
    headers: { 'content-type': 'application/json' },
    body: JSON.stringify(data),
  });
  if (res.ok) form.reset();
});

5. Deploy and test

Deploy to Vercel, Railway, or wherever you host. Set your environment variables in the dashboard. Send a test submission from the live form. You should receive a text within seconds. If you do not, check the Twilio console logs.

6. What this actually costs

  • Finnish number: approximately €1 per month
  • Per SMS to a Finnish mobile: approximately €0.07
  • 100 leads per month × 1 SMS each = about €9 per month
  • Your development time: 4 to 8 hours up front, plus maintenance

Gotchas to plan for

  • GDPR opt-in: add a checkbox confirming the person consents to being contacted. Store the consent with a timestamp.
  • Finnish alias registration: without it, messages silently fail. Do this before launch.
  • Rate limits: Twilio will throttle you on unverified trial accounts. Upgrade to a paid account before going live.
  • Delivery failures: wire the Twilio status callback webhook if you want to know when a message fails to reach the phone.
  • Character limits: 160 characters for plain ASCII, 70 for Unicode (any Finnish character with umlauts drops you to 70).
  • Error handling: what happens when Twilio is down? At minimum, log and email yourself so leads do not silently disappear.

Method 2: Zapier plus Twilio

If you do not want to write code, Zapier is the fastest path. You connect your form platform (Typeform, Google Forms, WordPress, Webflow) as a trigger, then add a Twilio SMS step.

  • Zapier Starter plan: around €30 per month for 750 tasks
  • Twilio SMS cost on top: same €0.07 per message, €1 number
  • Realistic total: €40 to €70 per month for modest volume
  • Setup time: 30 minutes if your form platform is pre-integrated

Downsides: Zapier adds 1 to 15 minutes of latency depending on your plan. For a lead where every minute matters, this is worse than it sounds. Tasks cost money, and errors are harder to debug when they happen inside Zapier's runtime.

Method 3: Make.com plus Twilio

Make.com is Zapier's cheaper sibling. The free tier gives you 1,000 operations per month, which is comfortably enough for any small business. The paid tier starts around €9 per month for 10,000 operations.

The setup is conceptually identical to Zapier: webhook trigger, Twilio action, map the fields. The interface is more technical but the results are the same. For most small businesses, Make is the better economic choice than Zapier.

Method 4: WordPress with WPForms Pro plus Twilio

If your site is already on WordPress and you already use WPForms, this is the lowest-friction path inside that ecosystem. You install the Twilio add-on, configure your Twilio credentials in wp-admin, and point it at the form submission event.

  • WPForms Pro licence: around €200 per year
  • Twilio SMS costs: same as every other method
  • Setup time: roughly an hour, mostly wp-admin clicks

If you do not already run WPForms, the licence cost plus the WordPress maintenance burden makes this a worse deal than the alternatives.

Method 5: localbot

Full disclosure: this is our product. Here is the honest pitch. You sign up, copy one line of JavaScript into your site, and the form on your site now texts you the moment someone submits it. No Twilio account, no code, no dashboards.

  • €99 per month, or €990 per year (two months free)
  • 30-day free trial, no credit card
  • Works on any website: WordPress, Wix, Squarespace, Shopify, Webflow, custom
  • Every SMS includes a tap-to-call link and a tap-to-WhatsApp link
  • Setup: paste the script tag, done

If your time is worth more than €40 an hour, localbot pays for itself on setup alone compared to the DIY path. If you have the volume and the engineering time, Method 1 is cheaper long-term.

Which should you pick?

Three short questions tell you which method is yours.

  • Are you a developer with time? Method 1 (Twilio + custom backend) gives you the most control and the lowest long-term cost. Plan on a day of work.
  • Do you already run WordPress with WPForms? Method 4 is the path of least resistance. Pay the add-on, move on.
  • Do you want it to just work today? Method 5 (localbot) is five minutes and no ongoing maintenance.

Zapier and Make.com are the honest middle ground. Pick them if you already use one of them for other automations. If you do not, the per-task pricing model has a habit of surprising you later.

Frequently asked questions

Is SMS marketing GDPR-compliant in Finland and the EU?

Transactional SMS that confirms a form submission you just received is generally fine. Marketing SMS requires explicit opt-in. The safe pattern is to add a checkbox to your contact form: "I consent to being contacted by SMS about my enquiry." Store that consent with a timestamp.

Do Finnish Twilio numbers need special registration?

Yes. Finnish carriers require an alias registration through Traficom before SMS traffic is delivered. Twilio handles this for you, but the process takes 3 to 5 business days and you need to supply your company details. Without it, your SMS may not reach Finnish recipients.

What does it actually cost per lead?

Twilio charges roughly €0.07 per SMS to Finnish numbers plus about €1 per month for the number itself. One SMS per lead, 100 leads a month, works out to around €9 per month before your development time. Zapier adds about €30 per month on top. Make.com adds less.

Can I send WhatsApp instead of SMS?

Yes. Twilio supports WhatsApp Business through its API, but you need Meta approval for a WhatsApp Business template and a verified display name. For most small businesses the extra setup outweighs the benefit: SMS open rates are already 98% within three minutes.

How reliable is each method?

All five work. Twilio has industry-standard delivery rates (around 95% to Finnish mobile). Zapier and Make add a 1 to 15 minute delay depending on your plan. WordPress plugins share Twilio reliability but depend on your WordPress site staying online. localbot uses the same underlying SMS infrastructure as the direct methods.

When should I build this myself versus use a SaaS?

Build it yourself if you are a developer, the volume justifies the time, and you need custom logic (routing leads to different phones, escalation rules, integrations with your CRM). Use a SaaS if you just want it to work and you value your time at more than €40 an hour.

Try it on your own site.

Start your 30-day free trial. No credit card required.