Asking June
What June can read, what June can change, what June will never touch, and how the daily question allowance works.
June is the assistant built into CeremonySync. June can read everything in your venue and answer questions about it in plain language — and June can make a limited set of changes, but only ones you confirm first.
June has two homes. Ask June in the sidebar is the full page, where every morning June writes a brief: what needs you today, what went well, and what's worth asking about. And June is in the bottom-right corner of every screen — click June's mark to ask something without losing your place.
It's one conversation, not two. Start a thread in the corner, carry on browsing, open the full page — it's all still there.
Because June can see which screen you're on, "is this one ready?" works on a wedding page without naming the couple. Say "this" or "here" and June will take it from the page you're looking at.
The short version
- June can read every part of your venue, including the modules you subscribe to.
- June can change a specific, listed set of fields — and never without showing you a card to confirm first.
- June can never send anything to your couples, take a payment, or delete a record.
- June can be wrong. Check anything that matters before acting on it.
What June can read
Everything belonging to your venue. Leads and their full activity history, weddings, guests, seating, invoices, payments, proposals, contracts, questionnaires, the calendar, vendors, mood boards, playlists — and every table belonging to the modules you subscribe to (EventSync, FacilitySync, AssetSync, KitchenSync, StaffSync).
If a module isn't on your subscription, June has no access to it and won't pretend otherwise.
What June can't see, ever
A small set of things is closed off to June completely, regardless of your access level:
| Closed to June | Why |
|---|---|
| Access tokens and share links | Guest-portal links, availability links, push-notification tokens |
| Payment settings and card data | Stored payment configuration is never readable |
| Your CeremonySync subscription | Plan, billing and module-subscription records |
| Team member profiles | User accounts, invitations, who's on your team and what each role can open |
June also can't see any other venue. Ever. If you belong to more than one, June only sees the one you're currently working in.
Separately, individual columns are stripped out before June sees the row, even on tables June is allowed to read: anything holding a token, PIN, secret, password or API key, plus a few things that aren't credentials but are nobody's business — the signature image on a signed contract, the IP address and browser it was signed from, and a wedding's TV display code.
What June can change
Every change goes through a confirmation card. Nothing is saved until you click it. June will tell you what's about to be recorded and that it's waiting on you — if June ever says "done" without a card, June is wrong.
| Area | What June can update |
|---|---|
| Weddings | Guest count, guaranteed count, invited count, actual attendance, planner name, status, and the finalized flags for guest count, seating and timeline |
| Leads | Status, guest count, budget range, source, venue preference, follow-up notes, booking phase, and loss reason/details/competitor |
| Tasks | Title, description, status, due date, assignee |
| Timeline items | Title, description, start and end time, location |
| Notes | Content |
| Calendar entries | Title, description, type |
| Vendors | Service description, tier notes, phone, email, website |
| Wedding vendors | Notes, arrival notes, arrival time, status |
| Catering orders (KitchenSync) | Guest count, service style, special notes, vendor notes, staffing needs, prep list status |
| Maintenance tickets (FacilitySync) | Title, description, status, priority, category, location, scheduled date, resolution note |
| Assets (AssetSync) | Name, quantities, minimum quantity, condition, status, notes, storage location, location details |
June can also log an activity on a lead and schedule a follow-up.
A note on headcounts: "the headcount" is usually two different numbers — the wedding's own guest count and the catering order's, which is what the kitchen actually cooks to. There's also the guest list itself, which is a third number and isn't editable. If they disagree, June will tell you what each one is and ask which you mean rather than guessing.
What June will not change
Anything that emails your couple
The largest category. Certain fields are read by scheduled jobs that email clients automatically, so changing them would send a message on your behalf without you seeing it. June refuses these and points you at the right screen instead:
- Invoice due dates, status, and reminder settings (on, paused, or schedule)
- Contract status and expiry
- Proposal status
- RSVP and guaranteed-count deadlines
- Questionnaire status
- Menu selection deadlines and menu approval status
- Staff assignment status
June won't work around this by editing something adjacent, either.
Anything with a wide blast radius
June cannot create or delete records, send email or messages of any kind, take or refund a payment, issue or void an invoice, change anyone's permissions or access level, alter venue settings, or touch your subscription.
If you ask for something June can't do, June will say so plainly and — where an article covers it — tell you the steps to do it yourself, with the article attached.
That works for any "how do I…" question too, not just refusals. Ask "how do I create a lead?" and June reads the help center and answers with the actual steps rather than handing you a link. June won't answer a how-to from memory; if nothing in the help center covers it, June will say so instead of guessing at a button that may not exist.
Your questions each day
June comes with CeremonySync Complete. On Free and Booked, June isn't part of the plan — you'll see the upgrade page instead of the assistant.
Complete includes five questions a day, shared across your whole team. They refill every night at midnight, in your venue's own timezone.
On the card-free trial it's one a day. The trial is there to show you what June does, and Complete takes it to five. The morning brief is free either way.
- The morning brief is free. It never counts against your five.
- Only questions you ask count — one each, however much work June does to answer.
- Asking June to rewrite the brief does cost one.
The meter at the bottom of the message box shows what's left — "3 left", or "0 left today" when you're out. Click it for a breakdown of Today and Purchased.
Busy day? Top up
If five isn't enough on a particular day, the venue owner can buy more from that same panel — the button reads Get more questions:
| 25 questions | $5 | |
| 60 questions | $10 | best value of the three |
| 150 questions | $20 |
Two things worth knowing about top-ups:
- They don't expire. Unused ones sit there until you need them.
- They aren't capped at five a day. That's the point — if you've run out mid-afternoon and you're in the middle of something, a top-up puts you straight back to work rather than making you wait for tomorrow.
Your five included questions are always used first, so a top-up is only drawn on once the day's allowance is gone.
When you're out and haven't topped up, the brief keeps working — you just can't ask anything new until it refills overnight.
Saved conversations
June saves your threads automatically. Open History in the message box to reload one and carry on where you left off.
Conversations are private to you — other people at your venue can't see yours, even though you share the same pool of questions.
Two things worth knowing about old threads:
- Resuming one works at any age, but June is told the conversation is old and that anything in it may be out of date. June looks everything up again rather than repeating figures from last week.
- Confirmation cards aren't saved. If you left one unconfirmed and come back tomorrow, ask again and June will re-derive it against today's data.
Getting good answers
- Be specific about the record. "Is the Bennett wedding ready?" beats "is everything ready?"
- Ask follow-ups. June keeps the thread's context, so "what about the catering order?" works fine.
- Click the record chips. When June names a wedding, lead or invoice, it's a link straight to that record.
- Ideas, in the message box, lists things worth asking if you're not sure where to start.
The disclaimer that matters
June is a language model reading your data. June looks everything up before answering rather than working from memory, and the record cards June shows are built from real query results — but June can still misread a question, miss context a human would catch, or summarize something in a misleading way.
Treat June's answers as a well-informed starting point, not as verified fact. Before you act on something consequential — chasing a payment, confirming a headcount to your kitchen, telling a couple something — open the record and check.
Keep reading
Still stuck? A person reads every email.
If a guide and the app disagree, the app is right. Tell us and the guide gets fixed.