KSIDol documentation > KSIDol modules > Public ticket pro

Module guide: Public ticket pro

Non-technical user guide: what the module is for, how to use it and how it fits together with Dolibarr.

Dolibarr objectNative tickets

Request submissionNo account

Custom fieldsUp to 12

Core modificationNone

1. Module overview

KSI Ticket Public Pro adds a public support-request page to your Dolibarr, fully customised to your brand, that your customers or visitors use without needing an account. Every request submitted becomes a genuine ticket in Dolibarr's native Tickets module: you then handle it exactly as usual, in your back office, with your own rules and teams. The module does not modify any Dolibarr core file: it publishes its own public page, which you adapt freely (logo, colours, texts, requested fields) by relying on the objects and settings already present in Dolibarr — the Tickets module, the type/category/urgency dictionaries, the Company record for the logo and the ticket's complementary fields (extrafields). It is a "pro", tailor-made alternative to the standard public ticket-creation page.

Provides a dedicated public web address for submitting requests, in your company's visual identity.
Turns every visitor submission into a standard Dolibarr ticket, handled normally in the back office.
Is fully configured from the module's administration page (texts, colours, logo, fields).
Alters no native Dolibarr file and stays compatible with updates.
Relies on native objects: Tickets, Third parties/Contacts, complementary fields, dictionaries.

2. A public ticket-submission page, no account needed

The module provides its own public request-creation page. The visitor fills in a form; on submission, a native ticket is created in Dolibarr and a tracking number is given to them.

Provide a dedicated public web address (displayed in the module configuration).
Let a customer or visitor submit a request without a username or password.
Record every submission as a standard Dolibarr ticket, then picked up in your usual workflow.
Show the visitor a tracking number (track ID) once their request is recorded.
Customise the confirmation message shown after submission.
Page deliberately not indexed by search engines.

3. Customise the design, logo and texts

From the module administration, you dress the public page in your company's colours and words, without touching a theme or the Dolibarr core.

Set the displayed name/brand, the main title and the page subtitle.
Write a help text that guides the customer and a custom success message.
Automatically display your company logo (taken from Dolibarr) or force another logo via a URL.
Make the logo clickable to the address of your choice.
Add a "Back to website" button with the desired URL and label.
Choose the main colour and the accent colour (hexadecimal codes).
Inject custom CSS (administrators only) for a fully tailor-made styling.

4. Choose the fields shown to the customer

You decide, field by field, what the visitor sees and must fill in, and how the form is laid out.

Show or hide the Company, Phone and Order/file reference fields.
Make these fields optional or mandatory according to your needs.
Keep the Email, Subject and Message fields always present and mandatory.
Reorder the fields and spread them across three zones: top, form, bottom.
Choose the width of each field (half-width or full-width).
Add a customer consent checkbox, displayed and required if needed.

5. Add your own fields (field builder)

Beyond the standard fields, the module offers a builder that lets you add your own questions to the public form. The answers are kept directly on the ticket.

Create up to 12 additional custom fields.
Choose the type of each field: short text, long text, email, phone, number, date, checkbox or drop-down list.
Set the label, the mandatory status, the order, the zone and the width.
Enter the options of a drop-down list (one per line, format "value|Label" or a plain label).
Automatically save the answers as native complementary fields of the ticket, visible on its record.

6. Automatic linking to the right customer

On submission, the module tries to link the request to a customer already known to Dolibarr, based on the email address entered, to avoid duplicates and save time.

Automatically search, from the entered email, for a company and a contact already recorded in Dolibarr.
Link the ticket to the right third party and the right contact when they exist.
Keep the requester's original email address on the ticket.
Option to require that the email matches an existing contact (native Dolibarr ticket setting).

7. Anti-spam, security and GDPR consent

As the page is public, the module reuses Dolibarr's protections and exposes no existing data: it is used solely to submit a new request.

Protect the submission with Dolibarr's anti-CSRF token.
Display a captcha when the native ticket captcha option is enabled.
Limit the number of submissions per IP address (native anti-abuse setting).
Ask for and record the customer's consent to the processing of their request.
Never display the content of an existing ticket: the page only allows creation.

8. Type, category and urgency from Dolibarr

To stay consistent with your usual configuration, the qualification lists come from the native ticket dictionaries, with no parallel list to maintain.

Offer the Request type, Category and Urgency lists from the native ticket dictionaries.
Display only the categories marked as public.
Hide one of these lists if needed and then apply a default code set in the configuration.
Keep a qualification identical to that of your tickets created internally.

9. Links with Dolibarr

The module does not work in isolation: it integrates with the native building blocks of Dolibarr.

Tickets (native module) : Every public request becomes a standard Dolibarr ticket, created through the Ticket object. The module depends on the Tickets module and its public interface, which must be enabled.
Third parties and contacts : From the email entered, the module automatically searches for and links the ticket to the company and contact already recorded in Dolibarr.
Complementary fields (extrafields) : The customer fields (company, phone, reference, consent, source) and your custom fields are stored as native complementary fields of the ticket, visible on its record and in its lists.
Ticket dictionaries : The Type, Public category and Urgency lists come from the native ticket dictionaries, with no duplicate or parallel list.
Company / Organisation : The logo displayed on the public page is taken automatically from Dolibarr's Company / Organisation record (or replaced by a URL of your choice).
Dolibarr security settings : The module reuses the ticket captcha and the per-IP submission limit configured in Dolibarr's security, with no additional security setting of its own.