Texting, inside the CRM
Text clients from the record.Replies come back to it.
Connect your own Twilio, Sendblue, Linq, Quo, Sinch or Brevo account. Send texts from a lead or client, from workflows, and from event timelines. Replies are matched to the right person and logged on their record.
You bring the SMS account and number, so message pricing and sender registration stay with your provider.
Twilio, Sendblue, Linq, Quo, Sinch, Brevo
Inbound replies matched to leads and clients
A default sending number for each brand
Clients answer texts. Your CRM never sees them.
When texting lives on your personal phone, nobody else on the team knows what was promised.
Client texts stuck on one person’s phone
Texts go out from your business number in Semuko and sit on the Communication tab with the email history.
Reminders that depend on you remembering
Workflows can send a text at a status change or on a schedule, using SMS templates with merge tokens.
Replies you never connect back to the job
An inbound text is matched by phone number to the lead or client, logged, and your team is notified.
How SMS works in Semuko
Bring your own provider. Semuko handles the sending, logging and replies.
- 1
Connect your provider
In Settings → Communication, add your SMS provider credentials and sending number. Semuko tests the connection before saving.
- 2
Pick a default per brand
Set which number sends for each brand. Multi-brand studios can text from different numbers.
- 3
Text from the record
Send a text from a lead or client, or schedule one for later. Every send is logged with its status.
- 4
Point replies at Semuko
Add the Semuko inbound webhook in your provider. Replies land on the matching lead or client.
Already have a Twilio number?
Connect it in a free trial and send your first text from a client record.
Where texts go out from
The same SMS connection works across Semuko.
One-off texts
Text a lead or client from their record. Pick a saved SMS template or write a quick note.
Workflow texts
Add a Send SMS step to any workflow for booking confirmations, prep checklists, and payment nudges.
Special dates
Birthday and anniversary automations can send a text, an email, or both.
Timeline links by text
Send an event timeline share link by SMS so the couple or planner can review it on their phone.
Ask Semu drafts
Ask Semu can draft a text for a client. You review and approve it before anything sends.
Your account, your number
Credentials are stored encrypted. Semuko does not resell SMS, so there is no Semuko markup on messages.
Supported providers
What you need from your provider
Semuko checks the fields and sends a test before the connection is saved. Numbers use full international format, like +15551234567.
Twilio
SMSAccount SID, auth token, and a Twilio sending number.
Sendblue
iMessage and SMSAPI key, API secret, and your Sendblue number.
Linq
iMessage, RCS and SMSAPI key and your Linq number.
Add the webhook signing secret to log replies.
Quo
SMSAPI key and your Quo business number.
Add the webhook signing key to log replies.
Sinch
SMSAPI token, service plan ID, and a sending number.
Regions: US, EU, AU, BR, CA.
Brevo
SMSAPI key and a sender name.
Brevo sender names are capped at 11 letters or numbers.
See every provider in the integrations catalog.
Works better together
More of Semuko that saves you time
One platform means fewer tabs, fewer tools, and one source of truth for your business.
FAQ
Questions before you try it
Straight answers for studios comparing tools or just getting started.
No. You connect your own account with Twilio, Sendblue, Linq, Quo, Sinch or Brevo, and that provider bills you for messages. Semuko does not send texts until a provider is connected.
Keep every text with the client it belongs to
Start free, connect your SMS provider, and send from the record.