Keep front-of-house focused on the guests already in the room.
Trelinx handles reservation calls and WhatsApp, answers routine outlet and menu questions, checks availability, books tables, updates existing reservations and brings in the team for large groups or special exceptions.
The host is seating guests during a busy service.
“Table for six tonight at Katong at 7:30.”
Availability checked, table booked, reference returned.
Give Trelinx one routine reservation job.
You should not need instructions or a sales call to understand whether the product works.
“Table for six tonight at Katong at 7:30.”
What Trelinx can finish before front-of-house gets involved.
The goal is to absorb routine reservation work during service without creating another queue for staff to clear later.
Book a table
Check supported availability and create the reservation at the requested outlet.
Change the party size or booking
Preserve the existing reservation and update it when a valid alternative is available.
Answer menu, outlet and direction questions
Provide approved menu information, outlet context and directions without interrupting service.
Large group, event or policy exception
Collect the context and bring in the appropriate team member when the request needs judgement.
When judgement belongs to a person, Trelinx prepares the handoff.
Routine reservations should complete automatically. Large groups, special events and exceptions should arrive at staff already prepared.
Trelinx does the preparation
Before the handoff, the routine context can already be assembled so the staff member starts from the actual issue, not from zero.
The restaurant team owns the exception
Large groups, events, complaints, unusual policy exceptions and other judgement-heavy requests stay with the appropriate team member.
Every outlet can have different rules. HQ sees one operation.
Trelinx can keep outlet-specific hours, availability and policies in context while the group sees completed reservations and exceptions across locations.
Works with the systems that already run the front desk.
Trelinx should fit the operation, not force staff to rebuild it around another tool.
Reservation system
Check supported availability and create or change bookings.
Deposits & payments
Send secure deposit or payment links when the reservation workflow requires one.
Guest records
Keep relevant customer context and prior interaction history available.
POS & internal systems
Connect supported or custom restaurant systems when the workflow requires them.
Operational automation with visible boundaries.
Trust comes from clear rules, visible actions and the ability for people to take over when needed.
Designed around Singapore-region infrastructure for customer data.
Data collection, retention and customer requests are handled within the stated PDPA framework.
Conversations, actions, handoffs and outcomes remain visible in Command Centre.
Your rules determine where routine automation ends and people take over.
Start with one outlet. Scale when the operation is ready.
The same platform can expand to more locations without turning the first conversation into an enterprise project.
Launch offer including the platform, 1,000 voice minutes and 1,000 WhatsApp messages.
Scale when you need to
Additional outlets start at S$88/month. Usage and custom integrations scale separately, so the operating model stays visible.
Enough detail to carry the conversation internally.
Can Trelinx change an existing reservation?
Yes. The intended workflow finds the existing booking and updates details such as party size or time when a valid alternative is available.
What if the restaurant is full?
Trelinx should use the supported availability data and offer valid alternatives rather than inventing a table.
Can it handle large groups and events?
It can collect the relevant context and route the request, but large-group and event decisions should stay with the appropriate restaurant team when they require judgement.
Can it send menu or direction information on WhatsApp?
Yes. Messaging is useful for persistent links, menu information, confirmations and directions after the conversation.
Can different outlets have different opening hours and policies?
Yes. The multi-location model is designed around outlet-specific context while HQ keeps one operational view.
One reservation is enough to test the real product.
Call or WhatsApp the restaurant demo, book a table, then change the party size and see whether Trelinx preserves the booking context.