Products / TETAMU
S.A.L.T CI TETAMU
Hospitality operations and intelligence in one install. Run the property and understand the guest, on the property's own server, with AI that works inside the owner's bounds.
Draft TM2610200001 Pending payment
Held for you; confirmed once payment is received. Your route on the 20th looks clear.
A stay is a chain of hand-offs. The guest notices every gap.
Most independent properties stitch together a reservation system, a booking engine, channel managers and a chat tool, each with its own login and bill. Nobody sees the whole stay.
Separate vendors a typical property stitches together, each with its own login and bill
Online travel channels whose rates and availability must stay in step
Languages guests write in: Bahasa Melayu, English and Mandarin
Mainstream hotel platforms that, to our knowledge, check a guest's route for rain, floods, landslides, road closures or rough seas
Typical figures for independent properties in Malaysia, not measured at one property.
Six stages of a guest's stay
In Malay, English or Mandarin
Rain, floods, roads and sea
Halal food, prayer places, the day
Availability, price, a held draft
Rooms, tasks and faults
Reputation and market
Record it once
Room types, rates, facilities and eateries set once, and used by the concierge, the planner and the pricing view.
Check before you sell
Heavy rain, floods, landslides, road closures and sea conditions decide whether a guest can arrive and what they can do. They belong in the same answer as the price.
Show where it is
Every booking has a code and a status, and every service reports its own health.
One install. Operations plus intelligence.
Tetamu is Malay for guest. TETAMU runs a property's daily business and adds an AI layer built on the same records. Each property gets its own copy, on its own server.
One property, one server
Guest, booking and operating data stay on the property's own server.
Bounded AI
Aina reads, prepares or escalates; PANTAU recommends inside the owner's band.
Configured, never forked
Channels, thresholds and schedules set on admin pages.
Degrade, do not break
If one service is down, the others carry on and the gap is shown honestly.
The owner sets the bounds. AI works inside them.
Price bands, autonomy levels, scan limits and allowed hosts are settings the owner holds. The concierge can prepare a booking but never confirm or charge one.
A concierge that checks before it answers
Aina answers guests in their own language from the property's live records, not a fixed menu. It checks availability, the journey and promotions, finds halal food and prayer places, drafts bookings and plans trips.
Three languages
Bahasa Melayu, English and Mandarin, answered in kind, on the web and on WhatsApp.
Live availability
Room types, dates and prices checked against the property's own system, matching what the guest actually asked for.
Drafts, never confirms
A booking is drafted at once with a code and held until payment confirms it.
Journey-aware
Asks OMBAK about rain, floods, landslides, roads and the sea before reassuring a guest about an arrival date.
Halal and prayer
Finds halal-certified eateries and the nearest masjid or surau, with prayer times, and hands over to the trip planner.
Escalates to people
Complaints, refunds and sensitive matters go to staff on record, logged.
Aina's tiers
| Aina may | Aina may not |
|---|---|
| Read rooms, rates, facilities, eateries, promotions and policies | Confirm a booking or take a payment |
| Prepare a draft reservation with a code | Change a price or grant a discount outside a live promotion |
| Plan trips and check the journey | Promise a safe journey when a warning check failed or a warning is in force |
| Escalate complaints and refunds to a named person | Decide a complaint or a refund itself |
The evidence rule
Answers are grounded in the property's own records and live checks, never generic knowledge. A check that could not run says so instead of reassuring.
Can the guest get here, and get around?
Weather and access decide a stay as much as the room does. OMBAK reads official weather warnings, flood and landslide alerts, road and traffic advisories and, where relevant, sea conditions, and turns them into one plain-language assessment for the guest's route and dates.
Heavy rain and storms
Official warnings for heavy rain, thunderstorms and strong winds along the route and at the destination, with timing.
Floods and river levels
Flood warnings and river levels near the property and the roads leading to it, especially during the monsoon.
Landslides
Landslide warnings and slope-risk advisories for hill and highland routes after prolonged rain.
Closures and accidents
Road closures, accidents, road works and heavy congestion reported on the guest's likely route.
Crossings
Wave height, wind and marine warnings for islands and coastal trips, where a property needs them.
Haze and heat
Air quality and heat advisories that change what is sensible to do outdoors.
How a journey check works
From the guest's origin or nearest hub to the property
Warnings, advisories and forecasts for the route and dates
Plain-language rating per hazard, with source and time
Best time to travel, an alternative route, or a warning to wait
Re-checked before arrival; guest and staff alerted on change
Alerts before arrival
If a warning appears on an arriving guest's route, Aina messages the guest with options, and the front desk sees it on the ops board.
Feeds the trip planner
Today's conditions decide which activities stay in the plan and which are swapped for safer ones.
Never a false reassurance
Every assessment shows its source and time. If a warning feed cannot be reached, OMBAK says the check failed. Aina will not tell a guest the road or the sea is clear on a guess. Sources are official where available, plus the operator's own local contacts.
An itinerary that adapts to the day
The trip planner turns a guest's interests into a day-by-day plan, built from the property's own list of places, halal food and prayer places nearby, live conditions and the guest's needs, and keeps it current during the stay.
Who is travelling, and how
Party size, children or elderly guests, mobility, pace, budget and interests. Dietary needs are asked, never assumed.
Day by day, in the right order
Places, eateries and activities from the property's curated list, ordered by distance, travel time and opening hours.
Re-plans when conditions change
Heavy rain swaps a hill trail for an indoor visit; a road closure re-routes the day; a rough sea moves the island trip.
Halal food and prayer, built in
Eateries labelled honestly
Halal-certified, Muslim-owned and Muslim-friendly are shown as different labels, never merged. The property confirms its list; status is shown with its source.
Nearest masjid and surau
Distance and travel time from wherever the guest is in the plan, including surau at attractions, malls and rest areas.
Built into the day
Local prayer times for each stop; Friday plans leave time for Jumaat prayers. Included only for guests who want it.
Every choice shows its reason. Activities, transport and rentals are bookable through connectors, and the plan is sent by WhatsApp or PDF and updated when it changes.
Rooms turn over without phone calls
TETAMU Core holds the property's rooms, rates, availability, reservations, guests and staff, and the ops board moves housekeeping and maintenance through verified steps.
Rooms and rate plans
Room types, units, plans, seasonal overrides and maintenance blocks.
Reservations
Codes, status, room assignment and holds, from draft to check-out.
Housekeeping
Check-out creates a task; the room stays off same-day sale until verified.
Maintenance
Faults become tickets with owners, and rooms go out of order until fixed.
Notifications and scheduling
Who is told what
Rules decide which staff hear about which events, by e-mail or WhatsApp, with recovery notices.
Scheduler
Scans, checks and reports on intervals the property sets, calling only allow-listed hosts.
Activity log
Who did what and when, across the front desk, housekeeping and the owner.
Know where you stand, price inside your band
PANTAU watches comparable properties and public mentions, reads the property's own history, and recommends prices with its reasons, always inside the band the owner sets.
A comparable stay is sold out for these dates, a school holiday starts in 12 days, and this week is historically strong.
| Autonomy | What PANTAU may do |
|---|---|
| Advisory only | Recommends with reasoning; the owner approves. The default for every new property. |
| Auto-promo | Starts or ends promotions inside the band; base rates still need approval. |
| Full auto | Runs pricing and promotions inside the band, for owners who have seen it work. |
The same minimum and maximum apply at every level. PANTAU can never price outside the band.
What it reads
Comparable stays
Found from public web search on a self-hosted engine, approved by the owner before they are watched.
Reputation
Mentions and reviews gathered across sources into one summary, using the operator's own review account.
Public data only
Never another property's private data. Every recommendation shows the evidence it used.
Configured by the operator. Never hard-wired.
Properties differ in rooms, rates, channels and guests. TETAMU keeps one platform and lets each operator configure what is theirs, with the right person holding each control.
| Layer | What changes | Who holds it |
|---|---|---|
| 1 · Knobs | Scan and check intervals, alert thresholds, recovery notices, housekeeping settings | Property administrator |
| 2 · Rules | Who is alerted about what, price minimum and maximum, competitor approval, halal mode, which hazards OMBAK watches, the curated places list, allowed hosts | Owner |
| 3 · Structure | Room types and counts, rate plans, facilities, eateries, brand colours, timezone, currency | Owner or revenue manager |
| 4 · AI behaviour | Which model each module uses, and PANTAU's autonomy level | Owner with platform administrator |
| 5 · New connectors | A ferry operator, a rental provider or a new channel | S.A.L.T CI engineering |
One platform, many kinds of property
Sea crossings, ferry connectors, halal-aware planner.
Road and flood checks, more room types, channel manager first.
Rates, channels and Aina as the front door; curated local itineraries.
Few units, WhatsApp-first, landslide and road checks for rural routes.
Setup wizard
A new property is onboarded by configuration, with no code change.
Operator-owned keys
Each operator brings its own review, mail and WhatsApp accounts, stored encrypted.
Safe defaults
Every new property starts with AI in advisory mode.
Sell everywhere, never sell a room twice
TETAMU connects the property to the channels guests already use, and closes the loop from booking to payment, receipt and Malaysian e-invoice.
Channel manager
Rates and availability kept in step across Booking.com, Agoda, Expedia and Airbnb.
Branded booking page
The property's own booking page and chat widget, in its brand colours.
Payment collection
Payment through the operator's chosen Malaysian gateway confirms the held draft.
Receipts and e-invoice
Receipts to guests, and e-invoices in the format required by LHDN.
Guest messages
Confirmation, reminders, journey alerts and itinerary updates by e-mail and WhatsApp.
One source of truth
Every channel reads the same availability in TETAMU Core.
From question to checked-out guest
Answers and drafts
Confirms the booking
Availability updated everywhere
Guest and staff told
Room prepared and verified
Receipt and e-invoice
Tested without touching real money
Payment and messaging flows are developed against the S.A.L.T CI Sandbox, which speaks the same APIs as real Malaysian gateways, mail and WhatsApp. Going live is a change of address and keys.
The property's data stays with the property
Reservations, guests, conversations, reviews and the activity log live in the property's own databases. AI calls pass one gateway, pointed at the models the operator chooses.
Web chat, WhatsApp or booking page
Core and services
One route to AI
The operator's choice
Weather, hazard and road advisories, maps, web search; read only
One install per property
One container deployment on the property's own server or a hosted server of its choice. Nothing is shared between properties.
Secrets out of code
Environment files and encrypted stored credentials; operator keys never leave the property.
Calls stay on the list
The scheduler calls only allow-listed hosts, checked on save and on every run.
Access you control
Staff roles in Core and protected settings panels, over HTTPS.
Visible health
Every service reports its health, checked every five minutes.
Backups
Database backups with tested restore, and key rotation.
Five questions for any hospitality vendor
The answers matter more than the demo.
| Question | TETAMU answer |
|---|---|
| Where do guest data and AI run? | On the property's own server. AI calls pass one gateway pointed at the models the operator chooses. |
| Who changes the setup: you or the vendor? | The operator, from admin pages: alert rules, schedules, price bands, facilities and models. |
| Can every AI action be bounded and traced? | Yes. The concierge cannot confirm or charge, PANTAU stays inside the band, escalations are recorded, and failed checks are reported as failed. |
| Does it fit local guests and conditions? | Three languages, halal food and prayer places that ask first, Malaysian time throughout, local payments and e-invoice, and journey checks for rain, floods, landslides, roads and the sea. |
| Is it one more silo? | Part of S.A.L.T CI, sharing the same gateway, models and search as the rest of the family. |
How it compares
| Capability | Typical local PMS | Global channel suites | TETAMU |
|---|---|---|---|
| Channel manager and e-invoice | Yes | Add-on | Yes |
| Concierge that checks live data | Rule-based FAQ | Chat drafting | Agentic, grounded |
| Journey and weather intelligence | None | None | OMBAK |
| Itinerary that re-plans with conditions | None | None | Trip planner |
| Data residency | Vendor cloud | Foreign cloud | Property's own server |
How to compare fairly
Give each vendor the same monsoon arrival: route check, three days with halal meals and prayer stops, a room booked. Run it on the property's own server, then cut the network.
Part of one sovereign platform
TETAMU runs on the TERAS core with the same sign-in, audit and models as every other S.A.L.T CI application.