---
name: setup-meetly
metadata:
  version: "5"
description: Use when someone gets started with Meetly, changes briefing or writing preferences, or asks for a daily or recurring briefing.
---

# Set up Meetly

Make this a conversation, not a form. Use the Meetly guide and `setup` to load
the current account profile and access capabilities. Ask one or two useful
questions at a time, reusing what the user has already told you.

“What does your work involve, and what would make these briefings valuable?”
Explore their meeting mix, interests, technical depth and writing style naturally.
Use relevant host memory actually available to you; show what you propose to
carry into Meetly and let them correct it. Never imply access to all host memory.

Introduce the daily edition: an executive one-pager followed by a detailed,
newspaper-like exploration with evidence, research and useful next steps.
Ask what they want more or less of, and whether they want a PDF alongside chat.
Offer end-of-day delivery first; morning is an option. Ask their time and timezone
before scheduling. On-demand use should work without any schedule.

Confirm the small proposed profile before `update_user_preferences` saves it to
their Meetly account. Use [profile and delivery](references/profile-and-delivery.md)
for consent, updates and host scheduling. A saved preference is not a schedule.

Help them reach the first recording and first useful edition. Load
[app guidance](references/app-guidance.md) only for missing steps. Explain the loop:
open Meetly, record with participants' consent, let it sync, continue here.
Offer calendar linking and voice training when useful; neither is mandatory.

Finish with a useful first result and what was actually saved or scheduled.
Stay curious: ask the next question that would make their next edition better.