Read the live day
Timeline state, protected moments, buffers, readiness, and the next handoff give the assistant the context a generic conversation does not have.
Wedding Day Assistant reads the live timeline, identifies what is at risk, and proposes one recovery for the authorized lead to review. SmartRipple suggests. Planner decides. Nothing changes or sends on its own.
$99.99 for one wedding. One-time purchase. Includes the Day-Of tools in Wedding Pass.
One-time purchase. Includes Wedding Pass, planning and final-week readiness, SmartRipple recovery suggestions, role-specific handoffs, and planner-approved action prompts.
Say it the way you’d say it out loud — “hair and makeup is 25 minutes behind and I’m freaking out” — and it reads your whole day: what’s at risk, what can absorb the delay, and one recovery plan grounded in your live timeline.
Behind that interaction is a custom interpreter model fine-tuned on wedding-day coordination language, paired with the deterministic rules engine that governs every recommendation path.
It does not ask you to translate a wedding-day problem into a generic prompt. It uses the live context already in EventSync Day-Of to keep the suggestion tied to this wedding, this schedule, and the people affected.
Timeline state, protected moments, buffers, readiness, and the next handoff give the assistant the context a generic conversation does not have.
It separates what is at risk from what can absorb a delay, so the whole day does not get rebuilt for a single issue.
The assistant presents a grounded recovery plan for review. The planner decides whether it is right for the room, the couple, and that moment.
A deterministic wedding rules engine has the final say, and you approve every change. It knows when to act, when to double-check, and when to say “that’s a rumor — no action.” Nothing sends on its own.
Planner control stays visibleThe deterministic wedding rules engine evaluates each situation before a recommendation can become a planner-facing action.
Wedding Day Assistant provides a suggestion. A planner or authorized lead chooses whether to apply an existing EventSync action.
Only fixed, registry-valid actions reach the engine, keeping a suggested action inside the operational vocabulary EventSync knows how to govern.
Wedding Day Assistant is evaluated against a locked, held-out 51-scenario wedding-day exam covering cascades, vendor problems, weather calls, and human emergencies.
What happens when one late moment puts several downstream handoffs at risk.
How the system frames a delay, missed arrival, or broken operational dependency.
When a weather report needs context, confirmation, or no action at all.
When the correct response is to hold, escalate, or wait for a planner’s judgment.
Powered by EventSync Embedded Intelligence.
It is wedding day AI built for live coordination: it reads the EventSync timeline, identifies what is at risk, and presents one recovery plan for planner review.
No. Wedding Day Assistant runs on AI trained specifically for wedding-day coordination, not a general chatbot with a wedding prompt. It reads the live EventSync timeline and suggests one recovery plan grounded in that wedding.
The planner approves every change. The deterministic wedding rules engine has final authority over the recommendation path, and nothing sends on its own.
The governed outcomes include hold, escalate, confirm first, refuse, and watch. The system is designed to recognize when it should double-check or take no action.
Wedding Day Assistant is evaluated against a locked, held-out 51-scenario wedding-day exam covering cascades, vendor problems, weather calls, and human emergencies.
See how live timelines, Wedding Day Assistant, and planner-reviewed SmartRipple recovery work together in EventSync Day-Of.