Can I put the "Text us" message form on my own website?

[jakesbarbershop]

I own a booth-rental barbershop in Medina, Ohio. Seven barbers, each with their own Square account and their own Appointments booking site. We also have our own shop website where customers browse the barbers and book.

The problem I'm trying to solve: my barbers don't want their personal cell numbers on the website, but they do want customers to be able to ask them a question before booking. On the free plan a customer can't text them directly - I tested this, a text to the number from someone with no prior conversation just disappears. The only way in is the "Text us" button on the barber's Square booking site, which works great, but it means pulling the customer off our site in the middle of booking.

So my question: am I allowed to put that "Text us" form on my own website, pointed at my own barbers' locations?

If yes, I'd want to do it properly - including showing the same consent language your version shows (agreeing to automated texts, reply STOP to opt out, the 18-and-over line). I'm not trying to skip any of that. I'd rather build the supported version than something clever.

If the answer is no, a few related questions:

1. Is there any official way to embed or link to the "Text us" form?

2. Is there a link that opens a booking site straight at the message form instead of the service list?

3. Does Messages Plus change this - can a customer text a dedicated business number with no prior conversation?

Totally fine being told no. I just want to know which door is the right one before I build anything.

[Surajs10]

```
Short version: I couldn't find a supported way to put the Text us form on its own on a site you host yourself. There is a supported route that may already get you most of the way there, though.

What Square documents: the "Manage your 'Text us' button" help article covers Text us on Appointments booking sites, Square Online sites, invoices, estimates, projects and contracts. It says the form fields (name, phone, message) can't be customized, and it doesn't describe any way to embed the form on a third-party site. The "Website" toggle in Messages settings appears to mean Square Online sites, not a site you host. So a copy you rebuild yourself wouldn't be the supported version, even with the consent wording matched word for word.

The route worth testing: the Appointments booking widget you can embed on your own site runs Square's own booking flow inside your page, and the Text us button can appear inside it. That would be Square's own form, consent lines and all, without the customer leaving your site. To check:
- In each barber's Dashboard: Appointments > Online booking > Settings > Enable Text us button. Also make sure Do not disturb is off in Messages, because it switches Text us off.
- On a page with the widget, send a Text us from a phone that has never messaged that barber. Confirm it lands in their Messages inbox, that the reply comes from a Square number and not their cell, and that on mobile it doesn't jump out to a new tab.
- Any barber who still links out to their booking site needs to copy the widget code from their own account. With booth rental, each account is theirs, so they each do this step.

Your three:
1. An official embed or link for the form by itself: none documented that I could find.
2. A link that opens a booking site straight at the message form: none documented either. The embedded widget is the closest thing.
3. Messages Plus: the dedicated business number is a toll-free number that takes calls, texts and voicemail. The help article lists it for Messages Plus and for the Square Plus and Premium plans. The catch for a booth-rental shop is that Square gives one number per paid location, so seven separate accounts means seven subscriptions and seven numbers. Each number goes through carrier verification that Square says usually takes up to seven business days. Before anyone subscribes, confirm with Square that a first text from a brand-new customer actually lands.

It would help to hear from Square staff on whether Text us inside the embedded widget is officially supported, since the article doesn't mention it either way.
```