Recurring workshops and seminars: one event per date, attendance per session, and no cut of your ticket money.

If you run workshops for a living — a monthly data-analysis class, a quarterly leadership seminar, a series of hands-on sessions in different cities — you repeat the same cycle: publish a date, take bookings, check people in, and keep a record of who attended. WebMobi runs that cycle one event at a time, and charges you per participant rather than per ticket sold.

WebMobi does not take ticket payments. A free session registers people on WebMobi; a paid one keeps selling wherever you sell today, and WebMobi runs everything around the sale — the event page, the list of who is coming, the door and the attendance record. This page covers what WebMobi costs, how free and paid dates are set up, the workshop day itself, and the limits a training business should know before it commits.

We count participants, not events. A participant is one person registering for one event, so someone who books four of your workshops in a year counts four times. There are two ways to buy, and they suit different calendars.

We take 0% of your ticket revenue. Always. Your customers pay you directly, through your own payment provider. The money never passes through WebMobi, so there is nothing for us to take a percentage of — on any plan, including Free. Every figure is on the pricing page.

Make each workshop date its own event. That keeps each date’s bookings, check-ins and attendance file apart, gives each date an address of its own to share, and matches the way participants are counted.

• Agenda: export one date’s sessions to a spreadsheet and import them into the next event. The export writes wall-clock times in the event’s time zone and uses the headings the importer reads, so rooms and trainers come across without sessions shifting by hours.
• Trainers: import them as speakers, keyed on email. A trainer who teaches several dates is recognised by the same email each time, and their profile is updated from the file.
• Addresses: renaming a date never changes its web address, so links already shared keep working; if you do change the address, the old one keeps forwarding.
• Emails and links: switch emails on for each new event before you share it, and for a paid date paste that date’s own ticketing page — each event carries its own link.

Many workshops have parts that not everyone stays for. Make each part a session, and check people into each one: on the web Check-In page, choose it under Session before scanning; in the WebMobi app, tap Scanning into and pick it. A session check-in counts the person as attended for the day as well, so you do not need a separate scan at the front door.

Use In only at a session door when arrivals are all you need. Use In / Out when leaving times matter — a badge already inside is then scanned out — and the record shows when each person left the lab. Someone who steps out and returns adds a visit but is still one attendee. Read the session name on screen after every break: a check-in made into the wrong part of the day cannot be moved afterwards.

Launching a new workshop is a good moment for a rehearsal. Publish the first date as Test rather than Live: it carries a TEST EVENT banner, takes up to 25 registrations, and its registrations and check-ins can be deleted. Register a few colleagues, run the door, read the attendance export, and fix what looks wrong. Going live is a separate, confirmed step that asks whether to keep or delete the test registrations, and it cannot be reversed.