AI agent playbooks for ten event types — and what comes next for AI agents on AnyEventTool

Each playbook below has the same parts, taken from what AET's server returns to an assistant (aet_page_playbook) and from the readiness checklist in the event cabinet:

• Reader — who the page is really for.
• Sections, in order — what the assistant builds first to last.
• First screen — what the headline, sub and chips must carry.
• Tone, proof, button — the voice, what makes it credible, the one action.
• Registration fields — questions worth adding, using AET's field types (text, long text, number, email, phone, date, choice, checkbox, photo).
• Readiness steps — the type's own checklist items, on top of the common ones (description, date and place, poster, registration, contacts, publishing, sharing, first ten registrations, programme, check-in, feedback, gallery).
• What you set up in AET — things the assistant cannot do: paid tickets, seat maps, quizzes.
• A prompt — one message that gets a strong first draft.

Two rules apply to every type: facts only from you, and at most eight sections for a one-day event.

Reader: someone deciding whether this will teach them something worth their evening.

Sections: first screen, about, highlights (what you will make or learn), schedule, people, FAQ; optional steps, gallery, materials.

First screen: promise a skill the guest leaves with; chips for level, duration and group size — "Beginners", "3 hours", "8 seats".

Button: "Register" or "Take a seat".

Registration fields: experience level (choice), what you hope to learn (long text), dietary needs (choice) if food is served.

Readiness steps: "What learners will be able to do" (a description of 400 characters or more), "Materials after the event", and optionally "A quiz to reinforce learning" on the day.

You set up in AET: paid tickets if it is paid; a live quiz if you want one (the assistant cannot create quizzes).

Prompt: "On AnyEventTool, make a page for my workshop: beginners' pottery, 15 November, 11:00–14:00, my studio at Franka St 12, Lviv, 8 seats, 900 UAH, materials included, you leave with two fired pieces. Calm, handmade mood. Add a FAQ about what to wear and whether I can bring a friend. Show me before publishing."

Reader: a buyer weighing time and money — often on someone else's budget.

Sections: first screen, numbers, people (speakers), schedule, partners, FAQ; optional highlights, testimonials, press, gallery.

First screen: theme, date and city; chips for tracks, number of speakers, format.

Proof: speakers with roles and companies, partner logos, last year's numbers — only if real.

Registration fields: company and position (built-in), track preference (choice), ticket type if tiers exist, invoice details (long text) for company payments.

Readiness steps: "Speakers with photos", "Partners and media", "Materials after the event".

You set up in AET: paid tiers, applications with approval if seats are limited, sub-events for parallel tracks.

Prompt: "Build an AnyEventTool page for our conference 'Data in Retail 2026', Kyiv, 4 December, two tracks, 14 speakers (list attached with roles), partners X, Y, Z. Last year: 420 attendees. Lead with numbers and speakers; keep the about section short."

Agent move: after the page, offer a schedule dashboard: registrations by day and by source, to see which partner brings people.

Reader: a peer deciding if the room will be worth it.

Sections: first screen, about, people, schedule, contacts; optional FAQ, gallery.

First screen: what we will talk about and who comes; chips for format, language, free or paid.

Tone: warm, short, informal.

Registration fields: role or company (text), "Would you like to give a lightning talk?" (checkbox).

Readiness steps: "Speakers with photos".

You set up in AET: an event calendar if the meetup repeats — subscribers get new dates; AET has no recurring-event series yet, so each meetup is its own event.

Prompt: "Make a page for our monthly Product Managers Meetup in Lviv, 20 November, 19:00, at Coworking Z, free, 40 seats. Two talks: (titles, speakers). Informal tone. Contacts: our Telegram channel."

Agent move: copy last month's structure by reading that event and creating the new one with updated speakers and date — faster than starting fresh.

Reader: a guest who needs to know when, where, what to wear and what to bring.

Sections: first screen, about, schedule, gallery, contacts; optional steps, FAQ.

