imbahub
Menu +
EN
Talk to us
IMBAHUB / Websites

Help visitors move from interest to arriving at the right place.

A conference website serves people deciding whether to attend and people who have already registered. ImbaHub can structure the public presentation around the programme, audience and practical questions. Tickets, payments and attendee records need a separately agreed solution.

A connected attendee journey

  1. Understand

    Programme and audience explain the event.

  2. Choose

    Registration describes the real next step.

  3. Arrive

    Practical information works on mobile.

Give prospective and registered attendees different routes

A prospective attendee needs to understand the subject, intended audience and commitment. A registered attendee is more likely to need the time, venue, entrance and latest programme. Give both a visible route from the homepage rather than sending everyone through the same sales presentation.

A fictional industry seminar might have a programme of topics and speakers alongside a dedicated attendee-information page. Confirm participation and approve each speaker description before publication. Label provisional programme items as provisional.

Distinguish interest from a confirmed booking

The button should explain whether it opens an enquiry form, an external ticketing service or registration terms. Submitting a contact form does not itself confirm a place. Explain what happens next and who answers questions.

If another system manages bookings, availability and confirmation messages should reflect its actual state. Avoid manually publishing a remaining-place count unless someone is responsible for keeping it current. A link to ticketing is a different deliverable from synchronised booking status.

Make practical information work on the day

Provide the address, date, times and contact in readable HTML. A map or PDF can supplement this, but attendees should find the entrance and start time without interpreting an image or installing an app. Describe only accessibility arrangements the organiser has checked.

For parallel tracks, present the time, room and audience together. Test a concrete mobile task: someone arrives late and wants to find the next session. Use the result to decide what belongs near the top and what can be secondary.

InformationOwnerCheck
ProgrammeProgramme leadTime and room agree
RegistrationBooking leadThe button describes the actual next step
VenueOrganiserAddress and entrance are confirmed
ChangeAssigned editorLanguages and references are reviewed

Commission a website someone can maintain

Start with the page structure, a real programme draft and the systems already in use. Assign responsibility for the programme, practical details and urgent corrections. Image permissions, speaker details and publication approvals should be settled before launch.

An initial delivery can include the event presentation, programme, practical information and a tested registration link. Integrations, payment, messaging and continuing incident cover are specified separately. Afterwards, choose a clearly dated archive or prepare the next edition without mixing the two.

Questions, answered

Is ticket selling included?

That must be agreed in the scope. A public website linking to existing ticketing is a different delivery from an integrated payment and booking solution.

Can the site be reused next year?

Yes, after reviewing dates, programme and links. Keep past editions clearly separate if the archive remains useful.

IMBAHUB

What would you like to make possible?

Bring a programme draft, the registration service and the allocation of responsibilities to an initial conversation.

Talk to us
Product interface set to English in an isolated environment with fictional English demo content.

Product interface set to English in an isolated environment with fictional English demo content.