iAmBruno.
Your illustrated manual · 25 practical chapters

Events Manager

Tell Bruno the idea. Review the draft. Publish when you are ready.

Bruno can prepare an event from a conversation and your references. You choose existing people and a place, check the proposed schedule and admission, then decide when to publish. This guide also shows optional manual edits, the public free-ticket experience and the owner’s attendee desk.

Download the PDF ↓Open Events Manager ↗

Before you start

  • Use the account with Events Manager access and select the correct available website. If no connected website is listed, use Connect WordPress to set one up first. If your site is already available, you do not have to reinstall plugins before every event.
  • Bring the factual date, timezone, location, admission and useful references. Bruno prepares the proposal; you do not need to write a complete event page or flyer yourself.
  • Saving a draft and publishing an event are different actions. Publishing can create a public page and promotional artwork. The walkthrough uses fictional content and mocks every write, registration and email.
  • Free admission means the attendee ticket costs zero. It does not mean the Events Manager service or every generation action is free. Review current service access and billing separately.

All event, person, venue, attendee and email details are fictional. Dashboard screenshots use the current Bruno templates and original JavaScript. The public page uses the actual WordPress event renderer, shell and assets with local WordPress data stubs; ticket output uses the current ticket template. Artwork is illustrative sample content. Every save, publication, RSVP, invitation and access change is mocked: no customer records, public sites, paid generation or real emails were changed.

01

Open the correct event workspace

Open the correct event workspace — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The selected website.
  2. 2Events, reusable People and reusable Places.
  3. 3Start a conversation with Bruno.
  4. 4Your saved event rows.
  1. Choose Events Manager and check Your website. Saved events are associated with that selected site.
  2. Events, People and Places are separate tabs. Existing event rows stay saved while you create another one.
  3. Use the conversation action to tell Bruno your idea. Create event is the optional manual form if you prefer direct field entry.
What happens nextYou can start a new idea or open an existing saved event.
02

Reuse a person you already saved

Reuse a person you already saved — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The People tab.
  2. 2Saved people you can reuse.
  3. 3Add a missing person.
  1. Open People to see your reusable hosts, presenters and other participants.
  2. Keep each person’s correct name, role, bio and reference photograph where you have one. You can edit the saved profile rather than creating a duplicate.
  3. Add person is available for someone missing. The example uses fictional host Maya Chen and a neutral avatar, not an invented photograph of her.
What happens nextSaved people are available to select during the event conversation or manual review.
03

Reuse a saved venue

Reuse a saved venue — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The Places tab.
  2. 2The reusable venue library.
  3. 3Add a new place if needed.
  1. Open Places to find your saved venues. Check the address, city and other location details.
  2. A saved place can be reused for another event. Add place is for a genuinely new venue.
  3. Return to Events when you are ready to bring the idea together.
What happens nextThe intended venue is ready to use in an event.
04

Tell Bruno what you have in mind

Tell Bruno what you have in mind — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1Your factual brief in ordinary words.
  2. 2The selected reference attachment.
  3. 3Send this request to Bruno.
  1. Open the event conversation and describe the purpose, audience, date, timezone, venue and admission. Plain notes are enough; Bruno prepares the proposed event.
  2. Attach useful images or documents if you have them. The interface also supports voice notes, but recording is optional. This example uses typed notes and a coffee reference picture.
  3. Check the facts, then choose Send. With text or attachments ready, the button sends the message instead of starting a microphone recording.
What happens nextBruno asks useful follow-up questions or proposes the event details.
05

Choose the right existing person

Choose the right existing person — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The developing event summary.
  2. 2The actual saved-person choice.
  1. Bruno offers Maya from the existing people library. Read the name and role before selecting her.
  2. Choose the saved person when it is the right one. You can explain a different person or place in the conversation when needed.
  3. The developing event summary helps you check which idea this conversation is shaping.
What happens nextThe selected person becomes part of the proposal without requiring a duplicate profile.
06

Read Bruno’s proposal before saving

Read Bruno’s proposal before saving — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The actual proposal and conversation.
  2. 2Confirm these details as a saved event draft.
  1. Bruno proposes the title, date, time, timezone, place, host, sessions and ticket details. Read them as a complete event, not just a title.
  2. If something is wrong, reply with the correction before using the confirmation. You do not have to rewrite the whole proposal.
  3. Choose Create my event draft only when the proposed details are right. This saves a draft; it does not publish the page.
What happens nextThe event is saved with its intended people, place, schedule and admission.
07

Open the saved draft

Open the saved draft — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The saved-draft confirmation in the conversation.
  2. 2Return to the saved event.
  1. Wait for Bruno’s saved confirmation. A running or failed turn is not proof that the event was saved.
  2. Choose See my event to return to the event list. The conversation and its work stay together.
  3. If you leave during a running turn, return to the saved conversation rather than immediately repeating the same request.
What happens nextThe new event appears in the Events tab with draft status.
08

Find the event without publishing it

