27 lines
1.6 KiB
Markdown
27 lines
1.6 KiB
Markdown
# Avis Email Verification Code Workflow
|
|
|
|
When a service (Avis, bank, etc.) emails a one-time security code, the agent can read the inbox faster than the user can find the email.
|
|
|
|
## Pattern: Monitor inbox for verification code
|
|
|
|
1. User triggers login at avis.com → email goes out
|
|
2. Agent checks inbox for "security code" from Avis
|
|
3. Extracts the code and tells the user
|
|
4. User enters it — logged in
|
|
|
|
The email content is HTML-only (no text/plain alternative). The code itself may be embedded in invisible HTML constructs — extract from body text after stripping tags.
|
|
|
|
## Confirmations: Avis reservation chain
|
|
|
|
After login, the user will click through to book. Avis sends immediate confirmations:
|
|
1. Avis sends "Reservation Confirmation" email — extract reservation #, vehicle, pick-up/drop-off, total
|
|
2. Agent reports the key details back to user
|
|
|
|
## Pitfalls
|
|
|
|
- Avis uses email-based login — the security code goes to the user's inbox, making the agent's IMAP access essential
|
|
- Avis For Business sends separate password reset emails — the password reset email from "Avis For Business" is a different flow from the personal account login. Distinguish by subject line
|
|
- Verification code emails have near-identical subjects — "Avis: Your security code" multiple times. The last one (highest UID) is the current login attempt
|
|
- Ford Explorer is the default mid-size SUV — Avis frequently assigns Ford Explorer or similar for mid-size SUV bookings
|
|
- Confirmation numbers — Avis reservations starting with #1958XXXXUSX pattern. Store both reservation #s when booking a round-trip-two-reservation itinerary
|