Two delivery modes

Finger Manager hosted delivery is suitable when a broker does not yet have its own SMS or email infrastructure. Finger Manager sends SMS and Email through platform-level third-party services, allowing the institution to enable notification delivery quickly.

Broker-owned delivery is suitable for institutions that already have SMS or Email infrastructure. The broker connects its provider account, SMTP account, Email API, SMS API, Sender ID, sending domain, sender address, SMS signature, API key, secret, or other provider credentials.

Hosted delivery is generally a paid service and may be affected by provider quotas, regional coverage, SMS template review, email frequency rules, anti-spam rules, delivery failures, bounce handling, and regional pricing differences.

Broker-owned account fees

When a broker uses its own SMS or email service account, Finger Manager does not charge an additional SMS or Email channel delivery fee.

Finger Manager is responsible for message creation, user selection, delivery rules, scheduled tasks, channel selection, status management, and calling the configured provider.

The broker's own carrier or email provider remains responsible for actual SMS delivery, email delivery, communication quota, service package, per-message cost, and third-party provider fees.

SMS service

SMS is suitable for short, time-sensitive, high-priority reminders such as verification codes, account status reminders, security alerts, important business notices, maintenance reminders, campaign reminders, market time reminders, and high-priority user notifications.

Operations staff can configure SMS content, target users, send time, sending channel, Sender ID, and whether the message uses the hosted account or broker-owned provider.

After sending, Finger Manager can record basic delivery status based on the provider response.

Email service

Email is suitable for more complete content that needs to be retained or contains longer explanations, such as account notices, service rule changes, product updates, maintenance notices, business explanations, campaign notices, and formal customer information.

Operations staff can configure email subject, body, target users, sender, reply address, send time, email template, and whether the message uses the hosted email service or the broker's own email service.

Compared with SMS, Email is better suited to full content, brand formatting, and more complex information structures.

Channel configuration

A broker can set the default Email and SMS delivery method in Finger Manager.

SMS can use Finger Manager SMS Service or Broker SMS Provider. Email can use Finger Manager Email Service or Broker Email Provider.

For broker-owned SMS providers, configuration may include Provider, API Endpoint, API Key, API Secret, Account ID, Sender ID, Callback URL, Default Region, and SMS template settings.

For broker-owned email services, SMTP configuration may include SMTP Host, Port, Username, Password, Encryption, Sender Email, and Sender Name. Email API configuration may include API Key, API Secret, Sending Domain, Sender Address, and Reply-To Address.

Multi-channel combinations

Email and SMS can be combined with other Finger Manager notification methods.

For example, In-App Notification + Push + Email can be used for important business notices, while In-App Notification + SMS can be used for account reminders that need higher read probability.

For higher-priority messages, institutions can configure In-App Notification + Push + SMS + Email. Finger Manager manages notification content and target users, then calls each channel separately.

Hosted service compared with broker-owned service

Finger Manager hosted service requires no separate provider application, is simpler to configure, can begin sending quickly, and is managed by the platform. Its limitations are that it is a paid service, may have quota or rule limits, depends on third-party regional support, and may be more expensive at high volume.

Broker-owned service accounts allow the broker to avoid Finger Manager channel delivery fees, use existing provider contracts, control its own sending quota, use its own Sender ID, sending domain, and brand, and better support large-scale or long-term operations.

When using broker-owned providers, the broker remains responsible for provider onboarding, account balance, service fees, API permissions, domain authentication, Sender ID approval, and regional compliance requirements.

Manager workflow

The workflow is: choose hosted delivery or broker-owned service account, configure SMS / Email channel, create notification content, set target users, set immediate or scheduled sending, and let Finger Manager execute the task.

If hosted delivery is selected, Finger Manager calls the platform-level provider. If broker-owned delivery is selected, Finger Manager calls the broker-configured Provider, SMTP, or API, then sends Email or SMS to users.

Typical use cases

Quick enablement: new institutions can use hosted delivery before they have their own SMS or email systems.

Use existing infrastructure: brokers with mature SMS or email services can connect existing accounts instead of migrating providers.

Lower large-scale notification cost: institutions with many clients and frequent notifications can continue using existing provider contracts and pricing.

Brand consistency: using broker-owned sending domains, Sender IDs, and accounts helps keep user-facing communication consistent with the broker's brand.