Steps

1. Select the Hardware module from the BackOffice Home screen.

2. Click Terminal Setup (a).

3. Select the desired terminal (b).

4. Select the Advanced Option tab (c).

5. Click Edit (d).

6. Select the Customer Order Notification via SMS checkbox (e).

7. Click Save (f).

8. Click Exit (g).

   Open

   

9. Perform a Data Synch.

Notes on Customer Order Notification via SMS

• This setting will be turned off by default.

• If this setting has been turned off, no notifications will appear on the Kiosk after a payment has been made.

• When enabled, the pop-up will after user makes a payment and cashier getting prompted to print/send receipt. 

• SMS is currently available for the following POS Use Modes:

  • Cashier

  • Tabs

SMS Notification Pre-requisites

1. Terminals needs to be registered/licensed to receive the SMS because it is subscription service.

2. QSR does incur a cost for SMS usage so this would need to be invoiced to Volante based on the usage. There is no setup fee or fixed cost, it’s a flat rate per message segment.  So, you would receive an invoice based on the actual usage each month (if you don’t use or send any SMS, nothing is billed). Below is the actual rate per message segment as seen in agreement/price list. 

   Open

   

3. User login credentials are required to setup SMS notifications on QSR cloud portal.

Create New User in QSR Cloud Portal

Below are the steps for creating a new user for the QSR cloud portal (for Carmen-Volante):

1. Navigate to https://portal.qsr.cloud and login using the provided credentials.

   1. If you are unable to remember the password, it can be reset using the Forgot your Password? option.

2. Once logged in, ensure that you are in the Company section of the portal – this will be indicated by the “Company” text under the QSR logo.

3. Select Company > Users. Select the “+” button to add a new user.

4. When the Add User window appears, enter all the information relevant for setting up the user. The bare minimum information should include all fields on the left.

5. On the right, ensure you have enabled Portal Access and Site Access.

6. Ensure in the Sites tab that you have provided access to all the sites that the user should have access too – this is generally for system admin users for all sites.

7. Select Done to save the changes. The user should get an email shortly after to verify their email and from there they should be able to login and change their password.

   1. Be sure to check the spam folder for any potential emails.

Order Ready Events SMS on QSR Portal

The following instructions advise how to setup Order Ready SMS via our QSR Portal.

1. Log into the Company Portal https://portal.qsr.cloud. Select the Concepts tab at the top of the page.  

2. On the Destinations tab from the left sidebar, click the “+” button to add a new Destination.

3. Enter a Name for the destination.

4. Enter the ID of the destination for which you will want Order Ready events to be triggered. This should match a destination configured in your Kitchen dataset for Destination Type.

   1. Data Types should be either Carryout, Delivery or Curbside.

5. Click Done to save your changes.

6. Use the 9-dot menu in the upper left logo, and from the new dropdown options, select the Kitchen page.

7. Open the Concepts tab. Select the Order Ready tab from the left pane.

8. Click the “+” button to add a new Order Ready event.

9. Enter a Name for the Order Ready event.

10. Click the pencil icon next to the Send Event for these Destinations.

11. Select the Destination(s) for which you want the Order Ready event to be triggered.

12. Click Done.

13. Select the Event Trigger.
    NOTE:  An Event Trigger must be set to an event other than “None” for all off-premise features to work correctly.

14. Available options are Order Prepared, Order Assembled, and Order Bumped From Kitchen View. If the Order Ready event trigger is set to Order Prepared and the order views are configured to mark prepared, then prepared status can be a trigger. 

    1. If Order Views are set to mark “Order Assembled”, then a prepared event will not trigger an Order Ready SMS.

    2. If “Order Bumped from Kitchen View” is selected, you must specify the View ID for Order Bump Event Trigger, as configured in your Kitchen dataset.

15. Click Done to save, and allow settings to sync down to the Kitchen Server.

Order Ready SMS Notifications

1. Select the SMS Notifications tab from the left side menu.

2. Under General Settings, use the pencil icon to select the destinations to send the Order Ready SMS notification.

   1. Note: The destinations will match the destinations you created in the Order Ready menu. You may opt to not send SMS to a particular destination type. 
      
      

3.  Customize the Order Ready Notification using the Dynamic Tags available on the page. Copy and paste the brackets into the Order Ready Notification box and create your message. Click save after configuring the custom message.

   1. Note: SMS messages must be 140 characters or less to maintain the lowest SMS pricing option.

QSR SMS Notification workflow without Customer

1. Go to BackOffice > Hardware > Terminal Setup > Advanced Options > Select Terminal from left pane > Enable “Customer Order Notifications vis SMS” > Perform Data Synch

2. Launch POS or Kiosk (SMS through POS “Tables” mode is not supported)

3. Order QSR item

4. Perform the Payment

5. SMS notification will pop up as below:

6. Click “Yes”

7. Enter the phone number to receive the SMS

8. Click “Done”

9. Go to Multi-display client and it will display the order as below:

10. Bump the order from QSR

11. SMS will be received as below:

QSR SMS Notification workflow without Customer

1. Perform Steps 1 to 3 from above scenario

2. Login the Customer to the transaction which has phone number in BackOffice CustomerDB profile

3. Perform the Payment

4. SMS notification will pop up as below:

5. Click “Yes”

6. Confirm the phone number to receive the SMS

7. Go to Multi-display client and it will display the order as below:
   
   

8. Bump the order from QSR

9. SMS will be received as below:

Current Limitations on SMS Notifications

• The first order sent to an offline instance will show a noticeable delay before the order is sent to the other instance. This is because the requests are sent in series, and the order that's sent to the offline instance needs to timeout before proceeding. Our application keeps track of what is offline, so the delay should not happen on subsequent orders.

• If the Primary instance comes back online, the POS must be restarted for orders to be sent back to the Primary instance.

  • Note that QSR does not send orders back to the Primary instance until End of Day processing runs, or the Secondary instance goes offline.

• The Legacy implementation requires pinging the Kitchen Server before sending an order. If the Primary instance is offline, pinging will block redundancy from occuring.

  • The REST implementation will not ping the Kitchen Server at all.