Find the event without publishing it — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The new saved draft row.
  1. Find Friday Coffee in the saved rows. It is a draft alongside the earlier saved idea.
  2. Expand the event row to reach its actions and event desk. Edit event opens the optional manual editor.
  3. Publish event is a separate action. Do not choose it simply to inspect or save the draft.
What happens nextYou can review or optionally refine the saved event before publication.
09

Optional: review the generated fields

Optional: review the generated fields — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The saved title.
  2. 2The saved proposed description.
  3. 3Continue through the review sections.
  1. Choose Edit event if you want to inspect or directly adjust the saved draft. Bruno has already supplied the title and description.
  2. The five sections are About, Date & time, People, Place and Schedule & tickets. Follow Next or the section navigation.
  3. Keep the proposed words if they are right. Direct manual editing is an option, not a required writing task after the conversation.
What happens nextThe next section shows the actual date, time and timezone.
10

Optional: correct a time

Optional: correct a time — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The event start.
  2. 2The optionally corrected end.
  3. 3The timezone used for the event.
  4. 4Continue to people.
  1. Check Starts, Ends and Timezone together. A correct clock time in the wrong timezone is still wrong.
  2. Our optional edit changes the event end from 11 AM to 10:30 AM. Use the timing that fits your actual event and sessions.
  3. Continue. Your edit is not stored until you save the draft at the end of the review.
What happens nextThe revised timing is included in the draft being reviewed.
11

Choose or add people inside the review

Choose or add people inside the review — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1Search saved people.
  2. 2Maya’s existing selected profile.
  3. 3Use these selections in the event.
  1. In People, choose Choose or add people. Search the reusable library and select the intended participants.
  2. Maya is already selected in this example. Add new person is available if someone is missing; you can save and select them without abandoning the event.
  3. Choose Use selected people when the list is correct. Removing someone from this event is different from deleting their saved profile.
What happens nextThe People section reflects the selected saved participants.
12

Check the venue

Check the venue — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The selected venue and its choose/add control.
  2. 2Continue to schedule and tickets.
  1. In Place, inspect the selected venue’s name and address.
  2. Use Choose or add a place to select another saved location or add a missing one. No venue for now is available when a physical place is not needed.
  3. Continue when the location matches the intended event.
What happens nextThe event retains the selected place for its page and ticket details.
13

Review the proposed program

Review the proposed program — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The proposed sessions; scroll to review each one.
  2. 2Optionally add another session.
  1. Read each saved session, including its start, end, people and place. Scroll inside the form to inspect the whole list.
  2. The example includes coffee and conversation, then a studio tour. Add session is optional when you need another part of the program.
  3. Keep the overall event times and session times consistent before saving.
What happens nextThe program is checked before reviewing admission.
14

Set the admission and save the draft

Set the admission and save the draft — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The named ticket, price, capacity and coverage.
  2. 2Save the checked event draft.
  1. Scroll to Tickets. Our explicit named Friday Coffee admission ticket has price 0, so it is free, with a capacity of 30.
  2. Check whether admission covers the whole event or a session. Capacity applies to that ticket type; 0 means no capacity limit.
  3. Choose Save event draft. This stores the checked event and optional edits. Publishing is still a separate decision.
What happens nextThe event list returns with the saved details, ready for deliberate publication.
15

Publish the checked event

Publish the checked event — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The published event row and its actions.
  1. Choose Publish event to create its public page and save the page QR in your QR Codes library. Bruno creates a flyer automatically if you did not supply one; an uploaded flyer is kept.
  2. Wait for the live confirmation rather than treating a queued job as finished. Use View event when it is available.
  3. If the event is already public, Update page applies later saved changes. Check the correct event and site before updating.
What happens nextThe public event page can be opened for a final check.
16

Check what guests will see

Check what guests will see — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The public event title.
  2. 2Open free-ticket registration.
  3. 3The flyer can be enlarged.
  1. Choose View event. This is the current public event renderer with the fictional Friday Coffee details and illustrative flyer.
  2. Check the title, venue, date, schedule, speakers and admission on the full page. Tap the flyer for a larger view where offered.
  3. Get free tickets opens the public registration flow. A guest does not need a Bruno dashboard login to use that free RSVP form.
What happens nextThe guest can inspect the event and request the offered admission.
17

Guest view: choose the admission

Guest view: choose the admission — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The admission type.
  2. 2The number of primary attendees.
  3. 3Continue to named attendee details.
  1. Choose the offered free admission. Check the ticket name and what it covers.
  2. Select how many primary tickets you need. The next step allows one +1 guest for each person.
  3. Choose Next: your people. The screenshot is the actual public form; no real registration is being made in this manual.
What happens nextThe form asks for the name and email of each person.
18

Guest view: name every attendee

Guest view: name every attendee — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The primary attendee’s name.
  2. 2Their email address.
  3. 3The separately named +1 guest.
  4. 4Confirm the checked free-ticket request.
  1. Fill the attendee’s full name and email. Each person receives their own ticket.
  2. If bringing a +1, select Bring a +1 and provide that guest’s own name and email. Our fictional example uses Nora and Eli Lane.
  3. Read the details, then Confirm free tickets only when you intend to register. For this walkthrough the confirmation request is fully mocked and sends no email.
