QwikPass
QwikPass by YK BuildsContact & onboarding

Start the right QwikPass path for your restaurant.

Create an Organization directly, review an Enterprise rollout, or use the verified security mailbox for account, privacy and security requests.

Self-service onboarding

Independent restaurant

Start Open Access without a card, then configure the Business, Outlet, menu, invoice settings and staff access.

Create an Organization
Custom rollout

Restaurant group or high-volume Outlet

Review the measurable first deployment, contracted capacity, integration and governance boundary before wider rollout.

Review Enterprise
Verified mailbox

Security, privacy or account access

Email from the verified owner or staff address and include only the minimum Organization reference needed. Never send passwords, OTPs, private tokens or card details.

security@qwikpass.in
For faster routing

Include the Organization and the action you need—nothing sensitive.

Choose the matching path and send only the minimum context needed to locate the workspace. These are service targets for the current pilot, not a contracted Enterprise SLA.

ImmediateTicket number and private tracker
1 business daySecurity or account acknowledgement target
2 business daysGeneral support reply target
  • Organization name and QwikPass subdomain when relevant
  • Your relationship to the Organization
  • A short description of the issue
  • Safe order, invoice or pass reference only when needed
  • No password, OTP, payment credential or private capability link
Security and privacy cases are routed separately. Support-call consent is optional and never becomes marketing consent.
Public and customer support

Create a trackable QwikPass case.

Use this form for guests, public requests or when you cannot enter a workspace. Signed-in restaurant staff should use Report an issue inside their workspace so Organization and error context are attached securely.

Keep credentials privateNever send passwords, OTPs, UPI PINs, card details or private invoice/pass links. QwikPass support does not need them.
Automated abuse checks and server-side limits protect this form.