Context
Carlo asked us to research whether Joanna could take a photo of a Dunkin receipt, extract the survey details from the image, complete the customer survey flow, and return the resulting validation code.
This should be evaluated as a legitimate receipt-owner workflow only, with guardrails around review and submission rather than assuming a fully blind automation path.
Why it matters
This would be a useful real-world vision + browser-automation test for Joanna:
- image understanding/OCR on noisy phone photos
- structured field extraction from receipts
- form navigation across a third-party survey flow
- returning a short actionable result back to Telegram
The main non-technical constraint is promo/survey policy. Dunkin's published redemption restrictions say the receipt with the validation code must be presented at redemption time, the receipt may not be reproduced/copied/traded/sold, and the validation code expires after 14 days. That suggests the workflow should stay tightly scoped to the original purchaser and keep the original receipt in hand.
Proposed next step
Build a small proof-of-concept with these guardrails:
- accept a receipt photo in Telegram
- use vision to extract store/date/survey code or receipt identifiers
- show the parsed fields back for approval
- automate the survey browser flow only after confirmation
- return the validation code plus any redemption timing notes
Success criteria:
- handles normal mobile receipt photos reliably
- does not submit if the receipt fields are low-confidence
- keeps a human confirmation step before final survey submission
- returns a concise result that can be used in-store with the original receipt
Research links
Context
Carlo asked us to research whether Joanna could take a photo of a Dunkin receipt, extract the survey details from the image, complete the customer survey flow, and return the resulting validation code.
This should be evaluated as a legitimate receipt-owner workflow only, with guardrails around review and submission rather than assuming a fully blind automation path.
Why it matters
This would be a useful real-world vision + browser-automation test for Joanna:
The main non-technical constraint is promo/survey policy. Dunkin's published redemption restrictions say the receipt with the validation code must be presented at redemption time, the receipt may not be reproduced/copied/traded/sold, and the validation code expires after 14 days. That suggests the workflow should stay tightly scoped to the original purchaser and keep the original receipt in hand.
Proposed next step
Build a small proof-of-concept with these guardrails:
Success criteria:
Research links