In cases where a text-centric experience is preferred, templates may be configured to support. For example:

To Introduce the Guest to Texting:

  1. Loop can send a welcome text directly to their phone (preferred, via invite, and allowing for a simple direct reply), or
  2. Guest can be given the location’s unique texting number
     (Done for example via DA email, or another means like physical signage. The limitations is: unless Loop has a record of this guest that includes the guest’s mobile number, the text will arrive ‘anonymously’ and will have no profile attached), or
  3. From an existing Loop web session, the guest updates their profile by adding a mobile number (this would have the effect of ‘turning on’ texting. Instructions in the ‘welcome text’ on Loop Web could encourage this).

As a Guest, to Engage via Text:

  1. The guest simply texts to that number.
     (All text messages are posted to the Loop timeline)

As Staff, to Engage with a Texting Guest:

  1. Simply reply to the conversation as usual.
     Guest will receive text messages that can include the reply, plus any additional links/info/etc. (all defined by template). We typically include a link back to Loop Web view in these templates, but this can be adjusted.

Configuration Examples:

As an example, with the following template configuration for a Guest-bound SMS message following a new Comment in a conversation,

The guest would receive a simple reply as follows:

Your order has been placed – thanks!
 
http://goo.gl/id=123abc

As a second example, with the following template configuration for a Guest-bound SMS message following a new Comment in a conversation,

The guest would receive:

“Your order has been placed – thanks!”
 from Marty, Front Desk at New Orleans Grand.
 
 View online:
http://goo.gl/id=123abc

Did this answer your question?