Support & frequently asked questions

Get support. Search our collection of frequently asked questions (FAQs).

Contact support

Fill out this form to get in touch with support.

Manage requests

Check answers and respond to your requests.

Need support outside normal business hours?

You can reach SuperOffice support during evening and during weekends with Premium Support.

Latest Forum Posts

  • Replied to Template variables and buttons in Screen designer for Custom Objects in Custom Objects

    Hit this limitation today again at a customer..., a wish has been registered for this earlier: Wish: placeholder for custom object id Would be great if this could be implemented, seems like a small change that would be very beneficial for custom object usage 😊

    7 h, 17 m ago | 01:04 PM
  • Replied to List user defined in new Service Module in Service management

    Hi Bas, Our tickets in CS are not only for our service & support but also Billing monthly sent to our Customer. Closing a ticket requires filling in several mandatory fields shown in bold in Tieckt Header; otherwise, it’s IDs will display in a red row to user, this ensures that no tickets being skipped to bill to our customer.   The associated lists of cost center in extra table and project are two of them. We have thousands of projects; For enabling users to quickly and easily find and select his correct project in TicketEdit, we need a filtered project-list with status neither closed nor cancelled, sorted by project start date, includes specific display fields. The Solution in Screen with Simple Value works exactly on our demand. In contrast, triggered dialogs require a step more   to ask user in dialog to confirm the Project Status -- The process lacks conciseness. Similar to the linked cost center list, which includes a "Disable" field in extra table, in TicketEdit should display only active cost centers, the Triggered dialogs require the user to confirm the display of active cost centers via an additional prompt -- an unnecessary step for the user.  In short, triggered dialogs is general good but not ideal for our this application. The ideal approach would be to implement the necessary conditions beforehand -- like simple value in Screen or conditions in Archive of ScreenDesigner.

    19 Jul 2026 | 03:54 PM
  • Replied to Conditional field pilot in Conditional fields

    I don't know how doable this is, but this would be a fabulous addition to SuperOffice.

    13 Jul 2026 | 11:37 AM

Active forums

  • Jianchun You Service management 07/19/2026 mode_comment 228
  • EC

    Settings and maintenance 06/16/2026 mode_comment 163
  • Catherine Ngo AI styling 05/18/2026 mode_comment 1