#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. Client Managers and partner roles keep Transfer Settings in their Settings menu.

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),
• the phone type — Local/landline or Mobile — chosen explicitly for every destination so transfer charges for that number are calculated correctly (the portal never guesses it from the number),
• 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. Open /settings?section=transfer-settings. Client Administrators need the direct link because the section is not listed in their Settings menu; Client Managers and partner roles can select Transfer Settings from the Settings menu.
2. Confirm the project you want to review. Client Administrators choose it with the project switcher in the sidebar, and the portal pins the active project into the page URL. Other roles use the Project picker inside the panel. A single in-scope project is selected automatically.
3. Review the runtime publish status pill and summary, then the list of existing destinations. Each card shows the destination name, phone number, current status, and — while the destination is enabled — its schedule summary. Client Administrators see the full number; Client Managers and partner roles see a masked number.
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 the delete action on the card or Delete destination inside the editor; the removal is applied when you save.
6. In the editor, set the destination name, phone number, phone type (Local/landline or Mobile), active hours, public-holiday handling, ring timeout, and failed-transfer alerts, then select Add destination (new) or Save destination (existing) to stage the change. A new destination has no phone type preselected; the editor stays open and points to the choice until you make it.
7. Failed-transfer alerts can also be managed without opening the editor. Turn on Notify when transfer fails on the card, then add email recipients or a single SMS recipient.
8. 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. Both actions stay disabled until there is an unsaved change.
9. 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 more than one project is in scope and none is selected, Client Managers and partner roles are asked to Choose a project to continue before destinations load. Client Administrators do not normally see this state, because the portal pins an in-scope project into the URL.

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 the error message with a Retry transfer destinations action. One exception is deliberate: when AiDial reports that a destination has no phone type on record, the panel shows a fixed message and a Contact support link instead of Retry, because retrying cannot resolve it (see Common Issues).

Roles that are not entitled to this section — including Client Staff — do not receive it in Settings at all, so the panel is never shown to them.

#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, and their alert recipients are redacted rather than returned as real email addresses and SMS numbers. Reads and saves are both rate-limited per user and project, 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