Skip to main content
GullySystem
Real estate and construction

Online Booking Portal for Property management companies

Let customers request or reserve an available service through a website.

Bookings and Appointments

Does this function belong in your operation?

Use when customers should make service or resource bookings online.

A customer chooses to book without contacting the office.

Prospective tenants book viewings of vacant flats or shared office floors online, choosing a slot. The agent receives the request. Confirmed visits are listed against each unit with the viewer’s name.

Bring the records the workflow depends on.

  • Bookable services
  • Availability rules
  • Required customer details

Outputs to check

  • Customer booking request
  • Confirmed or pending reservation
  • Change and cancellation history

Follow the online booking portal workflow.

Use this sequence to compare your current process with the proposed module. Agree the owner, permission and exception at each step.

  1. 1. Present the offer

    Show bookable services, conditions and available times.

  2. 2. Collect the request

    Validate customer details and chosen service requirements.

  3. 3. Recheck capacity

    Confirm that the slot remains available before committing it.

  4. 4. Apply confirmation rules

    Complete required approval or payment handoffs and distinguish pending from confirmed.

  5. 5. Manage later changes

    Record cancellation, rescheduling and any separate refund decision.

Who uses the module, and who approves?

Keep responsibilities distinct even when one person holds more than one role.

The customer

Selects a service, submits the required details and checks whether the request is pending or confirmed.

Receptionist or advisor

Works one list and not three, and confirms with a message from your number.

Owner

Compares online and staff-entered bookings and investigates cancellations or incomplete requests.

Decide how exceptions are handled.

These business rules belong in configuration and testing. A normal transaction alone does not demonstrate that the workflow is ready.

Payment succeeds but booking fails

Keep both references and route the case for reservation recovery or authorised refund.

Last slot taken concurrently

Recheck capacity before confirmation and show the customer a clear outcome.

Customer cancels

Apply the booking policy and send any refund decision to the payment process.

Can this work independently?

The portal needs a source of availability and booking rules. A local calendar can provide it, but staff scheduling, payments and messages require defined connections. Taking an online payment and confirming a reservation are separate events that must be reconciled if either fails.

Systems and records it connects with

  • Appointment scheduling: Confirmed slots, cancellations and attendance outcomes.
  • Job cards: Service findings, approved work, parts and completion records.
  • Customer records: Permitted customer identifiers and service-contact details.
  • Payment gateway: Authorised payment attempts, outcomes and settlement references.

Configure, test and introduce the workflow.

  • We list what you offer and when staff are free. You supply photographs, the map and the opening hours. A draft page returns for your comments.
  • Questions for each service are agreed, such as vehicle number or breed. You tell us what staff must know. Keep it short. The page is tied to the calendar your counter uses. A test booking shows slots closing when taken. We check it together.
  • Confirmation wording is written. A payment gateway account is connected if you want deposits, and trial payments use its test setting. The link goes on your signboard, visiting card and messages. Staff practise confirming requests. Then customers arrive.

Check the result before rollout.

Apply these checks to a sample from the agreed workflow, then repeat with an exception. Keep the expected result beside the test record.

  • Customers cannot reserve unavailable capacity.
  • Required details are validated.
  • A request is distinguishable from a confirmed booking.
Property management companies

How the business operates.

Owners judge you on one thing: did the money arrive on the fifth. Tenants judge you on another: did the plumber come. Both ask questions you should be able to answer from your phone, standing in a stairwell.

Lease register and rent roll

A custom piece for flat leases. It holds unit, tenant, rent, deposit, service charge, escalation, lock-in and notice dates together, with an alert before each date.

Rent collection and credit matching

Raise monthly demands and send reminders before the due date, as the paying guest product does for beds. Matching bank-transfer and card credits to flats is extra work we take on.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Owner, property, unit and lease version
  • Rent demand, tenant receipt and allocation
  • Repair ticket, approval, supplier bill and completion
  • Deposit, permitted deduction and move-out settlement

Operational bottlenecks to check

Nobody can tell who paid rent

A rent credit lands from an unknown sender with only a bank reference, and matching it to flat 4B takes days while the owner is already calling.

Renewals and escalations sneak up

Escalation dates, lock-in ends and notice windows sit inside scanned agreement PDFs, and the rent rise is noticed three months late. That income is gone.

How work flows across this business

This module sits within a wider operating process. Use the sequence to identify the other teams and records affected by a change.

  1. 1. Record the managed unit

    Identify the owner, unit and accepted management arrangement, then attach the current tenant and lease terms.

  2. 2. Raise and match rent records

    Create the agreed demands and allocate actual receipts, retaining unexplained payments for investigation.

  3. 3. Manage repairs

    Record the issue, responsibility, spending approval and supplier work. Keep the tenant update separate from approval of the supplier’s bill.

  4. 4. Reconcile the owner account

    Bring together collected rent, approved expenses and the agreed management fee. Explain unresolved items before recording remittance.

  5. 5. Handle renewal or move-out

    Record the agreed change or end of the lease, the unit condition and authorised deposit adjustments. Keep financial settlement distinct from readiness for the next tenant.

Industry reports to connect with

  • Rent demanded, received and unallocated
  • Repair tickets and supplier bills awaiting approval
  • Owner balances and remittance records
  • Lease milestones, deposits and vacant-unit readiness

Questions before implementation.

When should property management companies consider online booking portal?

Use when customers should make service or resource bookings online. A customer chooses to book without contacting the office.

What should we bring to the requirements discussion?

Bring anonymised examples of Bookable services; Availability rules; Required customer details. Show who creates, checks and changes each record. Use only records from an activity that meets the suitability conditions above.

Does this replace our existing business software?

The starting point is your current system and the gap you need to close. Let customers request or reserve an available service through a website. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Online payment, immediate confirmation and external calendar connections require explicit scope decisions.

How are scope, price and rollout decided?

The proposal follows a review of your records, user roles, branches and existing software. Data migration, connections, training and support are scoped separately where needed. Customers cannot reserve unavailable capacity. Use this check when reviewing the first working version.

Talk to us

Discuss online booking portal for your business.

Tell us which workflow needs attention and which systems your team uses. The next step is a requirements discussion and a written scope.

What happens after you share your requirements

  1. We review your brief and the systems you already use.
  2. We clarify the workflow, missing information and the work to consider first.
  3. The proposed scope sets out the deliverables, responsibilities and dependencies.
  4. Review the scope and commercial terms before deciding whether to proceed.

Start with your requirements

Describe your current process, the people involved and the change you need. Start with the details you know; we can clarify the rest together.

Share your requirements