Conversation follow-up
These choices are separate and optional. The demo records only the choices you make here. A production deployment would deliver an opted-in transcript by email after the provider’s delivery configuration is enabled.
DLR · VOICE DEMO
Ask naturally.
Hear a grounded answer.
Tide Original Liquid Laundry Detergent · independent US-English example
- Grounded answersReplies come from an approved product corpus, not open-web guesswork.
- Five-minute sessionThe microphone is open only while the session is running.
- No raw audio keptSpeech is processed live; this preview retains no recording.
- Transcript on requestEmailed only if you ask for one at the end.
Not affiliated with or endorsed by Tide or P&G. DLR answers from a limited public-source demonstration corpus. Your voice and the demonstration corpus are sent to xAI to generate responses. The microphone is used only while this session is active; this preview does not retain raw audio.
Hands-freeNoisy venue? Switch on to tap before speaking, instead of the microphone listening continuously.
Live product conversation
Ask questions first. At the end, DLR will show separate optional choices for a transcript record and marketing follow-up.
Ready to start a live voice conversation.
What DLR does
A GS1 Digital Link resolver is the layer between a scanned code and wherever the shopper ends up. From 2027, retail checkout moves to 2D barcodes, so the code that rings a product through the till is the same one a shopper points a phone at. DLR is the middleware that decides what happens next — per scan, rather than as one fixed redirect baked into the code.
This page is one surface of that. The assistant answers from an approved product corpus rather than from open-web guesswork, and says so plainly when a question falls outside what it has been given. Nothing is kept until the conversation ends and you choose: the microphone is open only while the session runs, no raw audio is retained, and a transcript reaches your inbox only if you ask for one.
Underneath the demo, the resolver covers what a brand operator actually needs:
- Digital Link parsing. GTIN, SSCC, GLN, ITIP, CPID and GMN keys, with check digits verified and GTIN qualifier order — consumer product variant, then batch, then serial — enforced rather than assumed.
- No back door to a generic answer. If a question falls outside the approved corpus, the assistant says so rather than guessing — and the question itself is logged for the brand to answer, not quietly outsourced to another model.
- Conditional routing. Each scan is resolved against the campaign rules that were published, using country, region, language, device, time window and how often that visitor has scanned before.
- Publishing that cannot be rewritten. A published version is written once and never edited, and a destination outside the brand’s allowlist is refused at publish time rather than at redirect time.
- Answers at the edge. A campaign can reply with a cached micro-page served from the edge instead of bouncing the shopper onward.
- Codes and embedding. An SVG code per product, validated through the same parser that serves scans, plus a paste-in tag for a brand’s own pages.
- Consent-gated capture. Transcripts are stored only on explicit opt-in, email addresses are kept as hashes and never in the clear, and the record is purged after 24 hours.
- Operator dashboard. Products, routing rules, publishing, a preview of unpublished drafts through the real renderer, scan statistics and interaction records — behind authentication.
- Conformance endpoints. A linkset response and a resolver description file, built to the specification so GS1 registration becomes configuration rather than code.
Scope, plainly: this is a demonstration on a placeholder domain, not a GS1-registered resolver. The voice conversation you can try here is live; the operator dashboard sits behind sign-in and is not part of this page.