A Squarespace SMS integration is a small chain: a form on your site collects a phone number and a consent checkbox, something forwards each submission, and a texting API sends the first message. The site itself doesn't text anyone. You add the missing piece.

This guide is for developers, agencies and sales teams building that chain for themselves or for the businesses they serve. We'll cover what a Squarespace site can and can't do on its own, three ways to forward a submission, the consent checkbox, and the request that sends the text.

What Squarespace can and can't do natively

Squarespace is built to publish a site and collect form data. Its forms store submissions, email them to you, and can pass them to some connected services. Features and plan limits change, so check your plan's current options before you design around one.

What it doesn't do is send text messages to your visitors. There's no native inbox for replies, no opt-out handling and no carrier registration. Those jobs belong to a messaging service. Ready has no native Squarespace connector either, so the hop between the two is something you build or wire with an automation tool.

That's less work than it sounds. Every approach below reduces to the same three moves: capture the number with consent, forward it, call the API.

Three ways to get a form submission to an SMS API

ApproachWhat you set upBest forWatch out for
Form webhookPoint the form's submission at your own endpoint, which calls the APIDevelopers who want full controlYou host and monitor the endpoint
Automation toolA Zapier-style or n8n-style workflow that triggers on a new submission, then makes an HTTP requestAgencies and sales teams without a backendTask limits and delays on the tool's side
Form to CRM, CRM to SMSSubmissions land in a CRM, which texts through its own connectionTeams that already live in a CRMTwo hops to debug

If your plan lets a form post to a URL you control, the webhook route is the cleanest. If it doesn't, an automation tool that watches the form's submissions or the email it sends can stand in. In both cases the receiving step needs the phone number, the name and the consent answer as separate fields.

Our guide to SMS webhooks and APIs for CRM and automation covers the receiving side in more depth.

Add the consent checkbox first

A phone number in a form doesn't prove someone agreed to texts. Add a separate, unchecked checkbox, and only text the people who tick it.

Wording to adapt:

I agree to receive texts from Acme Studio about my inquiry. Msg and data rates may apply. Msg frequency varies. Reply STOP to opt out, HELP for help.

A few practical points:

  • Leave the box unchecked by default, and place the disclosure next to it, not buried in the footer.
  • Don't make the checkbox a condition of getting a quote or a download unless you'd refuse to serve anyone who skips it.
  • Store the consent answer as its own field in whatever your workflow writes to, with the timestamp.
  • Name the business in the wording the same way your registration does.

Ready stores no per-contact consent record: you keep that in your form data or CRM. (The one exception is a sign-up on a Ready-hosted opt-in page, which is stored per contact.) The consent_attested flag on a send is your statement that the recipient agreed. Our SMS consent language guide goes through what carriers look for in that wording.

The request that sends the text

Whichever route you pick, the last step is one HTTP request:

POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: <the submission ID>
{"to": "+12125550199", "body": "Hi Dana, it's Acme Studio. Thanks for your inquiry. Is a call today or tomorrow better? Reply STOP to opt out.", "consent_attested": true}

Three details matter here:

  1. to is E.164. A 10-digit US number is treated as +1, but normalize it anyway, since forms collect numbers in every format.
  2. Use the submission's ID as the Idempotency-Key. Automation tools retry, and a retried request then never sends twice.
  3. Set consent_attested to true only on the branch where the checkbox was ticked.

Leave from out and Ready picks the number: the one this contact already texts with, otherwise your number closest to their area code. The full reference is at docs.tryready.com/api/messages, and the API quickstart walks through a key, a first send and a webhook.

Replies, opt-outs and what happens after the first text

A visitor who gets a text will reply. Those replies land in the Ready inbox, and the same inbox is where your team answers. If you'd rather get them in your own system, a webhook can deliver them; see receiving SMS with inbound webhooks.

Opt-outs are the part you shouldn't rebuild. A STOP reply is honored automatically, and phrases like "please stop texting me" are caught too. The number is blocked from further sends. Your form and workflow should still respect it: if the same person submits the form again next month, check the opt-out before you text. GET /v1/opt-outs/:phone answers that for a single number.

Registration, quiet hours and cost

Texts to US numbers from a local number go out on a registered 10DLC campaign. Ready files the brand and campaign registration for you in the app, for $25 a month, plus $2 a month per number, and most approvals take 2 to 7 days. Before you register, an account can send up to 500 texts a month at its normal per-text rate, so you can test the whole chain first. Our 10DLC explainer covers why registration matters.

Texts cost $0.0075 a segment plus a $0.0045 carrier fee, and that rate is the same whether the submission came from Squarespace or anywhere else. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.

Quiet hours follow the recipient's area. An API text goes out if the window opens within 6 hours. If it opens later, the API answers 409 QUIET_HOURS_BLOCK and the text isn't sent, unless your request includes hold_until_allowed: true, which holds it for up to 24 hours. A visitor who submits at 11 PM is better served by the hold than by a failed workflow run.

Frequently asked questions

Does Squarespace send text messages by itself?

No. Squarespace publishes your site and collects form data, but texting needs a messaging service behind it. You connect the two with a webhook or an automation tool.

Do I need a developer to build this?

Not always. An automation tool with an HTTP step can do it without a backend. A developer helps when you want your own endpoint, custom logic for duplicates, or several sites feeding one account.

Can I text everyone who submits the form?

Only the people who ticked the consent checkbox. A phone number alone isn't consent to marketing texts, and compliance is the sender's responsibility. Call or email the rest.

Next step

Add the checkbox to your form first, then connect one submission to one test text sent to your own phone. When you're ready, sign up, add a card and a number, and run that first send.