First screen: occasion and date; sub = what guests should know — dress code, gifts, children.

Tone: warm and personal, second person. Button: "RSVP" or "I'll come".

Registration fields: number of guests (number), dietary needs (choice), "Will you need a transfer?" (checkbox), a wish for the hosts (long text).

Readiness steps: "Guest list and groups", "First RSVPs", "Dress code and details", "Menu and diets", "Photographer and hashtag", optional "Table seating" and "Wishlist".

You set up in AET: a seat map for table seating; hiding the place until the ticket if the address is private.

Prompt: "Create an RSVP page for Anna and Oleh's wedding, 6 June, ceremony 15:00, dinner from 17:00, Villa X near Kyiv. Dress code: summer formal. No gifts please, a wishlist link instead. Ask guests for number of people and dietary needs."

Reader: someone planning a day out, often with friends — what is on, where, how much.

Sections: first screen, highlights (stages, zones), schedule, people (artists), gallery, partners, FAQ; optional numbers, ticker.

First screen: name, dates, place; chips for stages, days, headliners.

Button: "Get a ticket".

Registration fields: ticket day (choice), age confirmation (checkbox), how did you hear about us (choice) — useful for sources beyond tags.

Readiness steps: "Zone map", optional "Merch", "Weather plan".

You set up in AET: paid tiers per day, a shop for merch, sub-events for stages or days.

Prompt: "Build a festival page: 'River Sound', 18–19 July, Kaniv, 3 stages, 24 artists (list), camping available. Lead with highlights per stage, then schedule by day. Use a ticker for headliners."

Agent move: a ticker block for headliners and a numbers block only with real figures (stages, artists, days).

Reader: a participant checking distance, category, start time and rules.

Sections: first screen, about, steps (how to take part), schedule, FAQ, contacts; optional numbers, gallery.

First screen: distance or format and date; chips for categories, limit, start time.

Button: "Register".

Registration fields: category or distance (choice), date of birth (date), T-shirt size (choice), emergency contact (phone), a photo of a medical certificate (photo) if required, consent to rules (checkbox).

Readiness steps: "Categories and distances", "Waiver and rules", "Medical certificate", "Bib numbers", "Timing or judging", "Volunteers", "Results and podium".

You set up in AET: paid entry, check-in at the start with QR tickets.

Prompt: "Make a page for our 10 km trail run, 29 March, start 09:00, Holosiiv Park, limit 300, categories by age, entry 600 UAH. Registration should ask distance, date of birth, T-shirt size and an emergency phone, and require agreeing to the rules."

Reader: a parent, deciding with safety in mind.

Sections: first screen, about, schedule, people, FAQ, contacts; optional gallery.

First screen: what kids do and what parents get; chips for age range, duration, group size.

Tone: calm, reassuring, concrete ages and safety information.

Registration fields: child's age (number), allergies (long text), parent's phone (phone), "Will a parent stay?" (checkbox), photo consent (checkbox).

Readiness steps: "Age and supervision", "Safety", "Message for parents".

You set up in AET: applications with approval if groups are small; hiding the address until the ticket for private venues.

Prompt: "Create a page for a robotics class for kids aged 8–11, Saturdays in November, 10:00–11:30, 10 children per group, parents can wait in the lounge. Calm tone for parents; FAQ about safety, allergies and what to bring."

Agent caution: the assistant never sees children's or parents' data; registration answers stay in the organizer's cabinet.

Reader: a supporter asking what their money will change and whether to trust you.

Sections: first screen, about, numbers, steps (how to help), people, FAQ; optional partners, gallery.

First screen: what the money changes; chips for goal, date, format.

Proof: only verified numbers; name the beneficiary organisation.

Registration fields: contribution option (choice), "Show my name among supporters?" (checkbox).

Readiness steps: "Fundraising goal", "Report to donors" a week after.

You set up in AET: paid tickets for a ticketed charity dinner; AET has no donation or pay-what-you-want tickets.

