E.164 is an international telephone numbering standard that defines the format for globally unique phone numbers on the Public Switched Telephone Network (PSTN). Established by the International Telecommunication Union (ITU), this standard ensures that phone numbers are structured in a consistent and internationally recognizable format.
Under the E.164 format, phone numbers begin with a plus sign (+), followed by the country code and the national subscriber number, without spaces, dashes, or special formatting characters. For example: +13105555555
In this example:
- +1 represents the country code (United States).
- 3105555555 represents the national number.
E.164 allows up to 15 digits in total and ensures that each phone number is globally unique. This format is widely used in telecommunications systems, APIs, SMS gateways, and dialing platforms to maintain consistency and avoid ambiguity across international networks.
In CallTools, storing phone numbers in E.164 format helps ensure accurate dialing, proper routing, and compatibility with carriers and integrations.
Key Pointers
- International phone number standard.
- Begins with a “+” followed by country code.
- Maximum of 15 digits.
- Ensures globally unique numbering.
E.164 standardization supports reliable global communication by providing a consistent, carrier-compatible phone number format within CallTools and across telecom systems worldwide.
End Time refers to the specific timestamp at which a particular operation, event, or activity concludes within the CallTools platform. It marks the completion point of a process and is commonly used in reporting, logging, and workflow tracking to define when an action officially finished.
End Time can apply to a variety of system activities, including phone calls, campaigns, agent status sessions, data tasks, automations, and scheduled events. For example, in call reporting, the End Time represents the exact moment a call disconnects. In scheduled campaigns or system operations, it indicates when the task or activity stopped running.
When paired with a corresponding Start Time, End Time allows the system to calculate duration-based metrics such as total call time, session length, or task runtime. These timestamps are critical for accurate reporting, performance analysis, auditing, and troubleshooting.
Because End Time is system-generated, it provides a reliable and consistent record of operational activity across dashboards and reports.
Key Pointers
- Marks when an operation or activity concludes.
- Used in reporting and system logs.
- Works alongside Start Time to calculate duration.
- Applies to calls, campaigns, tasks, and more.
End Time provides a precise reference point for understanding when activities finish, supporting accurate reporting and operational transparency within CallTools.
End Weekday is a configuration option within Time Conditions in CallTools that allows administrators to define which day of the week should be considered the end of the operational week for scheduling and routing purposes.
Time Conditions are used to control when certain actions occur, such as when campaigns can dial, when inbound routes are active, or when specific workflows should run. The End Weekday setting works alongside the Start Weekday to define a structured weekly window in which these rules apply. By selecting an End Weekday, administrators can customize the active range of days that constitute the system’s “week.”
For example, some organizations may define their operational week as Monday through Friday, while others may operate Sunday through Thursday. The End Weekday setting allows flexibility to align system behavior with business schedules, staffing models, or regional workweek standards.
This setting ensures that time-based rules are applied consistently and accurately according to your defined calendar structure.
Key Pointers
- Located within Time Conditions.
- Defines the last active day of the week.
- Works with Start Weekday settings.
- Impacts scheduling and routing logic.
End Weekday provides structured control over weekly time-based rules, ensuring CallTools operations align precisely with your organization’s scheduling requirements.
Errors in CallTools refer to the total number of failed or unsuccessful execution attempts recorded within a specific process, report, or operational context. This metric tracks instances where a system action did not complete as expected due to configuration issues, data conflicts, permission restrictions, or other technical interruptions.
Errors may occur across various areas of the platform, including automations, API requests, dialing attempts, data tasks, integrations, and system workflows. For example, an automation may fail if required conditions are not met, an API call may return an error due to invalid parameters, or a dialing attempt may fail because of an unavailable caller ID or restricted number.
The error count is typically displayed in reports or logs to help administrators and managers identify operational issues. Monitoring this metric allows teams to diagnose problems, refine configurations, and improve system reliability.
It is important to note that Errors measure failed executions, not successful attempts or partial completions.
Key Pointers
- Represents total failed execution attempts
- Applies to automations, API calls, dialing, and more
- Used in reporting and troubleshooting
- Helps diagnose operational issues
Errors provide critical visibility into system performance, enabling teams to quickly detect, investigate, and resolve issues within the CallTools environment.
Errors Today refers to the total number of failed or unsuccessful execution attempts recorded within the current calendar day. This metric provides a real-time snapshot of how many system actions have encountered errors during that day’s operational window.
Unlike the broader Errors metric, which may reflect totals across a selected reporting range, Errors Today focuses specifically on daily activity. The count automatically resets at the start of a new day, allowing teams to monitor short-term performance and detect issues as they arise.
Errors Today may include failures related to automations, API calls, dialing attempts, data tasks, integrations, or other system-triggered processes. For example, an automation may fail due to missing required fields, an API request may return an invalid response, or a dialing attempt may be blocked due to configuration rules. Each unsuccessful execution contributes to the daily error count.
By reviewing Errors Today, administrators can quickly identify abnormal spikes or operational disruptions and take corrective action before they impact larger workflows.
Key Pointers
- Tracks failed execution attempts for the current day
- Automatically resets daily
- Applies to automations, API calls, dialing, and more
- Supports real-time monitoring and troubleshooting
Errors Today provides immediate visibility into daily system performance, helping teams maintain stable and efficient operations within CallTools.
Executions in CallTools refer to the total number of completed tasks, processes, or actions within a given reporting scope. This metric represents how many times a system-triggered event has run to completion without error.
Executions can apply to a variety of operational activities across the platform, including automations, API requests, data tasks, workflow actions, and other system-driven processes. For example, if an automation rule is triggered 500 times and completes successfully each time, those 500 instances would be counted as executions.
Unlike error-based metrics, Executions focus specifically on successful outcomes. This makes it a valuable performance indicator when evaluating automation efficiency, integration stability, and overall system throughput. When reviewed alongside metrics such as Errors or Errors Today, Executions provide context for understanding success rates and operational reliability.
Because this count reflects completed tasks, it is commonly used in dashboards and reports to measure activity volume and system productivity over a selected timeframe.
Key Pointers
- Represents successfully completed tasks
- Applies to automations, API calls, and system processes
- Used in reporting and performance monitoring
- Helps assess operational efficiency
Executions provide clear visibility into completed system activity, helping teams evaluate productivity and maintain reliable performance within CallTools.
Executions Today refers to the total number of completed tasks, processes, or system actions recorded during the current calendar day. This metric provides a real-time view of daily activity, reflecting how many operations have run to completion without errors within that day’s timeframe.
Unlike the broader Executions metric, which may represent totals across a selected reporting range, Executions Today focuses exclusively on activity occurring within the present day. The count automatically resets at the start of a new day, allowing administrators and managers to monitor daily system performance independently from historical totals.
Executions Today may include completed automations, API calls, data tasks, dialing-related processes, workflow actions, or other system-triggered events. For example, if an automation rule triggers 300 times in a single day and each instance completes successfully, those 300 instances contribute to the Executions Today count.
This metric is especially useful for identifying trends, monitoring workload spikes, and ensuring daily operations are running as expected.
Key Pointers
- Tracks completed tasks for the current day
- Resets automatically each calendar day
- Applies to automations, API processes, and system tasks
- Supports daily performance monitoring
Executions Today provides immediate visibility into daily system output, helping teams maintain consistent and efficient operations within CallTools.
Existing Caller Kick From Empty Queue is a configuration option within Queues in CallTools that determines how the system handles callers who are already waiting in a queue when no eligible agents are available. This setting controls whether callers remain in the queue or are automatically removed under certain agent availability conditions.
In inbound call environments, there may be times when no agents are logged in, all agents are unavailable, or members are paused. Without proper configuration, callers could remain waiting indefinitely. This feature ensures queue behavior aligns with your operational policy.
The available options include:
- Yes: Callers will be dismissed from the queue if no agents are logged in.
- No: Callers will remain in the queue even if no members are logged in.
- Strict: Callers will be removed if there are no logged-in agents or if all agents are unavailable.
- Loose: Similar to Strict, but paused queue members are not considered unavailable, allowing callers to remain queued if paused members exist.
Key Pointers
- Located in Queue settings
- Applies to callers already waiting in queue
- Controls behavior when agents are unavailable
- Offers Yes, No, Strict, and Loose options
Existing Caller Kick From Empty Queue ensures predictable and controlled queue management, helping maintain a consistent caller experience within CallTools.
Extension in CallTools refers to the internal dialing number assigned to a specific PBX destination. It acts as a shortcut number that can be manually dialed or referenced within the system to route calls to a particular endpoint.
Extensions are commonly associated with destinations such as an agent’s web phone, a queue, a conference room, an IVR (Interactive Voice Response) menu, a voicemail box, or other internal routing points. Instead of dialing a full external phone number, users within the system can simply dial the assigned extension to reach that destination directly.
Extensions are a fundamental component of PBX configuration and internal call management. They simplify call transfers, enable quick internal dialing between users or departments, and support structured routing within inbound and outbound call flows. For example, an inbound route may direct callers to extension 200 for Sales, while internal users can dial that same extension to transfer a live call to the Sales queue.
Because extensions are system-based identifiers, they help maintain organized call routing without relying on external phone numbers.
Key Pointers
- Internal dialing number within the PBX
- Assigned to destinations like agents, queues, IVRs, voicemail, and conferences
- Used for transfers and manual dialing
- Essential for organized call routing
Extensions provide a streamlined way to connect calls within CallTools, ensuring efficient and structured internal communication.
External Phone Numbers in CallTools are predefined PBX destinations that allow calls to be routed or transferred outside of the internal system. These destinations represent real-world phone numbers that exist beyond the CallTools environment, such as mobile phones, office landlines, or third-party call centers.
Once configured, External Phone Numbers can be used in several ways within call flow design. They may serve as routing endpoints for inbound calls, transfer destinations during live conversations, failover options in “follow me” scenarios, or controlled transfer targets within campaigns. For example, if a queue has no available agents, a call can be routed to a designated external number as a backup. Similarly, administrators can restrict agent transfers to approved external numbers to maintain call control and compliance.
External Phone Numbers function as fixed PBX destinations, meaning they are configured once and then selectable throughout routing and queue settings. At this time, only United States phone numbers are supported, excluding very high-cost rate areas.
Key Pointers
- Configured as PBX destinations
- Used for routing, transfers, and failover
- Supports controlled external call handling
- Limited to eligible U.S. phone numbers
External Phone Numbers provide flexible call routing options while maintaining administrative oversight within the CallTools PBX system.