Give your merchants QR check-in, without building it.
InQ is a white-label SDK you build into your POS or app. Your merchants get anonymous QR check-in and a live queue, and their customers get a “your turn” alert on their phone. It ships as your feature, under your brand, in days instead of months.
U.S. Patent No. 10,984,389
[Customer logo]
[Partner logo]
A feature your merchants want, without the build
Answer a top merchant request
Restaurants, clinics, salons and service counters all want waitlists and check-in. Give it to them inside the product they already use, with no pagers or extra hardware.
Ship in days, not a quarter
No QR, encryption, notification or queue infrastructure to build or maintain. Your roadmap gets the feature; your engineers stay on your core product.
Your brand, your relationship
It's white-label, so it ships as your feature. We never contact your merchants or their customers.
Stand out on privacy
Anonymous, patented check-in that keeps customer data on their own phone. It's a differentiator your merchants can explain to their customers in one sentence.
From SDK to your merchants in three steps
No separate app for your merchants' customers to download, and no queueing infrastructure for your team to maintain.
Integrate
Your developers add the InQ SDK (iOS, Android, web) to your POS or app, or call our REST API. A basic integration takes under 40 lines of code.
Configure
Set queue rules for each merchant and location, choose how customers are alerted (on their phone by default, or by text or email if they opt in), and apply your branding. Every screen stays in your design system.
Roll out to your merchants
Switch it on for your merchants. Their customers join the line and get a unique, encrypted QR code. When it's their turn, their phone gets the alert. They scan in, and your system gets the check-in event.
One check-in, two views
Your merchants' customers see their place in line. Your merchants' staff see a live, verified queue. Both views live inside your product. (Example screens shown.)
Every line runs on the same three calls.
A restaurant waitlist, a clinic waiting room and a permit counter look nothing alike from the front. Underneath they're the same: issue a code, advance the queue, and listen for the check-in.
- QR generation, encryption and code rotation handled for you
- Alert delivery to the user's phone, plus optional text and email
- Queue state machine and real-time sync with no infrastructure to run
- Plugs into your POS or app; your merchants keep the workflow they know
// 1. Add a guest to the queue: InQ issues an encrypted code const ticket = await inq.join({ queueId: "harbor-grill-main", notify: "device" // anonymous by default }); // 2. Advance the queue from your host / staff screen await inq.callNext("harbor-grill-main"); // → guest gets "Your table is ready" automatically // 3. Listen for the verified check-in inq.on("checkin", (event) => { seatGuest(event.ticketId); });
The whole flow in about a minute
What your merchants' customers experience: check in with a code, wait wherever they like, get the alert, get seated.
Your team has better things to build than queueing.
Your merchants are asking for waitlists and check-in. Doing it properly means QR generation, encryption, code rotation, notification delivery and a queue state machine. That's a quarter of engineering on something that isn't your core product. InQ has already solved it.
Average time to integrate, versus months to build in-house
Source: [internal data / customer]Lines of code for a basic integration
Less front-desk check-in time for merchants using InQ
Source: [pilot venue / case study]Everything the line needs, built into your product
Simple SDK & API
Clean, documented SDKs for iOS, Android and web, plus a REST API for backend or legacy integrations.
White-label by default
Your brand stays front and center. It ships as your feature, and we never contact your merchants or their customers.
Encrypted, rotating codes
Every QR code is unique to one customer, encrypted and rotated, so nothing can be shared or copied.
Real-time alerts
“You're up” alerts reach the customer's phone the moment staff advance the queue. Text or email is available when a customer chooses to share their details.
Built-in two-factor check-in
The code lives on the customer's phone and only that phone gets the alert, so a check-in proves it's the same person who joined. No password, no phone number.
Built for platforms
One integration serves every merchant and location on your platform, across every vertical you support.
One integration. Every vertical your merchants are in.
Examples of how platforms can build it in. The SDK isn't limited to these: if your merchants' customers wait for something, InQ can run the queue.
Any POS or App
Ship queueing as your feature, not ours.
Learn more →Restaurants & Bars
Waitlists that don't hand out pagers.
Learn more →Clinics & Pharmacies
A waiting room that isn't full.
Learn more →Government Services
High-volume counters, without the lobby.
Learn more →Salons & Service Desks
Walk-ins that don't have to sit.
Learn more →Pickup & Delivery
Handoffs without the crowd at the counter.
Learn more →Anonymous by default. No ads. No data resale.
Your merchants' customers keep their information on their own phone unless they choose to share it. That makes InQ easy for your security team to approve, and easy for your merchants to trust.
Stays on the phone
Customers join anonymously. The queue runs on an encrypted code and check-in timestamps. A name, phone number or email is shared only if the customer chooses to give it.
Short-lived
Queue data is kept only for the active session, then deleted or anonymized, unless you configure a different retention period.
Never shared
No ad networks, data brokers or third-party marketing anywhere in the pipeline.
Codes stay private
QR codes are encrypted, unique per user and never exposed publicly.
Questions platforms ask us
How do we integrate InQ into our POS or app?
InQ is available as an SDK for iOS, Android and web, and as a REST API for backend integrations. Most teams have a basic integration live within about a week.
How much engineering work is it on our end?
Far less than building it yourself. You build the screens your merchants and their customers see, in your own design, and wire up a few SDK calls. We handle QR generation, encryption, rotation, notification delivery and queue state.
Can one integration serve all of our merchants and locations?
Yes. You integrate once, then set up queues for each merchant and location from your side. The same integration works across every vertical you serve.
Can we keep our own branding?
Yes. InQ is white-label all the way down. Our name never appears in your app, and we never contact your merchants or their customers.
What data does InQ keep about our merchants' customers?
By default, none that identifies them. Customers join anonymously, and their information stays on their own phone. The service works with a unique identifier, an encrypted QR code, and queue status and check-in timestamps. If a customer chooses to share a phone number or email (for example, to get a text instead of an in-app alert), it's used only for that notification. Queue data is kept for the active session, then deleted or anonymized, unless you set a different retention period. It's never sold or shared.
Will it change how our merchants' staff work?
Very little. Staff advance the queue from screens inside your POS or app that they already use, and your system listens for the check-in event.
How is InQ priced?
We're finalizing platform pricing now. Tell us about your platform and merchant base, and we'll work out terms that fit.
Is there a sandbox or trial?
Yes. During evaluation, your engineers get sandbox access: a separate test environment with its own keys, where they can build and test the full check-in flow with test data before anything reaches your merchants. Request a demo to get access.
Is the technology patented?
Yes. InQ is built on U.S. Patent No. 10,984,389, “Notification System,” issued April 20, 2021, with priority dating back to 2013. The patent describes letting a person join a waiting list while disclosing only the personal information they choose, then receiving updates on their own phone: the same anonymous-by-default check-in your merchants' customers use.
Ready to build InQ into your platform?
Talk to our team about integration timelines, partnership terms, and how InQ fits inside your POS or app.