Skip to main content
Version: 0.9.14

Team overview

Path: /settings → Team tab

The Team tab surfaces the team's identity, resilience defaults, the base numbers assigned to it, team-scoped egress trunks and pools for outbound transfers, AWS Secrets Manager configuration for secret storage, and call recording configuration. Secrets Manager is the foundation for SECRET-type variables.

Team info​

FieldEditableDescription
Team NameNoSet by a superadmin. Read-only here.

Base numbers​

Lists base numbers assigned to your team by a superadmin. Per row:

FieldEditableDescription
NumberNoThe phone number.
DescriptionNoSet by superadmin.
Header Manipulation ConfigsADMINTeam-specific configs (multi-select). Default platform configs are applied separately.

AWS Secrets Manager​

FieldRequiredDescription
AWS RegionYesRegion where secrets live. Default eu-central-1.
Secrets Manager KeyYesPath/key for your team's secrets (e.g. delphi/teams/<team>/variables).
AWS Assume Role ARNNoCross-account setups only. arn:aws:iam::<ACCOUNT_ID>:role/<ROLE_NAME>. Empty if same account.
AWS Account IDAutoExtracted from Role ARN.
Complete ARNAutoFull Secrets Manager ARN with copy button.

Same-account vs cross-account​

  • Same-account — Delphi shares your AWS account. Only region + key required.
  • Cross-account — Delphi assumes a role into your account. Each team's secrets isolated; CloudTrail audit on your side; you can revoke at any time.

For the IAM role setup, see AWS security setup.

Call recording​

FieldRequiredDescription
Recording S3 BucketNoBucket for recordings. Required if recording is used.
Recording AWS RegionNoDefault eu-central-1.
Recording IAM Role ARNNoCross-account setups only.

Recording must also be enabled per-app. When configured, the platform installs an S3 lifecycle rule expiring recordings under recordings/ after 180 days. Transcript retention follows the same app Recording toggle: when recording is on, full transcript text is stored with the S3 artefact regardless of platform PII redaction. See Conversations → Recording and transcript retention.

Resilience defaults​

Team admins can either inherit the platform resilience defaults or enable a team override. The effective settings are merged in this order:

  1. Platform defaults from Platform settings.
  2. Team override on this tab, when enabled.
  3. Flow-level provider and error-handling settings in the Flow Designer.

Use team overrides when one tenant needs different provider timeout/retry defaults, bot-delay comfort messages, or failover transfer/hangup behavior from the platform baseline. Leave the override off when the team should follow platform policy.

Egress (outbound) routing​

Team admins configure reusable outbound SIP routing for number transfers. The Egress section uses the same Trunks | Pools layout as platform admin, scoped to your team.

Sub-tabWhat it manages
TrunksIndividual carrier or PBX destinations — SIP URI, transport, authentication, caller ID, codec preferences, and links to team base numbers.
PoolsNamed routing sets that group one or more trunks for round robin or priority / failover transfer behavior.

Trunks are the building blocks; pools are what flows, managed LLM callbacks, and failover policies reference by routing key (routeId). Full sip: or sips: URI targets bypass pool lookup and route by URI host instead.

How this connects to transfers​

Outbound transfers need a path from Delphi to your carrier or PBX:

  • Number or tel: targets — require egress. Set an Egress Base Number on the endpoint, then either link trunks to that base number or create a pool and select it in flow transfer settings (Egress route / routingPool). With no pool selected, the default base-number pool uses trunks linked directly to the base number.
  • sip: / sips: targets — route by URI host; pools are not used for those transfers.
  • Restrictions still apply — team transfer-restriction overrides and platform policy are checked before TelPro places the outbound leg.

Full runtime detail, failure modes, and Kamailio/Redis behavior are in Egress routing.

Pool and trunk changes auto-sync to TelPro. You do not need a manual re-sync after ordinary edits.

Typical team workflow​

  1. Create the trunks your carriers require (digest, registration, TLS mutual, and so on).
  2. Open Pools → New → set Name, Route ID, base number, strategy, and member trunks with priorities.
  3. Reference the pool from flow transfer settings or managed callback fields such as routingPool / transferRoutingPool.
  4. Verify with a test transfer and inspect the conversation Debug tab SIP ladder.

Platform-wide egress objects (no team owner) are visible here when your deployment uses shared routing. SUPERUSERs manage those from Egress routing in Admin Settings.

Workflows​

Configure Secrets Manager​

  1. Cross-account: finish the AWS security setup.
  2. Set Region + Secrets Manager Key.
  3. Set the Assume Role ARN (cross-account only).
  4. Save and verify the Complete ARN.
  5. You can now create SECRET variables.

Configure call recording​

  1. Enter the S3 bucket name (+ region if not the default).
  2. Set the Recording IAM Role ARN (cross-account only).
  3. Save.
  4. Enable recording on each app that should produce recordings.

See also​