Anyone who needs help right now

Resolve access, payment, kiosk, and data issues

Use a calm, evidence-first support path for the parts of Aplauso that need the most careful diagnosis.

Start with the exact scope: person, property, destination, and environment.

Avoid sharing passwords, card numbers, bank details, or verification codes in a ticket.

For payment questions, capture the time, amount, and non-sensitive reference rather than relying on a screenshot alone.

The practical path

1
Check the status page for a known platform incident.
2
Confirm the signed-in account, selected property, and live/training/demo environment.
3
Reproduce the issue once and note the exact action and visible message.
4
Use the relevant guide for the product area.
5
Contact support with the non-sensitive details needed to investigate.

Common questions

What should I include in a support request?

Include what you were trying to do, the time it happened, the affected property or destination, the environment, and any non-sensitive identifiers. Never include passwords, full card numbers, or one-time codes.

Where should I check for an outage?

Start with the Aplauso status page. If no incident is listed, submit a request with the scope and steps to reproduce.

Go deeper with the knowledge base

Use the detailed guide that matches your workflow, or ask the Aplauso assistant a specific question.

Check system status Troubleshooting guide Contact Aplauso support Contact support