# Authentication
Source: https://sbmg.app/api-reference/authentication

Authentication documentation for SBMG - Small Business Messenger

## Obtaining an API Key

To access our API, you need to obtain an API key from our web portal. The API key acts as a secure identifier for your application and allows you to authenticate and authorize your requests.

To obtain an API key, please follow these steps:

1. Visit our [web portal](https://coming-soon.com) and sign in to your account or create a new account if you haven't already.
2. Navigate to the "API Keys" section within "Settings" of your portal.
3. Click on the "Generate New API Key" button to create a new API key.
4. Make sure to securely store the API key, as it will be required to authenticate your API requests.

## Authenticating API Requests

Once you have obtained your API key, you need to include it in the header of each API request you make. This ensures that your requests are properly authenticated and authorized by our system.

To authenticate your API requests, include the following header:

```http theme={null}
x-api-key: YOUR_API_KEY
```

Replace `YOUR_API_KEY` with the API key you obtained from our web portal.

Please note that failing to provide the API key or providing an invalid API key will result in authentication errors, and your requests will be rejected.


# Send SMS
Source: https://sbmg.app/api-reference/endpoint/messaging/send-sms

POST https://api.sbmg.app/sms
This endpoint send an sms via your personal gateway.

This API endpoint allows you to send an SMS message to a specified recipient.

## Body

<ParamField type="array">
  A list of phone numbers of the recipient in E.164 international format.
</ParamField>

<ParamField type="string">
  The content of the SMS message.
</ParamField>

<ParamField type="string">
  Sim slot id to manage the sending sim in setups with multiple carrier connections. Ignore if your phone only has one sim installed or if you just want to use the default.
</ParamField>

<ParamField type="object">
  Additional metadata associated with the message. This can be used to create powerful two-way messaging applications without having to store persistent data in the application.
</ParamField>

<RequestExample>
  ```bash Example Request theme={null}
  curl --location 'https://api.sbmg.app/sms' \
  --header 'x-api-key: YOUR_API_KEY'
  --data '{
      "to": ["+6421#######"],
      "message": "Hello, this SMS has been sent via SBMG!",
      "sim": "1",
      "metadata": {
          "key1": "value1"
      }
  }'
  ```
</RequestExample>

## Response

<ResponseField name="message" type="string">
  Message of submission attempt.
</ResponseField>

<ResponseField name="message_id" type="array">
  Array of UUIDs of the messages from submission as it will appear in webhook callbacks and reporting. Ordered to match the destinations of the send request.
</ResponseField>

<ResponseExample>
  ```json Response theme={null}
  {
    "message": "Sending sms",
    "message_id": ["aa1a2a34-5678-9c01-d23d-abcdef4abc5"]
  }
  ```
</ResponseExample>


# Detailed Report
Source: https://sbmg.app/api-reference/endpoint/reporting/detail

GET https://api.sbmg.app/report
This endpoint creates a filtered message report.

## Query

<ParamField type="string">
  Start date of the report query. Format `YYYY-MM-DD` for example: `2023-01-30`
</ParamField>

<ParamField type="string">
  End date of the report query. Format `YYYY-MM-DD` for example: `2023-01-30`
</ParamField>

<ParamField type="string">
  Filter for messages containing a given metadata key.
</ParamField>

<RequestExample>
  ```bash Example Request theme={null}
  curl --location 'https://api.sbmg.app/report?start_date=2023-06-12&end_date=2023-06-14&metadata_key=myMetdataKey' \
  --header 'x-api-key: YOUR_API_KEY'
  ```
</RequestExample>

## Response

<ResponseField name="data" type="array">
  An array of message log entries containing the following fields

  <Expandable title="Toggle object">
    <ResponseField name="account_id" type="number">
      The account ID associated with the message.
    </ResponseField>

    <ResponseField name="destination_address" type="string">
      The phone number of the message recipient.
    </ResponseField>

    <ResponseField name="direction" type="string">
      The direction of the message (e.g. "OUTBOUND").
    </ResponseField>

    <ResponseField name="content" type="string">
      The content of the message.
    </ResponseField>

    <ResponseField name="date" type="string">
      The timestamp of the message in ISO 8601 format.
    </ResponseField>

    <ResponseField name="user_metadata" type="object">
      Additional metadata associated with the message.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json Response theme={null}
  {
    "data": [
      {
        "account_id": "f123bf12-f23b-345d-bddc-5e6789abb0c",
        "destination_address": "6422999888",
        "direction": "OUTBOUND",
        "content": "Hello world",
        "date": "2023-06-14T09:06:46Z",
        "user_metadata": {
          "myMetdataKey": "value 3"
        }
      },
      {
        "account_id": "f123bf12-f23b-345d-bddc-5e6789abb0c",
        "source_address": "6422999888",
        "direction": "INBOUND",
        "content": "Boom! Hello!",
        "date": "2023-06-14T09:10:56Z",
        "user_metadata": {
          "myMetdataKey": "value 1"
        }
      },
    ]
  }
  ```
</ResponseExample>


# Subscribe
Source: https://sbmg.app/api-reference/endpoint/webhooks/subscribe

POST https://api.sbmg.app/webhook
Subscribe to receive events to a specific webhook.

Whenever a new outbound message is received SBMG can send a POST request to your webhook for your services or integrations to process.

## Body

<ParamField type="string">
  The URL where events will be sent when inbound SMS messages are received.
</ParamField>

<RequestExample>
  ```bash Example Request theme={null}
  curl --location 'https://api.sbmg.app/webhook' \
  --header 'x-api-key: YOUR_API_KEY'
  --data '{
      "hookUrl": "https://my-webhook.com/inbound/sms"
  }'
  ```
</RequestExample>

## Response

<ResponseField name="hook_id" type="array">
  This is the key to your webhook. Retain this id to dele
</ResponseField>

<ResponseExample>
  ```json Response theme={null}
  {
    "hook_id": 234
  }
  ```
</ResponseExample>

## Inbound Recieved Action

When an inbound SMS message is received, the configured webhook(s) will receive a POST request with the following payload:

```json Response theme={null}
{
  "account_id": "f123bf12-f23b-345d-bddc-5e6789abb0c",
  "destination_address": "6422999888",
  "direction": "OUTBOUND",
  "content": "Hello world",
  "date": "2023-06-14T09:06:46Z",
  "user_metadata": {
    "myMetdataKey": "value 3"
  }
}
```


# Unsubscribe
Source: https://sbmg.app/api-reference/endpoint/webhooks/unsubscribe

DELETE https://api.sbmg.app/webhook
Unsubscribe from receiving events for a specific webhook.

## Query

<ParamField type="string">
  The unique identifier of the webhook to unsubscribe.
</ParamField>

<RequestExample>
  ```bash Example Request theme={null}
  curl --location --request DELETE 'https://api.sbmg.app/webhook?hook_id=234' \
  --header 'x-api-key: YOUR_API_KEY'
  ```
</RequestExample>

<ResponseExample>
  ```json Response theme={null}
  {
      "message": "Webhook unsubscribed successfully"
  }
  ```
</ResponseExample>


# Send SMS
Source: https://sbmg.app/api-reference/v1/endpoint/messaging/send-sms

POST https://api.sbmg.app/v1/message
This endpoint send an sms via your personal gateway.

This API endpoint allows you to send an SMS message to a specified recipient.

## Body

<ParamField type="array">
  A list of phone numbers of the recipient in E.164 international format.
</ParamField>

<ParamField type="string">
  The content of the SMS message.
</ParamField>

<ParamField type="string">
  Sim slot id to manage the sending sim in setups with multiple carrier connections. Ignore if your phone only has one sim installed or if you just want to use the default.
</ParamField>

<ParamField type="object">
  Additional metadata associated with the message. This can be used to create powerful two-way messaging applications without having to store persistent data in the application.
</ParamField>

<RequestExample>
  ```bash Example Request theme={null}
  curl --location 'https://api.sbmg.app/v1/message' \
  --header 'x-api-key: YOUR_API_KEY'
  --data '{
      "to": ["+6421#######"],
      "message": "Hello, this SMS has been sent via SBMG!",
      "sim": "1",
      "metadata": {
          "key1": "value1"
      }
  }'
  ```
</RequestExample>

## Response

<ResponseField name="message" type="string">
  Message of submission attempt.
</ResponseField>

<ResponseField name="message_id" type="array">
  Array of UUIDs of the messages from submission as it will appear in webhook callbacks and reporting. Ordered to match the destinations of the send request.
</ResponseField>

<ResponseExample>
  ```json Response theme={null}
  {
    "message": "Sending sms",
    "message_id": ["aa1a2a34-5678-9c01-d23d-abcdef4abc5"]
  }
  ```
</ResponseExample>


# Detailed Report
Source: https://sbmg.app/api-reference/v1/endpoint/reporting/detail

GET https://api.sbmg.app/v1/reporting/detail
This endpoint creates a filtered message report.

## Query

<ParamField type="string">
  Start date of the report query. Format `YYYY-MM-DD` for example: `2023-01-30`
</ParamField>

<ParamField type="string">
  End date of the report query. Format `YYYY-MM-DD` for example: `2023-01-30`
</ParamField>

<ParamField type="string">
  Filter for messages containing a given metadata key.
</ParamField>

<RequestExample>
  ```bash Example Request theme={null}
  curl --location 'https://api.sbmg.app/v1/reporting/detail?start_date=2023-06-12&end_date=2023-06-14&metadata_key=myMetdataKey' \
  --header 'x-api-key: YOUR_API_KEY'
  ```
</RequestExample>

## Response

<ResponseField name="data" type="array">
  An array of message log entries containing the following fields

  <Expandable title="Toggle object">
    <ResponseField name="account_id" type="number">
      The account ID associated with the message.
    </ResponseField>

    <ResponseField name="destination_address" type="string">
      The phone number of the message recipient.
    </ResponseField>

    <ResponseField name="direction" type="string">
      The direction of the message (e.g. "OUTBOUND").
    </ResponseField>

    <ResponseField name="content" type="string">
      The content of the message.
    </ResponseField>

    <ResponseField name="date" type="string">
      The timestamp of the message in ISO 8601 format.
    </ResponseField>

    <ResponseField name="user_metadata" type="object">
      Additional metadata associated with the message.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json Response theme={null}
  {
    "data": [
      {
        "account_id": "f123bf12-f23b-345d-bddc-5e6789abb0c",
        "destination_address": "6422999888",
        "direction": "OUTBOUND",
        "content": "Hello world",
        "date": "2023-06-14T09:06:46Z",
        "user_metadata": {
          "myMetdataKey": "value 3"
        }
      },
      {
        "account_id": "f123bf12-f23b-345d-bddc-5e6789abb0c",
        "source_address": "6422999888",
        "direction": "INBOUND",
        "content": "Boom! Hello!",
        "date": "2023-06-14T09:10:56Z",
        "user_metadata": {
          "myMetdataKey": "value 1"
        }
      },
    ]
  }
  ```
