Voice & SMS

Voice & SMS connects Leena AI to a phone number, so employees can text the assistant or call it.

Both channels share the same number. Setup runs through four sections in order, and each depends on the one before it.

⚠️

Voice 1.0 is being retired

Voice 1.0, the Retell-based pipeline, is deprecated and will be retired by January 2027. Voice 2.0 will then be turned on by default for every assistant still on voice 1.0.

If your assistant is on voice 1.0, switch your UAT assistant to voice 2.0 now and test it against your real use cases — see Voice orchestrator settings → Switching to voice 2.0. Phone calls on voice 2.0 currently need a Leena AI number; see Phone call.

Where to find it

Open the Admin Console, then go to External channels → Voice & SMS.

Before anything is configured, the page offers Start setup.

📘

Each section saves on its own

Sections have their own save actions rather than one save for the page. Complete and save them in order — later sections are blocked until the earlier ones are in place.

The Voice & SMS page before setup, with the message Setup voice & SMS and a Start setup button

Voice & SMS before setup

Before you start: the number is yours

In production, the phone number belongs to your organisation, not to Leena AI:

  • You provision and own the number in your own Twilio account, in every country you deploy.
  • Twilio bills you directly for telephony usage — number rental, call minutes, SMS, SIP trunking and any registration fees. Leena AI doesn't resell or invoice telephony.
  • The number must be a Twilio number. Numbers held with other carriers can't be connected; the number has to be on your Twilio account. The same applies to SMS sender IDs and short codes.
  • Country registrations are in your organisation's name. Business documents, US messaging registration and India's DLT registration are tied to the legal entity that owns the number. See Country requirements — some take weeks, so start them first.

What Leena AI does: connects to your Twilio account, verifies the number belongs to it, configures the SMS webhooks on the number for you, and runs the assistant on every call and text.

⚠️

The Leena AI account is for POCs and demos only

The Leena AI account type runs on Leena AI's Twilio account and number, so you can try the channel without any telephony setup. It isn't supported for production, in any country.

Move to your own Twilio account before employees rely on the number.

⚠️

Voice 2.0 phone calls currently need a Leena AI number

Phone calls on voice 2.0 run only on numbers from the Leena AI account for now. Numbers on your own Twilio account keep phone calls on voice 1.0 — SMS is unaffected.

Until your own Twilio account is supported on voice 2.0, keep production phone numbers on voice 1.0, and try voice 2.0 phone calls on a UAT assistant with a Leena AI number. We'll update this page when own-account numbers are supported.

1. Twilio credentials

Choose an Account type:

OptionWhat it means
Leena AIUses Leena AI's Twilio account and number. POCs and demos only — not supported for production. Currently the only option for phone calls on voice 2.0
Own Twilio accountUses your organisation's Twilio account and number. Required for production, and the recommended route for security and monitoring. Phone calls run on voice 1.0 for now

Using your own account requires two values from the Twilio console:

  • Account SID
  • Auth token
Setup voice & SMS step 1, Twilio credentials, with Account type set to Own Twilio account and Account SID and Auth token fields

Step 1: Twilio credentials

Save this section before continuing. Attempting to verify a number first is refused, with a prompt to choose and save a Twilio account.

⚠️

Account type locks once a number is verified

While a verified phone number is connected, the account type can't be changed. To change it, use Edit number from the configuration view — which disconnects the current SMS and voice setup.

Moving from a POC on the Leena AI account to production therefore means reconnecting on your own account with a number from that account, then saving the SMS and phone call sections again. Don't share the POC number with employees — production runs on your own number.

2. Select phone number

Enter the Phone number to use for SMS and inbound voice calls. It must be linked to the Twilio account from section 1, and must be in E.164 format — for example, +14155551234.

Each assistant connects to one number, which handles both SMS and calls, and a number can be connected to only one assistant. What a number can do depends on its type and country — check Country requirements before you buy one.

Verify confirms the number against Twilio. A verified number shows a verification indicator, and Edit phone number changes it later.

If verification fails, check the number is correct and actually present on that Twilio account.

3. SMS channel

Configures inbound SMS and delivery tracking.

Configure inbound SMS sets both the inbound SMS webhook and the delivery tracking callback on your Twilio number automatically. No manual work in the Twilio console is needed — this is the step people most often try to do by hand.

The Inbound webhook must be configured before this section will save.

SettingWhat it does
Delivery trackingTracks SMS delivery status via Twilio status callbacks
Show disclaimer in messageExtends the disclaimer to text responses. Only takes effect when the disclaimer is enabled in Orchestrator settings

Send a test SMS sends a real message to a number you supply, confirming the whole path works before employees rely on it.

If the test SMS doesn't arrive on a US number, check that the number's toll-free verification or A2P 10DLC registration is approved. US carriers block or filter texts from unregistered numbers.

4. Phone call

Enable inbound calls lets employees interact with Leena AI by calling the number. What this section asks for depends on the voice version the assistant runs on, set under Orchestrator → Voice.

This section can't be saved until a phone number is configured in section 2. A number that another assistant already uses is refused.

On voice 2.0

No SIP trunk details are needed. When you save with inbound calls enabled, Leena AI attaches the number to its voice 2.0 SIP trunk, which routes calls to the speech-to-speech model. Turning inbound calls off takes the number off that trunk.

The number must be on the Leena AI account type. With Own Twilio account selected, saving with inbound calls enabled is refused, and the phone channel stays as it was.

📘

Switching moves the number

When an assistant with phone calls enabled is switched to voice 2.0, its number moves to voice 2.0 at the same moment — no change is needed here. If the number is on your own Twilio account, the switch is refused instead and the assistant stays on voice 1.0.

