Turn AR/VR Booth Demos Into CRM Leads with Offline Sync

				
					DESCRIPTION
Generate the full deliverable pack: field map CSV, integration spec, flow diagram, storyboard frames, and follow-up templates.

TASK
Produce paste-ready assets with exact endpoints, payloads, offline buffer, retry/backoff, dedupe/upsert, and message templates.

ROLE
You are Offline-First Integrations Lead, a senior architect for event-grade reliability.

INPUTS
Use only the Outputs from Prompts 1 and 2.

WORKFLOW (no steps skipped)
1) Map each source field to CRM payload keys. Include types, required flag, validation, and normalization.
2) Specify CRM auth and upsert: endpoint paths, headers, request/response examples, rate limits, and idempotency keys if supported.
3) Design offline buffer: local schema, encryption at rest, TTL, sync policy (retry with exponential backoff), and conflict resolution (upsert with dedupe keys: email+phone+event_id).
4) Define reconciliation: how to detect and merge duplicates, error logging, operator re-try UI for failed posts.
5) Produce a flow diagram in Mermaid that can export to PNG showing entry → capture → buffer → sync → CRM → follow-up trigger.
6) Create a storyboard: 3–6 annotated frames with screen purpose, inputs, consent UI, success and failure views, and handling for unsynced returns.
7) Draft three follow-up templates (Email, LinkedIn DM, SMS/WhatsApp) with subject/preview, 2–3 short paragraphs, CTA, and send timing recommendations.
8) Include short inline citations where external docs informed technical choices.

OUTPUT FORMAT
# 1) Flow Diagram (Mermaid)

flowchart TD

A[Demo Moment: Natural Pause] --> B{Capture Path}

B -->|Pattern A| C[In-Headset Quick Capture]
B -->|Pattern B| D[QR Prefill on Mobile]

C --> E[Local Buffer Encrypt + TTL]
D --> E

E -->|Online? yes| F[Auth → CRM Upsert]
E -->|Online? no| G[Retry Backoff Queue]

F --> H[CRM Response 200/201/204]
H --> I[Trigger Follow-up via CRM Workflow]

G -->|Backoff succeeds| F

F -->|409/duplicate| J[Reconciliation: Upsert/Merge]
F -->|4xx/5xx| K[Error Log + Operator Retry UI]

(Export this to PNG at 800–1200px)


# 2) Field Mapping CSV


Provide a CSV in a fenced block ready to save as .csv:

source_field,crm_field,type,required,validation_rule,normalize_rule

first_name,Contacts.FirstName,string,true,^[A-Za-z' -]{1,50}$,capitalize

last_name,Contacts.LastName,string,true,^[A-Za-z' -]{1,50}$,capitalize

email,Contacts.Email,string,required_if_no_phone,^[^@\\\\s]+@[^@\\\\s]+\\\\.[^@\\\\s]+$,lowercase_trim

phone,Contacts.Phone,string,required_if_no_email,^\\\\+?[0-9\\\\s().-]{7,20}$,E164

company,Accounts.Name,string,false,^.{1,100}$,titlecase_trim

consent_opt_in,Contacts.Marketing_Opt_In,boolean,true,^(true|false)$,map_true_false

notes_tag,Contacts.Description,string,false,^.{0,240}$,strip_emoji

event_id,Custom.Event_Id,string,true,^[A-Z0-9_-]{6,32}$,uppercase

staff_owner,Contacts.OwnerId,string,false,^.{0,64}$,map_to_owner


# 3) Integration Spec (1–2 pages)

- Overview

- Goal: reliable AR/VR booth lead capture with offline-first sync under SLA.

- CRM: [from P1], Upsert method: [from P1 findings] (Source, Year).


- Authentication

- Flow: OAuth client credentials or PAT with scoped permissions (Source, Year).

- Token storage: secure keychain or platform keystore; rotate every X hours.


- Endpoints

- Upsert/Create Contact: [verb + path]. Include headers and example payload.

- Lookup for dedupe: by email and phone where supported. Note rate limits (Source, Year).


- Sample Request

- Provide JSON payload with fields from the CSV mapping.


- Responses & Errors

- 200/201/204 success semantics; 4xx validation; 409 duplicate; 429 rate limit with Retry-After (Source, Year).


- Offline Buffer Strategy

- Local schema: lead_id, payload_json, status, attempts, next_retry_at, error_code, created_at.

- Encryption: AES-256 at rest; keys via OS keystore.

- TTL: purge records after X days post-success; cap queue length at N to protect storage.

- Retry Policy: exponential backoff starting at 30s, then 2m, 5m, 15m, 60m, max attempts 8.


- Reconciliation & Upsert

- Dedupe keys: email, phone, event_id. If missing email and phone, queue for operator review.

- Merge strategy: keep most recent non-empty values; preserve consent timestamps and IP where available.


- Operator Tools

- On-device “Sync status” screen; manual retry; export queue as CSV via secure share if needed.


- Security & Privacy

- Consent capture: store timestamp, version of consent text, and staff_owner.

- Data minimization: capture only fields in Minimal Field Set.

- Compliance: honor delete requests on buffer and CRM entities.


- Monitoring

- Log metrics: queue size, success rate, average latency to CRM, error distribution.

- Alerting: if queue older than SLA threshold or error rate exceeds 5%.


- References

- Link to CRM docs used and SDK docs used, inline citations included above.


# 4) Storyboard Frames


Frame 1 Entry Pause

- Context: demo reaches a “wow” moment and natural pause.

- UI: minimal overlay with two chips [I want the deck] [Talk to a human].

- Input: gaze or controller select; no text yet.


Frame 2 Capture Lite

- Fields: first_name, email or phone, one chip for consent.

- UI: large targets; auto-format phone; voice-to-text optional where SDK supports dictation (Meta SDK, 2024).

- Offline note: if offline, show no spinner; buffer silently with “Saved to queue”.

Frame 3 Success

- Message: “You’re in. We’ll send the deck now.”

- Option: “Book 15 minutes” QR that opens scheduler on mobile.


Frame 4 Error or Duplicate

- If 4xx: “That email looks off. Try again or use phone.”

- If duplicate: “We found you. Updating your info.”

Frame 5 Unsynced Return



- Badge: “1 item waiting to sync” visible to staff only.

- Action: tap to force retry or export queue.



# 5) Follow-up Templates


Email (send within 30–90 minutes)
Subject: Your demo takeaways and a 15‑minute slot
Preview: Fast recap plus the deck from the booth
Body:
Hi {FirstName} — great meeting you at {EventName}.


Here’s the demo recap and deck we promised. If the {Problem we showed} hit home, I can walk you through how we sync AR VR demos straight into {CRM} and turn them into meetings under {SLA}.


Grab a 15‑minute slot here: {CalendlyLink}


If you prefer, reply with a window that works.


P.S. We can run offline at your venue and still sync in minutes (Source, Year).


LinkedIn DM (send same day by staff_owner)
Hey {FirstName}, enjoyed the {DemoTopic} walk‑through at {EventName}.


We capture leads in‑headset and sync to {CRM} even when Wi‑Fi flakes. If useful, I’ll send a 2‑minute clip and a quick slot link. Cool?


SMS or WhatsApp (send end of day if consented)
Hi {FirstName} from {Company} this is {StaffName} at {EventName}. We just sent your deck. Want a 10‑minute debrief on how we route AR VR booth leads into {CRM} under {SLA}? Reply 1 for yes.


RULES



- Include short inline citations where used.

- Keep total length under 1,200 words.

- No secrets or tokens in examples. Use placeholders.