</ResponseExample>


# Account Usage Report
Source: https://sbmg.app/api-reference/v1/endpoint/reporting/usage

GET https://api.sbmg.app/v1/reporting/usage

## Body

<RequestExample>
  ```bash Example Request theme={null}
  curl --location 'https://api.sbmg.app/v1/reporting/usage' \
  --header 'x-api-key: YOUR_API_KEY'
  ```
</RequestExample>

## Response

<ResponseField name="data" type="array">
  An array of message log entries containing the following fields

  <Expandable title="Toggle object">
    <ResponseField name="account_id" type="number">
      The account ID associated with the message.
    </ResponseField>

    <ResponseField name="destination_address" type="string">
      The phone number of the message recipient.
    </ResponseField>

    <ResponseField name="direction" type="string">
      The direction of the message (e.g. "OUTBOUND").
    </ResponseField>

    <ResponseField name="content" type="string">
      The content of the message.
    </ResponseField>

    <ResponseField name="date" type="string">
      The timestamp of the message in ISO 8601 format.
    </ResponseField>

    <ResponseField name="user_metadata" type="object">
      Additional metadata associated with the message.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json Response Example theme={null}
  {
    "data": [
      {
        "account_id": "f123bf12-f23b-345d-bddc-5e6789abb0c",
        "destination_address": "6422999888",
        "direction": "OUTBOUND",
        "content": "Hello world",
        "date": "2023-06-14T09:06:46Z",
        "user_metadata": {
          "key2": "value 3"
        }
      },
      {
        "account_id": "f123bf12-f23b-345d-bddc-5e6789abb0c",
        "destination_address": "6421765432",
        "direction": "OUTBOUND",
        "content": "Good morning...",
        "date": "2023-06-14T09:07:12Z",
      },
      {
        "account_id": "f123bf12-f23b-345d-bddc-5e6789abb0c",
        "source_address": "6422999888",
        "direction": "INBOUND",
        "content": "Boom! Hello!",
        "date": "2023-06-14T09:10:56Z",
        "user_metadata": {
          "key2": "value 3"
        }
      },
    ]
  }
  ```
</ResponseExample>


# Webhook List
Source: https://sbmg.app/api-reference/v1/endpoint/webhooks/list

GET https://api.sbmg.app/v1/reporting/webhooks

<RequestExample>
  ```bash Example Request theme={null}
  curl --location 'https://api.sbmg.app/v1/reporting/webhooks' \
  --header 'x-api-key: YOUR_API_KEY'
  ```
</RequestExample>

## Response

<ResponseField name="data" type="array">
  An array of message log entries containing the following fields

  <Expandable title="Toggle object">
    <ResponseField name="account_id" type="number">
      The account ID associated with the message.
    </ResponseField>

    <ResponseField name="destination_address" type="string">
      The phone number of the message recipient.
    </ResponseField>

    <ResponseField name="direction" type="string">
      The direction of the message (e.g. "OUTBOUND").
    </ResponseField>

    <ResponseField name="content" type="string">
      The content of the message.
    </ResponseField>

    <ResponseField name="date" type="string">
      The timestamp of the message in ISO 8601 format.
    </ResponseField>

    <ResponseField name="user_metadata" type="object">
      Additional metadata associated with the message.
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseExample>
  ```json Response Example theme={null}
  {
    "webhooks": [
      {
        "id": 397,
        "label": "Zapier Trigger",
        "webhook_url": "https://zapier.com/developer/public-invite/186462/8c573cbeab5bcfc1a7f95247506e9d6c/",
        "created": "2023-08-14 17:31:22"
      },
      {
        "id": 1253,
        "label": null,
        "webhook_url": "https://hook.my-sms-callback.net",
        "created": "2024-06-14 09:56:54"
      }
    ]
  }
  ```
</ResponseExample>


# Webhook Subscribe
Source: https://sbmg.app/api-reference/v1/endpoint/webhooks/subscribe

POST https://api.sbmg.app/v1/reporting/webhook
Subscribe to receive events to a specific webhook.

Whenever a new outbound message is received SBMG can send a POST request to your webhook for your services or integrations to process.

## Body

<ParamField type="string">
  The URL where events will be sent when inbound SMS messages are received.
</ParamField>

<RequestExample>
  ```bash Example Request theme={null}
  curl --location 'https://api.sbmg.app/v1/reporting/webhook' \
  --header 'x-api-key: YOUR_API_KEY'
  --data '{
      "hookUrl": "https://my-webhook.com/inbound/sms"
  }'
  ```
</RequestExample>

## Response

<ResponseField name="hook_id" type="array">
  This is the key to your webhook. Retain this id to dele
</ResponseField>

<ResponseExample>
  ```json Response theme={null}
  {
    "hook_id": 234
  }
  ```
</ResponseExample>

## Inbound Recieved Action

When an inbound SMS message is received, the configured webhook(s) will receive a POST request with the following payload:

```json Response theme={null}
{
  "account_id": "f123bf12-f23b-345d-bddc-5e6789abb0c",
  "destination_address": "6422999888",
  "direction": "OUTBOUND",
  "content": "Hello world",
  "date": "2023-06-14T09:06:46Z",
  "user_metadata": {
    "myMetdataKey": "value 3"
  }
}
```


# Webhook Unsubscribe
Source: https://sbmg.app/api-reference/v1/endpoint/webhooks/unsubscribe

DELETE https://api.sbmg.app/v1/reporting/webhook
Unsubscribe from receiving events for a specific webhook.

## Query

<ParamField type="string">
  The unique identifier of the webhook to unsubscribe.
</ParamField>

<RequestExample>
  ```bash Example Request theme={null}
  curl --location --request DELETE 'https://api.sbmg.app/v1/reporting/webhook?hook_id=234' \
  --header 'x-api-key: YOUR_API_KEY'
  ```
</RequestExample>

<ResponseExample>
  ```json Response theme={null}
  {
      "message": "Webhook unsubscribed successfully"
  }
  ```
</ResponseExample>


# Crypto Mining SMS Alerts
Source: https://sbmg.app/blog/crypto-mining-sms-alerts

Guide to setting up SMS alerts for crypto mining rig monitoring

## Crypto Mining SMS Alerts

**27 Dec 2023**

### Introduction

Crypto mining operations require constant monitoring to ensure optimal performance and quick response to any issues. When your mining rig goes offline or encounters problems, every minute of downtime can result in lost revenue. This guide will walk you through setting up SMS alerts for your crypto mining operations using SBMG's Email2SMS feature, ensuring you're immediately notified of any issues, no matter where you are.

### Why SMS Alerts for Crypto Mining?

1. **Immediate Notification:** SMS messages are delivered instantly to your mobile device, ensuring you're alerted the moment your mining rig goes offline.

2. **Reliability:** Unlike email notifications that can be delayed or filtered, SMS messages have a much higher delivery success rate.

3. **24/7 Monitoring:** Receive alerts anytime, anywhere, even when you're away from your mining setup.

4. **Cost-Effective:** SMS alerts are an affordable way to monitor multiple rigs simultaneously.

### Setting Up SMS Alerts for Your Mining Rig

#### Step 1: Choose Your Monitoring Software

Most mining monitoring software supports email notifications. Some popular options include:

* **Awesome Miner**
* **MinerStat**
* **Hive OS**
* **RaveOS**
* **Custom monitoring scripts**

For this guide, we'll focus on a general approach that works with most monitoring solutions that support email alerts.

#### Step 2: Configure Email Alerts in Your Monitoring Software

1. **Set Up Alert Conditions:**
   * Configure your monitoring software to send email alerts for critical events such as:
     * Rig offline/online status changes
     * High temperature warnings
     * Hash rate drops
     * Hardware failures
     * Network connectivity issues

2. **Configure SMTP Settings:**
   * Set up the SMTP server settings in your monitoring software to send emails.
   * Use your preferred email service (Gmail, Outlook, etc.) or your mining pool's email service if available.

#### Step 3: Set Up SBMG Email2SMS

1. **Sign Up for SBMG Pro Plan:**
   * If you haven't already, sign up for an SBMG Pro plan which includes the Email2SMS feature.
   * You can find our plans and sign up [here](/pricing).

2. **Configure Email2SMS:**
   * Follow our [Email2SMS setup guide](/user-guide/email2sms) to configure your SBMG account for email-to-SMS conversion.

3. **Set Up Your Alert Email Address:**
   * In your monitoring software, configure the alert recipient email address using the format: `+[countrycode][phonenumber]@sbmg.app`
   * For example: `+64215551234@sbmg.app` (for a New Zealand number)

#### Step 4: Test Your SMS Alerts

1. **Trigger a Test Alert:**
   * Manually trigger a test alert from your monitoring software (e.g., by disconnecting a miner or simulating a failure).

2. **Verify SMS Delivery:**
   * Check that you receive the SMS alert on your mobile device within seconds.
   * Verify that the alert contains all the necessary information about the issue.

3. **Adjust Alert Settings:**
   * Fine-tune your alert conditions and message content based on the test results.

### Advanced Configuration Options

#### Multiple Recipients

You can set up alerts to be sent to multiple team members by configuring multiple Email2SMS addresses in your monitoring software:

```
+64215551234@sbmg.app, +64223334567@sbmg.app, +14155551234@sbmg.app
```

#### Alert Escalation

For critical issues, you can set up escalation procedures:

1. **First-Level Alert:** Sent to primary technician
2. **Second-Level Alert:** If not acknowledged within X minutes, sent to backup technician
3. **Third-Level Alert:** If still not resolved, sent to management

#### Integration with Monitoring Dashboards

Many mining monitoring dashboards can be integrated with SBMG's API for more advanced alerting:

```javascript theme={null}
// Example API call to send SMS alert via SBMG API
const response = await fetch('https://api.sbmg.app/v1/messaging/send-sms', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_API_KEY',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    destinations: ['+64215551234'],
    message: 'CRITICAL: Mining rig #3 offline - Temperature: 95°C',
    source: 'MiningAlert'
  })
});
```

### Best Practices for Crypto Mining Alerts

1. **Prioritize Alerts:**
   * Set up different alert levels (Critical, Warning, Info) with appropriate notification methods.

2. **Avoid Alert Fatigue:**
   * Configure alerts only for truly important events to avoid being overwhelmed with notifications.

3. **Include Actionable Information:**
   * Ensure each SMS alert contains enough information to identify and potentially resolve the issue.

4. **Regular Testing:**
   * Test your alert system regularly to ensure it's working properly.

5. **Backup Notification Methods:**
   * Consider setting up secondary notification methods (email, push notifications) as backup.

### Troubleshooting Common Issues

**Issue: Not Receiving SMS Alerts**

1. Check that your monitoring software is properly configured to send emails
2. Verify your Email2SMS address format is correct
3. Ensure your SBMG account has sufficient credits
4. Check your spam/junk email folder in case emails aren't being processed

**Issue: Delayed Alerts**

1. Verify your internet connection stability
2. Check your email service's delivery times
3. Consider using SBMG's API for more immediate alerts

### Conclusion

Setting up SMS alerts for your crypto mining operations provides peace of mind and helps minimize downtime. With SBMG's Email2SMS feature, you can receive instant notifications about critical issues, allowing you to respond quickly and keep your mining operation running smoothly.

For more advanced monitoring and alerting options, explore SBMG's [API documentation](/api-reference) or contact our support team at [support@sbmg.app](mailto:support@sbmg.app).

*Email2SMS is a SBMG Pro feature required for this integration. [Upgrade here](/pricing).*

### Disclaimer

**Not a Financial Endorsement:** The content provided in this article, including the use of Nicehash and other crypto mining services, is for informational purposes only and is not intended as an endorsement of any specific cryptocurrency, mining service, or investment strategy. Cryptocurrency investments are subject to high market risks, including volatility and regulatory changes.

**Security and Privacy Considerations:** When using APIs and handling sensitive information like API keys and personal phone numbers for SMS alerts, it's crucial to prioritize security and privacy. Always ensure that your API keys are stored securely and not exposed in your scripts or to third parties.

**Financial Risks in Crypto Mining:** Be aware that crypto mining involves significant financial risks. These risks include potential losses due to hardware failure, fluctuating cryptocurrency values, and changes in mining difficulty. Energy costs associated with mining can also impact profitability.

**Regulatory Compliance:** Cryptocurrency mining and trading are subject to varying regulations in different jurisdictions. It's important to stay informed about and comply with all relevant laws and regulations in your region.

**Responsibility of Monitoring:** While automated monitoring systems can enhance efficiency and reduce the likelihood of unnoticed downtime, they are not foolproof. Continuous personal oversight and verification are recommended to ensure the accuracy and effectiveness of these systems.

**Changes in Technology:** The cryptocurrency market is dynamic, with frequent changes in technology, platforms, and best practices. The information presented in this article is based on the current state of technology and market conditions and may become outdated as new developments emerge.

**Consultation with Professionals:** For financial advice, investment strategies, or legal compliance, always consult with a qualified professional. Do not base significant investment or legal decisions solely on the information presented in this article.

**Limitation of Liability:** The author and publisher of this article are not liable for any losses or damages that may arise from the application of the information provided. Users are responsible for their own investment and security decisions.
By acknowledging these risks and responsibilities, you can make more informed decisions in your crypto mining ventures.


# Product Changelog
Source: https://sbmg.app/blog/product

Additions and updates to the SBMG service

## August → September '24

This release focuses on the web portal and on it's own the headline of our new Google Contacts integration is a major improvement!

<div>
  <div>
    <div>
      <p>
        <span>Web App</span>
      </p>

      <p>
        <span>Integrations</span>
      </p>
    </div>

    <div>
      * Integrate with Google Contacts with the ability to:
        * Search contact lists and groups and send messages to the contacts number
        * Match names to numbers in the web reports and chats
        * Save new contacts from SBMG messages to Google Contacts for later
      * Upgraded reporting summary to a larger chart integrating total counts
      * Feedback form added for you to share bug reports and your thoughts in a review or feature request for our team
      * Correcting display of sending limits to match updated limits from July
    </div>
  </div>
</div>

We have more in the works already for next month for SBMG android too!

## July '24

Another strong set of updates for you this month with more UI improvements and some backend updates to help address common issues we are seeing.

<div>
  <div>
    <div>
      <p>
        <span>Android</span>
      </p>
    </div>

    <div>
      Version 1.2.1 released

      * UI improvements
        * Login layout improved and shows loading state while registration in progress
        * Main view displays clearer status and count of messages recognised by the device in send processing
        * Settings clear button and inside the organisation and clarity of elements improved.
      * Improved send processing pipeline
      * Background connection observability improvements (see web section below)
      * Stability and bug fixes
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <p>
        <span>Web App</span>
      </p>
    </div>

    <div>
      * Introducing our new 'Chats' view for Boost and Pro users.
        * View recent messages in a chat conversation view.
        * Start new threads with new contacts from the same page.
        * Search the contact number or content of all recent messages.
        * Quick copy message content.
        * Emoji tool to simply send a quick 👍 or suggest special characters to enhance a message.
      * Device connection status indicator now shows in the footer.
        This shows the approximate last seen time of your registered gateway device.
      * Message timestamps are now shown in your local timezone (previously UTC time).
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <p>
        <span>API</span>
      </p>
    </div>

    <div>
      * Increased contact limit per send:
        * Base increased from 5 contacts to 50 contacts per send request
        * Boost increased from 10 contacts to 200 contacts per send request
        * Pro increased from 15 contacts to 500 contacts per send request
    </div>
  </div>
</div>

## June '24

New quality of life improvements and significant engineering improvements to services for continued developement.
We're taking onboard all your feedback, this month you'll see the theme of addressing as many challenges as possible to enhance experience and reliability.

<div>
  <div>
    <div>
      <p>
        <span>Android</span>
      </p>
    </div>

    <div>
      Version 1.2 released

      * Improved connectivity and reliability for delivery of messages.
        Testing has seen 99.5% delivery in sample runs up from batches of 1 to 500 messages.
      * Message deduplication to avoid repeated sends of a requested message of the previous 5000 messages sent in a session.
      * Login improvements disabling login button while processing device registration.
      * Background server usage improvements.
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <p>
        <span>Web App</span>
      </p>
    </div>

    <div>
      * Expanded reporting data avaliable with all messsages loaded improved from the previous 50.
      * Composer destination improvements:
        * Broader acceptance parsing phone number formats to improve compatiblity with your existing contact lists
        * E.164 (e.g. `+6427001002`) phone number validation highlighting in composer.
        * Contact limit counter display on composer.
      * New CSV validation [helper tool](https://portal.sbmg.app/messaging#csv-tool).
        Upload a CSV export from another system such as Google Contacts or Salesforce to prepare contact lists for messaging.
      * Background improvements from the API (see below).
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <p>
        <span>API</span>
      </p>
    </div>

    <div>
      Another larger background change that has been in the works and is ready to rollout. This will enable a lot of planned improvements across the SBMG service.

      * All API endpoints have had infrastructure uplifted for improved engineering management.
      * New API endpoint pattern (e.g. `/report` → `/v1/reporting/detail`) to allow more features provided on our api, see [API reference](/api-reference/authentication) for details.
      * API changes are backwards compatible with your integration using our original API (released and requiring no customer change).
        Original SBMG endpoints will be supported to at least Jan 2025.
        Planned API feature improvements in the pipeline will be avaliable on new endpoints which will provide value to you in any api upgrades you make.
      * New endpoints:
        * GET `/v1/reporting/usage` to retrieve a [summary of your account usage](/api-reference/v1/endpoint/reporting/usage) e.g. capacity, consumed capacity, message fragements, usage rollover date.
        * GET `/v1/reporting/webhook` to [list all your webhooks](/api-reference/v1/endpoint/webhooks/list) with the assigned labels and ids. When [creating webhooks](/api-reference/v1/endpoint/webhooks/subscribe) you can now set labels to for reference of what your webhook is for.
    </div>
  </div>
</div>

## March → May '24

A busy few months with lots of development in the background and internally testing improvements to our platform.
We have an Android update in flight iterating alongside significant backend improvements with the target of a June release.
For now though, we have some nice upgrades for web users:

<div>
  <div>
    <div>
      <p>
        <span>Web App</span>
      </p>
    </div>

    <div>
      * Sim options selector fixed for sending on dual sim setups
      * Navigation update for visual clarity. See the page you are going to select and the page you are on easily
      * Big reporting upgrade with a fresh new look and new additions
        * Messaging summary metric widgets
        * Quick visualisation of messaging with daily inbound and outbound charts
        * Easy access filters for direction and status
        * Refreshed table UI
        * Instant sorting, just select the column header you want ordered.
        * Clearer reporting quick action options for Boost and Pro users.
          Export CSV and quick compose actions are now directly above your report table.
          This also comes with flexibility improvements so you can now select a single/multiple/all records for follow-up/reply messages or export instead of the previous single message selection.
    </div>
  </div>
</div>

## Febuary '24

<div>
  <div>
    <div>
      <p>
        <span>Android</span>
      </p>
    </div>

    <div>
      Version 1.1 released

      * Dual sim support. If your phone has multiple sim slots this enables you to have multiple contact numbers for messaging use cases,
        for example you can have one number for sales & marketing while the other line is reserved for customer support.
      * Improved app background activity responsiveness
      * A collection of stability improvements (session management, sending processes, support logging)
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <p>
        <span>Web App</span>
      </p>
    </div>

    <div>
      * Sim optionality in sending with carrier and phone number details
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <p>
        <span>API</span>
      </p>
    </div>

    <div>
      * Supports sending option of sim slot in requests. [See docs](http://localhost:3000/api-reference/endpoint/messaging/send-sms)
      * Fixes to message sending performance and error handling.
    </div>
  </div>
</div>

## January '24

<div>
  <div>
    <div>
      <p>
        <span>Web App</span>
      </p>
    </div>

    <div>
      * Walkthrough of setup and sending your first message in minutes [here](http://localhost:3000/user-guide/sending-on-the-web)
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <p>
        <span>API</span>
      </p>

      <p>
        <span>Integrations</span>
      </p>
    </div>

    <div>
      * New guides and example integrations with email2sms and api avaliable [here](https://www.jungledrum.com/blog)
    </div>
  </div>
</div>

## December '23

<div>
  <div>
    <div>
      <p>
        <span>Android</span>
      </p>
    </div>

    <div>
      * Check for gateway updates in setting
      * Remote call forwarding configuration
      * Device registration support metadata
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <p>
        <span>Web App</span>
      </p>
    </div>

    <div>
      * Call forwarding configuration in settings
      * Password reset capability added
      * Significant improvement to sending response time (clicking send to submission) from \~12 seconds to less than 2 seconds
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <p>
        <span>API</span>
      </p>
    </div>

    <div>
      * `/sms` response time improvements (as seen in the web portal)
      * `/sms` returns the gateway's message id in `200` response
      * Architectural improvements
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <p>
        <span>Integrations</span>
      </p>
    </div>

    <div>
      * Chat GPT integration avaliable to GPT 4 subscribers. Find more <a href="/integrations/gpt">here</a>.
      * Zapier triggers avaliable alongside actions in our beta Zapier integration. Find more <a href="/integrations/zapier">here</a>.
    </div>
  </div>
</div>

## November '23

<div>
  <div>
    <div>
      <p>
        <span>Android</span>
      </p>
    </div>

    <div>
      * Background login refresh
      * Report status
    </div>
  </div>
</div>

<div>
  <div>
    <div>
      <p>
        <span>Web App</span>
      </p>
    </div>

    <div>
      * Usage reporting
        * Plan data consumed
        * Forecasted total usage
        * Plan capacity details
        * Summary metrics of total messages sent and traditional SMS fragments
      * New message send statuses as reported by SMS modem
      * Reporting column formating improved particularly around dates
      * Reporting actions improved removing SBMG sender id signature from generated template
    </div>
  </div>
</div>

More improvements and new features are in the pipeline and we'd love to here what matters to you. Please email us your suggestion at [support@sbmg.app](mailto:support@sbmg.app).


# SBMG Updates H1 2024
Source: https://sbmg.app/blog/sbmg-updates-h1-2024

Significant updates to SBMG service in the first half of 2024

## SBMG Updates H1 2024

**8 Jul 2024**

Hi there!

Over the past couple of months we've rolled out some significant updates to SBMG and wanted to take a bit of time to highlight the key elements for you.

### Plan Updates

First off, a [plan update](/blog/product). Across the service we've raised per request sending limits. A lot! Here's what that looks like over our plans:

* **Base**: from 5 to 50 destinations per send **(10x)** 💪
* **Boost**: from 10 to 200 destinations per send **(20x)** 🤩
* **Pro**: from 15 to 500 destinations per send **(33x)** 🤯

I think you'll agree that is quite an improvement to allow queueing of more messages for sending.

Now, on to the product updates…

### API 👷

Our API services are the backbone of SBMG. Many of our upgrades you see are enabled by our APIs and there are more you don't see such as those rolled out in June alongside v1.2 on Android. These are important developer updates for anyone with custom integrations, please skip ahead if this doesn't sound like you.

We've defined new endpoints to meet feature requests on our API and in the process clarified our endpoint pattern. We are backwards compatible but do not intend to update logic behind the original endpoint pattern due to architectural improvements we are making. Currently the plan is to keep these routes active through to January 2025 at least but we would welcome feedback on what your timelines could be to change endpoints given minimal to no other request changes. We will of course monitor usage and reach out in the coming months if you are affected and we have not already established a timeline with you.

To find out more please see our [June changelog](/blog/product).

### Android 📱

Version 1.2.1 of our app is now available with a collection of improvements and fixes for anyone on earlier 1.1 versions. Without getting too detailed on what's changed we've really been focused on connectivity and reliability which has seen:

* Tests between 1 and 500 message batches sent with a 99.5% success rate 🚀
* Duplication avoidance implemented to protect against some duplicated sending
* Multi-sim support for source address options when sending
* A lot of background improvements that help everything run smoothly 🥷

You can download version 1.2.1 from the gateway download page on portal.sbmg.app. Please reach out if you have any questions we'll be happy to help.

### Chats 💬

Seeing your conversation with a contact in a familiar messaging format has been on our roadmap for a while now and we're glad to be able to introduce this for users on *Boost* or *Pro* plans this month.

Chats is home to your messaging threads so now you can see all your messages with a contact in one place rather than scanning through your message log. We've added in some other bits like:

* Search functionality
* Quick copy
* Emoji recommendations
* A quick 👍 reaction

We have plans to continue developing on and around this view and so we are keen to hear from you how we can make this better too.

### Reporting 📊

Reporting data is at the core of our service and the raw message log just wasn't cutting it so at the end of May we released an overhaul of our reporting view with a new detailed report view. Like Chats the new detailed reporting has been in the pipeline and delivers a big change in the usability of SBMG. Reports now have:

* Summary metrics that update as you filter
* Chart visualisations for your inbound and outbound traffic
* Clearer reporting quick actions for *Boost* and *Pro* users to export and reply to messages in reporting views

### Feedback

You can jump in and get started with SBMG with one of our plans [here](/pricing). Our New Zealand based team are always happy to help with any questions or suggestions for our tools to continue improving our service 🇳🇿 If SBMG looks to be of interest to you but you still want to find out more our team's just an email away at [support@sbmg.app](mailto:support@sbmg.app), please say hi! 👋


# SMS TradeStation Order Alerts with Email2SMS
Source: https://sbmg.app/blog/sms-tradestation-order-alerts

Guide to setting up TradeStation order alerts via SMS using SBMG Email2SMS

## SMS TradeStation Order Alerts with Email2SMS

**9 Jan 2024**

### Introduction

TradeStation offers email alerts through the trade manager preferences but to enhance this with more responsive SMS we can send the email to SBMG to use Email2SMS. This is a relatively simple integration with a few simple settings for your mailbox TradeStation will be able to send the email and with an SBMG pro plan invoke an SMS to your mobile for a variety of TradeStation order confirmations.

### How To

After setting up Email2SMS in your account as guided [here](/user-guide/email2sms), we can configure email alerts in TradeStation.

From TradeManager open your preferences:

<img alt="TradeStation Preferences" />

In these preferences you can tailor configuration of notifications for different order statuses. Select the order status you want to receive sms notifications for, check '*Enable e-mail notification*', and then 'Configure…' to open the email detail modal.

<img alt="TradeStation Email Configuration" />

In this view there are two key sections for our configuration, 'To' for where we are going to send the email, and 'From' for the mailbox details TradeStation will use to email you from your own email.

Handling the destination email address is easy with SBMG's Email2SMS, just enter your phone number in international format (e.g. `+64215678899`) followed by '@sbmg.app'. Your end result will be something like `+6422987456@sbmg.app`. Easy!

The sending email will have some variation depending on your email service but a search for your email 'SMTP server settings' should yield results for most services. Here we will work with Google Workspace settings found [here](https://support.google.com/a/answer/176600?hl=en) (this resource might change over time). The key unknown details are the SMTP server name or IP and the port depending on the protocol (SSL/TLS/None). For Gmail one option is `smtp.gmail.com` with SSL port `465`. Enter these settings and for account name and password simply add the Google Workspace email and password. Depending on your organisation settings you may need to use an app password as TradeStation isn't using 2FA for this process, in such case follow the [details here](https://support.google.com/accounts/answer/185833?hl=en) for how to generate an app password and use this in place of your password.

A quick click of the 'Test' button should yield a successful result before saving your settings.

<img alt="TradeStation Test Success" />

Now when TradeStation has an order alert it will send a email to SBMG Email2SMS from your email service to trigger an SMS to your phone through your gateway.

### Conclusion

Get detailed trade SMS notifications from TradeStation with the highest reach communication channel to ensure the best chance of keeping track of your automated trading strategies on the go wherever you are. For details on TradeStation's TradeManager notification, visit their [Documentation](https://help.tradestation.com/10_00/eng/tradestationhelp/tm/set_order_notify_methods.htm). For information on Jungle Drum SBMG Email2SMS, see our documentation [here](/user-guide/email2sms).

*Email2SMS is a SBMG Pro feature required for this integration. [Upgrade here](/pricing).*


# TradingView SMS Alerts via Zapier
Source: https://sbmg.app/blog/tradingview-and-sms-via-zapier

Guide to setting up TradingView alerts with SBMG via Zapier for SMS notifications

## Enhancing Trading Strategies with SMS Alerts: Integrating TradingView and SBMG via Zapier

**3 Jan 2024**

### Introduction

In the fast-paced world of trading, timely information is crucial. TradingView offers a variety of alert options, but integrating these alerts with SMS notifications can provide traders with a significant edge. This article guides you through setting up SMS alerts for TradingView signals using SBMG via Zapier, enhancing your trading strategy with immediate and convenient notifications.

### Understanding TradingView Alerts

TradingView, a popular platform among traders, offers several alert types to suit different trading strategies:

* **Real-Time Price Alerts**: Get notified about specific price movements.
* **Indicator Alerts**: Use over 1,000 indicators for tailored alerts.
* **Strategy Alerts**: Receive notifications when strategy orders are executed.
* **Drawing Tool Alerts**: Set alerts based on your chart drawings.
* **Specific Condition Alerts**: Including 'Crossing', 'Greater/Less Than', and 'Moving Up/Down'.

These alerts can be set up easily through various means on the TradingView platform and offer different notification options including in-app notifications, emails, and webhook URLs​​​​.

### The Value of SMS Alerts in Trading

While TradingView's native alert systems are efficient, SMS alerts offer distinct advantages:

* **Immediate Notifications**: SMS alerts reach you instantly, crucial for time-sensitive trading decisions.
* **Accessibility**: Unlike emails or app notifications, SMS doesn't require internet access, ensuring you're alerted under various circumstances.

### Integrating TradingView Alerts with SBMG via Zapier

SBMG, when combined with Zapier, can turn TradingView alerts into SMS notifications. Here's how to set it up:

1. **Setting Up a Webhook in TradingView**: While creating an alert in TradingView, select the 'Webhook URL' option. This enables the alert to send data to a specific URL when triggered.
2. **Creating a Zap in Zapier**:
   * **Trigger**: Choose 'Webhook by Zapier' and configure it to catch the TradingView webhook.
   * **Action**: Select SBMG's Zapier action and set it to transform the webhook data into an SMS message.
3. **Test and Activate**: Ensure the Zap works correctly through testing, and then activate it for real-time usage.

### Step-by-Step Guide to Creating the Zap

1. **Create a TradingView Alert**:

   * Go to TradingView, choose your criteria for the alert, and in the alert settings, select 'Webhook URL'.
   * Enter the URL provided by Zapier (created in the next steps).
   * Configure your alert message as json in the template below

   ```json theme={null}
   {
     "auth": "YOUR PASSPHRASE HERE",
     "alert": "YOUR ALERT MESSAGE HERE"
   }
   ```

   As an additional security layer this example adds a passphrase we can validate in our zap.

   * Once setup your alert should look something like this (depending on your requirements):

   <img alt="TradingView Alert Setup" />

2. **Setting Up Zapier**:

   * Log into Zapier and create a new Zap.
   * Choose 'Webhook by Zapier' as the trigger and 'Catch Hook' as the event.

   <img alt="Zapier Webhook Setup" />

   * Add a filter for the passphrase in your alert as set in the TradingView alert.

   <img alt="Zapier Filter Setup" />

   * In the action step, select SBMG and configure the SMS message using the alert of the webhook and setting your phone number.

   <img alt="SBMG Zapier Action" />

3. **Testing**:
   * Test the Zap to ensure the SMS is sent correctly when the TradingView alert triggers.

4. **Deployment**:
   * Once testing is successful, activate the Zap.

### Benefits of Using SMS Alerts

1. **Immediate Notifications:**
   * SMS alerts are delivered instantly to your mobile device, ensuring that you never miss an important trading signal.

2. **Reliability:**
   * Unlike email notifications, which can sometimes be delayed or filtered into spam folders, SMS messages are highly reliable and are typically delivered within seconds.

3. **Convenience:**
   * With SMS alerts, you can stay informed about market movements even when you're away from your trading desk. This is particularly useful for traders who are frequently on the go.

4. **Customization:**
   * The integration allows for a high degree of customization. You can tailor the SMS messages to include the specific information you need, such as asset names, alert conditions, and current prices.

### Conclusion

Integrating TradingView alerts with SMS notifications via SBMG and Zapier offers a robust solution for traders needing immediate information. This setup ensures you never miss a critical market movement, regardless of your current digital access. With this guide, setting up this integration is straightforward and can be a game-changer in your trading strategy.

For detailed instructions on setting up TradingView alerts, visit their [Alerts Documentation](https://www.tradingview.com/support/solutions/43000595315-how-to-set-up-alerts/). For information on SBMG Zapier actions, refer to the [Integration Page](/integrations/zapier/actions).


# Google Contacts
Source: https://sbmg.app/integrations/google-contacts

Connect your Google account to access additional features

<Note>
  Our Google Contacts integration is in beta.
  During this time it will be avaliable to users on all plans including Base.
  Later this year we expect to complete our beta introductory period and Google Integration will be avaliable as an upgrade from Base on Boost & Pro.
</Note>

Your Google account can provide additional data for contacts in SBMG.
If you choose to connect your Google account your Google contacts will be avaliable for reporting, autocomplete and directory.

## Connect

Connecting is easy, here's how you can get setup.

1. Click avatar
   In the web portal simple click your avatar in the top right.

2. Sign in with Google

3. Authorise contact access

4. Connected

<Info>
  SBMG does not store or retain access to your contact data outside the session you directly authorise.
  This means on different browsers or after logging out from Google you will need to connect too.
</Info>

## Unlocked features

### Contact directory

Contact directory is your Google address book within SBMG.
You have access to all your contacts clearly presenting name, business name, tags (groups/labels), phone number, and some handy actions.

This data is not retained by SBMG and access can be removed instantly if you'd like to stop using this optional capability. See how to disconnect <a href="/integrations/zapier/introduction">here</a>.

Tags gives you a great way to segment contacts possibly by customer type, interest, event, team, etc.
This is totally in your hands as to what and how you'd like to use these.
We love automation and so would suggest using a tool like Zapier to update labels on your contacts after key events such as:

* <a href="/integrations/zapier/triggers">Recieving a keyword from them via SBMG</a>.
* A purchase on your Shopify store.
* An email to your support mailbox.

With automatic tagging you can then use the <a href="/integrations/zapier/actions">SBMG action in Zapier</a> to send a message right away or at a scheduled time.

Actions in the contact directory give you quick ways to interact with that contact. Actions include:

* Edit (opens the Google contact directly to edit, SBMG doesn't have access to modify your contacts).
* View report (opens a detail report filtered to the selected contact).
* Message (poplulates the message composer for you to forget the number and just write your message to send).

We'd like to add more actions in the future, use the feedback option in SBMG to let us know what you'd like to see.

Finally of course, you can search and filter your contacts by any of the displayed data to find exactly who you are looking for.

### Contact messaging

When sending an SMS your contacts are searched as you type to find suggestions of contacts to complete for you.
This search, like the contact directory, checks all fields (name, business, tags, number) to help find your contact as quick as possible.
Simply click the option to complete and the contact will be populated to send.

### Contacts in reports

This is a feature of popular request and what's better than nothing extra for you to do!

With your contact data connected SBMG can match the mobile numbers from your message log with your contacts.
Reporting will show the name of the contact you've been messaging to make reports much more comprehendible than a list of numbers.
We do our best to connect the dots even with different number formats you may have previously stored but recommend maintaining your contacts in international E.164 if possible (e.g. +642743435656)

## Disconnect

If you don't want to use Google Contacts with SBMG or want to change the Google account you've connected that can easily be done, here's how:

1. Click avatar
   In the web portal simple click your avatar in the top right.

2. Disconnect
   Hover over your email to reveal disconnect and click to complete.

3. Reconnect
   If you want your contact data again or to select your other Google account, just <a href="/integrations/google-contacts#connect">repeat the connection steps</a>


# Integration Introduction
Source: https://sbmg.app/integrations/introduction

Easily get setup and sending with integrations with popular platforms.

<CardGroup>
  <Card title="Find your connector" icon="grid-5" href="#our-integration-catalog">
    Connect to thousands of other apps as triggers with connectors for the most popular workflow platforms.
  </Card>

  <Card title="Get streamlined and automated" icon="person-running-fast" href="/integrations/examples">
    Use SBMG integrations to eliminate manual repeated process, check use case examples of triggers you could use.
  </Card>
</CardGroup>

## Our Integration Catalog

We are working on integrations with high connectivity to empower a wide variety of flexible
integrations for users requiring low to no-code.

| Property                                                               | Triggers available | Actions available |
| ---------------------------------------------------------------------- | ------------------ | ----------------- |
| <a href="/integrations/zapier/introduction">Zapier</a>                 | ✅                  | ✅                 |
| <a href="/integrations/power-automate/introduction">Power Automate</a> | 🕜                 | 🕜                |
| 🕜 More coming soon                                                    | 🕜                 | 🕜                |


# Zapier Actions
Source: https://sbmg.app/integrations/zapier/actions

Add SMS sending actions to your Zapier workflow

Get beta access to our Zapier integration <a href="https://zapier.com/developer/public-invite/186462/3a5a5ae4c18ed0b216f8e934e9df5369/">here</a>.

## Send SMS

### Fields

Fields required for your sending.

<ParamField type="string">
  The phone number of the recipient in E.164 international format (recommended) or in the local format if sent domestically.
</ParamField>

<ParamField type="string">
  The content of the SMS message.
</ParamField>

## Get Last Message

Use this to query your messages to find the newest message matching search critia (source, destination, direction...)

### Fields

Fields available to use in your query.

<ParamField type="string">
  The phone number of the recipient in E.164 international format (recommended) or in the local format if sent domestically.
</ParamField>

<ParamField type="string">
  Start date of the report query. Format `YYYY-MM-DD` for example: `2023-01-30`
</ParamField>

<ParamField type="string">
  End date of the report query. Format `YYYY-MM-DD` for example: `2023-01-30`
</ParamField>

<ParamField type="string">
  Filter for messages containing a given metadata key.
</ParamField>

### Returned Result

We return as much useful detail of the message as available.

<ParamField type="string">
  The phone number of the recipient in E.164 international format (recommended) or in the local format if sent domestically.
</ParamField>

<ParamField type="string">
  Start date of the report query. Format `YYYY-MM-DD` for example: `2023-01-30`
</ParamField>

<ParamField type="string">
  End date of the report query. Format `YYYY-MM-DD` for example: `2023-01-30`
</ParamField>

<ParamField type="string">
  Filter for messages containing a given metadata key.
</ParamField>


# Zapier Triggers
Source: https://sbmg.app/integrations/zapier/triggers

Use inbound SMS to trigger workflow automations

Get beta access to our Zapier integration <a href="https://zapier.com/developer/public-invite/186462/3a5a5ae4c18ed0b216f8e934e9df5369/">here</a>.

## Inbound Message Recieved

### Data out

Fields available for your zap from the message data.

<ResponseField name="account_id" type="number">
  The account ID associated with the message.

  Example: `2a1221ab-4b4b-4c4c-9cc9-9999abcd0808`
</ResponseField>

<ResponseField name="source_address" type="string">
  The phone number of the message sender.

  Example: `+64270010203`
</ResponseField>

<ResponseField name="direction" type="string">
  The direction of the message (inbound).

  Example: `INBOUND`
</ResponseField>

<ResponseField name="content" type="string">
  The content of the message.

  Example: `Hello world`
</ResponseField>

<ResponseField name="date" type="string">
  The timestamp of the message in ISO 8601 format.

  Example: `2023-08-19T05:28:11Z`
</ResponseField>

<ResponseField name="user_metadata" type="object">
  Additional metadata associated with the message.
</ResponseField>


# Email2SMS
Source: https://sbmg.app/user-guide/email2sms

Learn how to send a message from your email inbox with Email2SMS

## Configuration

For users on the Pro plan, after completing the account and gateway setup in the [**'Send your first SMS'** guide ](/user-guide/sending-on-the-web), we can configure Email2SMS for your email.

Email2SMS enables you to manage your SMS conversations through your normal email inbox (no extensions required).
Email2SMS requires email registration to send via your account. To configure Email2SMS follow the steps below:

<Steps>
  <Step title="Open Settings">
    In the SBMG portal click the *Settings* menu item and then select the [**Email2SMS** tab](https://portal.sbmg.app/settings#email2sms).
  </Step>

  <Step title="Add Email">
    The first time you visit this page you will have no configured permitted senders.
    An allowance for an email can be added by clicking the **Add Email** button and entering the email you want to allow to send SMS via email with your SBMG account.
  </Step>

  <Step title="Manage Emails">
    You can add additional emails repeating step 2 for up to 15 emails on the Pro plan.
    Emails can be removed from the whitelist by clicking the delete button alongside the configured email.
  </Step>
</Steps>

## Send it

In your email client simply compose a new message to the mobile number (E.164 internal format) you want to message followed by `@sbmg.app` (e.g. `+64210009988@sbmg.app`).
Sending that email will send an SMS with the content of your email.

## Tips

To avoid sending signatures or when replying to an Email2SMS thread, the entire email trail, user the `$END` terminator to mark the end of your message (example below).

```
Hi there,