On voice 1.0 (deprecated)

Calls are delivered via Retell, which needs SIP trunk details:

FieldWhat it is
Termination URIThe SIP termination endpoint
SIP trunk user nameThe SIP trunk username
SIP trunk passwordThe SIP trunk password
⚠️

The termination URI must be a Twilio SIP domain

It has to end in pstn.twilio.com or sip.twilio.com — for example, mycorp.pstn.twilio.com. Anything else is rejected.

This is the Elastic SIP Trunking termination URI from your Twilio account, not the phone number or the account SID.

Voice behaviour itself — the assistant's voice, instructions and speech settings — is configured separately under Orchestrator → Voice. This section only establishes the connection.

Languages on phone calls

VersionLanguages
Voice 2.0Callers can speak any language Leena AI supports, and switch partway through the call. The assistant speaks its default language until the caller is identified, then switches to the employee's language. See Voice orchestrator settings → Languages
Voice 1.0English only. Speech recognition is set to US English, whatever country the number is in

For employees who don't speak English, a phone number on voice 1.0 isn't usable — plan their rollout on voice 2.0.

Identifying callers

Connecting a number doesn't tell the assistant who is calling. That's handled by the phone call channel's authentication, set per assistant — full details in Phone call → Authenticating the caller. It works the same on voice 1.0 and voice 2.0.

MethodHow it worksDepends on
OTPMatches the caller's number to the phone fields on their employee record, then texts a six-digit code to itAccurate phone numbers in your HR system of record, for every country, and a text being able to reach the caller
KBAThe caller enters digits from two employee-profile fields on the keypad, such as the last 4 digits of their employee IDThose fields being populated on employee records
NoneNo identificationLow-sensitivity use only

KBA doesn't depend on the caller's phone number or on SMS, so it suits shared or desk phones, employees whose numbers change often, and countries where texting is restricted.

OTP and KBA prompts are spoken in English on voice 1.0. On voice 2.0 they are spoken in the assistant's default language, because the caller isn't identified yet; once they are, the call moves to the employee's language.

Country requirements

Regulators and carriers decide what each number type can do and what you must register before using it. The essentials for common deployments are below.

CountryNumber to useCallsTexts
USToll-free (+1 8XX)YesYes, once toll-free verification is approved
IndiaToll-free (+91 800)Inbound only, from Indian phones onlyNo
GermanyMobile (+49 157 / +49 158)YesYes
📘

Twilio's country pages are the source of truth

This section summarises Twilio's published guidelines as of October 2026. It isn't legal advice, and requirements change. Before buying numbers, check the country in Twilio's phone number regulatory requirements (document requirements by number type, for every country) and voice and SMS guidelines.

United States

  • Toll-free numbers (800, 888, 877, 866, 855, 844, 833) handle calls and texts. Before one can text US or Canadian phones, it must pass toll-free verification, which reviews your business and messaging use case. See Twilio: toll-free verification.
  • Local numbers (10DLC) also handle calls and texts, but texting requires A2P 10DLC registration: a brand (your company, identified by its business tax ID) and a campaign describing the messages you send. See Twilio: A2P 10DLC.
  • Incoming calls need no messaging registration on either type.

We recommend a single toll-free number for both calls and texts.

India

  • Twilio's only Indian number type is toll-free (+91 800), and it is inbound voice only — it can't place calls, or send or receive SMS.
  • It can only be reached from Indian phone numbers, dialled as 000 800 XXX XXXX: no +91, and the 000 prefix is required. Calls from outside India won't connect. Include this dialling format in employee communications.
  • The address registered for the number must be outside India.
  • Because the number can't send SMS, links the assistant would normally text during a call aren't delivered; employees find them in the call transcript in the web app.
  • Callers who speak Hindi or another Indian language need the assistant on voice 2.0 — voice 1.0 is English only. On voice 2.0, Hindi mixed with English words is handled as Hindi.
  • OTP codes don't come from the toll-free number. Codes to Indian mobile numbers go through a separate DLT-registered SMS route. Confirm the sender set-up for your deployment with Leena AI before choosing OTP; otherwise use KBA.
  • SMS to Indian mobile numbers is regulated separately. Business SMS on India's domestic route requires DLT registration by your Indian entity — the entity, the sender ID (header) and every message template, such as an OTP text — and Indian operators don't support SMS on standard long numbers. This registration sits with your organisation.

See Twilio's India pages: regulatory, voice, SMS, and calling an Indian toll-free number.

Germany

  • German numbers are not available to individuals. You need a business entity, evidenced by a commercial register excerpt (Handelsregisterauszug) or trade licence, plus a business registration number or VAT/tax number.
  • Mobile numbers (+49 157 / +49 158) need a business address in Germany. Recommended — they handle calls and texts.
  • Local numbers need an address within the area covered by the number's prefix; PO boxes aren't accepted. Check the number's SMS capability in Twilio before choosing one.
  • Toll-free numbers (0800) are allocated by the national regulator, BNetzA, on application, and need a German address. Twilio activates the number once it's allocated, so this has the longest lead time.
  • German-speaking callers need the assistant on voice 2.0 — voice 1.0 is English only.

See Twilio: Germany regulatory.

Other countries

Start from Twilio's regulatory requirements index. For each country it lists the available number types and the documents each one needs, and links to that country's voice and SMS guidelines.

Short codes

Short codes are SMS-only — they can't receive calls. Since each assistant uses one number for both calls and texts, a short code can't be the assistant's number. Short codes also need their own carrier approval, which takes weeks.

Use one regular number per country instead, as in the table above.


Did this page help you?