The participant books
They book through the external AI Dinner Portal and share event details, attendee information, and preferences.
Quietly in AIWBBooking and attendee changes arrive by webhook and preserve the source event state.
AI Dinner participant experience
From booking to table companion.
AI Dinner turns a live booking source, consent-aware context, curated seating, and a personal event portal into a more thoughtful guest experience.
Core promise
Each participant should feel expected, intelligently seated, and confident about who they will meet.
External booking source
Consent-aware context
Curated seating
Participant portal
Visual storyboard
A guest journey with the engine quietly underneath.
Each step starts with what the participant experiences, with AIWB visible as the support layer.
Consent shapes the experience
Their choices decide whether email, profile context, name visibility, and dinner eligibility can be used.
Quietly in AIWBThe event separates contact consent, profile visibility, attendance, and participant-facing safety.
Useful context is prepared
Eligible participants do not need to write a long profile for the evening to feel thoughtful.
Quietly in AIWBApproved context becomes safe chips: role, company, topics, and conversation hooks.
Seating is curated
The table feels intentional: who they meet, why the group works, and what the host wants to create.
Quietly in AIWBAssignments, rationale, companion context, and host review come together before release.
The portal becomes the companion
They receive a useful page with their table, practical details, people they may meet, and event prompts.
Quietly in AIWBReviewed participant-safe content renders into email and portal artifacts.
Late changes stay calm
If someone cancels or joins late, participants only see the update that matters to them.
Quietly in AIWBSource changes are classified by impact, event phase, consent boundary, and review need.
How it works
From live source to reviewed participant experience.
Bookings stay outside AIWB. Consent, context, and review happen before release.
External source
Bookings and changes arrive.
Event state
The live record stays current.
Consent boundary
Permissions stay separate.
Safe context
Approved context is prepared.
Seating review
The host reviews tables.
Portal release
The participant view goes live.
Source boundary
Booking starts outside AIWB.
Created, updated, cancelled.
Ready for consent, context, seating, and review.
Boundary protected
Consent model
Permission first.
Send portal invites.
Use approved profile context.
Show safe summaries.
Use for seating.
Destination experience
The participant portal is the product moment guests can feel.
The portal gives each participant a calm, practical sense of the evening: where they are seated, what makes the table interesting, what details matter, and what has changed.
Your table
Who you may meet
Why this table works
Event details
Updates
AI Dinner Portal
Ready for review
Your table
Table 4
Product leaders, operators, and founders exploring governed AI adoption.
Conversation hooks
AI in real workflows, customer operations, adoption trust.
Event update
No change to your table. Arrival details refreshed.
Behind the scenes
Codex configures. AIWB governs. Rules execute.
Three separate roles keep the dinner workflow fast, controlled, and reviewable.
Configures
Method becomes rules, prompts, and records.
>
AIWB
Governed workbench
Permitted work lives here.
Records
Consent
Review
Evidence
Outputs
Audit
>
Executes
Configured paths run consistently.
01
Booking change
02
Consent check
03
Host review
04
Guest output
Resilience
When the guest list moves, the experience stays composed.
Late cancellations, new attendees, consent updates, and profile changes become managed decisions instead of a scramble.
Change arrives
Booking, attendee, cancellation, or opt-in update.
Impact checked
Does seating, portal, host view, or email need to change?
Host reviews
Participant-visible changes wait for the right approval.
Guest stays clear
Only relevant updates reach the participant.