U.S. patent application number 15/562744 was filed with the patent office on 2018-03-15 for automatic after call social messaging connection platform.
The applicant listed for this patent is OnePIN, Inc.. Invention is credited to Feyzi CELIK, Marcin NOWAK.
Application Number | 20180075488 15/562744 |
Document ID | / |
Family ID | 57217790 |
Filed Date | 2018-03-15 |
United States Patent
Application |
20180075488 |
Kind Code |
A1 |
CELIK; Feyzi ; et
al. |
March 15, 2018 |
Automatic After Call Social Messaging Connection Platform
Abstract
This disclosure provides methods, systems, services, and
platforms for automatically prompting a user of a mobile device to
follow an entity on a social media network after a triggering
event. This disclosure enables Mobile Network Operators to generate
more followers on social media, and, thereby, connect better with
potential customers or fans. When a business, group, or other
entity has an active social media campaign, a message comprising
instructions to launch a browser on a mobile device and navigate to
the entity's social media page is sent automatically after a
triggering event occurs.
Inventors: |
CELIK; Feyzi; (Hopkinton,
MA) ; NOWAK; Marcin; (Westborough, MA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
OnePIN, Inc. |
Westborough |
MA |
US |
|
|
Family ID: |
57217790 |
Appl. No.: |
15/562744 |
Filed: |
May 4, 2016 |
PCT Filed: |
May 4, 2016 |
PCT NO: |
PCT/US2016/030699 |
371 Date: |
September 28, 2017 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
62156723 |
May 4, 2015 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
H04M 1/72525 20130101;
H04M 15/848 20130101; H04M 1/72561 20130101; H04M 2215/8158
20130101; H04M 15/705 20130101; H04M 3/42059 20130101; G06F 9/542
20130101; G06Q 30/01 20130101; H04M 3/42195 20130101; H04M 15/852
20130101; G06Q 30/0245 20130101; G06Q 30/0267 20130101; H04M 1/2757
20200101; G06Q 30/0203 20130101; G06Q 30/016 20130101; H04W 8/18
20130101; G06Q 30/0251 20130101; G06F 16/972 20190101; H04W 4/21
20180201; H04M 3/42102 20130101; H04W 4/14 20130101; G06Q 30/0201
20130101; H04M 15/735 20130101; H04M 2203/651 20130101; H04M 15/62
20130101; H04M 3/42357 20130101; H04W 4/16 20130101; H04W 4/60
20180201; G06F 16/955 20190101; H04M 3/42365 20130101; H04M 7/0042
20130101; H04M 15/58 20130101; H04M 15/7556 20130101; H04M 15/844
20130101; H04W 8/26 20130101; H04M 15/856 20130101; H04M 1/72563
20130101; H04M 3/42153 20130101; H04W 4/00 20130101; G06Q 50/01
20130101; H04M 2203/655 20130101; G06Q 30/0207 20130101; H04M 15/84
20130101; H04M 3/4931 20130101; H04M 15/80 20130101 |
International
Class: |
G06Q 30/02 20060101
G06Q030/02; G06Q 30/00 20060101 G06Q030/00; G06Q 50/00 20060101
G06Q050/00; H04W 4/14 20060101 H04W004/14; H04W 8/18 20060101
H04W008/18 |
Claims
1. A computer-implemented method for automatically prompting a user
to follow an entity on a social media network on a mobile device
after a triggering event, the method comprising: receiving, at a
server, an indication that a triggering event has occurred;
receiving, at the server, an indication that the triggering event
matches a triggering event stored in a database operably connected
to the server; receiving, at the server, a communication comprising
the Mobile Station International Subscriber Directory Number of the
mobile device; preparing a first social media message comprising
one or more first actionable response options; and sending the
first social media message to the mobile device.
2. The method of claim 1, further comprising: receiving, at the
server, a communication comprising the first actionable response
option selected on the mobile device; preparing a second social
media message comprising executable instructions to launch a
browser on the mobile device and to navigate the browser to a
social media website address; and sending the second social media
message to the mobile device.
3. The method of claim 2, further comprising logging the first
actionable response option selected by the user.
4. The method of claim 3, further comprising determining whether
social media messages sent to the mobile device have exceeded a
preset amount.
5. The method of claim 2, wherein the communication further
comprises the device type of the mobile device and information
regarding whether the mobile device supports browser launch from
executable instructions contained within a received message.
6. The method of claim 5, further comprising: preparing an SMS
message comprising a browser launch link; and sending the SMS
message to the mobile device, wherein the SMS message is prepared
and sent when the information indicates that the mobile device does
not support browser launch from instructions contained within a
received message.
7. The method of claim 1, wherein the triggering event is selected
from the group consisting of a phone call placed from the mobile
device to a first phone number, a phone call received at the mobile
device from a second phone number, navigation to a specific web
address on the mobile device, and navigation away from a specific
web address on the mobile device.
8. The method of claim 7, wherein the triggering event is a phone
call placed from the mobile device to a first phone number.
9. The method of claim 1, wherein the entity is selected from the
group consisting of a business, a university, and a political
campaign.
10. The method of claim 1, wherein the social media network is
selected from the group consisting of Facebook, Instagram, Twitter,
Google+, LinkedIn, Renren, Snapchat, Tumblr, Pinterest, and
YouTube.
11. The method of claim 1, wherein the first social media message
is selected from the group consisting of binary SMS, flash SMS,
MMS, standard SMS, USSD notification, and email.
12. A computer-implemented method for automatically prompting a
user to follow an entity on a social media network after a
triggering event on a mobile device, the method comprising:
receiving, at the processor in the mobile phone, an indication that
a triggering event has occurred; receiving at the mobile device a
first social media message comprising one or more first actionable
response options; and displaying on the screen of the mobile device
the first social media message.
13. The method of claim 12, further comprising playing an alert
tone on the mobile device when the first social media message is
displayed.
14. The method of claim 12, further comprising launching an
application installed on the mobile device, wherein the application
causes the first social media message to be displayed.
15. The method of claim 14, wherein the application causes the
alert tone to be played on the mobile device.
16. The method of claim 14, wherein the application is installed on
the SIM card of the mobile device.
17. The method of claim 14, wherein the application is installed on
the operating system of the mobile device.
18. The method of claim 14, further comprising receiving, in the
application, the first actionable response option selected by the
user.
19. The method of claim 18, further comprising: receiving, in the
application, a communication comprising executable instructions to
launch a browser of the mobile device and navigate the browser to a
website; causing the browser of the mobile device to be launched;
and causing the browser to navigate to the website.
20. The method of claim 18, further comprising: receiving, in the
application, a second social media message comprising a clickable
link; and displaying the second social media message on the screen
of the mobile device.
21.-25. (canceled)
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims priority to U.S. Provisional Patent
Application No. 62/156,723, filed May 4, 2015. The entire contents
of that application are incorporated herein by reference.
FIELD
[0002] This application relates to mobile devices and mobile
networks. Specifically, this application relates to data pertaining
to mobile devices and mobile networks.
BACKGROUND
[0003] Companies and brands are always looking for new ways to
connect with consumers. With the advent of social media, businesses
are now reaching out to new and existing customers through photo
feeds like Instagram, interest boards like Pinterest, quick news
and promotions vehicles like Twitter, and informal events and
communications sites such as Facebook. While brands may find it
easy to set up social media profiles, they typically find it
difficult to connect directly with consumers. Consumers may already
be using social media platforms like Facebook and Twitter, but may
not think to connect to a business unless they are directly invited
to do so at a relevant and convenient time. Companies need a quick,
simple, and personalized way to reach their consumer base to
connect on social media platforms.
SUMMARY
[0004] One aspect of this disclosure provides a
computer-implemented method for automatically prompting a user to
follow an entity on a social media network on a mobile device after
a triggering event. The method comprises: receiving, at a server,
an indication that a triggering event has occurred; receiving, at
the server, an indication that the triggering event matches a
triggering event stored in a database operably connected to the
server; receiving, at the server, a communication comprising the
Mobile Station International Subscriber Directory Number of the
mobile device; preparing a first social media message comprising
one or more first actionable response options; and sending the
first social media message to the mobile device.
[0005] In some embodiments, the triggering event is selected from
the group consisting of a phone call placed from the mobile device
to a first phone number, a phone call received at the mobile device
from a second phone number, navigation to a specific web address on
the mobile device, and navigation away from a specific web address
on the mobile device. In certain embodiments, the triggering event
is a phone call placed from the mobile device to a first phone
number.
[0006] In some embodiments, the entity is selected from the group
consisting of a business, a university, and a political
campaign.
[0007] In some embodiments, the social media network is selected
from the group consisting of Facebook, Instragram, Twitter,
Google+, LinkedIn, Renren, Snapchat, Tumblr, Pinterest, and
YouTube. In some embodiments, the social media network is any
social media network that allows followers.
[0008] In some embodiments of the method, the first social media
message is selected from the group consisting of binary SMS, flash
SMS, MMS, standard SMS, USSD notification, and email.
[0009] In some embodiments, the method further comprises:
receiving, at the server, a communication comprising the first
actionable response option selected on the mobile device; preparing
a second social media message comprising executable instructions to
launch a browser on the mobile device and to navigate the browser
to a social media website address; and sending the second social
media message to the mobile device. In some embodiments, the method
also comprises logging the first actionable response option
selected by the user. In further embodiments, the method comprises
determining whether social media messages sent to the mobile device
have exceeded a preset amount. In still other embodiments of the
method, the communication further comprises the device type of the
mobile device and information regarding whether the mobile device
supports browser launch from executable instructions contained
within a received message.
[0010] In some embodiments, the further comprises: preparing an SMS
message comprising a browser launch link; and sending the SMS
message to the mobile device, wherein the SMS message is prepared
and sent when the information indicates that the mobile device does
not support browser launch from instructions contained within a
received message.
[0011] Another aspect of this disclosure provides a
computer-implemented method for automatically prompting a user to
follow an entity on a social media network after a triggering event
on a mobile device. The method comprises: receiving, at the
processor in the mobile phone, an indication that a triggering
event has occurred; receiving at the mobile device a first social
media message comprising one or more first actionable response
options; and displaying on the screen of the mobile device the
first social media message.
[0012] In some embodiments of the method the triggering event is
selected from the group consisting of a phone call placed from the
mobile device to a first phone number, a phone call received at the
mobile device from a second phone number, navigation to a specific
web address on the mobile device, and navigation away from a
specific web address on the mobile device. In certain embodiments,
the triggering event is a phone call placed from the mobile device
to a first phone number.
[0013] In some embodiments of the method, the first social media
message is selected from the group consisting of binary SMS, flash
SMS, MMS, standard SMS, USSD notification, and email.
[0014] In some embodiments of the method, the entity is selected
from the group consisting of a business, a university, and a
political campaign.
[0015] In some embodiments of the method, the social media network
is selected from the group consisting of Facebook, Instragram,
Twitter, Google+, LinkedIn, Renren, Snapchat, Tumblr, Pinterest,
and YouTube.
[0016] In some embodiments, the method further comprises playing an
alert tone on the mobile device when the first social media message
is displayed.
[0017] In some embodiments, the method further comprises launching
an application installed on the mobile device, wherein the
application causes the first social media message to be displayed.
In certain embodiments, the application causes the alert tone to be
played on the mobile device. In some embodiments, the application
is installed on the SIM card of the mobile device. In other
embodiments, the application is installed on the operating system
of the mobile device. In still further embodiments, the method
further comprises receiving, in the application, the first
actionable response option selected by the user.
[0018] In other embodiments, the method further comprises:
receiving, in the application, a communication comprising
executable instructions to launch a browser of the mobile device
and navigate the browser to a website; causing the browser of the
mobile device to be launched; and causing the browser to navigate
to the website. In some embodiments, the method further comprises:
receiving, in the application, a second social media message
comprising a clickable link; and displaying the second social media
message on the screen of the mobile device.
DESCRIPTION OF THE FIGURES
[0019] FIG. 1 is a flowchart illustrating the basic architecture of
the SocialLinX platform.
[0020] FIG. 2 is a flowchart illustrating the steps related to a
phone call event that will lead to the eventual triggering of the
SocialLinX service.
[0021] FIG. 3 is a flowchart illustrating the Mobile Operator
Network as it would interact with the SocialLinX server
platform.
[0022] FIG. 4 is a flowchart illustrating the exemplary process of
the logic the SocialLinX platform uses to determine if a campaign
message should be sent to a specific targeted mobile
subscriber.
[0023] FIG. 5 is a flowchart illustrating the exemplary process of
how the SocialLinX application is expressed and interacts with the
user device, and thus the user experience.
[0024] FIG. 6 is a flowchart illustrating the exemplary process of
how the SocialLinX platform logs the mobile device user's response
and determines if any follow-up questions should be sent as a
result of the user's response.
[0025] FIG. 7 is a flowchart illustrating the exemplary process of
how the SocialLinX platform updates the database with subscriber
preference results, tracking the participation such that the MNO
may modify the frequency of campaign depending on subscriber
responsiveness.
[0026] FIG. 8 is a flowchart illustrating the exemplary process of
how a SocialLinX campaign is designed.
DETAILED DESCRIPTION
[0027] This application provides aspects and embodiments of
OnePIN's SocialLinX.TM. platform. The term "SocialLinX" is used
throughout this application to refer to multiple aspects and
embodiments of the methods, applications, services, systems, and
platforms disclosed herein. In some embodiments, SocialLinX is a
cloud based platform that interacts with a client application
residing on the phone--either as a downloadable application from an
external site, within the device OS or within a SIM card. However,
the name "SocialLinX" is not limited to any specific embodiment and
can refer to multiple embodiments or individual embodiments.
Furthermore, other names are also used to refer to embodiments
described herein.
[0028] As used herein, the terms "a" and "an" mean one or more than
one.
[0029] With SocialLinX, entities have the opportunity to increase
the effectiveness of their social networking communication channels
with customers. Brands are able to target mobile subscribers who
are using social media channels, and can subsequently invite the
mobile subscriber to connect on any social media platform.
Notifications are all relevant and timely for subscribers as they
only receive invitations for brands that interest them. As used
herein, the term "entities" refers to businesses, companies,
brands, corporations, partnerships, political campaigns, education
institutions, etc. These terms are used interchangeably to refer to
entities that can use and benefit from SocialLinX.
[0030] SocialLinX is preferably used with a mobile phone, but can
also be used with other devices that can be configured to make
phone calls or to navigate the internet. For example, tablets and
other computers that include Skype or Google Voice can be utilized
with the services.
SocialLinX Overview
[0031] SocialLinX focuses on enhancing the relationship a brand or
enterprise or any entity has with a consumer or follower. In one
embodiment, a mobile subscriber is able to indicate which social
media platforms he currently utilizes, such as Facebook or Twitter.
In one embodiment, this is done via a remote application on the
user's device which allows the user to indicate which social media
channels he uses, as well as to provide credentials securely such
that the SocialLinX application is linked to his social media
accounts. In some embodiments, the user's social media selections
could also be entered via a web site front end to the SocialLinX
platform. The SocialLinX cloud server stores this information.
[0032] In some embodiments, when a subscriber makes a phone call to
a brand, such as calling to book a flight on Lufthansa, the event
trigger information is passed from the (MNO) Mobile Network
Operator to the SocialLinX cloud. The cloud checks to determine if
the subscriber is active on any social networks and then sends a
message to the subscriber inviting him to connect to the brand just
called (i.e., Lufthansa) on social networking sites. Brands are
able to enhance their relationship with interested consumers, who
in turn are able to follow brands using their own preferred social
networking sites. Promotions, new product and service launches,
coupons, discounts, and new information can all be shared with the
consumer on the social networking site--making it a valuable
resource for the mobile subscriber and giving them a good reason to
connect to the brand.
[0033] Furthermore, subscribers are able to self-select brands that
are relevant to them, because they receive invitations only for
brands they have called.
[0034] Additionally, brands can target groups of subscribers using
specific social networks (tracked by the cloud platform), via a
campaign-based approach. With this approach, in some embodiments, a
set number of subscribers who are known social networking users are
targeted at a specific time. Subscribers do not need to opt-in to
the service. In some embodiments, subscribers receive relevant
notifications automatically as determined by the MNO. As used
herein, the terms "user" and "subscriber" are used
interchangeably.
[0035] In some embodiments, subscribers can opt-out from receiving
notifications anytime. When an invitation is sent to the
subscriber, the subscriber has the option to opt out, e.g., by
selecting "stop all notifications." In addition, the subscriber can
send a "STOP" SMS notification to a designated shortcode which will
automatically turn off the service. In some embodiments, SocialLinX
also has the intelligence to ask the user if he would like to
opt-out of the service if he consistently chooses not to accept any
of the invitations offered by through the service (e.g., by
tracking the subscribers responses and, once a target number has
been met, asking the subscriber if he would like to opt out).
[0036] In one embodiment, the SocialLinX platform will offer the
automatic opt-out opportunity if the user chooses not to accept
consecutive invitation offers. In one embodiment, this automatic
opt-out notification could be sent to the user after a specific
number of consecutive refusals. In other embodiments, the opt-out
invitation can be sent if the subscriber declines a percentage of
invitation offers. In some embodiments, the consecutive declines or
percentage of declines are tracked over a specific time period
before triggering the opt-out invitation. These values are
configurable and can be changed at any time, as it is managed at
the platform level. Subscriber selections are tracked within the
cloud in order to manage the automatic opt-out process.
Market Trends and Subscriber Targets
[0037] Trends: Brands (e.g., corporations, companies, businesses,
political groups--any branded entity or group; these terms are used
interchangeably throughout this disclosure to refer to all of the
entity types collectively) must have a mobile advertising strategy
in order to continue relationships with their consumer base.
Mobility is key often key to an advertising strategy. Companies are
looking for creative ways to engage with their consumers via mobile
devices and services, and to grow their base of followers on social
media sites.
[0038] Service Availability: The service is relevant for any
subscriber type (prepaid, postpaid, corporate subscribers, mass
market, etc.). Application marketing can be targeted for specific
segments.
[0039] Revenue: In one embodiment, brands are charged per campaign
to promote their social media sites to targeted subscribers.
Service Benefits
[0040] Subscribers are able to connect to relevant brands at their
discretion, and participate in promotions, special offers, and
feedback surveys.
[0041] MNOs can offer a valuable advertising service to brands
where a base of known social networking active users can be
targeted.
Operation
[0042] The SocialLinX platform includes a web interface that
enables businesses, enterprises, marketers, etc. to log in and
define a campaign. Within the campaign event, businesses or mobile
operators enter all relevant information including but not limited
to the target phone number(s) that will trigger different services
when called, and the timeframe during which a campaign will be
relevant.
[0043] The user interface specifics (i.e., the text mobile
consumers will see) and the social media linkages can be entered
via the web interface.
[0044] In one embodiment, the SocialLinX platform is connected to a
mobile network operator's call switch via an Application
Programming Interface (API). In other embodiments, the cloud
platform can also be connected to the mobile operator's billing
platform or HLR (Home Location Registry), or internet routing
equipment via an API, depending on the operator's network
structure. When a designated campaign number is dialed (i.e., a
business's phone number), the API informs the cloud platform. In
some embodiments, the business phone number and the mobile
subscriber's MSISDN (Mobile Station International Subscriber
Directory Number) are both passed to the platform via the API. In
some embodiments, the date and time of the event are also passed to
the platform.
[0045] When the platform receives communications via the API, the
business phone number is checked to determine which campaign should
be executed (in some embodiments, there will be multiple campaigns
for different businesses running on the platform at the same time).
The platform also checks the caller's phone number to determine if
the calling party has opted out from any services. If the calling
party has opted out of the service, then processing ends and no
further communications are sent to the mobile subscriber.
[0046] If the mobile user is not on the opt-out blacklist, then an
appropriate campaign message is prepared based on the configuration
criteria and sent to the mobile subscriber. Here, this
communication is described as a SMS which triggers a remote
application on the mobile user's mobile device. This could be a
binary SMS, standard text SMS, a specialized (flash, class 1) SMS,
or a class 2 SMS which the handset passes to a SIM card within the
device. Alternatively, communications can occur via MMS, email,
USSD, or via other web-based communications channels between the
mobile phone and the platform.
[0047] When the message is received on the calling party's mobile
device, the client application displays the prompt to the user. The
user is able to select a response, which is then sent back to the
cloud via the application. Communication back to the cloud can be
via a data channel, SMS, MMS, etc.
[0048] The above embodiments can also be implemented in a manner
where a client application (either on the phone or on the SIM card)
is not required. In this instance, a USSD channel is opened and the
communications between the mobile subscriber and the platform occur
via USSD communications.
[0049] In some embodiments, the cloud server can collect the device
type of the respective mobile devices and can send a message to the
respective client applications to "turn off" the client application
in mobile devices that have known issues that interfere with the
service.
[0050] In addition to after-call techniques, the service can be
conducted in an intelligent campaign manner. In some embodiments,
the server is able to track calls that individual subscribers make
to businesses. If a business would like to run a campaign at a
later date, subscribers who have called that business in the past
can be targeted. This makes the prompts to the mobile subscribers
relevant, as a previous relationship with the company had already
been established by the mobile consumer. Consumers targeted in this
manner receive a prompt, similar to that outlined in the before
mentioned embodiments. The intelligent campaigns can be arranged to
run a predefined dates and times, and for selected groups of
subscribers in a regional area based on the subscriber's area
code.
[0051] Initially, the SocialLinX service triggers and displays
prompts to the consumer after a phone call or other user generated
event, such as navigating to a company website. First, a phone call
is placed to a business currently running an SocialLinX campaign.
After the phone call ends, an interactive prompt is displayed on
the screen of the mobile device. In some embodiments, a tone is
played by the mobile device in conjunction with the displaying of
the interactive prompt.
[0052] The text displayed to the calling party is fully
configurable by the company or business that was called. In this
example, a mobile user calls an airline to make a reservation.
After the phone call, the user sees an automatic, interactive
prompt on her handset directly on the screen.
[0053] In the embodiment where the mobile user interacts with the
campaign message and chooses to accept the social media invitation,
a message is sent back to the SocialLinX platform. In some
embodiments, a command message is sent back to the remote
application on the user's phone, which automatically launches the
social media site for the specific brand. In the embodiment where
the user has provided correct credentials, the SocialLinX platform
can link the user directly to the brand's social media account. For
example, a user would begin to see news and events in her Twitter
feed from a specific brand, because the platform was able to make
the connection on her behalf.
[0054] FIG. 1 is a flowchart illustrating an exemplary embodiment
of the basic architecture of the SocialLinX platform. In one
embodiment, as pictured in FIG. 1, SocialLinX utilizes the
following connectivity structure: [0055] Mobile Subscriber A calls
a number defined in the SocialLinX target base ("1").
Alternatively, the user may navigate to a website defined as a
campaign target. The Operator Switch, HLR (Home Location Registry),
or web router bank are in communication with the SocialLinX
platform ("2"). This allows for the Mobile Operator network to
notify the SocialLinX platform when a specific target phone number
is dialed or when a specific website is visited. [0056] After a
trigger event occurs and subsequently, the information necessary to
trigger a campaign is passed to the SocialLinX platform (in some
embodiments, via an API). Then, the platform processes the
information and prepares a campaign message to be sent to a mobile
subscriber. [0057] In one embodiment, the SocialLinX platform is
connected to a Mobile Network Operator SMSC (Short Message Service
Center) via an SMPP (Short Message Peer-to-Peer) connection ("3").
Other connection types in other embodiments are also possible. In
some embodiments, the platform may also be connected to an MNO's
MMSC (MultiMedia Message Service Center). The Operator SMSC
forwards the SocialLinX campaign message to Subscriber A's device
("4"). [0058] The social media invitation appears on Subscriber A's
device as discussed above, at which point the subscriber selects
his or her preferred option. In one embodiment, if Subscriber A
chooses to accept the invitation, the SocialLinX application on the
device can launch the social media site for Subscriber A
automatically. [0059] In some embodiments, the SocialLinX remote
application within Subscriber A's mobile device forwards the
response to a designated short code at the Operator SMSC ("5") for
logging and further processing purposes. [0060] The Operator SMSC
receives and forwards the response to the SocialLinX platform
("6"). In some embodiments, the response is in the form of a binary
SMS message. [0061] In some embodiments, the platform parses the
message and determines an appropriate response to Subscriber A
based on Subscriber A's device type and interest in the campaign
promotion. [0062] In the embodiment where Subscriber A chose to
participate, the platform can send a message back to the
subscriber. This could be a command message that the remote
application processes and further launches other applications on
the device (such as a Facebook application) or it may be an SMS
(Short Message Service) thanking the subscriber for participating.
If the user has a feature phone that does not support automatically
launching a web browser session from the SIM card or from the
remote application, the message sent back to Subscriber A may be an
SMS with links to social media sites. Subscriber A is then able to
click on the link, launch a social networking session, and connect
to the brand or company being promoted. These messages would flow
through the MNOs SMSC and MMSC respectively ("7"). [0063] The
Operator SMSC forwards the contact information to the device user
"(8)".
[0064] FIG. 2 is a flowchart illustrating the steps related to a
trigger event that will lead to the eventual launching of the
SocialLinX service. In stage 305, a trigger event occurs. In one
embodiment, this could be a call a mobile user places to a
business. In another embodiment, this trigger event could be
navigation to a website by a mobile user. In stage 310, the event
begins, e.g., the call connects. A connected call can have a
multitude of scenarios including speaking with an actual
individual, interacting with an automated voice response system,
connecting to a recorded message or voice mail system. In all
cases, the call will end as signified by stage 315 ("Event ends").
At this point, the call is disconnected and communications between
the SocialLinX platform (server) and the Mobile Operator's network
continue, as outlined in FIG. 3.
[0065] FIG. 3 is a flowchart illustrating the Mobile Operator
Network as it would interact with the SocialLinX server platform.
In stage 405, an event trigger ends. In one embodiment, this could
be a Call Disconnect. The Call Disconnect is a formal event
recognized by the Mobile Operator network. This can be a caller
initiated Call Disconnect, or a Network Originated Call Disconnect
Event, meaning the called party terminates the call or the network
is not able to maintain the call and the call drops.
[0066] In some embodiments, when the call ends, the Mobile Operator
Network will automatically check the phone number dialed to
determine if a SocialLinX campaign is associated with the number.
In some embodiments, this information is stored within a database
in the Mobile Operator's network. In other embodiments, the
information can be stored within the SocialLinX platform with
regular communications between the MNO network and the SocialLinX
platform via web services or APIs. (Application Programming
Interfaces). If the phone number dialed in this embodiment does not
have a SocialLinX campaign defined, then the flow ends as shown in
stage 415, and no further processing continues. If the phone number
called does have a campaign defined, then the MNO network informs
the SocialLinX platform of the calling event as outlined in stage
420. Information needed to execute the social media promotional
campaign on the SocialLinX platform is passed from the MNO network
to the platform. In some embodiments, this information includes the
calling party's mobile MSISDN (Mobile Station International
Subscriber Directory Number). In this embodiment, the subscriber's
mobile phone number is also known as the OA, or Originating
Address. In some embodiments, the MNO network may also provide time
and date to the SocialLinX platform. In some embodiments, the
called phone number, referred to as the DA or Destination Address,
is also sent to the SocialLinX platform. This number may be a
mobile phone number dialed, an international number, a landline or
fixed number, a 1-800 phone number, a 1-900 phone number, an
abbreviated number such as those used for emergency services such
as 911, a shortcode number often used in the mobile industry for
Short Message Service (SMS) communications or any other number or
address mechanism used for connecting two or more parties to
communicate. The SocialLinX platform then continues processing, as
outlined in FIG. 4.
[0067] FIG. 4 is a flowchart illustrating an exemplary embodiment
of the logic process the SocialLinX platform uses to determine if a
campaign message should be sent to a specific targeted mobile
subscriber. In some embodiments, the SocialLinX platform receives
the Origination Address, Destination Address, and other information
including date and time from the MNO network as shown in stage 505.
In stage 510, the SocialLinX platform performs a check for the
Destination Address to determine if the campaign is still relevant.
In some embodiments, the SocialLinX platform checks to see if the
date and time settings fall within preconfigured allowable ranges.
In some embodiments, the Originating Address is also checked by the
platform in stage 515. The platform checks to determine if the user
has opted out of receiving message notifications. In some
embodiments, a mobile subscriber may opt out of receiving any
SocialLinX notification for any brand, company, or business, etc.
called. In other embodiments, the platform and remote application
residing within the user's device are configured to allow the user
to manage which brands, businesses, companies, groups, etc. that he
would like to received SocialLinX notifications from after phone
calls or other trigger events. At stage 515, the platform is also
checking to ensure that the user has not exceeded pre-configurable
counters (e.g., whether the user has declined an invitation a
specified number of times or a specified percentage of times).
[0068] In one embodiment, the counters track the number of total
SocialLinX messages the user has received over a given timeframe
for all brands and for all trigger events. This tracking ensures
that the user does not receive an over abundance of social media
messages in a short time period, which could lead to him opting out
of all notifications in the future. If the has exceeded the
allowable limit, the processing ends as outlined in stage 516. In
some embodiments, this limit may be set by the user. In other
embodiments, the limit may be set by a network administrator within
the MNO or may be set by an advertising agency or company managing
the platform and overall user experience. In the embodiment where
the user has not exceeded the predefined counter limits, a
SocialLinX message is prepared by the platform and sent to the
mobile subscriber at stage 520. The message sent could be a
standard SMS, binary SMS, a class 2 SMS which will directly
communication with a SIM (Subscriber Identity Module) card within
the mobile subscriber's mobile device, an MMS message, a USSD
message, or a web message sent over an IP (Internet Protocol)
network. Processing on the user's device then ensues, as depicted
in FIG. 5.
[0069] FIG. 5 is a flowchart illustrating an exemplary embodiment
of how the SocialLinX application is expressed and interacts with
the user device. This embodiment exemplifies the user experience.
In stage 605, the SocialLinX remote application is triggered on the
mobile user's device. In some embodiments, the application may play
a configurable tone as shown in stage 610. In some embodiments,
this tone can be configured by the mobile user. In some
embodiments, this tone can be configured by the platform
administrator. In some embodiments, the tone can also be turned off
for specific subscribers, for specific campaigns, or for certain
device types. After the tone is played, the campaign text is
displayed to the mobile user as shown in stage 615. The text shown
to a mobile user is fully configurable and can contain letters,
numbers, special characters and punctuation, or may contain UCS2
Unicode encoded characters such as Greek, Cyrillic, or Mandarin
characters as an example. In most embodiments, the message
displayed in stage 615 will be actionable by the calling party,
meaning the user can make a decision as to whether or not he would
like to accept the invitation being promoted via the SocialLinX
service. In stage 620, the user makes the decision. If he decides
to ignore the prompt, or if he declines the invitation (e.g., by
selecting "Cancel" or "No"), he sees no further information and his
"No" response is automatically sent back to the SocialLinX server
in stage 630. In one embodiment, the remote application is able to
automatically launch a browser session. In this instance, if the
user decides to accept the invitation at stage 620 (e.g., by
selecting "OK" or "Yes"), the remote application will check if the
user's device is able to launch a browser session, as outlined at
stage 640. If the mobile phone does not support an automatic launch
of a browser, a response is sent back to the server at stage 645
indicating that the subscriber accepted the invitation, and that
the device does not support an automatic browser launch. In some
embodiments, the device type, as indicated by a mobile device TAC
(Type Allocation Code) is also sent back to the SocialLinX
platform. The platform continues processing, as outlined in FIG. 6.
In the embodiment where the mobile device can support the automatic
launch of a browser and the campaign is defined such that a website
should launch, the webpage is displayed on the user's device at
stage 650. At stage 655, a response is sent back to the server
indicating the user accepted the invitation and that the browser
launch was successful. In some embodiments, the user's device type
is also sent to the platform.
[0070] FIG. 6 is a flowchart illustrating an exemplary embodiment
of how the SocialLinX platform logs the mobile device user's
response and determines the appropriate next steps based on the
campaign definition and the user's device type. At stage 705, the
user's selected response to the social media campaign is received
at the SocialLinX platform. In stage 710, the server processes the
response and determines if the user was interested in the campaign.
If the user was not interested, in some embodiments, the platform
logs the response at stage 715. If the user was interested, in some
embodiments, the platform logs the response at stage 720, and then
checks at stage 725 whether or not the device supported an
automatic browser launch. If the device did not support the browser
launch, then at stage 730 a follow-up message is prepared. In one
embodiment, this could be a standard SMS message. In one
embodiment, the SMS can contain links to social media sites and
platforms on which the company is inviting the subscriber to
connect. An exemplary message could read: [0071] "Thanks for being
a great United Airlines customer. Like us on Facebook and follow us
on Twitter to receive the latest promotions!" [0072]
www.facebook.com/unitedairlines [0073]
www.twitter.com/unitedairlines
[0074] The message is sent to the user at stage 735 and further
logging within the platform, as exemplified by the flow in FIG. 7,
continues. If the device did support a browser launch, the
SocialLinX platform looks to determine if any optional messages or
follow-up should be sent to the user and sends these messages at
stage 740.
[0075] FIG. 8 is a flowchart illustrating the exemplary process of
how the SocialLinX platform updates the database with subscriber
preference results, tracking the participation such that the MNO
may modify the frequency of campaign depending on subscriber
responsiveness. At stage 805, the SocialLinX server database is
updated with the resulting user selection from a targeted mobile
subscriber. The platform looks to determine if the mobile user
responded in a positive or negative fashion at stage 810 and
updates configurable counters per MSISDN accordingly.
[0076] FIG. 8 is a flowchart illustrating an exemplary embodiment
of how a SocialLinX campaign is designed. At stage 905, the
campaign is defined within the server. In some embodiments, this
includes the days and times during which the campaign will be
relevant. Specific geographic regions can also be configured. A
maximum number of targeted mobile subscribers can also be set. At
stage 910, user or network generated events that should trigger a
campaign are defined. In one embodiment, this may include phone
numbers called after which the campaign should trigger. In some
embodiments, this may include websites that should trigger a
campaign when the mobile subscriber launches the web session, or
ends a web session for that specific address. Next, during stage
915, the actual campaign text that will be shown to a mobile
subscriber is defined. In one embodiment, a web site may launch
immediately if the user accepts the social media invitation. This
specific website is defined within the configuration at stage 920.
In stage 925, configurable counters and rules for the campaign are
set. In one embodiment, this could include the number of times a
specific unique mobile subscriber, as defined by his MSISDN, is
prompted to connect on a social media platform.
EQUIVALENTS
[0077] It is to be understood that the foregoing description is
intended to illustrate and not limit the scope of the invention,
which is defined by the scope of the appended claims. Those skilled
in the art will recognize, or be able to ascertain, using no more
than routine experimentation, numerous equivalents to the specific
embodiments described specifically in this disclosure. Such
equivalents, and other aspects, advantages, and modifications are
within the scope of the following claims.
* * * * *
References