Configuration

Leilani's configuration controls how your agent connects to your SIP environment, how it behaves on calls, who can manage it, and what external capabilities it can use.

Most configuration changes affect new calls, not calls that are already in progress. Connection detail changes are more sensitive: if you update SIP connection settings, you should restart the agent for the change to take effect. Restarting the agent will drop any active calls.

How configuration behaves

At a high level:

• connection settings control how Leilani registers to your SIP environment
• behavior settings control how Leilani speaks, listens, and responds on calls
• access settings control who can administer the agent
• integration settings control what outside resources the agent can use

In practice:

• changes to connection details require an agent restart
• active calls are not reconfigured mid-call
• most non-connection settings are picked up on new calls

Connection details

These settings define how Leilani connects to your SIP stack.

Display Name

The public-facing name of the agent.

Use this for the organization, department, queue, or brand name callers should see or hear. Keep it short and recognizable. The UI enforces a maximum of 32 characters.

Username

The SIP username Leilani uses to authenticate with your PBX.

This is often a numeric extension such as 100 or 5005, but it can also be alphanumeric depending on your system.

Password

The SIP password for the configured username.

Leilani uses this to authenticate to your SIP server. Keep it aligned with the credential configured in your PBX or SIP platform.

Host

The SIP server hostname or IP address Leilani connects to.

This endpoint must be reachable from the public internet. If you use TLS, the server certificate must be issued by a trusted certificate authority.

Leilani's SIP traffic originates from leilani.dev (178.156.204.11), which may need to be allowlisted depending on your network and SIP environment.

Port

The SIP signaling port Leilani connects to.

Use the port that matches your SIP server and transport choice.

Transport (SIP)

The SIP signaling transport:

• UDP
• TCP
• TLS

Choose the same signaling transport your SIP environment expects. If you use TLS, Leilani requires a valid trusted certificate for secure signaling.

Connection best practices

• use a dedicated SIP account for each Leilani agent so call handling is isolated and easier to manage
• keep host, port, and transport aligned with your PBX or SBC configuration
• allowlist Leilani's public source address when your SIP environment restricts inbound connections
• plan connection changes during low-traffic windows, since restart is required and active calls will drop

Instructions

Instructions define the agent's tone, priorities, and behavioral rules.

If you leave Instructions empty, the agent uses Leilani's default receptionist instructions. If you provide custom instructions, they override that default behavior.

Use Instructions to control:

• tone and persona
• what information the agent should collect
• when the agent should transfer, search, or use a Function
• how the agent should prioritize competing goals

The UI supports up to 2,048 characters.

Instruction best practices

• describe outcomes, not just tone
• tell Leilani what it should collect before taking action
• explicitly say when to transfer, send email, search, or stop
• keep instructions operational and specific rather than marketing-oriented

Language

Language is an optional ISO 639-1 language hint for transcription.

This setting improves transcription accuracy and latency for the caller's speech. It does not control the language Leilani responds in by itself; it primarily helps speech recognition perform better.

If most of your callers speak one language consistently, set it here. If call language varies heavily, you may prefer to leave it unset.

Language best practices

• set it when your inbound traffic is mostly one language
• use it to reduce transcription errors in specialized or high-volume environments
• do not rely on it as the only mechanism for multilingual behavior

Voice

Voice controls which synthetic voice Leilani uses when speaking to callers.

Current voices in the UI are:

• alloy
• ash
• ballad
• coral
• echo
• sage
• shimmer
• verse
• marin
• cedar

Voice selection best practices

• choose a voice that matches your brand and call context
• use a calmer voice for service and support flows
• use a more energetic voice for routing, intake, or short transactional flows

Greeting

Greeting is an optional opening message Leilani can read when the call connects.

If Greeting is set, callers hear that exact text before the conversation begins. If Greeting is null or left blank, Leilani starts the conversation based on the provided Instructions instead. The UI supports up to 1,024 characters.

Use Greeting for:

• brand identification
• setting caller expectations
• brief compliance or recording language
• telling the caller what Leilani can help with

Keep it short. Long greetings slow down the start of the interaction.

Greeting best practices

• identify the organization immediately
• tell the caller what kind of help is available
• keep it concise so callers can respond quickly

Max Duration

Max Duration sets the maximum call length in seconds before Leilani hangs up automatically.

The UI allows values from 60 seconds to 14,400 seconds.

Use shorter limits for:

• screening
• intake
• routing
• short transactional flows

Use longer limits for:

• consultative support
• detailed intake
• complex guided workflows

Email

Email is the default recipient for call transcripts.

When set, Leilani sends the transcript from completed calls to this address. If it is blank, no default transcript recipient is configured.

Email best practices

• send transcripts to a shared operations inbox
• use a monitored mailbox for support or quality review
• avoid personal inboxes when multiple people need access

Owner

Owner is the primary administrator for the agent.

If an owner is set, that user becomes the main permission authority for the agent. If it is left empty, any user with access can make permission changes, including adding or removing users or changing the owner.

In the UI, Owner is chosen from the current user list.

Ownership best practices

• assign a clear owner for production agents
• leave it empty only when shared administration is intentional
• keep ownership aligned with the team responsible for the callflow

Users

Users is the list of email addresses that can access the agent.

Enter one email address per line. If this list is left blank, the agent becomes inaccessible from the console.

Access best practices

• use a shared access list for operational continuity
• grant access only to people who need to change call handling or integrations
• avoid leaving the list empty unless you are intentionally locking access during migration or cleanup

Web Search Allowlist

Web Search Allowlist controls whether Leilani can use web search, and which domains it is allowed to search.

Enter one fully qualified domain name per line, such as:

• en.wikipedia.org
• docs.example.com
• support.example.com

If the list is empty, web search is disabled.

If the list contains domains, Leilani can use web search, but results are restricted to those allowed domains.

Web search is not HIPAA eligible. Customers that require HIPAA compliance should not enable or use this feature.

Web search best practices

• allow only trusted domains that contain the information you want Leilani to use
• keep web search disabled for any HIPAA-regulated deployment or workflow
• use product docs, help centers, policy pages, and internal documentation mirrors where possible
• keep the list narrow to reduce low-quality or off-policy responses

Common configuration patterns

Front desk or receptionist

• short greeting
• clear custom instructions
• moderate max duration
• shared transcript email
• directory and Functions configured for routing

After-hours coverage

• greeting that explains hours and next steps
• Functions for follow-up, ticketing, or escalation
• longer max duration if callers need to leave detailed information

Intelligent intake

• custom instructions that collect required fields in order
• language hint set for your caller base
• transcript email sent to the intake team
• web search allowlist enabled only if callers need factual answers from trusted sources

Operational notes

• restart the agent after changing SIP host, port, transport, username, or password
• expect active calls to continue using the configuration they started with
• validate user access and owner settings before handing an agent to a broader team