Organization settings reference

Manage a ThunderPhone organization: profile, dashboard language, members, outbound confirmation, blocked callers, webhooks, SSO, API keys, alerts, billing, spending limits, and history.

Open Organization Settings (/dashboard/organization) to manage the active organization and your own account. Settings are split into six tabs; your role determines which controls you can change.

My account#

The My account tab contains settings for the signed-in user, not the whole organization:

• First name, last name, email, and an avatar URL.
• Dashboard display language.
• macOS desktop app download.
• Add, verify, list, and remove passkeys.
• Cookie preferences.
• Sign out on the current device.

When you sign in through organization SSO, the identity provider manages your email and it is read-only here. See Account & security for the detailed passkey and profile workflow.

General#

Outbound calling compliance#

For organizations where the requirement applies, an owner or admin must review and record the one-time outbound-calling confirmation before agents can place outbound calls. Members can see that action is required but cannot submit it. See Outbound calling laws.

Reporting#

Time zone, weekly business hours and the organization's own test numbers. Business hours decide which calls count as after hours in the call report numbers on Home, in each agent's Calls tab and in Client Portals, and the Business hours filter in Call History. With no days checked, after-hours calls are not tracked and every call counts as business hours. Calls from or to a test number are left out of every report count, and out of portal lists, Overview numbers and CSV exports; they cannot be opened in a portal. An agent can carry its own time zone and hours under Reporting in the agent builder, which then apply to that agent's calls only.

Owners and admins change these settings under General → Reporting. Choose the time zone and check each open day, then enter its opening and closing times. Under Test numbers, enter each number and choose Add. Then choose Save reporting settings. Until a time zone is saved, reports use UTC; the page suggests your browser's zone as an unsaved change. Once any business hours are set, unchecked days count as after hours for calls using that schedule.

Configure reporting through the API#

Owners and admins can PATCH /v1/orgs/{id}/ with timezone, business_hours and excluded_numbers:

• timezone: an IANA time zone name such as America/Los_Angeles, up to 64 characters.
• business_hours: weekday keys mon through sun, each a list of at most four {start, end} windows in 24-hour HH:MM, with each end later than its start. {} means no after-hours split.
• excluded_numbers: up to 50 phone numbers, stored in E.164 form. A bare 10-digit North American number gets the +1 country code.

curl -X PATCH https://api.thunderphone.com/v1/orgs/42/ \
  -H "Authorization: Bearer sk_live_YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "timezone": "America/Los_Angeles",
    "business_hours": {
      "mon": [{"start": "09:00", "end": "17:00"}],
      "sat": [{"start": "10:00", "end": "14:00"}]
    },
    "excluded_numbers": ["+14155550199"]
  }'

Blocked callers#

Numbers on this list cannot reach your agents. When a blocked number calls any of your organization's phone numbers, ThunderPhone hangs up before an agent answers and does not bill the call. It still appears in Call History, as a failed inbound call with end reason Blocked caller. Calls with a withheld or anonymous caller ID are never matched, and outbound calls to a blocked number are not affected. A caller you block during a call is not cut off; the block applies from their next call.

Every member can see the list; owners and admins change it under General → Blocked callers:

• To block one number, enter it with an optional note and choose Block number. Use + and the country code; a national format such as (415) 555-0123 also works when all of your organization's phone numbers are in one country.
• To block many at once, choose Paste a list, paste up to 500 numbers (one per line or separated by commas) and submit. The result shows how many were added, already blocked or invalid, and lists the invalid entries.
• To unblock a number, choose Remove on its row and confirm.

You can also open an inbound call in Call History and choose Block this caller. An organization can block up to 10,000 numbers. To manage the list through the API, see Blocked Callers.

Organization identity and membership#

The organization card shows the organization id, your membership role, and the editable organization name. The team card combines active members and pending invites.

Owners and admins can invite a Member or Admin, revoke a pending invite, change eligible member roles, and remove members. Invites are email-specific and expire after seven days. See Invite your team.

The danger zone lets an eligible user leave an organization or permanently delete it. Deletion removes the organization's agents, numbers, call history, and billing data and cannot be undone.

To delete your own account, open the Account tab and choose Delete account. The dialog lists the organizations that will be deleted (those where you are the only member) and the ones you will leave. API keys you created in an organization you leave are revoked. Deletion is blocked while you are the only owner of an organization that has other members (make someone else an owner first), while you created custom voices in an organization that stays, while a call is in progress, or while a legal hold applies; the dialog lists whatever is blocking it. It cannot be undone.

Default webhook#

Set one legacy webhook URL to receive events from all web widgets and phone numbers in the organization. For per-endpoint secrets, subscriptions, delivery history, and retries, use the recommended webhook endpoints instead.

Enterprise SSO#

Configure one or more SSO connections, allowed email domains, just-in-time provisioning, the default role, and optional group-to-role mappings. The security policy can require SSO, allow emergency password access for admins, and require passkeys for organization access. See SSO.

Keys#

The Keys tab manages secret sk_live_ server API keys. Each row shows the name, prefix, active/revoked state, creation time, last use, and revocation time.

The complete secret is displayed only once, immediately after creation. Copy it then and store it in a secret manager. Revocation is permanent and stops every integration using the key. See API keys.

Publishable pk_live_ keys belong to Web Widgets, because they are origin-restricted browser credentials rather than server keys.

Alerts#

Create metric rules for success rate, failure rate, average score, call volume, or suite regressions. A rule includes:

• Comparator and numeric threshold.
• Evaluation window from 1 to 720 hours.
• Up to 10 email recipients.
• Optional Slack incoming-webhook URL.
• Optional developer-webhook delivery.
• Cooldown in whole minutes and enabled state.

The same tab lists recent firings. See Alerts.

Billing Settings#

Manage the organization balance and payment behavior:

• Add or replace the default payment card.
• Add funds manually.
• Enable auto top-up and set its threshold and refill amount.
• Set or remove a monthly spending limit.

The monthly limit pauses new calls and usage at 100% and remains active even when auto top-up is off. See Pricing and Billing and top-ups.

Billing History#

Use Billing History to inspect balance and spend for Today, 7 days, 30 days, 90 days, or all time. It includes:

• Balance trend.
• Billing mix across call charges, reports, phone-number fees, and top-ups.
• Top agent spend.
• Transaction table with date, category, description, type, amount, and resulting balance.
• Category filtering and CSV or JSON export of the displayed history.

The dashboard reports when only the most recent transactions are displayed; older rows beyond that limit are also absent from the export. The Billing API supports programmatic pagination.