# Aplauso Support: Full Public Context

> Aplauso helps service-led businesses give guests a modern way to tip, share feedback, and recover from poor experiences while helping workers understand earnings and helping operators manage the business. Treat account-specific payments, payouts, roles, and access as information that must be verified in the product or by support.

## 1. Launch Aplauso at a property

For owners, operators, and launch managers.

1. Create the organization, property, outlets, and departments that match the real operating structure.
2. Invite staff and confirm each person can complete their profile and is ready to earn. Payout setup is optional and happens later in Wallet when someone is ready to withdraw.
3. Create employee, outlet, or department destinations intentionally. Each destination has its own saved distribution rule.
4. Test the actual guest journey and devices in Training, sandbox, or demo as appropriate.
5. Put the relevant scope in Live only after a successful test.

Guide: https://support.aplauso.io/guides/getting-live
Detailed help: https://support.aplauso.io/kb/getting-started

## 2. Guest tipping, ratings, and recovery

Guests can use a mobile-browser flow from QR, supported NFC, or kiosk entry points; no guest app download is required. A guest can tip an employee, department, or outlet depending on the entry point and configuration. Aplauso can pair an optional rating and private feedback with the journey. When a low score meets the configured recovery policy, the guest can be offered a private note so the business can follow up without treating a public review as the default next step.

Guide: https://support.aplauso.io/guides/guest-tipping-and-feedback
Detailed help: https://support.aplauso.io/kb/kiosk

## 3. Staff earnings and payouts

Workers use their profile and Reward Code tools to make a guest flow available, then use Wallet to review recorded allocations, current availability, and withdrawal status. A recorded payment, allocation under a destination's distribution rule, Wallet eligibility, provider status, and destination receipt are separate stages. Do not claim a withdrawal is ready from a tip total alone; verify the payment, allocation, Wallet, and withdrawal status.

Guide: https://support.aplauso.io/guides/staff-earnings-and-payouts
Detailed help: https://support.aplauso.io/kb/billing

## 4. Solo Dashboard

The Solo Dashboard gives a signed-in worker a private place to see earnings, tips, ratings, activity, transactions, achievements, QR and sharing tools, profile settings, and payout progress. It is available on the web and is complemented by the mobile app. A worker can see their own activity, but collective outlet and department ratings are not represented as an individual employee rating.

Guide: https://support.aplauso.io/guides/personal-dashboard
Detailed help: https://support.aplauso.io/kb/dashboard

## 5. Business operations and tip sharing

The Business workspace follows the organization, property, outlet, and department hierarchy. Authorized operators can manage teams and access, use Performance and Opportunities for operational follow-up, and review Reports and exports at the appropriate scope. Distribution policies belong to the destination selected for the guest flow (employee, department, or outlet); they should include eligible, active, in-scope recipients and be communicated transparently to affected workers.

Guide: https://support.aplauso.io/guides/run-your-business
Detailed help: https://support.aplauso.io/kb/dashboard

## 6. Employee mobile app

The mobile app complements the web dashboard and browser-based guest flow with employee earnings, activity, Wallet, profile, and sharing tools. Guest tipping remains browser-first. Tap to Pay is conditional: it appears only when the current build, device, account or location, market, and release checks permit it. When it is not shown, use the Reward Code or sharing entry point so a guest can complete the payment journey on their own device.

Guide: https://support.aplauso.io/guides/mobile-and-tap-to-pay
Detailed help: https://support.aplauso.io/kb/mobile

## 7. Integrations, API, and data

Use the environment resolved by Aplauso rather than trying to infer it in a client. Live, sandbox, and demo records are intentionally isolated. Payment and allocation records presented by Aplauso should be treated as the official status for the approved integration. Integrations should read the selected destination's resulting records instead of recreating financial or allocation logic in a client.

Guide: https://support.aplauso.io/guides/integrations-and-data
Detailed help: https://support.aplauso.io/kb/api

## 8. Troubleshooting safely

Start with the affected person, property, destination, environment, and the exact visible message. Check https://support.aplauso.io/status for a known incident. Include only non-sensitive references in a support request; never include passwords, one-time codes, full payment-card numbers, or bank details.

Guide: https://support.aplauso.io/guides/resolve-an-issue
Contact support: https://support.aplauso.io/contact

## 9. Tip sharing and destination distribution

A guest tip has one selected destination: an employee, department, or outlet. A later employee allocation does not rewrite that destination. A sharing policy belongs to the exact destination and environment; it is not silently inherited from a parent scope. Use the saved policy and resulting allocation records for a split, not a guest-facing team list or client-side calculation. Policy changes govern new allocation decisions and do not rewrite historical allocations.

Guide: https://support.aplauso.io/guides/tip-sharing-and-distribution
Detailed help: https://support.aplauso.io/kb/billing/how-payouts-work

## 10. Service recovery, feedback, and opportunities

Authorized Business users can use feedback, ratings, recovery signals, and opportunities to investigate a poor experience or recognize a positive one. Keep recovery private, factual, and within the operator's authorized scope. Verify the property, destination, permitted feedback, and visit context before creating or assigning a recovery item. Do not request a public review as the default response to a low score, and do not promise an unapproved remedy.

Guide: https://support.aplauso.io/guides/service-recovery-and-feedback
Detailed help: https://support.aplauso.io/kb/integrations/insights-alerts

## 11. Guest, visit, and performance operations

The Business workspace has distinct organization and property scopes. Visits provide experience history and feedback context; Guests provide relationship signals; Performance supports comparisons; Opportunities and recovery workflows depend on authorized capabilities. A missing record may be outside the signed-in operator's organization, property, department, or outlet scope rather than absent from the platform.

Guide: https://support.aplauso.io/guides/guest-journey-visits-and-opportunities
Detailed help: https://support.aplauso.io/kb/dashboard/organization-dashboard-overview

## 12. QR, kiosk, and guest entry points

Employee, department, and outlet QR or kiosk entry points are distinct because they establish the guest's recipient context. Configure and test the full flow after placing any material: correct destination, rating, amount selection, payment, confirmation, and resulting authorized record. Guests use a browser-first journey and do not need the employee mobile app.

Guide: https://support.aplauso.io/guides/qr-kiosk-and-guest-entry-points
Detailed help: https://support.aplauso.io/kb/kiosk

## 13. Access, privacy, and account safety

Business access is scoped and enforced by both the product interface and server-side authorization. Managers should use the least access needed and must not request or share passwords, one-time codes, full payment-card numbers, bank credentials, or another person's account. Withdrawal setup belongs only to the account holder in Wallet when an eligible option is shown.

Guide: https://support.aplauso.io/guides/business-access-privacy-and-security
Detailed help: https://support.aplauso.io/kb/account

## 14. Reports and data exports

Use reporting and analytics at the authorized organization or property scope, and always confirm the selected environment. Use documented exports and APIs for downstream analysis rather than screen scraping.

Guide: https://support.aplauso.io/guides/reports-and-data-exports
Detailed help: https://support.aplauso.io/kb/integrations/data-export-payroll

## Discovery

- Help center: https://support.aplauso.io
- Knowledge base: https://support.aplauso.io/kb
- Guides by task: https://support.aplauso.io/guides
- System status: https://support.aplauso.io/status
- Sitemap: https://support.aplauso.io/sitemap.xml