Use the numbers you already have

Nothing here moves your customers to a new number unless you choose to. Every connection happens in your own accounts.

Texts

  • You have a Twilio number: set “A message comes in” to https://YOUR-AGENT/twilio/sms.
  • You use another provider (Bandwidth, Vonage, Plivo, Telnyx and others): describe its send API once in sms_provider and map its inbound webhook as a source with "as": "sms". No Twilio account needed.
  • A landline or toll-free number you want to keep: ask your carrier about hosted SMS or porting to a texting provider.
  • A personal mobile: do not automate it; carriers block that. Use a business number.
"sms_provider": {"method": "POST", "url": "https://api.example-carrier.com/v1/messages", "headers": {"Authorization": "Bearer env:CARRIER_TOKEN"},
                 "json": {"from": "+15551234567", "to": "{{to}}", "text": "{{text}}"}}

Calls

  • Twilio number: set “A call comes in” to https://YOUR-AGENT/twilio/call.
  • Your existing business line: keep it and forward calls (all, busy or no answer) to a Twilio number that points at the agent.
  • A PBX (3CX, RingCentral, Asterisk, FreePBX): add a SIP trunk to Twilio and route the calls you choose, for example after hours.
  • Other providers: outbound calls through call_provider; inbound menus need Twilio today.

You control the limits

Choose strict, standard or open mode, or set any number yourself, including no limit. Consent, opt-outs, the notices your industry must say, and the kill switch stay on in every mode.

Honest limits

  • Porting is done by your providers and can take days; keep your old number until it completes.
  • US texting requires carrier registration in your provider account.
  • Tested with simulated services; start with one test number you control.

Keep reading