Welcome to Tesla Motors Club
Discuss Tesla's Model S, Model 3, Model X, Model Y, Cybertruck, Roadster and More.
Register

'Get Amped Tour' Email Invites

This site may earn commission on affiliate links.
Got ours this afternoon, 3807. Will attend in Oregon. We are disturbed that there is only one drive slot for our reservation. Our Model S will be our only car and my wife and I consider it ours equally. Both of us need to test drive it. We understand the need to limit time if 5000 reservation holders are going to be accommodated in such a short time. Perhaps our time slot could be divided in the middle and we can both drive it in the limited time window. This is only reasonable. Come on Tesla.
With that reservation number, you'd probably be looking at an October delivery at the earliest. If that's the case, I'd like to think that there will be another opportunity to test drive before then. I'm 4398, and may not be able to make any of the test drives in my area or elsewhere. But I'm expecting that this is NOT the only chance to test drive before my time to order. Just my guess.
 
Side note: I got a reply back from the gentleman that took care of my MVPA paperwork re: the test drive weekend.

He indicates even some of the folks working the event haven't had a chance to test drive the cars yet! The product specialists are very much looking forward to the test drives as well.
 
Anyone else wondering if Tesla over-estimated our collective ability/desire to fly in for this one?

It would seem Tesla over-estimated the amount of people interested in flying to Fremont last minute. Something tells me LA will book fast.

^ Haha. Sorry mate, missed that one. Great minds think alike.

Hi Nigel,

The key of course is that Tesla sent these invitations for Fremont at the last minute. Unquestionably the turnout would have been a lot better if they had provided sufficient notice to permit folks to arrange their schedules and obtain more reasonable airfares.

I don't attribute any ulterior motives to Tesla, such as they intentionally wanted to favor local reservation holders, etc. Nevertheless this apparent inability to provide more timely notification definately hurt those out ot state, low-number reservation holders who not unreasonably wanted to have a test drive prior to making a final commitment.

Larry
 
Hi Nigel,

The key of course is that Tesla sent these invitations for Fremont at the last minute. Unquestionably the turnout would have been a lot better if they had provided sufficient notice to permit folks to arrange their schedules and obtain more reasonable airfares.

I don't attribute any ulterior motives to Tesla, such as they intentionally wanted to favor local reservation holders, etc. Nevertheless this apparent inability to provide more timely notification definately hurt those out ot state, low-number reservation holders who not unreasonably wanted to have a test drive prior to making a final commitment.

Larry

Any questions of motivation aside, the practical effect of Tesla not releasing the event invites until Saturday has made it so only those out of towers who REALLY want a reservation before finalizing will do so. It's unlikely to be impossible to get a flight, just more expensive than it might have been a few days earlier.
 
Any questions of motivation aside, the practical effect of Tesla not releasing the event invites until Saturday has made it so only those out of towers who REALLY want a reservation before finalizing will do so. It's unlikely to be impossible to get a flight, just more expensive than it might have been a few days earlier.

Quite true.

So are you suggesting that the late notification is warranted?

Larry
 
That makes it sounds like conspiracy and... could've done the conspiracy better. :wink:

I think the event was penciled in. They had some buffer time built into the schedule in case things went well. They must have made a call that things went well enough that they could build some cars solely for demo purposes without showing yet-another-beta and not impacting the delivery schedule. If things didn't go that well, the events couldn't have been planned at all.

At least that's my theory.
 
Quite true.

So are you suggesting that the late notification is warranted?

Larry

No, sorry, I didn't mean to imply that. All I was saying was that the late announcement seems to have made early reservations holders weigh how much they want that pre-signing test drive. I don't think that it was their intent to do so.

Frankly I'm annoyed that they couldn't get their act together sooner so that early reservation holders (who don't live in the Bay Area) wouldn't be in this position. After all, it IS a lot of money and a short window in which to make a decision. My dad's in this position and, after they announced the event we just decided to go for the weekend. Then again, it's a relatively short, direct, flight from Eugene, OR.
 
No, sorry, I didn't mean to imply that. All I was saying was that the late announcement seems to have made early reservations holders weigh how much they want that pre-signing test drive. I don't think that it was their intent to do so.

Frankly I'm annoyed that they couldn't get their act together sooner so that early reservation holders (who don't live in the Bay Area) wouldn't be in this position. After all, it IS a lot of money and a short window in which to make a decision. My dad's in this position and, after they announced the event we just decided to go for the weekend. Then again, it's a relatively short, direct, flight from Eugene, OR.

Thanks for the clarification. I'm in complete agreement with you.

I'd like to emphasize that I'm not one of those folks that thinks that there was some sort of conspiracy to limit out of towners from getting early test drives. In fact I really like the manner in which Tesla set up the process. The only sticking point is they did not execute their invitation plan in a timely manner and this hurt early reservation holders.

Larry
 
My guess is that Tesla set up a software process to send the invitations in sequence, and process the RSVPs in near real time on return. It is quite a cat of procedure to test. You must bombard it with all kind of requests and with big numbers to detect any problems that occur under heavy load. They blew the deadline just to make sure everything goes well, and apparently it does.