Demo Accounts

A demo account lets you try Jonot with no card and no contract. Activate one at join.jonot.io and you get a fully working organisation — every feature turned on — sized down to a rate and a term that make it obviously a demo rather than a production deployment.

Limits

Limit	Value
Locations	1
Queues per location	1
Paired devices (kiosk, display, desk)	3
Tickets	4 per fixed 4-hour window
API tokens	1

Nothing else is scaled down — a demo org has webhooks, custom branding, custom sounds, marketing screens, customer feedback, analytics, and the read-only /v1 API, exactly like a paid plan. Only these five numbers are capped.

Ticket limit: 4 per 4-hour window

If joining a queue fails with a message that the demo’s ticket allowance is used up, you’ve hit this cap. It’s a rate, not a daily quota — but the window is fixed, not a rolling look-back from your first ticket. Each day’s windows start at 00:00, 04:00, 08:00, 12:00, 16:00, and 20:00 UTC, so the allowance resets at the next of those boundaries regardless of when your first ticket in the window was issued. A demo that issues 4 tickets at 03:50 UTC can issue 4 more at 04:00 — it doesn’t need to wait four hours from 03:50.

What’s included

A demo organisation has every feature enabled, at the limits above:

• Webhooks — configure and inspect real payloads; deliveries are simulated rather than sent (see below).
• Custom branding — logo, colors, fonts, and corner radius across the display, kiosk, and customer screens.
• Notification sounds — call chimes and the hard-of-hearing call cue.
• Marketing content — text messages and image banners on the display and customer screens.
• Customer feedback collection.
• Analytics, in the admin panel’s usual dashboards.
• The read-only /v1 API, with a demo-specific quota and export marking — see Simulated webhooks and the read-only API below.

The DEMO watermark

Every customer-facing surface a demo org can produce is marked as a demo, and the marking is not something you can turn off from the admin panel:

• Customer ticket page: DEMO — this is not a real queue
• Kiosk: DEMO — this is not a real queue
• Display: a DEMO ribbon
• Printed kiosk tickets: DEMO — not a valid ticket

This exists so that a real end customer scanning a demo QR code can never mistake it for a live queue. The marking is server-driven — it doesn’t depend on anything you configure, and it can’t be styled away with custom branding.

Caution

Your own copy on customer-facing surfaces — including a location’s printed ticket header and footer text — may not contradict, obscure, or instruct a customer to disregard the demo marking. Doing so is grounds for immediate termination of demo access. See Terms and privacy below.

Simulated webhooks and the read-only API

A demo org can configure webhook endpoints exactly like a paid org, but deliveries are simulated: Jonot records what it would have sent and shows it in the delivery log with a Simulated badge, but the request never leaves Jonot. This lets you wire up an endpoint and inspect real payload shapes without a demo firing at your production system. Converting to a paid plan is the only way to start delivering for real — see the Webhooks guide for endpoint setup and payload formats.

The read-only /v1 API works the same way with a lighter touch: it’s fully functional, but demo orgs are additionally capped by a small daily request quota on top of the usual per-minute rate limit, and CSV exports carry a demo- filename prefix and an extra demo column so an exported file can’t be mistaken for production data. Details and the exact quota are in Demo organisations in the API reference.

Term, extension, and data deletion

A demo account runs for 14 days from activation.

The one-time extension

You can extend a demo once, for a further 14 days, from the billing page in the admin panel in the final days of your term. It works exactly once — there’s no second extension and no separate renewal purchase. If you don’t extend, or once you’ve used your one extension, the term ends automatically and the deletion schedule below begins.

Note

Jonot may, at its own discretion, grant a particular demo longer access than this (for example for a trade show or partner pilot). That’s not something you can request through the product — don’t assume longer access is available on request.

Data deletion schedule

None of the following is recoverable — there is no export-after-the-fact.

• Live ticket data is deleted approximately 24 hours after it’s created.
• A demo missing a location or a queue is deleted approximately 48 hours after creation. Logging in and exploring the admin dashboard don’t count — setting up your first location and queue (the same first step every paying customer completes) is what keeps the org alive past this point.
• The whole organisation and everything in it — locations, queues, devices, staff, and any remaining ticket history — is permanently deleted approximately 7 days after the term (including any extension) ends.

Danger

Fully extended, a demo’s maximum possible lifetime is 14 + 14 + 7 = approximately 35 days from activation. You’ll get a warning email 2 days before the final, irreversible deletion.

Converting to a paid plan

From the billing page (see Billing and Plans), choose Starter or Pro and complete checkout — the same flow as a brand-new paid signup, run through our payment provider. Once checkout completes, the demo restrictions lift immediately: the watermark stops appearing, the limits above are replaced by your new plan’s limits, webhook deliveries start going out for real, and the deletion schedule no longer applies. Your existing locations, queues, and devices carry over unchanged.

Terms and privacy

A demo account has no fee, no contract for the supply of a paid service, and no service-level or support commitment. The full demo terms — the term and its single extension, the deletion schedule, non-production use, and the volume limits — are in the Terms of Service. Data handling for demo orgs, including how end-customer data inside a demo is processed and retained, is covered by the Privacy Policy and the Data Processing Addendum.