Home Getting Started

Getting Started

By Admin General
8 articles

Adding Agents

Agents are the operational users within Support Portal who view, respond to, and manage customer conversations. Every team member who participates in conversation handling requires an agent account provisioned by an Administrator. Operational objective Agent provisioning controls who has access to your workspace and at what permission level. Proper agent management ensures that conversations are handled by authorized personnel and that role-based access aligns with your organization's operational structure. Agent roles Support Portal defines two roles: - Administrator — Full access to all platform features, including workspace settings, agent management, automation rules, and reporting. - Agent — Access limited to conversations, inboxes, Canned Responses, and reporting. Agents can be assigned conversations and participate in team-based workflows but cannot modify workspace-level settings. Provisioning a new agent 1. Navigate to Settings > Agents to open the agent management interface. Alternatively, use the team-member invitation link available on the Dashboard welcome screen. 2. Select Add Agent in the upper-right region of the interface. 3. The provisioning dialog presents the following fields: - Name — The agent's full name. - Email — The email address used for authentication and notification delivery. The system sends an invitation to this address. - Role — Select either Administrator or Agent based on the required permission level. 4. Select Add Agent to confirm. The system displays a confirmation message and adds the agent to the management list. The invited agent receives an email with instructions to complete account activation. Modifying an existing agent 1. Navigate to Settings > Agents and locate the target agent in the list. 2. Select the edit icon (pencil) adjacent to the agent entry. 3. The modification dialog allows updates to the agent's name and role assignment. 4. Select Edit Agent to persist the changes, or Cancel to discard. Removing an agent 1. Navigate to Settings > Agents and locate the target agent. 2. Select the delete icon adjacent to the agent entry. 3. Confirm the removal when prompted. Removing an agent revokes their access to the workspace. Conversations previously assigned to the removed agent may require reassignment. Governance implications Agent provisioning should follow your organization's access control policies. Limit the Administrator role to personnel responsible for platform governance. Regularly audit the agent list to ensure that only active, authorized team members retain access to the workspace.

Last updated on Feb 25, 2026

Adding Inboxes

An Inbox in Support Portal represents a configured connection to a communication channel. Each Inbox receives customer messages from a specific source — such as a website widget, email address, or messaging platform — and surfaces them as conversations on the Dashboard. Operational objective Inboxes define the entry points through which customers reach your organization. Configuring the appropriate set of Inboxes ensures that all relevant communication channels are monitored, that conversations are attributed to the correct source, and that channel-specific settings (such as business hours and greeting messages) are applied consistently. Supported channel types Support Portal supports the following channel types: - Website — Embedded live-chat widget for web properties - Email — Inbound email integration - Facebook — Facebook Messenger conversations - Twitter — Direct messages and mentions - WhatsApp — WhatsApp Business messaging - SMS — Text message conversations - Telegram — Telegram bot integration - Line — Line messaging platform - API — Custom channel integration via the API Creating an Inbox There are multiple navigation paths to the Inbox creation interface: - From the onboarding screen — Select the create-inbox prompt presented during initial workspace setup. - From Settings — Navigate to Settings > Inboxes and select Add Inbox. - From the sidebar — Select + New Inbox beneath the existing Inbox list on the Dashboard sidebar. After selecting a channel type, the system presents a channel-specific configuration wizard. Provide the required parameters for the selected channel and complete the setup steps. Expected system behavior Once an Inbox is provisioned, incoming messages from the connected channel appear as new conversations on the Dashboard. Each conversation carries the Inbox identifier, enabling agents to determine the originating channel at a glance. Inboxes are also available as filter criteria, automation conditions, and reporting dimensions. Channel-specific configuration Each channel type requires distinct configuration parameters. Refer to the dedicated channel setup documentation for detailed instructions: - Website live-chat channel - Email channel - Facebook Messenger channel - Twitter channel - WhatsApp channel - SMS channel - Telegram channel - Line channel - API channel Governance implications The number and type of active Inboxes should reflect your organization's supported communication channels and service-level commitments. Each Inbox introduces an additional source of conversation volume; ensure that agent capacity and routing rules account for all connected channels.

Last updated on Feb 25, 2026

Changing Your Email Address