This is a SMS message sent with Email2SMS on SBMG. You can reply here and I'll receive your message as a reply to this email.

Have a great day 👋

$END

Email signature conent with images, links and francy formatting that would be long mess in plain text will not be included as I've used the terminator above.
```


# FAQs
Source: https://sbmg.app/user-guide/faq

Find Answers to your Questions.

## Getting Started

If you have a question that do not currently appear on here, please advise us via our: <a href="https://apishift.co.nz/contact/">contact</a> page

***

**Q**: Do you have a free trial offer?

**A**: Yes we do. Navigate to <a href="https://apishift.co.nz/marketplace/sbmg/">our home page</a> and click on the free trial offer at the bottom of the page.

***

**Q**: I opened and closed the invite, now I get a page with no credentials. What should I do?

**A**: Contact our <a href="https://apishift.co.nz/contact/">support</a> to resend the invite

***

**Q**: What do I need to get started?

**A**: To get started with SBMG, you'll need three things: an Android phone, a SIM card with a messaging plan, and a stable internet connection (Wi-Fi is recommended). For a detailed list of supported devices, please see our <a href="https://sbmg.app/user-guide/supported-device-list">supported device list</a>.

***

**Q**: When I download the app, I get the message “Unsafe app Blocked”, what should I do?

**A**: This is a generic warning from Android for apps installed outside of the Google Play Store. Our app requires certain sensitive permissions to function correctly, but it is safe to use. For the best experience, we recommend installing SBMG on a dedicated Android device that can remain connected to power and Wi-Fi. This ensures stable operation and helps separate your SBMG activity from personal communications and other apps, which can improve performance and maintains data privacy.

***

**Q**: How do I import contacts from my phone?

**A**: While direct phone contact syncing isn't available, you can import contacts via a CSV file on the web. Navigate to: <a href="https://sbmg.app/user-guide/send-to-csv-contact-list">Uploading a CSV</a> for instructions. Additionally, SBMG now integrates with Google Contacts, allowing you to use contacts stored in your Google account. For more details on new features, please check our updates.

***

**Q**: I need to do a password reset, how do I go about this?

**A**: You can reset your password on our <a href="https://sbmg.app/login">login page</a>. Look for the password reset option below the login form. If the issue persists, contact our <a href="https://apishift.co.nz/contact/">support</a>

***

## General

**Q**: I can send messages from the web portal, but I'm not receiving any inbound messages there. What should I do?

**A**: It is possible that your phone is having errors, pushing the inbound messages back to us. The device might be experiencing an authentication error in the background. In the Android app's top right corner you'll have a menu button that drops down to show settings. To try and resolve:

* open settings
* click the log out button
* close the app from app switcher
* once you're logged out and the app has been shutdown you can open it again and sign back in.

This should successfully resolve the issue and messages should start to appear in the web.

***

**Q**: Which countries do you operate in?

**A**: While our main operational focus is Australia and New Zealand (ANZ), our service can technically send internationally and is applicable in other regions too. This list is forever growing, do watch our <a href="https://apishift.co.nz/marketplace/sbmg/">website</a> or contact our <a href="https://apishift.co.nz/contact/">support</a> if you have any questions.

***

## Billing and Account Management

**Q**: How would I know to which plan I am subscribed to?

**A**: Go to Settings, and under the Configuration tab the Plan will be specified under Your Profile

***

**Q**: I cannot use Email2SMS, any reason for this?

**A**: You might be on the Base or Boost plan, as Email2SMS is a Pro plan feature. You will need to upgrade. Please contact support to process the upgrade.

***

**Q**: Who do you use as your payment service provider?

**A**: We partner with Stripe for our payment processing to ensure secure and reliable transactions.

***

**Q**: What details do you collect from me, and why?

**A**: We collect details like your contact details (email; etc); the date you signed up; the plan you subscribed to; etc. These are mostly for billing purposes, but also for us to provide the best service to you possible. Your details are not shared.

***

**Q**: What is Message Data, and how does it relate to my plan?

**A**: Message Data refers to the size of each message, measured in kilobytes (KB). Your subscription plan determines the total amount of message data you can send and receive, affecting how many messages you can transit through our gateway each month.

***

## App and Troubleshooting

**Q**: What are the most recent changes you have made to the app and your product?

**A**: Some of the most recent changes (for the latest updates, please visit our <a href="https://sbmg.app/blog/product">product changelog</a>):

* We increased Sending Limits (10x for Base plan; 20x for Boost plan and 33x for Pro plan!)
* We defined new endpoints on our API
* We implemented better duplication detection
* You are now able to see all your messages with a contact in one place (for those on the Boost or Pro plan) via the Chats view function
* We improved our detailed reporting function
* We are always making improvements and optimisations in the background to keep things running smooth.

***

**Q**: How do I get an improvement or new feature suggestion to you?

**A**: We really appreciate your suggestions! You can provide those to <a href="https://apishift.co.nz/contact/">support</a>, or alternatively, use the feature request option within our web portal's helpdesk. We will endeavour to keep you in the loop of progress.


# Message Statuses Explained
Source: https://sbmg.app/user-guide/message-statuses

Understand the different statuses a message can have and what to do if a message gets stuck

This guide provides a detailed explanation of the various message statuses you may encounter when sending messages through our service.
Understanding these statuses can help you troubleshoot issues and ensure your messages are delivered successfully.

## Status Flow Diagram

Below is a diagram illustrating the approximate flow of message statuses and their transitions.

```mermaid theme={null}
graph TD
    Queued --> Pushing
    Pushing --> Pending
    Pending --> Sent
    Pending --> PartialSent[Partial Sent]
    Pending --> Failed
    Failed --> Retried
    Retried --> Pending
    Pushing --> Blocked

    style Sent fill:#90EE90,stroke:#333,stroke-width:2px,color:#000
    style PartialSent fill:#90EE90,stroke:#333,stroke-width:2px,color:#000
    style Blocked fill:#FFB6C1,stroke:#333,stroke-width:2px,color:#000
    style Retried fill:#FFB6C1,stroke:#333,stroke-width:2px,color:#000
    style Failed fill:#FF6347,stroke:#333,stroke-width:2px,color:#000
    style Queued fill:#ADD8E6,stroke:#333,stroke-width:2px,color:#000
    style Pushing fill:#ADD8E6,stroke:#333,stroke-width:2px,color:#000
    style Pending fill:#ADD8E6,stroke:#333,stroke-width:2px,color:#000
