AT&T text notification issue
02-24-2019, 09:40 PM
#1
Gets Weekends Off
Thread Starter
Joined APC: Apr 2008
Posts: 1,803
AT&T text notification issue
Does anyone know the current status of the AT&T delayed text message trip trade notifications?
I just got one 4 hours after the event occurred, nice.
I'm not clear if the issue is actually AT&T, UAL, or Crew Companion or a combination of all. A switch to T-Mobile might be an easy fix. Any info would be appreciated, thanks!
I just got one 4 hours after the event occurred, nice.
I'm not clear if the issue is actually AT&T, UAL, or Crew Companion or a combination of all. A switch to T-Mobile might be an easy fix. Any info would be appreciated, thanks!
02-25-2019, 05:31 AM
#3
Gets Weekends Off
Joined APC: Nov 2008
Position: Airbus 320 Right Seat
Posts: 1,440
Been going on for months now . I thought it was fixed but people seem to continue to have problems .
Issue is you don’t know what you missed in some cases . The prob is ATT , had this issue at Jetblue. Took months but found out ATT was blacking the messages from coming through in a spam filter. Spent hours on the phone with ATT trying to explain and fix the issue . And they are worthless . Even the IT guy was like this is way above the average IT guy . Got a 50 dollar credit . Big deal. I’m on a huge family plan so it’s hard to up and leave . But if I see that it continues I will bail for sure . Prob go to Verizon .
Issue is you don’t know what you missed in some cases . The prob is ATT , had this issue at Jetblue. Took months but found out ATT was blacking the messages from coming through in a spam filter. Spent hours on the phone with ATT trying to explain and fix the issue . And they are worthless . Even the IT guy was like this is way above the average IT guy . Got a 50 dollar credit . Big deal. I’m on a huge family plan so it’s hard to up and leave . But if I see that it continues I will bail for sure . Prob go to Verizon .
02-25-2019, 09:57 AM
#9
Gets Weekends Off
Thread Starter
Joined APC: Apr 2008
Posts: 1,803
Thanks! That worked.
For anyone else having this problem the fix that worked for me was:
Add the suffix posted above behind your phone number in the notifications section of the crew companion options menu.
It should look like this:
[email protected]
Select AT&T as you carrier. You can send a test message to verify the connection. Now, crossing my fingers that it works for CCS generated notifications.
For anyone else having this problem the fix that worked for me was:
Add the suffix posted above behind your phone number in the notifications section of the crew companion options menu.
It should look like this:
[email protected]
Select AT&T as you carrier. You can send a test message to verify the connection. Now, crossing my fingers that it works for CCS generated notifications.
02-26-2019, 07:48 AM
#10
Line Holder
Joined APC: Apr 2013
Posts: 33
Don’t use dashes in the phone #. It should be “[email protected]”. This has been working for me for several weeks now.
Thread
Thread Starter
Forum
Replies
Last Post
