Sik Sorulan Sorular

Open checkout, enter your transfer reference, and submit. Keep your receipt for verification.

Your pending payment remains in history so you can retry from the checkout screen.

Hotel name, city, contact details, default language, and logo should be filled.

Chat responses, weather cards, and help content quality drop; complete missing fields before launch.

Not only body, but header, menu, card, and text color tokens must switch to dark variant.

Keep frequent modules visible; secondary items like calendar or budget can be hidden from mobile quick menu.

Yes. Show and mini club screens should auto-open the active week tab.

If remaining time is over 15 minutes: Soon. Under 15 minutes: Countdown. After time passed: Ended.

Submission is blocked when selected party size is outside the configured range.

A dedicated success modal clearly displays confirmation and message details for better UX.

Type selection is required first to reduce invalid or ambiguous feedback entries.

Assign fixed color tokens per platform and verify contrast in both light and dark themes.

Horizontal scroll is often more stable for many columns. Card layout is optional but one standard should be enforced.

Manual salary entry is supported. Hour-based calculation can be disabled if not required.

Date range, category, status, and assignee filters should be primary defaults.

Yes. Linking is required to track activity-based material consumption accurately.

To keep messages clean, URLs are replaced with descriptive text labels and can be embedded behind phrasing.

Chat first checks available data. If no match is found, it returns a clear fallback with guidance.

Pagination keeps long history lists readable and improves performance.

Yes. While targeting users, message language should match their language code.

Use remaining-time badge in panel plus email and in-app warning notifications.

Yes. AI chat can be enabled per package and can also have quota limits.

User is redirected by role; language is resolved from user preference or company default.

Prefer .env storage; if database storage is mandatory, keep keys encrypted at rest.

Scrollable dialog class may be missing, or modal-body max-height/overflow rules may be overridden.

Clear browser cache, refresh session, and reset application cache files when needed.

FAQ and knowledge-base content is stored in dedicated translation tables with language fallback.