QR codes

Scan me to register!

Result of QR code scan

About QR codes

QR codes are the perfect bridge between printed and online media.

Using the Rogerthat platform, your service stands out by offering a threefold superior QR code experience.

• First, Rogerthat QR codes do not point to a mobile web page. Instead, scanning the QR code starts an automated interactive message flow between your service and the user who scanned the QR code.
• Second, there is no need for the user to register or log in. Your service knows who scanned the QR code. The user will automatically be connected to the service, if that was not already the case.
• Finally, the Rogerthat toolset makes it easy to create designer QR codes, embedding your brand in the QR code graphics.

Poking a service

There are three ways for users to take the initiative to interact with a TPS (Third Party Service):

• Scanning a QR code
• Explicitly poking a service
• Clicking an action link URL e.g. received in an email or SMS text message or in the browser

1. User scans a service action QR code

Users can do this by pressing the scan button on the scan tab in the Rogerthat app, or using a third party QR code scanner app that is installed on their mobile device.

If scanned using a third party QR code scanner app, the user might be asked whether Rogerthat app is installed on his mobile device. If yes, the app will open. If not, Android Market or Apple Appstore will open on the appropriate app page.

Once in the Rogerthat app the user will see a page containing the logo and email address of the TPS, the Action description on a button, and a branded description of the TPS.

Once the user presses the Action button, the TPS will receive a poke call containing the tag that was baked into the Service Action QR code.

Note: if the user is not yet connected to the TPS, he will be automatically connected to the TPS before the Service Action is sent to the TPS. For more information refer to the API sequence diagrams.

2. User pokes Third Party Service

Users can explicitly poke a TPS. This is possible from the Service Detail page on the mobile app, or from the Service Detail in the web view. The user basically states to the TPS “I need your attention”.

The TPS will receive poke call (having an empty poke tag).

Typically, a TPS will react to the poke action by sending a message to the user, containing a text “How can I help you?” and a number of buttons.

Service Detail
in mobile view

This is comparable to the top level menu of an IVR system. One typical button could be a “Call Service” button which automatically opens the phone app, or “Locate Service” which opens the Maps application pointed to the correct location.

Service Detail in web view

3. User clicks an an action link

Services can directly distribute the action link URL that is embedded in the QR code. Some possibilities:

• Send an SMS text message containing that link, e.g. to bootstrap a non-Rogerthat user.
• Embed the action link in an email or a web site.

The behaviour is as follows:

• When the link is clicked from a smartphone (e.g. email, browser, SMS text message), the system behaves as if the corresponding QR code were scanned.
• When the link is clicked in a browser of a desktop or tablet, the user is redirected to the in-browser Rogerthat web application. The user might be prompted to log in first.

QR codes are created from QR code templates. QR codes can be created

• Manually in the service panels. A QR code template, color scheme, description and a tag have to be configured.
• Programmatically using the Rogerthat service API.

Here are some example QR code templates. Note that the gray areas are in fact transparant.

More information on how to create and manage QR codes can be found in the QR code guide.