Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't show order pop-up screen when order is going to be 1st in server's queue #17

Open
demant opened this issue Jan 22, 2016 · 3 comments
Assignees

Comments

@demant
Copy link

demant commented Jan 22, 2016

To prevent customers receiving too many text messages, when an order is dropped into a servers queue and it's their first order, don't show the order pop-up screen. The goal being that dispatch won't send a text message from Atlas and instead the customer will receive the automated text message from the server accepting the order.

VJC: And, they will have already received the automated 1st txt message.

@vcardillo
Copy link
Member

Hey Marc. Are you able to possibly get to this after OA? We've had several complaints about too many texts in a row.

@demant
Copy link
Author

demant commented Feb 3, 2016

I found another problem that's causing this. Orders are unassigned when the app disconnects. Then we have to reassign. When we reassign, server confirms order again, sending another text message.

On Feb 3, 2016, at 2:06 PM, Vincent Cardillo [email protected] wrote:

Hey Marc. Are you able to possibly get to this after OA? We've had several complaints about too many texts in a row.


Reply to this email directly or view it on GitHub.

@vcardillo
Copy link
Member

I see.

Let's prioritize fixing Atlas/Houston first then. Obviously the case can
still happen, but the connectivity issues are a primary root cause. Then we
can look into tracking what sort of txts we have already sent, and not
sending them again.

On Wed, Feb 3, 2016 at 2:53 PM, Jason Demant [email protected]
wrote:

I found another problem that's causing this. Orders are unassigned when
the app disconnects. Then we have to reassign. When we reassign, server
confirms order again, sending another text message.

On Feb 3, 2016, at 2:06 PM, Vincent Cardillo [email protected]
wrote:

Hey Marc. Are you able to possibly get to this after OA? We've had
several complaints about too many texts in a row.


Reply to this email directly or view it on GitHub.


Reply to this email directly or view it on GitHub
#17 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants