#Transfer Settings

#Overview

Transfer Settings lets a Client Administrator manage the transfer destinations a project's agent can hand calls off to. Each project keeps its own list of destinations, and each destination has its own phone number, availability, ring timeout, and failed-transfer alert recipients.

The section is exposed at /settings?section=transfer-settings (transfer-settings is the section's canonical URL key; the panel itself is headed Transfers). It is no longer shown in the visible Client Admin Settings menu, but direct links still open it for authorised users.

For each destination you can set:

• a display name (unique within the project),
• the phone number the agent dials (Australian mobile or landline; the server normalises it to E.164),
• whether the destination is enabled,
• active hours — follow the project's opening hours, always available, or a custom weekly schedule,
• public-holiday handling for that destination,
• a ring timeout between 10 and 60 seconds, and
• failed-transfer alerts by email and/or SMS.

A project can hold up to 10 transfer destinations. Live test calls from the destination editor are not yet available; the Send test call button is shown but disabled.

The panel also shows the runtime publish status, the last-changed timestamp, and provenance of the live configuration, so you can see whether the saved portal copy matches what the runtime is currently using.

Client Managers and partner roles see a read-only summary of the same destinations (with phone numbers masked). Some projects remain partner-managed: when a project requires the partner-managed workflow, the panel stays summary-only for everyone and shows a notice instead of editing controls.

#Prerequisites

• You are signed in to the AiDial portal. See Signing In for instructions.
• Your current session includes at least one in-scope project.
• You are a Client Admin to add, edit, or remove destinations. Client Managers and partner roles can review a summary only, and Client Staff do not receive this Settings section.

#Configuring transfer destinations

1. Select Settings from the sidebar, then open the direct Transfers route at /settings?section=transfer-settings.
2. If more than one project is in scope, choose the project you want to review. Client Administrators use the project switcher in the top bar; a single in-scope project loads automatically.
3. Review the runtime publish status pill and summary, then the list of existing destinations. Each card shows the destination name, masked phone number, current status, schedule summary, and whether failed-transfer alerts are on.
4. To add a destination, select Add transfer destination and complete the destination editor.
5. To change a destination, select Edit on its card. To remove one, use Delete on the card or inside the editor; the removal is applied when you save.
6. In the editor, set the destination name, phone number, active hours, public-holiday handling, ring timeout, and failed-transfer alerts, then select Add destination (new) or Save destination (existing) to stage the change.
7. Review the staged cards, then select Save destinations to persist all changes for the project. Use Discard changes to revert to the last saved state.
8. If the page reports that the destinations changed elsewhere, select Reload latest, review the current state, and apply your change again.

#Field Reference

#Empty State

If your session has no in-scope projects, the panel displays No in-scope projects available and does not show editing controls.

If your session has multiple in-scope projects and none is selected, the panel asks you to choose a project before loading transfer destinations.

If a project has no destinations yet, the panel shows No transfer destinations yet with an Add transfer destination action for Client Administrators.

If the selected project's destinations cannot be loaded, the panel shows a temporary unavailable state with Reload latest. If your role is restricted, the panel shows a restricted message and does not show destination detail or editing controls.

#Security and Scope

The browser uses your signed-in portal session and calls the portal server routes at /api/settings/transfer-settings (project scope) and /api/settings/transfer-destinations (destination read and save). You do not need to enter or send an API key. The portal server resolves project scope, enforces your role, and forwards the session bearer token to AiDial.

Transfer destinations are checked against your role and project scope. The full destination phone number is only returned to Client Administrators; summary roles receive a masked number. Saves are rate-limited, and out-of-scope project requests or disallowed writes fail without exposing other project identifiers.

#Common Issues

#Related Pages

• Settings Overview
• Opening hours
• Call Limits
• Role Reference