Welcome to the Pult Changelog! πŸš€

Here you'll find all the latest updates and improvements we've made to the platform. If you have any questions, feel free to reach out to our support team at support@pult.com

© 2026 PULT GmbH

Improvements

Jul 14, 2026

The PULT AI assistant can now display parking utilization data when asked. Previously, customers with active parking lots could not get parking usage insights through the AI assistant. This has been fixed β€” you can now ask the AI assistant questions about your parking space utilization and get accurate answers.

Jul 14, 2026

PULT is now available in French, Spanish, and Portuguese. All frontend interfaces have been translated, making it easier for international teams to use PULT in their preferred language. This expands our language support beyond English and German.

Jul 10, 2026

You can now star meeting rooms as favourites β€” starred rooms always appear at the top of the "Select a room to book" panel, so you can find your go-to rooms instantly. On top of that, location filters (e.g. selecting "DE") now stay applied between sessions, so you no longer need to re-select your preferred location every time.

Jun 23, 2026

Visitor invitations now include a calendar file. When you invite a visitor and enable the email notification, the invitation email now includes an .ics calendar file with the visit date and time. Your visitors can add the appointment to their calendar with a single click.

Jun 18, 2026

We now include the visitor’s company on printed badges. This helps front desks identify guests faster and gives visitors more complete badges without extra manual work. Please remember to update your PULT Kiosk app to use this new feature!

Jun 11, 2026

Colleagues and managers can no longer view each other's past desk bookings. Only the individual user (and admins) can see their own booking history on the timeline. This gives organizations tighter control over employee booking privacy β€” especially important for works-council and data-protection requirements. Admins can enable or disable this setting from the company settings page.

May 26, 2026

Booking a meeting room now comes with a redesigned attendee picker. You can search and add co-workers, select from existing visitors, or invite a brand-new guest by entering any email address β€” all from a single, streamlined "Attendees" field. No more switching between separate flows to include external participants in your meetings.

May 22, 2026

When a user is archived β€” whether manually or through directory sync (e.g. Microsoft, HR systems) β€” their future bookings and default desk assignments are now automatically released. This prevents "ghost bookings" from blocking desks after someone leaves the organization, saving admins from having to clean them up manually.

May 22, 2026

The Visitor Management table now shows visitor type (e.g. Interview, Contractor), check-in time, and badge-printed status directly in the table columns. Front desk staff can see key visitor information at a glance without opening individual visitor details.

Visitor Management Table: Inline Visitor Details

May 18, 2026

Admins can now control whether Frontdesk users can also book desks and use the full webapp. A new "Allow Frontdesk users to book desks" toggle is available in Settings > Booking. When enabled, Frontdesk staff can book desks, parking, meeting rooms, and more β€” just like regular members. When disabled, they only see guest booking. This gives organizations full flexibility to match how their reception staff actually works.

May 11, 2026

Admins can now select multiple device authorization requests at once and approve or deny them in bulk from the dashboard. This saves significant time when onboarding many devices, especially those with automatically matched users. Unmatched devices are automatically excluded from bulk approval to prevent errors.

May 08, 2026

Admins can now control documents and forms independently for returning visitors. Previously, documents (e.g. NDAs) and forms (e.g. visitor logs) were coupled β€” if one was shown again on a repeat visit, both were. Now you can configure each separately, so returning visitors only see what's actually needed. For example, skip the NDA on a second visit but still collect the visitor log.