Organizer support Fast help when an event is on the line. Hobbybop support starts with an AI triage pass for common organizer problems, then moves frustrated or time-sensitive organizers straight to a human escalation path.
AI first response Start calm, then watch for urgency. The assistant can answer simple setup, import, RSVP, and billing questions while keeping human help one click away.
Escalate now Event is live and something broke RSVPs, check-in, publishing, payment, or attendee access problems during an active event.
Review with care Import or migration feels wrong Missing contacts, duplicate people, consent questions, skipped records, or source data confusion.
Route to ops Email delivery or domain setup Support addresses, DNS, sender reputation, invite delivery, bounces, and reply routing.
Human review Billing, plan, or checkout Subscription questions, failed checkout, invoices, refunds, paid-event readiness, and plan limits.
AI support embedded
Organizer triage Tell me what changed, which event is affected, and whether attendees are blocked right now.
My event is live tonight and guests cannot RSVP.
I would offer a short fix, ask one follow-up question, and keep the support inbox ready if the issue becomes time-sensitive.
Organizer message Escalation signals Organizer sounds blocked, angry, panicked, or repeatedly repeats the same failure. A live event, check-in line, payment, ticket, or public page is affected. The user mentions losing attendees, money, venue access, reputation, or trust. The answer needs account-specific records, refunds, DNS verification, or private data. Assistant playbook Confirm what is broken and whether an event is currently live. Capture organizer email, event URL, workspace name, deadline, and screenshots or error text. Give one stabilizing next step, then escalate to the support inbox with urgency and context. For calm how-to questions, keep the AI answer short and offer a human handoff without friction. Email operations
Support mail should resolve to one operator inbox first. Use PurelyMail for `support@hobbybop.com` plus a catch-all rule so any early Hobbybop address can reach the same destination while the product is still owner-operated.
Trust center
Dedicated policy and reporting routes keep sensitive requests out of public channels.