First Organizer Path
- Workspace setup: sign in, name the organizer workspace, confirm timezone, billing state, team access, and privacy defaults.
- First event: create a draft, set date, location or online details, visibility, capacity, registration rules, ticket mode, groups, sponsors, and publish readiness.
- First RSVP: open the public event page, collect a free RSVP or send paid guests to the configured checkout path, then watch waitlist, cancellation, and check-in status.
- Follow-up: review AI-assisted thank-you, no-show, sponsor recap, and reactivation drafts before sending to contactable guests.
- Analytics: use dashboard funnel, source attribution, attendance, revenue, email, sponsor, group, and marketplace signals to choose the next action.
Account And Workspace
- Hobbybop keeps organizer-owned event operations connected to the workspace, guest list, CRM, billing, and email records that power each event.
- Use /signin to create or access the organizer account tied to your workspace.
- Workspace records own drafts, published events, guest lists, CRM records, billing state, API keys, imports, and email operations.
- Protected organizer routes should ask unauthenticated users to sign in instead of exposing private event or people data.
Events, RSVPs, Paid Events, And Billing
- Save drafts before publishing; published or full public events can show a public event page when visibility allows it.
- Room Operations handles guest lookup, walk-up adds, check-in, undo, status changes, notes, waitlist, and attendance export.
- Paid events currently use a validated checkout URL or configured payment provider state; public free RSVP creation is blocked when the event is marked paid.
- Billing help covers plan selection, trial activation, Polar checkout, billing portal access, failed checkout, receipts, refunds, transfers, payout status, and plan limits.
CRM, Email, Imports, And Privacy Controls
- RSVP, waitlist, cancellation, and check-in activity can update organizer-owned people records and event history.
- No-contact and unsubscribe states suppress outbound organizer-to-attendee email.
- CSV, Eventbrite, Meetup, Luma, Mailchimp, and provider migration previews should be reviewed before committing records, especially consent, source confidence, undo, and duplicate decisions.
- Privacy controls include unsubscribe suppression, no-contact states, attendee self-service, export, correction, deletion, and data-request escalation boundaries.
Groups, Sponsors, And AI Features
- Groups can organize memberships, join requests, discussions, albums, series calendars, moderation, member privacy, and notification loops.
- Sponsor workflows support partner CRM records, placements, deliverables, outreach, proposal drafts, package value, and performance reporting.
- AI features draft event descriptions, relationship reports, organizer copilot answers, lifecycle playbooks, audience follow-ups, and approved actions, but organizers remain responsible for review and approval.
- High-risk AI actions such as external sends, publishing, billing changes, or provider writes require explicit confirmation before execution.
Demo And Training Data
- Use /demo and /api/demo/readiness for customer walkthroughs, onboarding, screenshots, sales calls, support practice, and documentation review.
- Demo fixtures are read-only, tagged as fixture data, use example.com addresses, and do not write accounts, events, RSVPs, orders, groups, sponsor records, or CRM contacts into production customer tables.
Escalation
If a published event, payment, check-in line, attendee access, public page, import, sponsor workflow, group moderation queue, AI action, billing portal, or analytics report is blocked, email support@hobbybop.com with the event URL and deadline. For unsafe content or abusive behavior, use /abuse. For export, deletion, correction, or suppression requests, use /data-requests.