Skip to content
OrqLabs
Türkçe'ye geç: ENTR

Messaging

Twilio SMS integration: SMS campaigns and a two-way SMS chatbot

Add SMS to OrqLabs with your Twilio Account SID, Auth Token and sender number. Campaigns go out to lead segments at a controlled rate, texts to your number become Inbox conversations, and the AI chatbot replies.

Start freeStep-by-step setup guide
Connection type
Username / password
Scope
Per project: every brand connects its own account
Inbound webhook
Yes, you get a webhook URL for incoming events
Capabilities
send messages, receive messages, broadcast
Setup time
20 min

What it does in OrqLabs

The Twilio SMS integration uses Twilio's Programmable Messaging API. When connecting, you enter your Account SID, Auth Token and, as the sender, a number in E.164 format (e.g. +14155551234) or an approved alphanumeric sender ID. Test connection shows the account's name, status and type (trial or full).

For incoming SMS, you set the OrqLabs webhook URL as your Twilio number's A message comes in handler; requests are verified with X-Twilio-Signature. Each message opens an Inbox conversation, the AI Chatbot or a workflow with a Message received trigger replies, and the sender's number is matched to an existing lead by phone.

For campaigns, the Broadcast node and the Campaigns page send to leads that have a phone number and haven't opted out, at a per-minute rate. When someone replies with just an opt-out keyword such as STOP, DUR, İPTAL or ÇIK, OrqLabs marks them as opted out, skips their queued campaign messages and sends a short confirmation.

What you can automate

  • SMS campaigns

    Send personalised texts – with fields such as name and company – to a segment of consenting leads; sends are queued at 20 messages per minute by default.

  • Two-way SMS chatbot

    The AI Chatbot answers customers who text your number from your knowledge base and hands the conversation to your team when needed.

  • Reminder and notification texts

    Send appointment, order or payment reminders one by one from a workflow with the Send message node (channel SMS).

  • First-touch outreach by SMS

    With the SMS channel selected, the Outreach Agent sends leads a short, personal first message and follow-ups.

Agents that work with it

Nodes that use this integration

In the workflow editor these nodes run with your Twilio SMS account.

  • Message received

    Starts when a customer message arrives on a connected channel like WhatsApp or Telegram; e.g. so your chatbot answers automatically.

  • Send message

    Sends a message to one person on WhatsApp, Telegram, SMS and more, e.g. delivering a chatbot reply or an appointment reminder.

  • Broadcast campaign

    Sends a personalised message to a group of leads at a controlled pace, e.g. announcing a webinar to qualified leads.

  • Hand off to human

    Passes the chat to someone on your team, silences the bot in that chat and alerts the team, e.g. when a customer complains or asks for a person.

Setup at a glance

  1. In Twilio Console, buy an SMS-capable number under Phone Numbers → Buy a number, or pick one you already have.

  2. Copy the Account SID and Auth Token from Account Info on the console home page.

  3. In OrqLabs, go to Integrations → Twilio SMS → Connect, pick the project and enter the SID, token and sender number (E.164).

  4. Paste the webhook URL from the card into your number's Messaging Configuration → A message comes in field in Twilio as HTTP POST and save.

  5. Text your number – the conversation should appear in the Inbox. Then send a test to your own phone with the Send message node.

Read the full setup guide →

Requirements

  • A Twilio account: Account SID, Auth Token and an SMS-capable number or an approved alphanumeric sender ID.
  • An upgraded account rather than a trial – trial accounts only send to verified numbers and add a Twilio prefix to messages.
  • Compliance with the destination country's rules: A2P 10DLC registration for the US; Twilio doesn't sell local numbers in Turkey, so you need an international number or a pre-registered alphanumeric sender ID.
  • Recipient consent for marketing texts – and in Turkey, an İYS record for commercial messages to consumers.

What you enter when connecting

  • Account SID *
  • Auth token *
  • From number *

Good to know

  • SMS containing Turkish characters (such as ş, ğ, ı) is split into 70-character segments, each billed separately; with standard characters a segment holds 160. OrqLabs sends at most 1,600 characters per message.
  • Alphanumeric sender IDs are one-way: recipients can't reply to them, so a two-way chat needs a number.
  • On a trial account, broadcasts don't work and only numbers on the Verified Caller IDs list receive messages.
  • Twilio charges SMS fees directly to your own Twilio account.

Frequently asked questions

Can I send SMS to Turkey with Twilio?

Yes, with an international number or a pre-registered alphanumeric sender ID. Twilio doesn't sell local Turkish numbers, and commercial SMS to consumers requires an İYS record.

Why is Turkish SMS more expensive?

Turkish characters split messages into 70-character segments, each billed separately. Simplifying characters (ş→s, for example) reduces the number of segments.

Does the chatbot work over SMS?

Yes. Once Twilio's incoming-message webhook points to OrqLabs, texts to your number land in the Inbox and the AI Chatbot replies.

How do I handle people who want to opt out?

Add an instruction such as “Reply STOP to opt out” to your messages. When someone replies STOP, DUR, İPTAL or ÇIK, OrqLabs marks them as opted out and leaves them out of later campaigns.

Get started with OrqLabs

Build your first workflow today

Start on the free plan: connect your accounts, pick a template and stay in control with approval steps. No credit card required.

Start freeExplore the product