What happens nextA successful registration lists the separate attendee ticket references.
19

Guest view: recognize the confirmation

Guest view: recognize the confirmation — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
  1. 1The registration result and individual references.
  1. You’re on the list confirms the successful registration response. Each listed person has their own reference.
  2. In normal use, each attendee’s ticket is sent to the supplied email. If there is an error instead, keep the page open and follow the displayed retry instruction.
  3. The pictured confirmation is fictional; it does not prove real email delivery or reserve a place at a real event.
What happens nextThe attendee can keep their own ticket when it arrives.
20

Guest view: keep the individual ticket

Guest view: keep the individual ticket — actual Bruno interface with fictional example data
Atelier Demo · Example account and simulated responses. Open the picture to zoom.
    1. The ticket shows the event, named attendee, admission, timing, timezone and venue. The example continues with Nora and her separately registered +1, Eli.
    2. This QR identifies one attendee’s registration. It is different from a public flyer QR that opens the event page. Keep a real attendee ticket private.
    3. Use Print or save as PDF to save a browser copy, or keep the ticket on your phone to show at the event.
    What happens nextEach attendee has their own admission pass and QR code.
    21

    Manage the event from its expanded row

    Manage the event from its expanded row — actual Bruno interface with fictional example data
    Atelier Demo · Example account and simulated responses. Open the picture to zoom.
    1. 1The event’s actual KPI row.
    2. 2Attendees and Invitations are separate lists.
    3. 3The selected roster and statuses.
    1. Return to Events Manager and expand the intended event. The event desk shows confirmed attendees, awaiting replies, invitations and revoked access.
    2. Attendees lists completed registrations and +1 guests. Invitations is the separate list of personal invitations and their delivery/reply states.
    3. Use Refresh to check the latest state and search for a specific person. Do not infer attendance from an invitation that is still awaiting a reply.
    What happens nextYou can identify the right person and the current state before taking an action.
    22

    Invite someone personally

    Invite someone personally — actual Bruno interface with fictional example data
    Atelier Demo · Example account and simulated responses. Open the picture to zoom.
    1. 1The invitee’s name.
    2. 2Their email address.
    3. 3The remaining shared invitation allowance.
    4. 4Queue this personal invitation.
    1. The event must be published, have eligible free admission and have invitation allowance remaining before this form can send.
    2. Fill the intended person’s name and email. If there are multiple eligible tickets, choose the admission. Check the address before Send invitation.
    3. The allowance is 25 invitations across your owner account’s events in a rolling 24 hours. It is not 25 per event and does not reset at midnight; capacity returns as individual invitations become 24 hours old.
    What happens nextThe invitation is queued and appears in Invitations with delivery status.
    23

    Check delivery and the reply separately

    Check delivery and the reply separately — actual Bruno interface with fictional example data
    Atelier Demo · Example account and simulated responses. Open the picture to zoom.
    1. 1Search the selected roster.
    2. 2The matching invitation and delivery state.
    3. 3The queued confirmation.
    1. After Send invitation, look for Invitation queued and the list entry. Queued is not the same as Email sent or Accepted.
    2. Use Find someone to search by name or email. The example searches for Ari.
    3. An accepted invitation becomes a confirmed attendee with linked admission. In this walkthrough, queuing and every status are simulated; no real email was sent.
    What happens nextYou can tell whether the invitation is pending, delivered, accepted or needs attention.
    24

    Revoke access when intended

    Revoke access when intended — actual Bruno interface with fictional example data
    Atelier Demo · Example account and simulated responses. Open the picture to zoom.
    1. 1The revoked row and its Reinstate action.
    1. Choose Revoke for the correct person and read the confirmation before accepting it.
    2. Revoking disables access, including any linked ticket. It is not a reminder email and does not delete the event.
    3. The row changes to Revoked and offers Reinstate if the action needs to be reversed.
    What happens nextThe person’s linked access is disabled until reinstated.
    25

    Reinstate without another email

    Reinstate without another email — actual Bruno interface with fictional example data
    Atelier Demo · Example account and simulated responses. Open the picture to zoom.
    1. 1The restored roster state.
    2. 2Confirmation that no email was resent.
    1. Choose Reinstate on the intended revoked row. Check the resulting status.
    2. Access reinstated. No email was resent means the existing linked access was restored; it did not send another invitation.
    3. Use the Attendees/Invitations tabs and search again to confirm the person you intended was changed.
    What happens nextAccess is restored while the original event and invitation history remain in place.
    Keep this guide handy

    Come back whenever you need it.

    Use Quick guide for a short reminder of the main controls. Keep this full manual for the complete task and its different choices.

    In your dashboard, choose Quick guide → Show me around to replay the short tour. Use Read the guide or Download PDF for these complete instructions.

    Need help? Email help@iambruno.com with the service name and what happened. Do not send passwords or connection keys.