Booking Page: How to Publish Services and Receive Requests in Diamond Operations Pro

What the booking page is

The "Booking Page" is the tool that allows you to create and manage a public page connected to Diamond Operations Pro.

From that page, a client can:

• View company information.
• Review available services.
• Request a booking.
• Ask for an estimate.
• Submit contact information.
• Share details about the service they need.

The client does not need access to the internal panel. They only interact with the public page, while the team reviews received requests from the system.

What this module is used for

The "Booking Page" module is used to control how the company presents itself to clients or prospects online.

From this module, you can:

• Activate a public booking page.
• Publish available services.
• Configure text visible to the client.
• Manage page sections.
• Review which services will be available online.
• Share a public link with clients.
• Capture booking, estimate, or contact requests.
• Connect public requests with the internal review workflow.

This module is important because it can directly influence the quality of requests the team receives.

Who should use this module

The "Booking Page" should be managed by users responsible for public presence and service configuration.

It can usually be used by:

• Owners.
• Administrators.
• Sales team.
• Users responsible for publishing services.
• Users in charge of configuring public forms.
• Staff who coordinate incoming requests.
• Users who review how the company is presented to clients.

It is not recommended that any user modify the public page without review, since changes may affect what clients see and the requests that reach the system.

When to use the "Booking Page"

Use this module when the company needs to receive requests from a public page.

Common cases include:

• The company wants to receive online requests.
• Available services need to be published for clients.
• A public booking link needs to be shared.
• Estimate requests need to be captured.
• Contact requests need to be received.
• Client-facing text needs to be updated.
• Public services need to be activated or deactivated.
• The page needs to be reviewed before sharing.
• The quality of information clients submit needs to be improved.

Important concepts

Public booking page
Page visible to clients or prospects where they can submit requests.

Main section
Initial presentation area of the page. It can include the company name, description, main message, or highlighted company information.

Services section
Part of the page where available services are shown for booking or inquiry.

Estimate section
Form or area intended to receive quote requests before confirming a service.

Public access
Link that can be shared with clients so they can visit the page.

Request
Petition generated from the public page and later reviewed inside the system.

Visible service
Service configured to appear publicly on the booking page.

This flow separates the client experience from the team’s internal review.

The client submits information from a simple page, while the team validates availability, data, service, and next steps before converting the request into a booking or job.

Before sharing the link, confirm that the published information is correct and that the visible services match what the company can actually provide.

Reviewing from a new window helps you see the page from the client’s perspective.

Main page section

The main section is one of the most important parts of the public page.

It should quickly explain who the company is and what the client can request.

It may include:

• Company name.
• Main message.
• Brief description.
• Contact information.
• Call to action.
• Image or visual content, if the configuration allows it.

A clear main section helps the client understand what they can do on the page and reduces confusion before submitting a request.

Published services should be written for clients, not only for the internal team.

For example, an internal name may be useful for operations, but a public description should clearly explain what the service includes and when it should be requested.

How to write services for clients

Visible services on the public page should be easy to understand.

Recommendations:

• Use clear names.
• Avoid internal abbreviations.
• Explain what the service includes.
• Indicate whether the client should submit additional information.
• Do not publish services the team cannot provide.
• Keep descriptions simple.
• Avoid promising times, prices, or conditions that are not confirmed.
• Review spelling and clarity before publishing.

Recommended example:

"Deep cleaning for properties that require more detailed cleaning before or after occupancy."

Not recommended example:

"Special complete service."

A good description reduces questions, incomplete requests, and interpretation errors.

Configuring estimate requests

The estimate section allows requests to be received when the client needs a quote before confirming.

This option is useful when:

• Price depends on the size of the job.
• Details need to be reviewed before confirming.
• The service requires manual evaluation.
• The client must submit additional information.
• The company does not want to publish a fixed price.

When estimate requests are accepted, it is important that the form asks for the information needed so the team can respond correctly.

Sharing the public link

The public link allows clients or prospects to access the booking page.

Before sharing it:

• Review the full page.
• Confirm that visible services are correct.
• Send a test request if needed.
• Check that the request reaches the "Requests" module.
• Verify that contact information is updated.
• Confirm that the page looks good from the client’s point of view.

After validation, the link can be shared by email, messages, website, social media, or other company communication channels.

The public page captures the request, but the final decision should be reviewed internally before converting it into a confirmed job or booking.

Relationship with other modules

The "Booking Page" can connect with other system modules.

Requests
Requests generated from the public page reach the "Requests" module for review.

Services
Configured services can influence what is shown to the client.

Activities
Some configurations may use activities as the operational base for services.

Schedule
Approved requests may end up affecting the operational schedule.

Jobs
An approved request can move toward a confirmed job, depending on the configured workflow.

Keeping the booking page well configured helps other modules receive clearer information.

Best practices

To keep a public page clear and useful:

• Review the page after every important change.
• Keep descriptions simple and client-oriented.
• Do not publish services the team cannot provide.
• Confirm that contact information is updated.
• Use easy-to-understand service names.
• Test the public link before sharing it widely.
• Review requests daily if the link is active.
• Adjust forms if incomplete requests are received.
• Coordinate changes with sales, operations, and dispatch.
• Keep consistency between published services and real services.

Expected result

By the end, the user should be able to:

• Activate a public booking page.
• Configure client-facing information.
• Publish clear and correct services.
• Share a public booking link.
• Receive online requests.
• Review requests from the "Requests" module.
• Validate that published services match the real operation.
• Keep the public page updated.
• Use the "Booking Page" as a connection between clients and the internal operation of Diamond Operations Pro.