what STOP2end does?

[RJ]

Can Location Labs clarify what happens if a user sends back "STOP"?
We have a couple theories.

A) If the user previously was sharing location ongoing, the "STOP"
causes location to not be sharable. Basically the permission to get
location is removed for this phone for the app.

B) Not only is locaiton not shared, but the STOP causes the phone to
be put in a special status where no more SMS's will be sent to the
phone. If another invitation API were attempted for the phone, it
would not work, as an SMS would not be sent to the phone.

Can Location Labs clarify?

Thanks!

[Jesse Myers]

RJ -

You are basically correct. If an end user replies STOP, subsequent
calls to the invitation API will return an error indicating that the
message cannot be sent. The end user may clear this state in the
account settings of the veriplace.com privacy manager.

The STOP message may also remove existing opt-ins that the user has.
In addition it may provide instructions for the user to visit the
veriplace.com privacy manager to change their account settings or
close their account.

Jesse

[Mishit]

Hello Jesse
Developer guide says : "The user can send an SMS reply to grant
permission, and also to register with Veriplace at the same time if
not already registered; or the user can refuse, either by declining
that particular invitation or by requesting a block on all future SMS
invitations."

Have few questions regarding this:
1) Lets say user receives his first SMS inviation and he is not
already registered.
Now if he replies "Y" then how does veriplace register that
user ? I mean how does registration procedure look like? Because in
developer mode we can not see how this registration works.
If he replies "STOP" to this very first invitation then does
veriplace still create the user account and put his state to block
future invitations ?
2) How can user decline particular invitation request ?

thanks
/Mishit

[Jesse Myers]

If the user replies "Y" to an invitation and their mobile number is on
a support carrier, the registration process is immediate and
automatic. From your perspective, it will look exactly the same as if
the user was already registered and opted-in to your application.

If the user replies STOP the very first invitation, future invitations
will be blocked. Currently, the only way to remove this block is from
within the veriplace.com privacy manager, which means the user would
have to visit the site, sign up, and then remove the block.

The user can decline an invitation request by replying "N" or by
ignoring the request.

Jesse

[Mishit]

Thanks Jesse
Please see my response as below :
1)

> If the user replies "Y" to an invitation and their mobile number is on

> a support carrier, the registration process is immediate and....

Don't this registration process ask for password for account
creation ?

2)

> If the user replies STOP the very first invitation, future invitations

> will be blocked. Currently, the only way to remove ...

So this means even if user doesn't want to opt-in it creates user
account at veriplace.com ?

3) > The user can decline an invitation request by replying "N" or by
> ignoring the request.

Good to know that we can reply "N" to deny particular invitation. Is
there any reason why we are not seeing this option in invitation SMS
text.
We only see Y,STOP and HELP options.

thanks
/Mishit

On Oct 22, 11:18 am, Jesse Myers <jesse.my...@gmail.com> wrote:
> If the user replies "Y" to an invitation and their mobile number is on
> a support carrier, the registration process is immediate and
> automatic. From your perspective, it will look exactly the same as if
> the user was already registered and opted-in to your application.
>
> If the user replies STOP the very first invitation, future invitations
> will be blocked. Currently, the only way to remove this block is from
> within the veriplace.com privacy manager, which means the user would
> have to visit the site, sign up, and then remove the block.
>
> The user can decline an invitation request by replying "N" or by
> ignoring the request.
>
> Jesse
>

[Jesse Myers]

> Don't this registration process ask for password for account
> creation ?

No. The account is created, but without a password. The user will have
to go through the password reset flow on the privacy manager site to
create a password. This involves another SMS to their phone.

> So this means even if user doesn't want to opt-in it creates user
> account at veriplace.com ?

No. The list of blocked numbers that have replied STOP is kept
separately from our user accounts, so no account is created. However,
to remove the block, the user will have to visit the site and create
an account themselves.

> Good to know that we can reply "N" to deny particular invitation. Is
> there any reason why we are not seeing this option in invitation SMS
> text.
> We only see Y,STOP and HELP options.

I suspect this is an oversight and will be fixed in a future release.

[Mishit]

Thanks Jesse. That was clear.
By the way Do you know ETA for "N" option fix.

thanks
/Mishit

[Jason F.]

Mishit,

We are looking into adding the "N" option to the SMS, but to be quite
candid, this not only makes the text message fairly long, but it's
also not a MMA best practice.

Would an acceptable alternative be to make it easier for the end user
to proactively remove the block from their account (without visiting
the Veriplace end user site)?

Please advise.

Thanks,
Jason

p.s. - Maybe you could ask RJ what he thinks on this. ;-)

[Danny]