Overview Support Portal allows operators and administrators to update the email address associated with their account at any time. The updated email address will be used for all subsequent authentication and platform communications. A verification step is required before the new email address becomes active. Operational Objective Update the email address on your Support Portal account and complete the verification process to activate the new address. Procedure Step 1: Access Your Profile Select your avatar in the lower-left corner of the dashboard to open the profile menu. Step 2: Open Profile Settings From the profile menu, select Profile Settings to access your profile configuration. Step 3: Update the Email Address Locate the Email Address field on the Profile Settings page. Clear the current value and provide the new email address. Verify accuracy before proceeding. Step 4: Save the Change Select Update to submit the email address change. A confirmation message indicates the update has been recorded. Step 5: Verify the New Email Address A verification message is sent to the new email address. Open the verification email and select the verification link to confirm the address change. Step 6: Authenticate with the New Email After verification is complete: 1. Sign out of your current session. 2. Sign in using the new email address and your existing password. Expected Behavior - The new email address becomes the primary address for authentication and platform notifications upon successful verification. - Until verification is completed, the previous email address remains active. - Password credentials are not affected by the email address change.

Last updated on Feb 25, 2026

Enabling Browser Push Notifications

Overview Browser push notifications enable operators to receive real-time alerts for new conversations, assigned messages, and other workspace events directly through their browser, even when the Support Portal dashboard is not the active tab. Ensuring push notifications are properly configured is critical for maintaining response time SLAs and operational awareness. Operational Objective Configure your browser's notification permissions to allow the Support Portal dashboard to deliver push notifications for workspace events. Configuration by Browser Google Chrome 1. Select the three-dot menu in the upper-right corner and navigate to Settings. 2. Navigate to Privacy and security > Site Settings > Notifications. 3. Verify that Sites can ask to send notifications is enabled. 4. To explicitly permit notifications for your Support Portal instance, select Add under the Allow section and provide your Support Portal dashboard URL. Alternatively, while on the Support Portal dashboard, select the padlock icon in the address bar, then select Site settings and adjust the Notifications permission to Allow. Mozilla Firefox 1. Select the menu button (three horizontal lines) and navigate to Settings. 2. Navigate to Privacy & Security. 3. Under Permissions, locate Notifications and select Settings. 4. Verify that the Support Portal dashboard URL is listed with Allow status. If not present, ensure Block new requests asking to allow notifications is unchecked so that the permission prompt is presented. Safari (macOS) 1. Select Safari in the menu bar and navigate to Preferences. 2. Select the Websites tab, then select Notifications. 3. Locate your Support Portal dashboard URL and set the permission to Allow. Verify that Allow websites to ask for permissions is enabled. Microsoft Edge 1. Select the three-dot menu in the upper-right corner and navigate to Settings. 2. Navigate to Cookies and site permissions > Notifications. 3. Verify that Ask before sending is enabled. 4. To explicitly permit notifications for your Support Portal instance, select Add under the Allow section and provide your Support Portal dashboard URL. Alternatively, while on the Support Portal dashboard, select the padlock icon in the address bar, then select Permissions for this site and set Notifications to Allow. Expected Behavior Once push notifications are enabled, operators will receive browser-level alerts for workspace events such as new conversation assignments, incoming messages, and mention notifications. Notifications appear regardless of whether the Support Portal dashboard tab is currently active. Additional Resources For detailed browser-specific notification documentation, refer to the following vendor resources: - Google Chrome notification settings - Safari notification settings - Mozilla Firefox notification settings

Last updated on Feb 25, 2026

General Settings

The General Settings interface in Support Portal governs workspace-wide parameters that affect how the platform identifies your organization and how conversations are managed at a system level. Operational objective These settings establish foundational workspace behavior. The organization name appears across the Dashboard and in outbound communications. The language setting controls the interface locale for all users in the workspace. The auto-resolution interval defines how long a conversation may remain inactive before the system automatically resolves it. Accessing general settings Navigate to Settings > Account Settings to access the configuration interface. Configuration parameters - Account Name — The organization or business unit name associated with this workspace (e.g., Meridian Telecom). - Site Language — The locale applied to the Dashboard interface and conversation displays. Select the appropriate language from the dropdown (e.g., English). - Auto-Resolve Duration — The number of days of inactivity after which the system automatically transitions a conversation to Resolved status. This parameter directly affects operational metrics such as resolution time and open-conversation volume. Applying changes After modifying any parameter, select Update Settings to persist the configuration. The system displays a confirmation message upon successful update. Governance implications The auto-resolve duration should align with your organization's service-level agreements and operational policies. A shorter duration reduces open-conversation backlog but may prematurely close conversations awaiting customer responses. A longer duration preserves conversation continuity but can inflate open-conversation counts in reporting.

