Demo · For brokers
Watch a broker route a single enrollment record into 834 transmissions to four different carriers — medical, dental, vision, and life — without writing a line of X12.
01 · Send your shape
You don't shape the data to fit Velora. Velora reads what your DB already produces. Workday export, Paylocity CSV, custom JSON — all accepted. You POST one enrollment record; Velora derives the carrier-targeting from the plan elections.
# Your existing HRIS export — no transformation curl -X POST https://velora-edi.vercel.app/api/v1/enrollments/raw \ -H "Authorization: Bearer vb_live_..." \ -d '{ "member_id": "E445221", "first_name": "Maria", "last_name": "Chen", "ssn": "***-**-1234", "dob": "1987-03-14", "effective_date": "2026-06-01", "plans": [ { "carrier": "AETNA", "plan_id": "HSA-PPO-2K", "tier": "family" }, { "carrier": "DELTA", "plan_id": "PPO-DENTAL", "tier": "family" }, { "carrier": "VSP", "plan_id": "VISION-BASIC", "tier": "family" }, { "carrier": "METLIFE", "plan_id": "LIFE-2X", "tier": "employee" } ], "dependents": [...] }'
What just happened
One POST. Four carriers targeted. Velora reads the plan elections, identifies the four carriers (Aetna medical, Delta dental, VSP vision, MetLife life), and queues four parallel 834 generations.
02 · AI mapping
First time you send to a new carrier, Claude proposes the field-by-field mapping with confidence scores. High-confidence mappings auto-confirm; lower ones land in your review queue. Once approved, Velora reuses the mapping for every subsequent record.
# /broker/mappings/AETNA — auto-proposed SOURCE FIELD → X12 TARGET CONFIDENCE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ member_id → REF*0F 0.99 ✓ auto first_name → NM104 0.99 ✓ auto last_name → NM103 0.99 ✓ auto ssn → NM109 (qualifier 34) 0.97 ✓ auto dob → DMG02 0.99 ✓ auto effective_date → DTP*348 0.95 ✓ auto plan_id → REF*1L 0.78 ⚠ review tier → INS04 0.81 ⚠ review ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 24 of 26 fields auto-approved · 2 pending review [Review · 2] [Test against sample] [Approve all]
What just happened
26 fields mapped in seconds. 24 of them auto-approved at confidence ≥ 0.9. The 2 pending fields land in your review queue with the AI's reasoning attached. Approve once, and the mapping is locked for every future record.
03 · Multi-carrier transmission
Velora generates four X12 834 files — one per carrier — with each carrier's specific control numbers, ISA segments, and validation rules applied. Transmissions queue against each carrier's SFTP window. Acknowledgments stream back through your webhook feed.
# /broker/transmissions — Maria Chen enrollment CARRIER FILE STATUS ACK ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ AETNA 834.20260501.0244.x12 ✓ transmitted 999 accepted DELTA 834.20260501.0103.x12 ✓ transmitted 999 accepted VSP 834.20260501.0058.x12 ✓ transmitted 999 accepted METLIFE 834.20260501.0091.x12 ✓ transmitted 999 partial # MetLife 999 partial — drilling in... METLIFE 999 ACK · LINE 4 IK4*INS04*1273*5*F~ (spec rejection: invalid coverage tier) AI EXPLANATION MetLife rejected INS04 with code F because their plan LIFE-2X is employee-only — they don't accept dependent coverage on this plan. The record was correct; the plan election conflicts with MetLife's product configuration. SUGGESTED FIX Either resubmit with INS04=EMP (employee-only) or check with the employer about whether dependents need separate enrollment.
What just happened
Four parallel transmissions. Three accepted instantly. The MetLife rejection came back as a cryptic 999 segment — Claude explained it in plain English and proposed the fix. Your team didn't have to decode `IK4*INS04*1273*5*F`.
04 · Voice + AI assistance
Voice button in the broker portal. Ask 'why did the MetLife transmission partial-reject?' and the agent reads the 999 segment, explains it in English, and offers to retry with the suggested correction. Same answer the AI explanation gave you — but you didn't have to click into the ledger.
YOU Why did the MetLife transmission for Maria Chen partial-reject? AGENT MetLife rejected the INS04 segment because the plan you selected — LIFE-2X — is employee-only. Maria's record had coverage tier set to family, which doesn't apply to that product. Want me to retry with the tier set to employee-only, or do you want to check with the employer first? YOU Retry with employee-only. AGENT Submitting now. Velora is generating an updated 834 with INS04=EMP and queuing the transmission. You'll see the new 999 acknowledgment in your ledger within 60 seconds. ━━━ 47 seconds later ━━━ AGENT MetLife accepted the corrected transmission. Maria Chen is now active across all four carriers — Aetna, Delta, VSP, MetLife. Anything else?
What just happened
A 47-second voice exchange resolved a transmission rejection that would normally require a tier-1 support ticket, a manual ledger review, and a re-submission. Every action the agent took is logged in your tenant audit log.
Self-serve signup, or talk to us about your specific timeline and integration shape.