Skip to main content
GullySystem
Hospitality

Contact & Account Management for Serviced apartments

Keep organisations and their individual contacts connected.

CRM

Does this function belong in your operation?

Use when accounts have several contacts or owners change.

A business relationship or contact is added.

A corporate travel desk, relocation agent and staying guest can all be involved in the same apartment booking but have different responsibilities. Configure the company account separately from individual contacts and occupants, with the billing contact and rate-agreement owner identified. Guest identity documents and stay details require their own permitted access rather than being exposed to every commercial contact. Keep access to corporate statements within the account's authorised billing relationship. A guest's presence in a company booking does not mean the guest can inspect other employees' stays. Likewise, a relocation agent needs only the information its agreed role permits, even when it originally introduced the corporate client to the property.

Bring the records the workflow depends on.

  • Company, agent and individual guest identifiers
  • Booking, billing and decision-contact roles
  • Applicable corporate rate or agreement reference
  • Contact permissions and relationship changes

Outputs to check

  • Corporate and agency relationship directory
  • Named booking and billing responsibility
  • Contact-change and stay-reference history

Follow the contact & account management workflow.

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

  1. 1. Register the organisation

    Check identifiers and possible duplicates.

  2. 2. Add contacts

    Record each person's role and permitted communication details.

  3. 3. Assign ownership

    Identify who maintains the relationship and next actions.

  4. 4. Record interactions

    Keep history against the correct account and contact.

  5. 5. Maintain changes

    Handle moves, departures and mergers without transferring unrelated history.

Who uses the module, and who approves?

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

Reservations manager

Identifies who can request a stay and which company or agent arrangement applies.

Corporate account owner

Maintains the travel-desk relationship and records changes to authorised contacts.

Accounts clerk

Uses the correct billing contact without treating every occupant as the party liable for payment.

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.

Employee leaves the corporate client

Remove their booking access while preserving the company's earlier stay history.

Guest pays personal extras

Keep the payer and charge allocation separate from the corporate room account.

Agent books for an unnamed occupant

Retain the commercial booking contact and collect guest details through the appropriate check-in process.

Can this work independently?

The directory can stand alone with controlled imports and updates. Leads, opportunities, billing and support use the same account identifier when connected. A person may have several business relationships, so contact identity should not be confused with one account's financial responsibility.

Systems and records it connects with

  • Lead management: Enquiry sources, owners and qualification decisions.
  • Quote and proposal management: Commercial proposal versions and acceptance details.
  • Invoice management: Issued invoice references, line amounts and outstanding balances.
  • Accounting software: Posted financial entries and reconciliation references.

Configure, test and introduce the workflow.

  • Share your customer sheet or software. A summary lists the firms, people and branches found inside.
  • Decide which roles and terms matter in your trade. Try a trial account. It holds people, branches and terms. After a trial load your staff merge the flagged duplicates. The cleaned list returns for sign-off. Only then does the real load run.
  • Sales staff, accounts and the owner see their own part. Every role takes home a sheet. It is short and written for their work. Calls and visits are logged on the account from now on. The owner and team go through some accounts. Fields are adjusted as needed.

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.

  • A company account can distinguish booker, occupant and invoice recipient.
  • Personal guest details follow the agreed access boundary.
  • A departing contact does not remove the client's historical booking references.
Serviced apartments

How the business operates.

A serviced apartment sits between a hotel and a rental. One block can hold a consultant staying two nights, an engineering team posted for a commissioning season and a family waiting for their own flat to be handed over.

Apartments and the stay chart

Set up each block, floor and unit as a studio, one bedroom or two bedroom, and see every flat against every date. A second booking over held nights is refused until the unit is released.

Corporate rate contracts

Hold each company’s negotiated rate by unit type and date range, post stays to the company account, and see what the account still owes after a month of occupancy.

See the full industry workflow, reports and implementation plan →

The records that hold the operation together.

  • Apartment identifier and date-based availability
  • Guest, company payer and booking agreement
  • Check-in record and permitted identity-document reference
  • Stay folio, approved extras and deposit

Operational bottlenecks to check

Two bookings land on one apartment

Availability lives in a spreadsheet and an extranet login, and a quiet extension collides with a new arrival. The night manager shuffles luggage to another floor.

Corporate statements take days to build

Someone retypes every company stay from separate guest folios, with the corporate rate, minibar and laundry lines, and the purchase order reference is lost on the way. Payment waits.

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. Check availability and terms

    Identify the apartment type and dates, payer and agreed rate terms. Distinguish an enquiry or temporary hold from a confirmed stay.

  2. 2. Prepare and check in

    Confirm apartment readiness and record the agreed guest information and handover inventory using the operator’s requirements.

  3. 3. Record the stay

    Post authorised extra charges and service or maintenance requests to the correct apartment and guest stay.

  4. 4. Manage changes and extensions

    Check availability before extending or moving a stay. Retain the original and revised dates, rate basis and payer approval.

  5. 5. Check out and reconcile

    Record the apartment handback and authorised adjustments. Reconcile the guest folio or corporate statement and release the unit only when its readiness state is confirmed.

Industry reports to connect with

  • Apartment occupancy and upcoming availability
  • Corporate stays and statements awaiting settlement
  • Unresolved maintenance and turnover tasks
  • Deposits, approved extras and folio differences

Questions before implementation.

When should serviced apartments consider contact & account management?

Use when accounts have several contacts or owners change. A business relationship or contact is added.

What should we bring to the requirements discussion?

Bring anonymised examples of Company, agent and individual guest identifiers; Booking, billing and decision-contact roles; Applicable corporate rate or agreement reference; Contact permissions and relationship changes. 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. Keep organisations and their individual contacts connected. Configuration, a connected module or a custom build are evaluated against that gap before a replacement is proposed.

What is outside this module?

Storage does not establish marketing consent or permission to share data.

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. A company account can distinguish booker, occupant and invoice recipient. Use this check when reviewing the first working version.

Talk to us

Discuss contact & account management 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