Skip to main content

Demo workspaces

A demo workspace is a full copy of Joryio for a trial, a sales demo or a training session: every feature works, campaigns send, journeys run, reports fill up - and no message ever reaches a real person by accident.

What is different in a demo​

  • Messages reach only members. Email, SMS, WhatsApp, Viber and push are delivered for real only when the recipient is a member of the organization (the people who log in). That includes Send test: a test to anyone else is simulated too. Everyone else receives a simulated delivery: the send is recorded, and over the next minutes and hours the report fills with simulated deliveries, opens, clicks and the occasional bounce or unsubscribe, at realistic rates. Every simulated row is marked as such. For push, a member's device is found through their email, their phone, or the app user id entered on their member record under Team & Access.
  • In-app messages are shown, not sent. There is no provider to hold them back: your app or website fetches them through the Joryio SDK and displays them. In a demo they therefore appear to anyone using an app or visiting a site that runs this workspace's SDK key - including the visitors of a connected store - not only to members, and their impressions and clicks are real, not simulated. To try in-app messages on a real store without showing them to its shoppers, target them at yourself with an audience filter (for example your own email).
  • Every channel works without credentials. A demo has no email, SMS, push or Viber credentials and needs none: the Create campaign menu offers those channels marked Demo, and every send on them is simulated for everyone, members included, because nothing can leave the platform. Attach real credentials to a channel and the member rule takes over: members receive real messages, everyone else stays simulated. The demo ships with a mobile app, Driftwood Goods app, so push campaigns have a target. WhatsApp needs a connected WhatsApp Business Account even in a demo, because its messages are Meta-approved templates.
  • Nothing else leaves the platform either. Data streams, warehouse syncs, webhook sends and store connections are off in a demo: a stream or sync cannot be created or resumed, a webhook step records a simulated delivery and the journey moves on, and connecting a real Shopify, WooCommerce or Magento store is refused, so no real customer ever lands in the demo. Joryio can open a specific demo to external connections when a prospect needs to see their own store or warehouse.
  • Alerts show in the app, not in an inbox. Monitoring alerts are still checked and still appear in the notification bell, the alerts list, the History log and the event-tracking banner, so you can show how they work. While the demo's external connections are closed they send no email - no first alert, no still-firing reminder, no resolved email - and alert webhooks are not called: the demo's data is invented and stops arriving, so an "events stopped" alert would otherwise email you about it. When Joryio opens a demo to external connections, real data is flowing and alerts email and call webhooks as usual. The same goes for the weekly digest: it is not sent while external connections are closed, because it would summarise invented data.
  • The data is fake. The workspace comes seeded with a few hundred people, their browsing and their orders, all invented: example.com addresses, fictional phone numbers, no real customer anywhere. The shop's orders, products and abandoned carts are real rows, so the E-Commerce pages work too. Your team can reset it to a clean state at any time. It also comes with sample content for a fictional business: a brand voice, designed emails, segments, campaigns that already went out with simulated results, push drafts, an in-app message and draft journeys. The demo data comes in industry flavours - a shop (Driftwood Goods), an online bingo site (Northlight Bingo), a hotel group (Harbour House Hotels), a gym chain (Ironline Fitness) or a Hebrew fashion store priced in shekels (MODA, written right to left) - so the events, attributes, segments and journeys look like your business; ask Joryio for the one that fits you.
  • A banner says so. Every page shows "Demo workspace" with the days left in the trial, so nobody mistakes simulated results for real ones. A channel with no sender set up (for example email with no sending domain attached) delivers nothing, not even to members: Launch Review names it for every channel a campaign or journey uses, says its messages will be simulated for everyone, and links to the page where its sender is set up.
  • Simulated rows are marked. Every simulated send or engagement carries a "Simulated" tag in the campaign recipients list, the recipient timeline, a person's activity timeline and the live event feed, and the $simulated property on the event itself.
  • A daily cap on real sends. A demo can send at most a couple of hundred real messages a day, and only to its members.
  • It ends. When the trial expires the workspace becomes read-only until it is upgraded; nothing is deleted. Joryio can extend the trial at any time, by up to a year from today, also after it has ended: extending a demo that became read-only because its trial ended opens it again.

Going live​

A demo becomes a live organization when Joryio support converts it, which needs two things in place: a verified sending domain and an active subscription. Until both exist the conversion is refused, so a fresh account cannot send to real recipients on its first day by mistake. Your data, segments, journeys and campaigns are kept.

For trainers​

Use the members list to decide who receives real messages during a session: invite the trainees as members, and every message they address to themselves arrives for real, while the rest of the audience stays simulated. Reset the demo data between sessions to start from the same state.