Skip to main content
Call recordings

Call Taking settings

Set how callers are identified, how call scripts and AI triage behave, and the defaults a ticket gets when it is created from a call.

Last updated 26 days ago

These settings tune call taking for your whole organization: how callers are found, how scripts and AI triage behave, and the defaults a ticket gets when it is created from a call. They are read by the create-ticket dialog on the Call Taking screen (see Taking a call) and by the extension's Call tab.

Before you start: the Call Center Operations module must be on, and you need the Administrator or Q-Director Configuration role. Without the module, the Call Taking tab is not shown.

Open and save the settings

  1. Open Q-Director Settings (Q-Director Config in the sidebar).
  2. Select the Call Taking tab in the column on the left. The Settings sub-tab opens first. The other sub-tab, Scripts, is where scripts are written (see Building call scripts).
  3. Change what you need. Each group of options is a card with its own heading. A switch has a one-line hint under its name, and a green switch is on.
  4. Select Save Changes at the bottom of the page, on the right. A message confirms that the settings were saved.
The Call Taking tab of Q-Director Settings with the tab column on the left, the Settings and Scripts sub-tabs, and the Caller Identification and Call Scripts cards
The Call Taking tab: the Settings sub-tab opens on Caller Identification and Call Scripts

This tab has its own Save Changes button. The page header's Save Changes button is not shown while this tab is open. The older Call Taking settings address opens this tab too.

The defaults in the tables below apply until you change them.

How to read the tables

The Effect column says where an option applies: on the Call Taking screen (the web screen your phone system opens), in the create-ticket dialog, in the extension's Call tab, or in more than one. The Call Taking screen and the create-ticket dialog are HaloPSA's web screens; on Autotask and ConnectWise calls are taken in the extension's Call tab, so only the options that apply there matter.

Caller Identification

OptionDefaultEffect
Auto-Search on Phone ParameterOnOn the Call Taking screen, turning it off fills in the caller's number from the link but waits for the agent to search.
Allow Continue Without UserOnTurning it off hides the option to take a call without identifying the caller, on the Call Taking screen (Continue Without Identification) and in the extension's Call tab.
Enable Name Search FallbackOnOn the Call Taking screen, turning it off removes the Name search next to the phone box, so callers are found by phone number only.
Allow Phone Field SelectionOnOn the Call Taking screen, when a caller found by name has a new number, turning it off removes the field choice: the number is saved to the Default Phone Save Field only.
Default Phone Save FieldWork PhoneThe HaloPSA phone field a new number is saved to on the Call Taking screen, unless the agent picks another. Choose from Work Phone, Work Mobile, Home Phone or Home Mobile.

When your phone system opens the Call Taking screen with the caller's number, the screen searches for that number as soon as it opens, unless Auto-Search on Phone Parameter is off. See Connecting your phone system.

Call Scripts

OptionDefaultEffect
Require Script SelectionOffOn the Call Taking screen, with scripts available, the agent cannot create a ticket, link a ticket or end the call until a script is selected (a script that was run, or skipped where skipping is allowed, counts). The screen says Select a call script first.
Auto-Select Default ScriptOnOn the Call Taking screen, turning it off stops the default script being chosen for the agent; they pick one in the script window. A script made for a white-label brand is still chosen for calls from that brand.
Allow Skip ScriptOnTurning it off hides the control that skips a script, in the Call Taking screen's script window (Skip Script and Continue without a script) and in the extension's Call tab (while scripts exist).
Show Step HistoryOnOn the Call Taking screen, turning it off hides the Completed Steps list in the script window.

Select Manage Call Scripts to jump to the Scripts sub-tab.

Context Panels

OptionDefaultEffect
Show Organization TicketsOnTurning it off removes the caller's organization's open tickets from the call, on the Call Taking screen (Organization Tickets) and in the extension's Call tab.
Show Similar IncidentsOnOn the Call Taking screen, turning it off removes Find Similar and stops the similar-incident search that runs while the agent types the issue.
Show Caller/Client ProfilesOnOn the Call Taking screen, turning it off removes the Caller Context panel.
Max Organization Tickets15 (5 to 50)The most organization tickets listed, on the Call Taking screen and in the extension's Call tab.
Max Similar Incidents8 (3 to 20)On the Call Taking screen, the most similar incidents the search asks for and lists.

AI & Triage Recommendations

These options apply to the AI Triage Recommendation in the create-ticket dialog and, where noted, to the AI Triage button next to Issue Description on the Call Taking screen.

OptionDefaultEffect
Enable AI TriageOnWhen off, the create-ticket dialog does not produce an AI recommendation and the Call Taking screen has no AI Triage button.
Auto-Generate TriageOffWhen on, the Call Taking screen requests a recommendation by itself as the agent types the issue, a moment after the typing stops, once the description reaches the minimum length below (never fewer than 15 characters). Each one is an AI request, which is why it starts off. It does not change the create-ticket dialog, which asks for its recommendation when it opens and when you leave Summary or Additional Notes, whenever Enable AI Triage is on.
Show Triage ReasoningOnShows or hides the Why? buttons next to the recommendation, in the create-ticket dialog and on the Call Taking screen.
Auto-Triage Minimum Characters30 (10 to 100)How much text the summary and notes need before a recommendation is requested automatically: when you leave a field or open the dialog in the create-ticket dialog, and, with Auto-Generate Triage on, as the agent types on the Call Taking screen (never fewer than 15 characters there).

