Demo Accounts

A demo account lets you try Jonot without a card or contract. The account includes every feature, but has lower limits and a fixed end date because it is not for production use.

Start a demo

You can start a demo in either of two places:

• Signup wizard — in step 3 at join.jonot.io, choose the Start a 14-day demo link below the plan cards. See Create your account.
• Billing page — if your organisation has no plan yet, the billing page in the admin panel shows a Try it free section with a Start a 14-day demo button.

Each email address can start one demo, and Jonot refuses disposable email domains. Jonot asks for a quick verification check before it starts the demo. When Jonot has reached its daily demo capacity, you must try again later.

Limits

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

Nothing else is limited. A demo organisation 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 you cannot join a queue because the demo ticket allowance is used up, you have reached this limit. The limit applies to fixed four-hour windows, not to a rolling period that starts with the first ticket. Each day’s windows start at 00:00, 04:00, 08:00, 12:00, 16:00, and 20:00 UTC. The allowance resets at the next boundary. For example, a demo that issues 4 tickets at 03:50 UTC can issue 4 more at 04:00 UTC.

The first two windows after activation allow 10 tickets each, so you can test your set-up before the limit drops to 4.

Walk-up tickets that you add at a desk count towards the same allowance as tickets that customers join with. When the allowance is used up, the desk shows a message with the time it resets.

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.

A demo organisation emails a staff invitation only when the invited address already belongs to one of its org-managers. Any other invitation is created but not emailed, and the team list labels it Not delivered — demo.

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

The marking prevents a customer who scans a demo QR code from mistaking it for a live queue. The server controls the marking. Your settings and custom branding cannot remove it.

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 organisation can configure webhook endpoints in the same way as a paid organisation, but deliveries are simulated. Jonot records what it would send and shows it in the delivery log with a Simulated badge, but does not send the request. This lets you configure an endpoint and inspect real payloads without contacting your production system. You must switch to a paid plan to send webhooks. See the Webhooks guide for endpoint setup and payload formats.

The read-only /v1 API is fully functional, but demo organisations also have a daily request quota on top of the usual per-minute rate limit. 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 counted from the day you click the extend button, not from the original end date. Jonot offers the extension only when all of these are true:

• The demo has issued at least one ticket.
• The term ends within 3 days, or it ended less than 7 days ago and Jonot has not yet deleted the organisation.
• You have not extended the demo before.

Only org-managers can extend a demo. The Extend by 14 days button appears in the demo banner on the dashboard and on the billing page. You cannot extend a second time or buy a separate renewal. If you do not extend the demo, or the extension ends, the deletion schedule below begins.

Note

Jonot may give a specific demo more time, for example for a trade show or partner trial. You cannot request more time through the product. Do not plan on receiving it.

Data deletion schedule

You cannot recover or export this data after Jonot deletes it.

• 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 at the last possible moment, a demo’s maximum possible lifetime is 14 + 7 + 14 + 7 = approximately 42 days from activation: the term, the period in which you can still extend, the extension, and the final period before deletion.

Jonot emails the demo owner up to three times and sends each notice only once: 3 days before the term ends, when the term ends, and 2 days before the final, irreversible deletion. If you extend late, Jonot does not repeat a notice it already sent.

Converting to a paid plan

On the billing page, choose Starter or Pro and complete checkout. See Billing and Plans. When checkout finishes, the demo restrictions end immediately. The watermark disappears, your new plan’s limits apply, webhooks start sending, and the demo deletion schedule stops. Your existing locations, queues, and devices remain 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.