Prompt: "Build a page for our charity concert for the 'Warm Hands' foundation, 12 December, Lviv Philharmonic, goal 200,000 UAH for 40 heaters. Use a numbers block only with the goal and number of heaters. Steps: buy a ticket, share, come."

Agent move: after the event, a dashboard with revenue by currency and a text widget drafting the donor report from the numbers.

Reader: someone drawn by the work, not by the logistics.

Sections: first screen, about, people (artist, curator), gallery, schedule, contacts; optional testimonials, FAQ.

First screen: title and artist or curator; chips for opening, dates, venue.

Tone: spare and visual; let images carry it.

Registration fields: opening night or general visit (choice), group size (number).

Readiness steps: "Media announcement".

You set up in AET: the gallery images — or let a connected assistant add them by URL; a poster from the artwork.

Prompt: "Make a spare, image-led page for the exhibition 'Salt and Iron' by Iryna K., curated by M., Lviv, opening 14 November 19:00, open until 14 December. About in under 100 words. Gallery from these image links."

Agent move: choose a layout with a strong gallery, keep text short, and use a text-and-image block for the artist's statement.

Reader: a fan who wants the artist, date, venue and a ticket — in that order.

Sections: first screen, people (artists), schedule, FAQ, contacts; optional gallery, partners, ticker.

First screen: artist, date and venue; chips for doors, start, age limit.

Button: "Get a ticket".

Registration fields: usually none beyond the ticket; for small venues, "Seat preference" (choice).

Readiness steps: "Rider and equipment", "Soundcheck" on the day.

You set up in AET: paid tiers, a seat map for seated halls, check-in with QR tickets at the door.

Prompt: "Build a concert page: 'Quartet Nova — Winter Strings', 20 December, doors 18:30, start 19:00, Lviv Organ Hall, 12+. Skip a long about; lead with the artists and programme. FAQ: parking, cloakroom, age limit."

Agent move: a video block with a recording if the artist has one on YouTube or Vimeo.

The general playbook is a good default: first screen, about, schedule, people, FAQ; optional steps, highlights, gallery, partners, contacts; plain, concrete, friendly tone; one button. Tell the assistant the closest type anyway — a hackathon is closer to a conference, a book club to a meetup, a market to a festival — because the readiness checklist follows the type.

Part 1 proposed three numbers that would show whether assistant-built event pages change how organizers work: the share of new events that start in a chat, the time from first message to a live page, and the money organizers keep. One week after launch it is too early to report them. The first week went to testing and to the reviews by the Claude and ChatGPT directories, and the directories have not listed AET yet — and a listing is the first door for most users.

One of the three is already measured on the server side: building a guest draft took 4.3 seconds in production on 19 October 2026. The other two need outside organizers using AET through their assistants. AET will publish them, with the date, once it is listed and there is real use to measure.

From AET's integration plan as of 25 October 2026. These are plans, not promises, and none has a date.

Guest drafts, completed: images by URL in drafts, moderation of images, safety checks of links against known malicious sites with an interstitial page, a queue for complaints about drafts, and a brief link that lets a person start a draft from a short web form.

Accounts and directories: listings in Claude's and ChatGPT's directories once reviews finish (submitted 19 and 20 October 2026), publication in the official MCP registry, instructions for Perplexity and Gemini.

Later: working with co-organizers, guests and mailings through the assistant; deleting events; switching on sales; handling applications, orders and check-in — each behind the organizer's explicit confirmation; widgets; asking the user for missing details through the client; choosing events on the consent screen.

Not planned for assistants: reading guests' personal data. Statistics stay aggregate by design (part 8).

Known gaps today, in one line each: no event end time, no image upload from chat, no recurring events, no webhooks, no cross-event analytics, paid tickets and seat maps set up by the organizer (part 9 lists the developer-facing ones).