Last updated on Feb 25, 2026

Performing a Hard Reload

Overview A hard reload forces the browser to bypass its local cache and retrieve the latest version of all page resources directly from the server. This procedure is useful when the Support Portal dashboard displays outdated content, fails to reflect recent configuration changes, or exhibits rendering issues caused by stale cached assets. Operational Objective Perform a hard reload of the Support Portal dashboard to ensure the browser is rendering the most current version of the application. Hard Reload by Browser Google Chrome Standard hard reload: - Windows/Linux: Ctrl + F5 - macOS: Cmd + Shift + R Hard reload with full cache purge: Open Developer Tools (F12 or Cmd + Option + I), then right-select the reload button and choose Empty Cache and Hard Reload. Mozilla Firefox Standard hard reload: - Windows/Linux: Ctrl + F5 or Shift + F5 - macOS: Cmd + Shift + R Hard reload with full cache purge: Open Developer Tools (F12), select the settings (gear) icon, enable Disable Cache, then reload the page. Microsoft Edge Standard hard reload: - Ctrl + F5 Hard reload with full cache purge: Open Developer Tools (F12), right-select the reload button and choose Empty Cache and Hard Reload, or enable Disable Cache in the Network tab and reload. Safari (macOS) Standard hard reload: - Cmd + Option + R Expected Behavior After performing a hard reload, the browser retrieves all Support Portal dashboard resources — including JavaScript, CSS, and API responses — directly from the server. Any issues caused by stale cached content should be resolved. If the issue persists after a hard reload, contact your Altores support representative for further diagnostic assistance.

Last updated on Feb 25, 2026

Personal Profile

Support Portal associates each agent with a personal profile that governs how your identity appears across the Dashboard, live-chat interactions, and outbound email communications. Profile configuration is accessible from the avatar icon in the lower-left region of the sidebar. Operational objective Accurate profile data ensures that customers and fellow agents can identify you correctly across all channels. The profile also controls your authentication credentials and message composition preferences. Agent identity fields Navigate to your profile settings to review and update the following parameters: - Profile Image — Upload a professional headshot. If no image is provided, the system falls back to the Gravatar image associated with your email address, when available. - Full Name — Your complete name as it appears in internal records. - Display Name — The name presented to customers in conversation threads and email correspondence (e.g., "Jane M." rather than "Jane Morrison"). - Email Address — The address used for authentication and system notifications. Updating this value terminates the current session; you must re-authenticate with the new address. After modifying any field, select Update Profile to persist the changes. The system confirms the operation with a success notification. Message signature Support Portal supports per-agent message signatures that are appended to outbound email communications. Signature configuration is available within the profile settings interface. For detailed instructions on crafting and applying your omnichannel signature, refer to the message signature documentation. Password management To update your password, provide your current password followed by the new password. The new password must satisfy the following complexity requirements: - At least one uppercase letter (A-Z) - At least one numeric character (0-9) - At least one special character If you have lost access to your current password, sign out and initiate a password reset from the authentication screen. Message send behavior Support Portal provides two hotkey options for submitting messages in the reply editor: - Enter — Pressing Enter sends the message immediately. - Cmd/Ctrl + Enter — Requires the modifier key combination to send, allowing Enter to insert line breaks. Select the preferred behavior from the send-key configuration section of your profile settings.

Last updated on Feb 25, 2026

Platform Overview

