N24 SMS Sender - Setup and Configuration

Setup Page Overview

The N24SMS | Setup page provides comprehensive configuration options for the SMS Sender extension. Access it by searching for "N24SMS | Setup" in Business Central or through the ⚙️ N24SMS | Start Here page.

SMSAPI Configuration

API Token Setup

The SMSAPI API Token is the core authentication mechanism for the SMS service:

  • Field: SMSAPI API Token
  • Type: Encrypted and masked text field
  • Purpose: Authenticates your Business Central with the SMSAPI service
  • Requirements:
    • Must be generated from your SMSAPI account
    • Should be kept secure and confidential
    • Required for all SMS functionality

To obtain an API token:

  1. Log in to your SMSAPI account at https://ssl.smsapi.pl
  2. Navigate to Settings → API Settings → API Tokens (OAuth)
  3. Generate a new token
  4. Copy and paste it into the Business Central setup

SMS Sender Name

  • Field: SMS Sender Name
  • Purpose: Defines how your organization appears to SMS recipients
  • Default: If left blank, "Test" is used as the sender name or the default name that is set in your SMSAPI panel.
  • Best Practice: Use your company name or a recognizable identifier. Must be registered in your SMSAPI panel.

SMSAPI Account Access

The setup page includes a direct link to access your SMSAPI customer portal for account management, balance checking, and advanced configuration.

Test Mode Configuration

Test mode provides safe testing capabilities before sending SMS messages to actual recipients.

Test Mode Options

  1. Off (Production Mode)

    • Messages are sent to actual recipients
    • Use only when you're confident in your configuration
    • All SMS charges apply normally

  2. Test Number

    • All SMS messages are redirected to a specified test phone number
    • Actual recipients never receive messages
    • Ideal for testing templates and workflows
    • Requires setting up a test phone number
    • All SMS charces apply normally

  3. Simulate

    • SMS processes are executed but no messages are actually sent
    • Perfect for testing workflows without any SMS charges
    • All logging and error handling occurs normally
    • No actual phone number receives messages

Test Number Configuration

When Test Mode is set to "Test Number":

  • Field: Test Number
  • Purpose: Specifies the phone number that will receive all SMS messages
  • Format: Enter the full international format (e.g., +48123456789) or Polish format will be added automatically
  • Recommendation: Use your own phone number for testing

Test Mode Indicators

The setup page displays dynamic tooltips explaining the current test mode behavior, helping users understand what will happen when SMS messages are sent.

SMS Templates Management

Accessing Templates

From the setup page, use the SMS Templates action to access template management:

  • Purpose: Create, edit, and manage SMS message templates
  • Benefit: Standardize communications across different business scenarios
  • Integration: Templates automatically populate with data from Business Central records

Template Organization

Templates are organized by business areas:

  • Customer communications
  • Vendor notifications
  • Sales processes
  • Purchase processes
  • Service management
  • Warehouse operations
  • Financial processes

Testing and Verification

Send Test Message

Use the Send Test Message action to verify your configuration:

  • Opens the SMS Creator dialog
  • Allows manual message composition
  • Tests SMSAPI connectivity
  • Validates authentication
  • Demonstrates the sending workflow

SMS History

Access comprehensive logging through the SMS History action:

  • View all sent SMS messages
  • Check delivery statuses
  • Review error messages
  • Monitor user activity
  • Track template usage

Security and Permissions

Permission Requirements

Users need the N24SMS Sender permission set to:

  • Access setup pages
  • Send SMS messages
  • View SMS history
  • Manage templates

Data Security

  • API tokens are stored securely using masked fields and encryption
  • SMS content is logged for audit purposes
  • User tracking maintains accountability
  • Test modes prevent accidental message sending

Best Practices

Initial Setup

  1. Start with Test Mode: Always begin with "Test Number" or "Simulate" mode
  2. Verify API Connectivity: Use the test message feature before going live
  3. Create Essential Templates: Set up templates for your most common scenarios
  4. Train Users: Ensure users understand test vs. production modes

Ongoing Management

  1. Monitor SMS History: Regularly check for failed messages
  2. Maintain Templates: Keep message templates current and relevant
  3. Review Permissions: Audit who has SMS sending capabilities
  4. Check API Balance: Monitor your SMSAPI account usage and billing

Troubleshooting

  • Authentication Issues: Verify API token validity in your SMSAPI account
  • Sending Failures: Check SMSAPI account balance and service status
  • Template Problems: Ensure template fields map correctly to Business Central data
  • Permission Errors: Confirm users have appropriate permission sets assigned