1. The event manager who never sleeps — four platforms let assistants act; AET alone builds pages for people with no account, at 0% platform fee.
2. Connecting your assistant — one URL, https://aet.events/api/mcp; sign in only when needed; three access levels.
3. Guest drafts in depth — 24 hours, noindex, registration closed until claimed, two secrets.
4. Writing a better page — playbooks, facts only from the user, 3–9-word headline, 4–8 FAQ.
5. Design by agent — 58 layouts × 58 styles, readable colours by default, images by URL.
6. Running a live event — 17 sections item by item, versions, six confirmations, undo.
7. Trust by design — server-side guardrails, untrusted data, no guest PII.
8. Numbers without names — 22 metrics and live dashboards without personal data.
9. For developers — transport, OAuth, 26 tools, errors, idempotency.
10. Playbooks for ten event types and what comes next — this article.

Whatever the type, read the preview on a phone and check these ten things before you tell the assistant to publish:

1. The headline promises something a guest can check — a skill, an experience, a result — in 3–9 words.
2. Date, time and place are exactly right, including the time zone your guests live in and the entrance if the venue is large.
3. The price and what it includes are on the first screen or in the first FAQ answer.
4. Every name is real and spelled the way the person spells it; roles come from you, not from the assistant.
5. No invented numbers. If a numbers block is there, you can say where each figure comes from.
6. The FAQ answers what people really ask you: parking, refunds, age, what to bring, language.
7. Registration asks only what you will use. Every extra field costs sign-ups.
8. One button, one action, with a label in the event's language.
9. The type's readiness steps are planned: ask "What is still missing?" and decide what you will do this week.
10. You know what you set up yourself in AET — paid tickets, a seat map, a quiz — and when.

When all ten hold, ask the assistant to publish; AET will show you a confirmation before the page goes live.

1. Map the event to one of the ten kinds; if unsure, choose the closest and say so, or use the general playbook.
2. Call aet_page_playbook(kind) and follow its section order; do not add sections the user gave no facts for.
3. Suggest the type's registration fields from the lists above, but add only what the user agrees to.
4. After creating, read readiness and offer the type's next two steps, not all of them.
5. Do not promise what the organizer must set up: paid tickets, seat maps, quizzes, shops, communities, calendars.
6. For repeating events, read the previous event and reuse its structure with new facts.
7. Keep children's, guests' and donors' data out of the conversation; it is not available to you anyway.

• Recurring series with one registration for all dates — AET has no series yet; each date is its own event, linked through a calendar.
• Donation-based fundraising with pay-what-you-want — AET has no donation tickets.
• Large festivals with box offices, promo codes and waitlists — AET has none of those.
• Sports with chip timing and live results feeds — AET tracks the checklist step, not the timing system.
• Events where the assistant must message guests — not available through the assistant today.
• A marketplace audience — AET has no event marketplace; you bring your own audience.

• AnyEventTool code on 25 October 2026: lib/aiops/playbook.ts (ten playbooks), lib/eventCabinet/index.ts (readiness checklist by type), lib/aiops/sections.ts (registration field types), interface texts from AET's English and Ukrainian dictionaries.
• Roadmap: AET's AI integration specification (stages E1b, E3 and v3), not a public commitment.
• Directory submissions: AET's records — Claude on 19 October 2026, ChatGPT on 20 October 2026.

If something here no longer matches what AET does, write to support@anyeventtool.com — we correct with the date.

This is part 10 of 10, the last one.

1. The event manager who never sleeps — the landscape, three zeros, guardrails (19 October) · 2. Connecting your assistant to AET — Claude, ChatGPT, Claude Code, Cursor, Gemini (20 October) · 3. Guest drafts in depth (22 October) · 4. Writing a page the agent is proud of (22 October) · 5. Design by agent (23 October) · 6. Running a live event by key (24 October) · 7. Trust by design (25 October) · 8. Numbers without names (25 October) · 9. For developers: building on the AET MCP server (25 October) · 10. Playbooks for ten event types and the road ahead — this article (25 October).