Kind of related to this subject, is there a call back method available
to know when a user has texted stop?

Thanks!
D

[Jason F.]

Danny - not yet. It's in the works...

[Mishit]

Is there a API to know whether end user has blocked the SMS
invitations or not ?

thanks
/Mishit

[Eli Bishop]

Mishit,

Not at present. However, if you try to send an invitation and you
receive an HTTP 403 error (which, in the SDKs, is converted to an
InvitationNotPermittedException), it must mean one of three things:
1. your application is unpublished and that number is not enabled as a
test phone;
2. the phone is on an unsupported network; or,
3. the user has blocked SMS invitations.

For a published application, #1 does not apply. You can rule out #2
using the Verify Locatability API - the low-level web service API for
this is described in section 11 of the Developer Guide, and in the SDKs
it's represented as a method of the PermissionAPI class. If that API
tells you that the number is valid and on a supported network, but you
are still not allowed to send an invitation, then it's safe to assume
that the user has blocked invitations.

best,
Eli

--
Eli Bishop
Wavemarket, Inc. / Location Labs
e...@location-labs.com

[Mishit]

Hello Eli
Thanks for the quick and detailed response. It makes sense.
But we take some actions on our side before sending an invitation to
end user. If end user has texted STOP earlier then we should not take
those actions.
So our situation is we can not call invitation API to check this
because if end user hasn't texted STOP then invitation will be sent
automatically before we take our actions.

/Mishit

[Brad]

Hello,

A user successfully opts in (replied with "Y") and days later decides
they wish to stop using the service. Could they find the original opt-
in message and just reply "STOP" to that? That is, would the STOP
functionality described in this thread pertain to someone who already
had opted in?

Sorry if the answer is buried in the thread; I may have missed it.

Thanks,
Brad

On Dec 21 2010, 6:28 am, Mishit <mishi.pa...@gmail.com> wrote:
> Hello Eli
> Thanks for the quick and detailed response. It makes sense.
> But we take some actions on our side before sending an invitation to

> end user. If end user has textedSTOPearlier then we should not take

> those actions.
> So our situation is we can not call invitation API to check this

> because if end user hasn't textedSTOPthen invitation will be sent

> > > > > > to proactively remove the block from theiraccount(without visiting

> > > > > > the Veriplace end user site)?
>
> > > > > > Please advise.
>
> > > > > > Thanks,
> > > > > > Jason
>
> > > > > > p.s. - Maybe you could ask RJ what he thinks on this.  ;-)
>
> > > > > > On Oct 25, 8:00 am, Mishit <mishi.pa...@gmail.com> wrote:
>
> > > > > > > Thanks Jesse. That was clear.
> > > > > > > By the way Do you know ETA for "N" option fix.
>
> > > > > > > thanks
> > > > > > > /Mishit
>
> > > > > > > On Oct 22, 1:32 pm, Jesse Myers <jesse.my...@gmail.com> wrote:
>
> > > > > > > > > Don't this registration process ask for password foraccount
> > > > > > > > > creation ?
>

> > > > > > > > No. Theaccountis created, but without a password. The user will have

> > > > > > > > to go through the password reset flow on the privacy manager site to
> > > > > > > > create a password. This involves another SMS to their phone.
>
> > > > > > > > > So this means even if user doesn't want to opt-in it creates user

> > > > > > > > >accountat veriplace.com ?
>
> > > > > > > > No. The list of blocked numbers that have repliedSTOPis kept
> > > > > > > > separately from our user accounts, so noaccountis created. However,

> > > > > > > > to remove the block, the user will have to visit the site and create
> > > > > > > > anaccountthemselves.
>
> > > > > > > > > Good to know that we can reply "N" to deny particular invitation. Is
> > > > > > > > > there any reason why we are not seeing this option in invitation SMS
> > > > > > > > > text.

> > > > > > > > > We only see Y,STOPand HELP options.

>
> > > > > > > > I suspect this is an oversight and will be fixed in a future release.
>
> > --
> > Eli Bishop
> > Wavemarket, Inc. / Location Labs

> > e...@location-labs.com- Hide quoted text -
>
> - Show quoted text -

[Eli Bishop]

Brad,

When someone sends a STOP to our shortcode, this is what we do:

1. If the user is currently opted into a single application, we remove that location permission.

2. If the user is currently opted into multiple applications, we don't remove those permissions, but we send a reply message explaining that they have multiple opt-ins, and that they can go to veriplace.com to remove one or all of them.

3. Regardless of the above, we place a block on that number so no further SMS invitations will be sent to it (this is the primary meaning of STOP which we're required to support). The user can undo this block in their account settings.

best,
Eli