QR Codes

A QR Code in EmberX is the physical-to-digital bridge. It encodes a unique URL that, when scanned, automatically identifies the location and routes the guest to the correct Service Center — no app download, no login required.

How a QR Code Works

Each QR Code contains a unique token that maps to a specific Location + Service Center combination:

QR Code Token: "abc123"
  └── URL: https://app.emberx.app/chat/abc123
        ├── Location: Room 101
        └── Division: Reception

When a guest scans this code:

1. Their browser opens the chat URL
2. EmberX reads the token to determine which Location and Division to use
3. A Guest profile is created (or matched) from the device fingerprint
4. A Conversation is opened inside the linked Division

Creating a QR Code

1. Navigate to QR Codes in the main sidebar
2. Click Generate QR Code
3. Configure the QR:
   • Location — Select the physical location (required)
   • Service Center — Select which Division handles requests from this QR (optional — falls back to the system default if not set)
   • Description — Optional label to help identify the QR (e.g., “Room 101 – Door QR”)
   • Priority — Numeric priority for routing (higher = processed first if multiple rules apply)
4. Click Generate

The system creates a unique token and displays the QR code image ready for printing.

Printing and Deploying QR Codes

After generation:

• Download the QR code image (PNG format)
• Print and place it in the physical location (door, wall, table)
• Test by scanning with a phone to confirm the correct Division receives the conversation

Multiple QR Codes per Location

You can create multiple QR codes for the same location, each pointing to a different Service Center. For example, Room 101 might have:

• A door QR → Reception (general requests)
• A desk QR → Room Service (food & beverage orders)

QR Code Status

Status	Behavior
active	Scanning opens a conversation normally
inactive	Scanning shows an error — no conversation created

Deactivate a QR code when you need to temporarily stop accepting requests from a location (e.g., room under maintenance).

The Division Fallback

The Service Center (Division) field on a QR code is optional. If left empty:

• EmberX checks the system Settings → Urgent Division as the fallback
• If no fallback is configured, the conversation may be unrouted

Best practice: always assign a specific Division when generating QR codes.

Token Security

QR code tokens are:

• Globally unique — each token maps to exactly one QR code
• Persistent — the token does not change after generation (safe to print)
• Not secret — the token only routes the conversation; it does not grant any privileged access

License Limits

The number of active QR codes is controlled by the maxQrCodes license setting. The QR Codes page shows current usage versus the allowed limit. Inactive QR codes do not count toward the limit.

Deleting a QR Code

Deleting a QR code permanently removes the token. Any printed QR codes with that token will no longer work. Consider setting the status to inactive instead of deleting if you may need to reactivate later.