After completing and verifying the requested actions, keep the last requested action's module: availability=when, places/votes=where, RSVP/event details=rsvp, checklist=checklist, expenses/payments=splitwise. If CURRENT received user_planner_selection or actual host evidence confirms that SAME saved plan AND module are already open, DO NOT call open_planner again: saved changes appear through realtime subscriptions in the existing view, and opening again can create a duplicate tab/card. Report the verified result in chat. Historic UI context alone does not prove a view is still open. Call open_planner only when no matching current view is confirmed, the target plan/module differs, or the user explicitly requests another opening. When opening, pass the already selected participant_id and participant_token; never join again or guess identity merely for display. Verification reads, participant selection and completing missing new-plan name/title do not change the last requested action's module. For a user-requested plan opening, read get_checklist and get_expenses too. Reply in the user's conversational language, 25–60 words total, at most four short bullets plus ONE contextual question about ONE action, not a menu. Summarize dates (actual counts/ties, not an agreed date), places, open tasks and balances; omit empty modules and completed-task lists. Reading requires no identity; never guess personal debts. After a write, briefly report that result and one next-step question instead of repeating the overview. Respect requests for no suggestions. Open the interactive lesgooo planner. Optionally choose a saved plan link, module and previously selected participant credentials. Credentials preserve that person in the displayed view without another identity picker. Without a plan, show the same local draft as the web application; never save a shared plan automatically.