EventBot · AI event support layer

The event help desk in every attendee’s pocket.

EventBot gives attendees and vendors a WhatsApp-first way to find published schedules, venue information, registration paths, and the right staff contact. Routine questions get a useful answer; exceptions arrive as a clean human handoff.

Book an EventBot demo See example exchanges

EventBot WhatsApp CTAPublished schedule answersRegistration routingStaff handoff

Design Week EventBotPublished event support

Saturday · 10:18

Where is the Future Cities keynote, and is there accessible seating?10:18

It starts at 11:30 on Stage A in the Waterfront Hall. The published venue guide lists step-free access. Would you like me to ask guest services to reserve accessible seating?10:18

Yes. I’m Lerato and my registration is DW-1842.10:19

I’ve prepared the request with your registration, session, and access need. Guest services will confirm the arrangement with you.10:19

Guest services handoff ready

Illustrative exchange. Answers, registration states, outbound messages, and staff actions follow the event’s published data, permissions, and configured channels.

Answers the repeat questions

Schedules, venues, access, registration, and vendor details stay easy to find.

Guides the next step

People get the right event page, form, session, or contact instead of another search.

Recognises the event context

The handoff can carry the person, event, role, registration, and request together.

Escalates what matters

Safety, accessibility, refunds, complaints, and exceptions move to authorised staff.

Three support moments

Fast answers. Useful routing. No dead ends.

EventBot is the conversation layer around the event hub. It helps attendees and vendors act on approved information, then gives staff the context needed for anything outside the normal path.

Attendee scheduleIllustrative exchange

Design Week EventBotSchedule and venue help

Friday · 08:41

I only have Friday afternoon. What talks are about sustainable materials?08:41

The published programme has Circular Materials at 14:00 and Building with Bio-Composites at 16:15. Both are in Workshop Hall 2.08:41

Open the registration for both.08:42

Here is the event registration path with those sessions selected. Availability and your final registration status will be shown there.08:42

Two sessions selected · registration path ready

EventBot searches the published programme and routes the attendee into the real registration flow.

Vendor logisticsIllustrative support view

Vendor arrival assistant

Answers assembled from the published vendor pack and the vendor’s event record.

Load-in windowFriday · 07:00–09:00

Published

EntranceService Gate B · Dock Road

Published

StandV-18 · Food court

Vendor record

Site contactOperations desk · on arrival

Published

Needs staff“Can I get a 32A power point?”

Site-specific service changes are routed with stand, arrival, and vendor contact attached.

Known logistics get a direct answer. New infrastructure requests become an operations handoff.

Human escalationIllustrative team view

EventBot support queue

Context-rich briefs ordered by urgency and responsible team.

Guest servicesHigh

Accessible seating · keynote

Lerato · registration DW-1842 · Stage A · 11:30

72 min to sessionAssign →

Site operationsReview

Vendor power request · V-18

Coastal Coffee · 32A supply · Friday 07:30 arrival

Vendor context attachedOpen →

Registration deskNormal

Name correction · attendee pass

Reference and requested correction captured

Identity check neededReview →

Your team opens the brief and the next action, with the conversation available for reference.

The support flow

Ask. Find. Guide. Contextualise. Hand off.

Ask

Attendees and vendors use the familiar event WhatsApp entry point from the public hub or QR code.

Find

EventBot checks the published programme, venue information, FAQs, registration paths, and vendor guidance.

Guide

The answer includes a useful next step: a session, page, form, desk, direction, or contact.

Contextualise

With permission, the request can carry the event, role, registration, session, vendor, and urgency.

Hand off

Staff take over for exceptions, approvals, disputes, safety issues, and anything missing from the published source.

Context without guesswork

The right answer for this event and this person.

A generic chatbot sees a sentence. EventBot can use the active event, published content, and permissioned attendee or vendor context to make the next step specific and useful.

Event-aware

The correct programme, venue, policy, dates, and event links stay attached.

Role-aware

Attendees, vendors, speakers, sponsors, and staff can be guided to different approved paths.

Consent-aware

Profile and POPIA context is used only for the event purpose, within the configured workspace and permissions.

Illustrative attendee context

Lerato MolefeAttendee · Design Week Cape Town

Registered

ReferenceDW-1842

SessionsFuture Cities · Circular Materials

Open requestAccessible seating review

Preferred contactWhatsApp · consent recorded

Staff ownerGuest services

Registration and delivery states must come from the configured event records and verified channel, not from the assistant’s assumption.

Published sources only.

EventBot answers from approved event content. Conflicts, missing answers, and sensitive requests become visible staff handoffs.

Verified delivery only.

Confirmations, reminders, and proactive messages run only when the event channel is configured, permissioned, and tested.

People own exceptions.

Refunds, complaints, emergencies, access arrangements, identity changes, and commercial decisions stay with authorised staff.

Let people ask. Give your team fewer threads to untangle.

Bring your event programme, venue guide, registration path, and most common support questions. We will show how EventBot answers the known, captures the missing, and hands off the important.

Book the EventBot demo See the organiser operations hub