What you need before you start
This page uses placeholder copy for now, but the workflow is intentionally realistic. Before you begin, make sure you have:
- access to your Squarespace admin
- a live or draft contact form block
- a Form2SMS inbox or forwarding address ready to paste into the form settings
- one mobile number or destination inbox configured to receive the alert
If you are building this for a client, collect the exact email address they want to keep as the primary submission destination. That makes testing cleaner and avoids swapping settings twice.
Step 1. Create your Form2SMS inbox
Open Form2SMS and create a new forwarding inbox for this site. The platform will generate a destination address you can use inside the Squarespace form notification settings.
Copy the forwarding address
For this placeholder guide, imagine Form2SMS gives you an address like launch@notify.form2sms.test. In the real guide, this section can include a screenshot, a short callout, or a note about naming conventions for client sites.
Add at least one destination
Before you leave Form2SMS, attach the phone number or inbox that should receive new lead alerts. There is no point wiring the form if the destination list is empty.
Step 2. Open the form block in Squarespace
Inside Squarespace, edit the page that contains your contact form. Open the form block settings and move to the storage or notifications area, depending on the version of Squarespace you are using.
If the site still uses an older form setup, the labels may differ slightly. That is fine. The thing you are looking for is the setting that controls where submission notifications get sent.
Step 3. Add the Form2SMS notification address
Paste the Form2SMS forwarding address into the email notification field. If Squarespace supports multiple recipients, keep the original recipient in place and add Form2SMS alongside it. If it only allows one destination, use Form2SMS as the primary receiver and let Form2SMS forward onward.
Keep the original inbox if the client needs it
Many teams still want a normal email record for CRM handoff, triage, or compliance. Form2SMS works well as the immediate alert layer while the original inbox remains the archive.
Save and publish the change
Do not skip the publish step. A common setup mistake is updating the draft form block, sending a test, and then assuming the integration failed when the live page never changed.
Step 4. Test the full submission flow
Open the live page in a new tab and submit a fake enquiry with obviously test-only details. Use a subject line or message body that is easy to recognise when it arrives.
Look for three things:
- the form submits without error
- the Form2SMS destination receives the submission
- the final SMS or email destination receives the alert in a readable format
If one of those steps breaks, stop there and fix that layer before testing again.
Common mistakes to watch for
The usual failure points are boring, which is useful because they are easy to check.
- the forwarding address was copied with an extra space
- the destination number in Form2SMS was never confirmed
- the Squarespace page was edited but not published
- the test was run against a duplicate staging page instead of the live form
When you turn this into production content, this section is a good place for short callouts and screenshots. It also gives search traffic a better reason to stay on the page because the answer is not just a linear checklist.
Final setup checklist
Use this as the final pass before you call the integration complete.
- Form2SMS forwarding inbox created
- destination phone number or email connected
- Squarespace form notification field updated
- live form submission tested successfully
- backup inbox flow confirmed if the client needs one
Once this is live, the next useful article is usually about testing frequency, team routing, or what to do when multiple forms should feed different alert destinations.