Sticky idea - travel date, route, date points posted
#1
Original Poster
Join Date: May 2000
Location: Knoxville TYS TN
Programs: Hilton (D)
Posts: 256
Sticky idea - travel date, route, date points posted
I'm always left wondering, is there an issue with my rail points posting or should I just wait longer ?
If we had a sticky with travel date, route #, and date points posted, if others were on the same itinerary, they'd know if there's an issue or not.
Thoughts ?
If we had a sticky with travel date, route #, and date points posted, if others were on the same itinerary, they'd know if there's an issue or not.
Thoughts ?
#4
Original Poster
Join Date: May 2000
Location: Knoxville TYS TN
Programs: Hilton (D)
Posts: 256
On the same line of thought....I sent an email to AGR asking them to consider placing a date notice on their website that states "Points for all travel on or before mm/dd/yyyy have been processed."
Their workflow should get them to point where all expected stubs from x days ago, have been collected, turned in, and reviewed.
Their workflow should get them to point where all expected stubs from x days ago, have been collected, turned in, and reviewed.
#5
#6
FlyerTalk Evangelist
Join Date: Jul 2003
Posts: 11,377
On the same line of thought....I sent an email to AGR asking them to consider placing a date notice on their website that states "Points for all travel on or before mm/dd/yyyy have been processed."
Their workflow should get them to point where all expected stubs from x days ago, have been collected, turned in, and reviewed.
Their workflow should get them to point where all expected stubs from x days ago, have been collected, turned in, and reviewed.
#7
In Memoriam
Join Date: Mar 2004
Location: New York, NY, USA
Programs: HH Diamond, Amtrak Exec
Posts: 3,262
On the same line of thought....I sent an email to AGR asking them to consider placing a date notice on their website that states "Points for all travel on or before mm/dd/yyyy have been processed."
Their workflow should get them to point where all expected stubs from x days ago, have been collected, turned in, and reviewed.
Their workflow should get them to point where all expected stubs from x days ago, have been collected, turned in, and reviewed.
This is due to where the conductor turns in the tickets, which then have to be sent elsewhere in most cases for processing. Making things even more interesting is the following scenario. One person rides NY to DC tomorrow. Another person boards the Texas Eagle tomorrow in Chicago, headed for LA.
The ticket from the person riding NY to DC will be turned in on Thursday at DC by the conductor of that train. The ticket from the person riding the Eagle won't get turned in until Sunday when the train reaches LA.
So already the person riding the NEC has a 3 day advantage over the person riding the Eagle.
#9
Join Date: Nov 2003
Location: SFO
Programs: UA Silver, HH/Bonvoy Gold, AA, WN CP
Posts: 154
Points posting in the month of February has been very spotty for me. I haven't gotten credit yet for some Capitols trip earlier in the month, as well as for a Starlight trip. Separately, two Acela Express trips posted within 3 or 4 days, while another two taken the following day (middle of the month) haven't posted at all. I'm going to wait until next week before I put in the ticket info online and see if they will post that way.