```

## Status Breakdown

### Queued

**Meaning**: The request to send the message is with our servers, waiting to be processed. It should be sent to the phone shortly.

**What to Do if Stuck**: If a message remains in the "Queued" status, could indicate a server or service issue, especially if all your messages are queued.
Alternatively, there might be an unhandled rejection of your message.
In any case, you can contact support, and we will investigate to clarify and improve our handling of the message status.

### Pushing

**Meaning**: The message has been processed by the service server and is on its way to the mobile gateway.

**What to Do if Stuck**: If a message is stuck in "Pushing," it likely indicates that the phone is offline or unable to acknowledge receipt of the message.
Check the phone's status to ensure it is as expected.
You can also refer to the status readout in the footer of the Web App (portal.sbmg.app), which uses a traffic light signal to indicate if the phone appears healthy, along with an approximate "last heard from" time.

### Blocked

**Meaning**: The message has been prevented from being sent, likely due to opt-out or account suspension actions.

**What to Do if Stuck**: If all messages are being blocked, it is likely that your account has been suspended.
You should contact support if they haven't reached out to you already.
Typically, suspensions occur due to billing issues or misuse, and we proactively communicate with customers in such cases.

### Failed

**Meaning**: The message reached the phone, but it failed to send.
This can happen due to airplane mode being on, no credit on the phone, carrier rejection, or lack of cell service.

**What to Do if Stuck**: Check the phone to ensure it is in an expected state with good connectivity.
Address any issues like airplane mode, credit balance, or service availability to resolve the problem.

### Retried

**Meaning**: These are messages that initially failed and have been replayed to attempt sending again.
This will create a new message entry in your report, and the metadata of the message will indicate it was retried from a prior failed attempt.

**What to Do if Stuck**: Monitor the status of the retried message to see if it progresses to "Sent" or fails again.
If it continues to fail, refer to the troubleshooting steps for "Failed" status.

### Pending

**Meaning**: The message is on the mobile gateway, which has acknowledged the request to send and has it queued, preparing to send.

**What to Do if Stuck**: It is normal for messages to take a while to send, especially if you are sending a large number.
We randomly trickle the messages out with a configuration to comply with fair use policies.
Over time, depending on the size of your send, you should see these progress to a final status like "Sent" or "Failed."

### Partial Sent

**Meaning**: We have received a status update from the mobile gateway modem for some segments of the message.
This usually means the whole message was sent, though we are yet to see a message that is only partially sent in reality.
Experience with feedback from mobile modems shows that if we don't receive confirmation for all fragments (which would be a "Sent" status), we typically receive confirmation for at least 70% of the fragments.

**What to Do if Stuck**: Unless you are persistently getting "Partial Sent" statuses, we consider these messages as sent, likely due to race conditions.
If this status persists, contact support for further investigation.

### Sent

**Meaning**: The message has been successfully sent, and from everything we can see, it appears to have gone out without issues.

**What to Do if Stuck**: No action is needed. Everyone's happy—the message has been delivered successfully!


# Mobile Phone Plans
Source: https://sbmg.app/user-guide/mobile-plans

BYO SIM suggested options

SBMG provide the software to connect your workflows and messaging remote from the android phone so you
expand beyond physically holding the phone and typing your messages but you must bring your own mobile
plan and SIM. This is a requirement as we cannot resell you network messages (i.e. a phone plan).
With so many mobile phone plans as options this guide aims to help clarify what you need and when with some possible choices.

## Decision Matrix

This is a summary of the key considerations of suggesting a plan type for you.

|                           | Buy phone outright      | Buy phone on plan       |
| ------------------------- | ----------------------- | ----------------------- |
| **International sending** | [*Postpaid*](#postpaid) | [*Postpaid*](#postpaid) |
| **Only sending domestic** | [*Prepay*](#prepay)     | [*Postpaid*](#postpaid) |

To dive into more details continue reading.

## Sending destination

### Domestic

When sending within the country of your SIM [Prepay Plans](#prepay) are the most cost effective messaging option.
In New Zealand most carriers offer unlimited SMS\* capability to Australia and New Zealand destinations.

<sup>\*</sup>Fair use policy applies. SBMG respects fair use on consulation from carriers with usage limits and the processing methodology of messages.

### International

If you are sending internationally you will incur varying charges depending on where in the world you are sending from/to.
We recommend checking with your carrier for these rates which may change over time.
Some carriers offer bundles for sending to overseas destinations that can reduce your cost
but act like prepay credits in being consumed with your sending.

Due to varying rates to send we suggest that users wanting to send messages to international numbers
have a [Postpaid](#postpaid) account with the carrier so you don't face credit issues between plan renewals.
This will result in being charged at the end of the month for the base plan and the international surcharges based on your use.

## Phones

To use SBMG you need an Android phone [see requirements here](/user-guide/supported-device-list) and
this can be a factor in the plan and provider you choose.
We do recommend that you run SBMG on a dedicated phone that can be left at home or in an office on wifi
and connected to a power adaptor for the best result.
If you have a dedicated phone already set aside that could be used as your gateway then you've checked
this box and can continue.

The phones to run SBMG can be purchased outright around the \$250 mark from various retailers.
However it might be worth considering purchasing a molbile on your plan for some of the benifits this
can offer and the ability to spread the setup cost over a few months.
Phone and plan deals can be found with carriers and can get you the SIM purchase, mobile plan and
interest free phone (along with any bonuses) on a [Postpaid](#postpaid) account.

## Plan Types

### Prepay

This is the simplist option to get sending for most SBMG users where you just need to send within the country.
Prepay is the cheapest sending option but you must consider the [sending destination](#sending-destination)
for your messages to avoid running into credit issues due to surcharges.

<Tip>Setup auto payment of your prepay plan</Tip>

**Suggested Options:**

<CardGroup>
  <Card title="2Degrees">
    Unlimited texts to NZ & AUS.

    Starts at \$10<sub>/month</sub>

    [<u>Find more</u>](https://www.2degrees.nz/mobile-plans/prepay)
  </Card>

  <Card title="Spark">
    Unlimited NZ SMS *(terms also say AUS)*

    Starts at \$20<sub>/28 days</sub>

    [<u>Find more</u>](https://www.spark.co.nz/online/shop/mobile-plans?category=prepaid_retail_extra)
  </Card>

  <Card title="One">
    Unlimited NZ SMS *(terms also say AUS)*

    Starts at \$14<sub>/28 days</sub>

    [<u>Find more</u>](https://one.nz/prepay/)
  </Card>
</CardGroup>

<Warning>
  **Carrier T\&Cs**

  * T\&Cs do apply to unlimited such as fair use and SMS to standard NZ & AUS numbers only *(not sending to special numbers like shortcodes e.g. 3880)*

  **Prepay plans are different to prepay top ups.**

  * Ensure you are getting a monthly plan with messaging included rather than
    credit to consume on messaging at standard rates
</Warning>

### Postpaid

Postpaid is our recommendation to anyone using SMS consistently and has the need to deliver to international numbers.
At the end of the month you will be charged for the plan and any extras such as your international messages
or a mobile phone that is being paid for alongside your plan.

<Tip>
  Carriers can offer group plans which can reduce the costs of plans.
  If you already have a pay monthly plan with the carrier it could be worth considering adding a connection
  to your existing plan which can be cheaper than a whole new postpaid account.
</Tip>

**Suggested Options:**

<CardGroup>
  <Card title="2Degrees">
    Unlimited texts to NZ & AUS.

    Starts at \$40<sub>/month</sub>

    [<u>Find more</u>](https://www.2degrees.nz/mobile-plans/pay-monthly)
  </Card>

  <Card title="Spark">
    Unlimited NZ SMS *(terms also say AUS)*

    Starts at \$27<sub>/month</sub>

    [<u>Find more</u>](https://www.spark.co.nz/online/shop/mobile-plans?category=postpaid\&plan=rollover_plan)
  </Card>

  <Card title="One">
    Unlimited NZ SMS *(terms also say AUS)*

    Starts at \$45<sub>/month</sub>

    [<u>Find more</u>](https://one.nz/pay-monthly/)
  </Card>
</CardGroup>

<Warning>
  **Carrier T\&Cs**

  * T\&Cs do apply to unlimited such as fair use and SMS to standard NZ & AUS numbers only *(not sending to special numbers like shortcodes e.g. 3880)*
</Warning>


# Using a CSV contact list
Source: https://sbmg.app/user-guide/send-to-csv-contact-list

Send a stream of messages from the web portal to contacts in a csv format

## Create your CSV

You can have as many columns as needed in your csv for contact properties with the only requirement being
the contact numbers have the column heading `phone_numbers` and these are formatted in E.164 international format.

## Upload your CSV

In the web portal message composer click the upload button and watch the contacts populate.

<img alt="csv upload button" />

Now you will have the valid contacts as destinations for your message.

<Tip>Consider the size of your message and the number of contacts you have to send to.
Remaining data volume capacity for your plan can be seen in the [usage report here](https://portal.sbmg.app/reporting#usage)</Tip>


# Send Your First SMS
Source: https://sbmg.app/user-guide/sending-on-the-web

Learn how to send a message from the web portal

<iframe title="YouTube video player" />

## Create a SBMG account

Head to SBMG to create an account using the invite link provided in our invite email.

## Log in on Android

On your Android browser head to the settings page at SBMG portal (<a href="https://portal.sbmg.app/settings#download">portal.sbmg.app</a>) and select
the 'Gateway Download'. You will see a button to 'Download APK' (this is only available on android browsers).
Proceed through the download, open the downloaded file and install.

Now in your app tray you will see the SBMG Gateway app. Opening the app you will be able to sign in with your
credentials created earlier.

<Note title="Android 15 and up">
  On **Android 15+** you’ll need to explicitly grant SMS permissions via the\
  Restricted settings menu.\
  For step-by-step instructions, see our\
  <a href="/user-guide/troubleshooting">Troubleshooting → Messages Not Appearing in Reports</a> guide.
</Note>

## Send it

In your browser (you can use mobile or **desktop**), the messaging view you saw ealier logging in to SBMG is
the easiest way to send.

Add a phone number of your sending destination using international format e.g. `+642199887766`. Write your message content and send it.


# Failure Alerting
Source: https://sbmg.app/user-guide/setting-up-failure-alert

Learn how to configure alerts and stay informed when messages fail to send.

Failure alerting notifies you immediately when a message cannot be sent from your gateway, allowing you to quickly address any potential issues.

## Basic alerting vs Detailed alerting

We offer two levels of Failure Alerting: Basic and Detailed.

Both settings will send an instant notification for the first time an error occurs in a 4 hour period. The primary differnce is how frequently you will receive a notification after the initial alert.

As shown below, Basic alerting will only notify you once in a four hour period that you should check the Gateway Portal to look into the issue. Detailed alerting will send you additional notifications summarising the alerts of any failures that occured within a 30 minute period.

### Illustrated difference between Basic and Detailed

<img alt="Diagram showing how Failure Alerting responds with Basic alerting setting vs Detailed alerting" />

***

| Time     | Basic                                  | Detailed                               |
| :------- | :------------------------------------- | :------------------------------------- |
| 09:30 AM | It appears one of your messages failed | It appears one of your messages failed |
| 10:00 AM |                                        | It appears 2 of your messages failed   |
| 10:30 AM |                                        | It appears 1 of your messages failed   |
| 12:00 PM |                                        | It appears 5 of your messages failed   |
| 01:31 PM | It appears one of your messages failed | It appears one of your messages failed |

## Configuration

<Steps>
  <Step title="Open Settings">
    In the SBMG portal, click the **Settings** menu item, then navigate to the
    [**Configuration** tab](https://portal.sbmg.app/settings#configuration).
  </Step>

  <Step title="Enable Failure Alerting">
    Under the **Failure Alerts** heading, select either the **Basic** or **Detailed**
    option.
  </Step>

  <Step title="Save Changes">
    Click the **Save** button to apply your changes. The new configuration will
    be applied to your gateway shortly.
  </Step>

  <Step title="Test Your Alerts">
    We strongly recommend testing this feature to ensure it works as expected.

    1. Ensure your gateway device is logged in and connected to the internet via Wi-Fi.
    2. Enable **Airplane Mode** on the device.
    3. From the SBMG portal, send a test message to your own number.

    The message status in your Dashboard should change to "Failed," and you should receive a failure alert notification.
  </Step>

  <Step title="Disable Airplane Mode">
    Once you've confirmed that alerting is working, disable **Airplane Mode** on your
    gateway device to resume normal message sending.
  </Step>
</Steps>

<Note>
  **Message stuck in "Pending" status?**

  When you enable Airplane Mode, your device's Wi-Fi may also turn off automatically. For this test to succeed, your gateway must remain connected to the internet. Most phones allow you to re-enable Wi-Fi while keeping Airplane Mode active.

  If the issue persists after confirming your internet connection, please contact our support team for assistance.
</Note>


# Supported Device
Source: https://sbmg.app/user-guide/supported-device-list

Details on what devices can be used for an SBMG SMS gateway

SBMG is built to support as broadly as possible but different devices provide different challenge particularly due to the fact manufacturers
modify characteristics of the device OS. Below are the specifications we target to support acting as a guide for finding a device to install
the SBMG SMS gateway service.

| Atrribute          | Target minimum spec                                    |
| ------------------ | ------------------------------------------------------ |
| OS                 | Android 9.0                                            |
| RAM                | 3GB                                                    |
| Supported networks | <ul><li>Spark</li><li>2Degrees</li><li>OneNZ</li></ul> |

While most devices meeting this criteria will be compatible with SBMG we are aware some devices/brands can cause problems due to thier software
including:

* Motorola
* *This list will be updated with any other problematic brands*

To avoid issues we recommend using devices already confrimed to be using SBMG by testers, partners, and customers. If you already have a device
of a brand listed below or better yet, the same year or model as one listed we would expect SBMG should work as expected.

| Brand   | Active devices                                                       |
| ------- | -------------------------------------------------------------------- |
| Samsung | <ul><li>Galaxy S8, S10 & S21</li><li>Galaxy A04, A05 & A14</li></ul> |
| Nokia   | <ul><li>C01 Plus</li></ul>                                           |


# Troubleshooting
Source: https://sbmg.app/user-guide/troubleshooting

This page is here to help you solve the most common problems

## Messages are not sending

### Messages Not Appearing in Reports

**Symptom**
You see “Message sent successfully” in the portal, but the message never shows up on the Reports page.

**Potential Cause**
Newer versions of Android are starting to require apps to be explicitly granted the SMS permission via “Restricted settings.”

**Resolution**

Confirm whether SBMG was given the SMS permission already:

1. Open **Settings** on your Android device.
2. Search for **SBMG** and tap the SBMG app in the results.
3. Tap **Permissions**.
4. If **SMS** is already listed under **Allowed**, you’re done.

If 'Allow' is greyed out and you get this pop-up:

<Columns>
  <Card>
    <img alt="Screenshot with Allow toggle greyed out" />
  </Card>

  <Card>
    <img alt="Screenshot showing &#x22;App was denied access&#x22; pop-up" />
  </Card>
</Columns>

1. Go back to the SBMG **App Info** screen.
2. Tap the three-dot menu **(⋮)** in the top right corner.
3. Select **Allow restricted settings** and follow the on-screen instructions.
4. Return to **Permissions**, tap **SMS**, and choose **Allow**.

> If you still don’t see messages in your reports after granting SMS permission, please contact support.
> [Help Desk](https://apishift.atlassian.net/servicedesk/customer/portal/1/group/4/create/3)


# Update SBMG SMS Gateway
Source: https://sbmg.app/user-guide/updating-sbmg-gateway

Learn how to update to a new version of our android sms gateway service

## Prior to v1.0.8 (Regular install method)

Go to the settings page at SBMG portal (<a href="https://portal.sbmg.app/settings#download">portal.sbmg.app</a>) and select
the 'Gateway Download'. This will present a QR code that you can scan on your android device to get the app download.
Proceed through the download, open the downloaded file and install.

## v1.0.8 onwards

In version 1.0.8 we added the ability to check for updates directly in the android app. Open the SBMG SMS gateway on android, click settings
under the menu button in the top right and then tap *'check for updates'*. This will confirm if a new version is available and being downloading
the update.

Once the download completes you will be prompted to install the update by the system. Confirm the install and reopen SBMG once
complete to confirm the gateway is connected and you don't need to log in after the update.


# Calling forwarding
Source: https://sbmg.app/user-guide/using-call-forwarding

Learn how to setup call forwarding with your SBMG equipped phone

# Configuration

<Steps>
  <Step title="Open Settings">
    In the SBMG portal click the *Settings* menu item and continue in the [**configuration** tab](https://portal.sbmg.app/settings#configuration) that opens as the first tab.
  </Step>

  <Step title="Enable Call Forwarding">
    In the Options section, check the box next to 'Enable call forwarding'
  </Step>

  <Step title="Set Call Destination">
    In the text area enter your call forwarding destination e.g. 021556677 or +6427334422.
    This number is the phone that calls will be redirected to when someone tries to call your gateway.
  </Step>

  <Step title="Save">
    Lock in the configuration by confirming with save. This will trigger the call forwarding configuration on your gateway shortly after.
  </Step>
</Steps>