This article explains the account settings in Aloware Admin and how each configuration affects your organization. It also clarifies whether changes impact Aloware Talk functionality or remain limited to account-level configuration in the admin panel.
Only account admins can access this section. To manage these settings, log in to Aloware Admin and navigate to Account > General settings.
General settings
General settings define core account-level configurations that apply across the entire system. These settings are used to keep data consistent across reporting, messaging behavior, and user experience.
Account name
The account name is used as the primary identifier for your Aloware account in administrative views, reports, and system references.
Account name in Aloware admin
Account name in Aloware Talk
Timezone Settings
The account timezone establishes a single standard reference point for time-based data across the platform. Once configured, it becomes the baseline for how Aloware interprets dates and times.
This setting affects reporting accuracy, filters, dashboard metrics, activity logs, and broadcast scheduling because all system-generated timestamps are normalized against this timezone.
Timezone is reflected in the dashboard
Inbox timezone display
This setting controls how timestamps are presented inside the inbox and related communication views. Admins can decide whether all users see timestamps in the centralized account timezone or in their own local browser timezone.
When the account timezone option is used, everyone sees the same time reference, which is useful for teams that need consistent interpretation of activity across regions.
When user-local timezone is enabled, each user sees timestamps based on their own device, which can make individual workflows easier to follow but introduces variation across users.
In Aloware Talk, this affects how users interpret message and call timing inside the inbox, call logs, dashboards, and reports. It does not change when events occur or how they are processed, only how the time is displayed to each user.
Timezone display in Aloware Talk messages
Private Lines
Private lines control whether users can view other users’ direct or personal lines within the system. This setting is primarily used to manage internal visibility and maintain separation between individual user resources.
When enabled as a restriction, users will only see the lines they are permitted to access instead of viewing all available user lines.
Inside Aloware Talk, this affects only what a user can see in the interface.
Send long text messages as MMS
When this setting is enabled, messages that exceed 160 characters are automatically converted from SMS into MMS instead of being split into multiple SMS segments.
This ensures that long messages are delivered in a single format and preserves message readability. It applies to supported sender types including toll-free, short code, and A2P 10DLC numbers in the US and Canada.
In Aloware Talk, this behavior is transparent to the user composing the message. The main impact is in delivery format and potential carrier handling, since MMS is processed differently from SMS.
The message remains a single composed text from the user’s perspective, but the system changes the delivery method based on length.
Message segments in Broadcast
Broadcast Settings
Broadcast settings define how bulk messaging behaves when it overlaps with business hour restrictions. These rules are used to ensure that high-volume messaging follows organizational timing policies.
When configured, broadcasts may be restricted or regulated outside approved hours to maintain consistent messaging practices across the account.
If a broadcast is scheduled or triggered outside allowed time windows, delivery may be delayed or restricted depending on configuration. This ensures that bulk messaging behavior remains consistent regardless of where it is initiated.
Broadcast scheduling is restricted in Aloware Talk.
Sequence re-enrollment
Sequence re-enrollment controls whether contacts can move between sequences and ensures that a contact is only actively enrolled in one sequence at a time. This prevents overlapping automation paths that could result in duplicate or conflicting outreach behaviors.














