Text messages (SMS): VenueWS's number, Twilio or GoHighLevel

Texts work out of the box from VenueWS's number with prepaid credits; or connect your own Twilio account or GoHighLevel sub-account. Guests who gave only a phone number get their invitation by text, and the door can text a waiver link.

4 min read For: AdminsOpen in VenueWS

Texts work with nothing to set up: they go out from VenueWS's own number, with your business name first, and you pay with prepaid credits. If you would rather text from your own number and bill, connect your Twilio account or the GoHighLevel sub-account your CRM runs in. Pick under Settings → Text messages (SMS); everything else (who gets a text, when, STOP) works the same.

VenueWS texting (credits)

One credit is one text of up to 160 characters to a US or Canadian number. A longer text uses one credit per part, other countries cost two or three credits a part, and a picture message costs three. Pro includes credits every month and your free event comes with a few; beyond that, buy a pack under Buy credits — paid once through PayPal, on your workspace within a minute, with a numbered receipt. Credits never expire.

A text the balance can't cover is not lost: it waits, the dashboard says so, and it goes out the moment a pack lands. A text the carrier reports as undelivered is refunded. Because the number is shared, every text starts with your business name, and a guest's reply reaches the workspace that texted them last.

Connect Twilio

  1. In the Twilio Console, copy your Account SID and Auth Token, and buy (or pick) the number you'll text from. For US numbers, register it for A2P 10DLC so carriers deliver your texts.
  2. In VenueWS go to Settings → Text messages (SMS).
  3. Fill in Account SID, Auth Token and Send from (the number, or a Messaging Service SID starting with MG).
  4. Click Check and connect. VenueWS checks with Twilio that the number is on that account before saving; the token is stored encrypted.

Use Send a test text to see one arrive. Texts come from your number and Twilio bills you for them directly.

Running several workspaces (an agency, or one venue per workspace)? The same Twilio account can be connected to each of them — give each workspace its own number, or Messaging Service, so a guest's reply reaches the workspace that texted them.

Connect GoHighLevel

Texts go out through the sub-account's LC Phone number, and every guest you text is created (or updated) as a contact there, with the name on their invitation, the source "VenueWS" and two tags: venuews, and venuews · <event name> for the event the text was about. GoHighLevel has no folders for contacts; tags are how it groups them, so a smart list on the event's tag is your guest list inside the CRM, and the venuews tag is everyone VenueWS ever texted.

  1. In the sub-account, go to Settings → Private Integrations → Create. Give it the scopes locations.readonly, contacts.write and conversations/message.write, and copy the token (it starts with pit-).
  2. Copy the Location ID from Settings → Business Profile (it is also the part after /location/ in the sub-account's address).
  3. In VenueWS, under Text messages (SMS), choose GoHighLevel, paste both and click Check and connect. VenueWS checks the token against the location before saving; it is stored encrypted.

The number, its A2P 10DLC registration and the per-text price are all GoHighLevel's: a US number that is not yet registered will not deliver, whatever VenueWS sends. GoHighLevel also rate-limits its API, so a large send is paced rather than refused.

For guests' replies to reach VenueWS, add a workflow in GoHighLevel: trigger Customer Replied (channel SMS), action Webhook, method POST, to the address shown under Replies and STOP — it carries a key that identifies your workspace, so keep it private. Include the contact's phone and the message body in the payload (the defaults do). A guest's "Sí" / "No" then becomes their RSVP, and their other words wait under the event's Replies. STOP is handled by GoHighLevel's own do-not-disturb; VenueWS records it too and stops queuing texts to that number.

Text the guests nothing else reaches

In the venue's Settings & devices, switch on Send as a text message (SMS) and save. A guest with a phone number whom neither email nor WhatsApp reaches then gets their invitation and the day-before reminder as a short text with the link to their page (the waiver first, if the event has one). The order is email → WhatsApp → text: a guest with an email gets the email, a guest WhatsApp reaches gets the WhatsApp, and a WhatsApp that cannot be delivered is sent again as a text by itself. See Send passes on WhatsApp for how the channels combine.

By switching it on you confirm those guests agreed to get texts about the event.

At the door

The scanner's Sign on their own phone → Text sends a guest their waiver link. See A guest who hasn't signed, at the door.

STOP

Every invitation text ends with "Reply STOP to opt out". Twilio honours STOP on its side; to have VenueWS stop queuing texts to that number too, set the webhook shown under Replies and STOP as the number's "A message comes in" webhook in Twilio. Last 30 days shows what was sent, what failed and how many opted out.

Was this guide helpful?

Related guides