OĞUZ EROL · MarkdownTR
Open MarkdownClose
Source: https://oguzerol.com/en/ai-for-hotels/

[![Example scenario: a late-night parking question gets a reply draft built from approved hotel information; old details are not used, and the reply waits for morning approval before it is sent.](https://oguzerol.com/gorseller/senaryo/ai-for-hotels-senaryo-en.webp) View full size](https://oguzerol.com/gorseller/senaryo/ai-for-hotels-senaryo-en.webp)

# Custom Hotel Cash, Guest CRM and Team Application

[Oğuz Erol](https://oguzerol.com/en/about-me/)  |  16 min read  |  Published: 29 July 2026  |  Updated: 31 October 2026

## Key takeaways

- Guest enquiries, confirmed bookings, payments and room preparation remain linked but separate.
- Reception, accounting and housekeeping work within role-specific permissions.
- Initial scoping is paid; PMS access is verified and OTA rate and availability distribution is excluded.

As a hotel general manager, you need to see more than occupancy at the end of the day. Outstanding payments, rooms awaiting preparation and promises made to guests matter too. I can bring your spreadsheets, reception notes and WhatsApp conversations into a custom web application with individual employee permissions. This is a proposed development scope for your hotel, not a list of existing product features or a completed client project.

I select the first scope around the process causing the most difficulty. If reception is waiting for payment while accounting checks a separate spreadsheet, cash control and reconciliation come first. If requests disappear on employees’ phones, we can start with guest communication and task tracking. Your existing property management system, or PMS, can remain the primary source for bookings and room inventory.

## A situation report for the general manager’s morning meeting

Different departments may give different answers to the same question: sales considers a booking confirmed, reception says the deposit has not arrived, and housekeeping reports that the room is under maintenance. I do not compress those statements into one “completed” status. The booking, payment, room preparation and guest request are related but separate records.

The management screen shows why a task remains open, its owner, the next action and source freshness. Issues needing your decision are distinguished from work an employee needs to complete. The meeting can therefore produce assigned tasks on existing records rather than another spreadsheet to prepare. The application’s value depends on accurate recording becoming part of daily work; unused screens do not improve operations by themselves.

## Example workflow: from WhatsApp enquiry to checkout balance

This scenario is entirely fictional. A guest sends stay dates and a transfer request on WhatsApp. A sales employee collects missing information and prepares a quote using an authorised rate source. Reception checks current room availability and confirms the booking in the source system; the application links its reference to the quote.

| Event | Record created | Owner | Completion condition |
| --- | --- | --- | --- |
| A stay enquiry arrives | Guest and sales enquiry | Sales | Requirements and follow-up date are clear |
| A quote is accepted | Quote version and booking link | Reception | Confirmed booking verified in the source |
| A deposit is due | Due date and receipt record | Accounting | Bank or provider result verified |
| A transfer is requested | Service request | Guest relations | Provider confirmation received |
| Room preparation starts | Cleaning and inspection task | Housekeeping | Staff room inspection completed |
| The guest checks out | Additional services and remaining balance | Reception | Payment and any refund verified |

A guest sending proof of payment does not automatically complete a receipt. A transfer response may say “We have received your request”; it must not confirm the transfer before a vehicle is confirmed. When an employee’s shift ends, open work and promises pass to the next employee through the same record.

## Which screens can I develop?

Rather than add modules the first version will not use, I specify the required screens in the delivery list. Each screen has a data source and a condition for completion.

- **Daily management:** approaching arrivals, outstanding payments, overdue tasks and exceptions needing decisions.
- **Guest profile:** previous stays, conversations, permissions and open requests.
- **Quote list:** rate source, validity, version changes and follow-up owner.
- **Reception workspace:** arrivals, departures, balances and special preparation notes.
- **Cash closing:** opening count, cash movements, physical count and discrepancy approval.
- **Bank/POS reconciliation:** batch settlements, commissions and unmatched transactions.
- **Room preparation:** dirty, being cleaned, awaiting inspection, ready and under maintenance.
- **Maintenance requests:** room or equipment, fault description, photographs and activity history.
- **Supplier account:** invoices, due dates, payment plans and open balances.
- **Shift handover:** unfinished tasks, commitments and acknowledgement of handover.

Phone screens are simplified around the employee’s daily work. Housekeeping does not need every amount on a guest account, and accounting does not need to work through every cleaning note.

## Hotel CRM is the history of the guest relationship

For a hotel, CRM is more than a phone number list. It is a record structure showing which dates a quote covered, what the guest requested, what was confirmed and what remained unresolved after the stay. Corporate customer and agency relationships can link through separate profiles.

I do not automatically merge family members who share a phone number. The system may suggest a match, but an authorised person controls merging, which can be reversed. A temporary email supplied by an OTA is not permanent communication consent. Guest preferences are retained only as needed for the service. Health and other sensitive details are not spread through general customer notes; access to necessary information is restricted separately.

## What can your guests do from their phones?

I can develop a stay portal that guests open without installing an application. Verified access lets them view only their own stay information and the services available to them. The hotel guide, service descriptions and relevant contact details are kept in one place.

- Share their arrival time and request a transfer.
- Request room service, additional cleaning or maintenance.
- Ask for an available time for a spa appointment, restaurant booking or another additional service.
- Follow the status of their request and read the team’s response.

Your team can assign each request to the relevant department, see its owner and waiting time, and link the resolution note to the guest history. The next shift continues on the same record. The authorised team confirms availability, timing and price; submitting a form does not confirm a booking or payment. Automatically posting a charge to the room account depends on a supported and verified PMS integration.

## How can you track department requests and stock?

I can develop screens that connect requests for cleaning materials, minibar supplies and kitchen consumables to purchase approval, ordering and receipt. You can see who requested an item, which step is pending and how much has arrived.

- Track receipts, issues and transfers by store and department.
- Record a partial delivery while keeping the remaining quantity open.
- Create alerts or purchase requests when items fall below the minimum levels you define.
- Reconcile physical counts with recorded stock using an explanation and authorised approval.
- Link the supplier invoice and payment status to the relevant order and receipt.

Recorded stock is shown separately from quantities physically counted in storage. Keeping it current depends on the team recording movements or a verified source providing them. We separately define whether a minimum-level alert should generate an order; purchasing and payment retain their own approval rules.

## Repeat stays and a loyalty programme

I can develop a loyalty module that shows what a returning guest has earned and what your team can offer. The programme may use points, membership levels or defined service benefits. Your hotel’s rules, validity dates and participating properties remain recorded. Guests can also view their own benefits through verified access if this is included in the scope.

| Event | Record kept by the application |
| --- | --- |
| Membership created | Guest link, accepted programme terms and joining date |
| Stay completed | Verified source reservation and earned benefit |
| Benefit redeemed | Relevant service, date, approving employee and remaining entitlement |
| Cancellation or refund | Reversal or correction linked to the original transaction |
| Exception approved | Authorised person, reason and change history |

For example, reception can see an eligible hotel service benefit on a returning guest’s CRM record. The entitlement is deducted when an authorised employee confirms redemption. Acceptance checks cover importing the same stay twice without awarding it twice, correcting transactions without deleting history and explaining expired benefits. Availability of the service is confirmed separately.

Membership does not replace permission to send marketing messages. A suitable repeat-stay offer can be prepared for a guest who has consented, with sending and opt-out rules applied. Using the same entitlement in the PMS or at another property requires separately verified read and write access. This module does not send rates to OTAs. Reports can track repeat stays and redeemed benefits; increased revenue is not guaranteed.

## Employee permissions and approval order

Each user has an individual account. Permissions apply when reading, changing and exporting records or asking AI questions, as well as determining which menus appear.

| Role | Visible work | Permitted action | Additional approval |
| --- | --- | --- | --- |
| General manager | Selected property management records | Review exceptions and closing | According to the permission policy |
| Reception | Relevant stays and accounts | Arrival, task and receipt entry | Refunds and discounts |
| Accounting | Documents, banking and account records | Reconciliation and document checks | Reopening a period |
| Housekeeping | Room preparation and necessary notes | Task status and inspection | No permission to release rooms for sale |
| Sales | Enquiries, quotes and company history | Quotes and follow-up | Rates outside authorised terms |
| Guest | Areas available for their own stay | Requests and arrival information | Individual access verification |

Access is removed when an employee leaves. Multiple properties require separate design for shared guest policies, company boundaries and head office permissions. One group does not mean every record is open to everyone.

## Separate cash from recorded sales

Expected closing cash is the approved opening balance plus cash received minus cash paid out. Card payments do not increase the physical cash drawer. Transfers between tills, deposits and sales revenue are different concepts. Each currency has its own balance; conversions show the rate and date used.

A single bank settlement may cover several POS transactions. Sale dates, settlement dates, commissions, refunds and deductions are compared together. A partially matched record remains open. Historical movements can use reasoned corrections or reversals instead of deletion. This scope supports internal financial control; it is not presented as a replacement for statutory accounts, tax filings or an accountant. Creating a PDF does not mean an official electronic invoice has been issued.

## Importing spreadsheets that can safely be uploaded again

I first establish the file owner, column meanings, date formats and authoritative system. Room, agency and expense names are matched to shared lists. Identifiers with leading zeros, different decimal formats and cancellation rows are checked using a sample file.

Uploading the same file again must not create another sale or receipt. I use source references where available; otherwise I explain matching limitations and send doubtful records for review. After import, row counts, period totals, open balances and sample bookings are compared. A faulty upload can be reversed. Without regular file delivery, the report is not current; the screen shows the latest file timestamp. Excel exports can continue where needed.

## Where can AI help?

I can configure AI to work with approved hotel information, procedures and accessible records. It can answer check-in questions, translate guest messages, extract invoice fields and summarise shift conversations. The supporting document or record remains visible.

Financial totals, availability and loyalty benefits follow defined rules. The model does not estimate and recreate them. If it cannot access a rate source, it passes the enquiry to staff instead of inventing a price. Discounts, refunds, record merges and booking changes can require human approval. Because AI could assign the wrong priority, urgent requests retain real phone numbers and access to staff. The model provider, shared data, retention settings and usage costs are agreed separately.

## Multilingual first replies and review drafts

Late-night parking or check-in questions use current, approved hotel information. If information is stale or a reply needs approval, its draft stays with staff. Automatic sending is a separately selected and tested workflow; not every draft is sent immediately.

Where authorised access exists, OTA review replies can also be drafted for the hotel to approve. Central access to every platform’s reviews and reply functions is not assumed.

The [hotel WhatsApp booking example](https://oguzerol.com/en/hotel-whatsapp-booking-automation/) uses illustrative data to explain rate sources, availability and connection failures. Its screens do not represent an integration already installed at your hotel.

## When are WhatsApp and SMS messages sent?

Checked 30 October 2026: the [WhatsApp Business messaging policy](https://business.whatsapp.com/policy) requires approved templates outside the 24-hour window following the customer’s last message. Consent and opt-out rules also apply.

Each message’s trigger, recipient and approval are part of the workflow. Official WhatsApp API access, appropriate permissions and approved templates where required are verified under Meta’s WhatsApp messaging policy. SMS uses an authorised provider with the consent, opt-out and Turkish commercial messaging registry checks appropriate to the message type; [İYS](https://iys.org.tr/) records are considered separately.

| Trigger | Recipient | Before sending |
| --- | --- | --- |
| A quote needs follow-up | Enquirer | Permission and owner approval |
| A deposit due date approaches | Relevant guest | Current outstanding balance check |
| A transfer is confirmed | Guest requesting the transfer | Provider confirmation |
| A room is ready | Relevant internal team | Staff room inspection |
| A service request is resolved | Guest who opened the request | Authorised completion record |
| An offer follows the stay | Previous guest with consent | Marketing consent and opt-out checks |

An opt-out blocks subsequent marketing sends. Message identifiers and event records prevent duplicate notifications. Delivery errors or failed messages are not treated as completed services. Automatic replies can stop when staff take over a conversation.

## Limits of PMS and OTA connections

We can start with CSV reports. If actual API access exists, I test readable fields, refresh frequency and support for write actions. A read connection does not provide permission to create or cancel bookings. Notification emails alone are not a complete reservation source.

This service does not include developing a channel manager that sends rates, availability, allocations or sales restrictions to OTAs. Your existing provider continues that work. Payments and statutory guest identity reporting are scoped separately if the authorised provider and current interface are verified. Owning a hotel account does not automatically permit automated access to every platform field. If a source fails, old information is not presented as live; critical booking and payment decisions need current confirmation.

## Which records are visible in reports?

Management reports measure receipts, receivables, quote conversion, service delays and room preparation separately. A WhatsApp click is not a confirmed booking. Booking, stay and payment dates answer different reporting questions. The amount left after commission is not called net profit after all expenses.

The website and advertising can also link to enquiry records where technical access and consent allow. Unmatched enquiries remain visible. Incorrect or delayed records enter a review queue; reports show their period, filters and last update. Without historical snapshots, last year’s booking pace is not invented. Any estimate explicitly states its assumptions.

## Initial scope, training and delivery checks

The initial process and data review is paid. Using sample files, current programs and employee roles, I document screens, integration status and acceptance criteria. The starting point may be cash closing and reconciliation or WhatsApp enquiries and task handover. Further modules follow regular use of the first workflow.

Migration includes a controlled comparison period and employee training. A daily data owner is identified. Backups, restore tests, support hours and incident priorities appear in the agreement. Hosting, messaging, AI and third-party connection costs are explained separately from development. Offline operation is committed to only if that scope has been built and tested.

We can test these examples together at delivery:

1. Uploading a file again must not change revenue or record counts.
2. A deposit receipt must not complete before payment is verified.
3. A cash discrepancy must not close without explanation and approval.
4. AI must not reply simultaneously after reception takes over.
5. Housekeeping must not reach unauthorised financial data.
6. A failed source must show its error and data timestamp.
7. An opted-out guest must not return to the marketing list.
8. A sample backup must restore with selected balances compared.

## When is another solution more suitable?

If standard PMS screens meet your needs, using the existing product’s settings may be the better first step. I do not present a complete channel manager, statutory accounting or ready-made connections to every device as existing features of this offer. Custom development makes sense for the work between existing tools whose rules can be clearly defined.

## Frequently Asked Questions

### Must we replace the existing hotel software?

No. Accessible fields can support operational and control screens alongside it. Full PMS replacement is assessed separately.

### Can we start without an automatic integration?

Authorised CSV or Excel reports can be used. Report freshness is limited by the file timestamp; real-time room confirmation remains a separate check.

### Does AI confirm bookings itself?

A transaction can be considered only with a supported write integration, current availability checks and defined permission. Otherwise, authorised reception confirmation is required.

### Is every guest message automatic?

No. The transaction type, consent, message template and approval order are defined. Opt-out and duplicate checks run before sending.

### Does the first version include every module?

It includes the selected workflow. Screens, sources and delivery checks are agreed in writing; there is no promise of unlimited modules.

### Do you guarantee higher revenue or occupancy?

Delivery of defined workflows can be committed to. Commercial outcomes also depend on rates, season, service and demand. I do not promise unmeasured gains.

## Choose your hotel’s first workflow

Together, we can identify which file is repeatedly prepared, which payment needs investigation and which request disappears during a shift. You can request a scope by saying, **I want to define my hotel’s cash, guest and task workflow**. The first paid engagement produces a written plan of the screens to develop and how they will be checked.

[Send your scoping enquiry through the contact page](https://oguzerol.com/en/contact/).

[Back to top ↑](https://oguzerol.com/en/ai-for-hotels/#icerik)