Requests

Drag-and-drop forms on your website, your own REST API integration from a CMS or any other website, manual entry in the backoffice after a phone call: every request lands in the central inbox in a structured way.

The go~mus + forms add-on provides the drag-and-drop editor and the public widget for a low-threshold start. If you want to maintain your own forms in your CMS or feed requests from an existing system, use the Requests API. Backoffice processing runs in every instance.

General requests are the universal contact form: fields for the matter at hand, callback preferences, accessibility info. They land with the communications person and get distributed in the backoffice.

Booking requests capture preferred dates, group size, programme requests and circumstances. For large groups or curated offers that are not self-service bookable, they are the central inbound channel. In the backoffice, group splitting and the programme planner help convert the request into one or more binding orders.

Accreditation requests apply for access to a specific customer category, e.g. as a teacher, student, press or researcher. The approval happens in the backoffice; afterwards the prices and privileges of that category apply to the accredited person. Further sub-types are in preparation.

Every request runs through intake, categorisation, assignment, response and archiving. Status transitions are traceable; everyone in the team sees who is working on what. Comment levels keep internal notes and customer replies separate, so neither view bleeds into the other.

Reminders to unanswered requests can be sent manually or automatically so nothing gets stuck.

From a booking request, a prepared programme with times, rooms, prices and guides emerges in the backoffice. Via token link, the programme goes to the requesting person; they accept or ask for adjustments. On acceptance, the programme converts directly into one or several binding orders, without your team retyping the data. On adjustment, the workflow loops back without data loss.

Conversion rate from request to order per sub-type and month, average handling time, backlog per team member: typical KPIs can be derived from the request data. Closed requests sit in the archive with search and filter functions, so your team can trace, weeks later, what was discussed when.