Ticket Creation

The Ticket Creation card with the require-team and require-type switches, Include Script Notes, the default dispatch mode, routing mode, impact and urgency, and the Queue for Triage defaults
The Ticket Creation card, with the Queue for Triage Defaults and Scheduling & Estimates groups inside it
OptionDefaultEffect
Require Team SelectionOnA team must be chosen before a Dispatch Now ticket can be created, in the create-ticket dialog and in the extension's Call tab.
Require Ticket Type SelectionOnThe same for the ticket type.
Include Script NotesOnIn the extension's Call tab, sets whether the ticket form starts with Include script notes in the ticket checked. On the Call Taking screen, turning it off leaves the script's questions and answers out of the ticket the screen creates.
Default Dispatch ModeImmediate DispatchWhich mode a new ticket starts in: Immediate Dispatch (Dispatch Now) or Add to Triage Queue (Queue for Triage). Applies to the create-ticket dialog and the extension's Call tab.
Default Routing ModeLoad BalanceThe routing mode a new ticket starts with: Load Balance, Round Robin, Specific Agent or Intelligent Routing. Applies to both.
Default Impact3 - Moderate/LimitedThe impact a new ticket starts with, unless the script or the recommendation sets one. Applies to both. HaloPSA only: these are HaloPSA's own impact levels, so the setting is not shown on Autotask or ConnectWise, where a ticket gets the impact the call taker chose, or else the PSA's own default.
Default Urgency3 - MediumThe urgency a new ticket starts with, unless the script or the recommendation sets one. Applies to both. HaloPSA only, for the same reason: on ConnectWise a ticket gets the severity the call taker chose, or else ConnectWise's own default.

Queue for Triage Defaults

A ticket queued for triage gets this team and ticket type instead of asking for them. These defaults are also used when a finished script creates a ticket queued for triage; see What happens when the script ends. Without them, a ticket that needs them cannot be created and the Call Taking screen asks you to update these settings.

OptionEffect
Default Ticket Type (Queue for Triage)The ticket type for tickets queued for triage. Choose from the ticket types in HaloPSA.
Default Team (Queue for Triage)The team for tickets queued for triage. Choose from the teams in HaloPSA.

Scheduling & Estimates

OptionDefaultEffect
Default to SchedulingOffIn the create-ticket dialog, Schedule Appointment starts checked when a specific technician is chosen.
Show Estimate RangesOnShows the Resolution Estimate and Appointment Duration ranges in the create-ticket dialog when they are available.
Default Appointment CommitmentTentativeThe Commitment a new appointment starts with: Tentative or Firm.

Estimates and appointment booking also need Enable Historical Estimation and Enable Appointment Scheduling on the Dispatch & Scheduling tab of Q-Director Settings. See Dispatch workflow and scheduling settings.

UI & Display

OptionDefaultEffect
Show VIP BadgeOnOn the Call Taking screen, turning it off hides the VIP badge and the VIP color and label of the call's status bar.
Show High Risk BadgeOnOn the Call Taking screen, turning it off hides the High Risk badge and the high-risk color and label of the status bar.
Real-time Workload UpdatesOnOn the Call Taking screen, turning it off stops the agent availability and workload list being refreshed when the live connection pushes a change. The connection light still shows.
Call Duration DisplayElapsed TimeHow the call timer reads on the Call Taking screen. Elapsed Time shows minutes and seconds (05:12) and adds hours once the call passes an hour. Timer (Count Up) always shows hours, minutes and seconds (0:05:12).

Quick Actions

The Quick Actions card with switches for Mark Spam, Transfer and Escalate, of which only Transfer is on
Quick Actions: Transfer is on, Mark Spam and Escalate are off
OptionDefaultEffect
Show "Mark Spam" ActionOffShows Mark Spam in the Call Taking screen's action bar. It ends the call with the outcome Spam and creates no ticket.
Show "Transfer" ActionOnShows Transfer in the action bar. It asks for the destination and notes, and ends the call with the outcome Transferred.
Show "Escalate" ActionOffShows Escalate in the action bar. It asks who the call is escalated to and notes, and ends the call with the outcome Escalated.

The action bar's Resolved and No Action buttons, Transfer, Escalate and Mark Spam all save how the call ended on the call's record, together with the destination and your notes, so the call log shows what happened.

Click-to-Call

OptionDefaultEffect
Default dial prefixEmpty (no prefix)In the extension, goes in front of every number on the Call button of the Ticket and User tabs for your own customers, for example the digit for an outside line. It may hold only digits, * and #, up to 10 characters; the field says why when it does not accept what you typed, and Save Changes saves nothing until it does. A white-label partner's customers use that partner's own dial prefix, and fall back to this one when their partner has none.

Dial prefixes for click-to-call explains how a number becomes a dial string, which prefix wins and when to leave this empty.