Support Portal by Altores is a conversational operations platform designed for organizations that require structured, auditable, and scalable customer communication. It consolidates interactions from multiple channels into a unified workspace where agents, teams, and AI Modules collaborate to resolve customer inquiries. Operational objective This article provides a high-level understanding of the platform's architecture and capabilities. It is intended for administrators, operations managers, and agents who are beginning to work with Support Portal and need to understand how its components relate to one another. Core architecture Support Portal operates around four primary constructs: Workspace The workspace is the top-level organizational container. All configuration, user accounts, conversations, and data reside within a single workspace. Each workspace is isolated, ensuring that data and access controls do not cross organizational boundaries. Inboxes Inboxes are the connection points between external communication channels and the workspace. Each Inbox represents a configured integration with a channel such as email, website live chat, WhatsApp, SMS, Facebook, Twitter, Telegram, Line, or a custom API endpoint. When a customer sends a message through any connected channel, the platform creates a conversation and routes it to the appropriate queue. Agents and Teams Agents are the users who handle conversations. Each agent is assigned a role — Administrator or Agent — that determines their level of access to platform features and settings. Teams group agents by function or department, enabling conversations to be routed to an operational group rather than a specific individual. Conversations A conversation is the fundamental unit of work in Support Portal. It represents an interaction between a customer and your organization, regardless of the originating channel. Conversations carry status indicators (Open, Pending, Snoozed, Resolved), can be assigned to agents or teams, and accumulate a full history of messages and internal notes. Key capabilities Omnichannel message handling Support Portal normalizes messages from all connected channels into a consistent conversation interface. Agents respond from a single Dashboard regardless of whether the customer initiated contact via email, live chat, or a messaging platform. Replies are delivered back through the customer's original channel. Conversation routing and assignment Conversations can be assigned manually to individual agents or teams, or routed automatically using automation rules. Automation supports event-based triggers and condition evaluation, enabling routing logic such as language-based team assignment or keyword-driven escalation. Labels and classification Labels provide a tagging system for categorizing conversations by topic, urgency, department, or any operational dimension. Labels are available as filter criteria in the conversation list, as conditions and actions in automation rules, and as reporting dimensions. Canned Responses Canned Responses are pre-authored reply templates that agents invoke using shortcodes during conversation handling. They reduce response time for frequently asked questions and ensure consistency in messaging across the team. Custom Attributes Custom Attributes extend the data model for conversations and contacts beyond standard fields. Organizations can define attributes such as subscription tier, account number, or service region, and use them for filtering, reporting, and automation. Contacts and segmentation The Contacts system maintains a record of every individual who has communicated with your organization, along with any manually imported contact data. Contacts can be filtered by standard and custom attributes, and saved filter configurations can be stored as segments for repeated use. Reporting and analytics Support Portal provides reporting across multiple dimensions — agents, teams, inboxes, labels, and conversations. Available metrics include first response time, resolution time, resolution count, and CSAT scores. Reports can be filtered by time period and exported for external analysis. Help Center The built-in Help Center enables your organization to publish and manage a customer-facing knowledge base directly from the Dashboard. Articles can be organized into categories and portals, and referenced during conversations to provide self-service resources. Automation Automation rules allow administrators to define event-driven workflows that execute without manual intervention. Common automation patterns include assigning conversations based on channel or content, applying labels based on message keywords, and sending notifications based on conversation status changes. AI Modules Support Portal supports AI Module integration for automating portions of the conversation lifecycle. AI Modules can handle initial greetings, route conversations based on intent, and provide suggested responses before escalating to a human agent. Platform navigation The Dashboard is organized around a persistent sidebar that provides access to: - Conversations — The primary workspace for viewing and responding to customer interactions. - Contacts — The contact directory with filtering and segmentation capabilities. - Reports — Operational analytics and performance metrics. - Help Center — Knowledge base management. - Settings — Workspace configuration, agent management, inbox setup, team management, and automation rules. Getting started To begin using Support Portal, proceed through the following configuration sequence: 1. Account Setup — Provision your workspace. 2. Personal Profile — Configure your agent identity. 3. General Settings — Set workspace-level parameters. 4. Adding Agents — Provision your operations team. 5. Adding Inboxes — Connect your communication channels. 6. Adding Teams — Organize agents into functional groups. 7. Notifications — Configure notification preferences. For a hands-on walkthrough of core platform operations, see the Quickstart Guide.

Last updated on Feb 25, 2026