Skip to Content

← All guides

Mobile apps, QR & updates

Android hubs: TA5 FROZEN. Use RC1+TA8 (Colourcraft commercial) or RC2 1.9.x + TA13 1.13.x (tourism) · CareerWIL TA10 uses RC2 chat until dedicated TA10 hub. Planned TA11 i-Spaza.online · TA12 eHemp.online · merge TA14/TA15. Full chat features require register — guest web chat is demo only. Each product line self-updates only within its line. iPhone: /businessite/ios/install.

Download PDF How-to videos

Chat commands

show me apps · install … · scan qr · login to web · link my phone to web · Photo login /businessite/login · Logout → homepage · unlink phone · check for update · update now

1. Apps (Powered Apps) — product lines

  • show me apps — catalog + install
  • Homepage Powered Apps: download, QR under More info, rich HTML, Release history & notes
  • Filters: RC1 · RC2 · TA8 · TA13 · Education · 32/64-bit
LineVersionRole
TA51.6.xFrozen — inactive on catalog
RC11.7.xProduction RC for TA8 process (Colourcraft)
TA81.8.xCommercial Chat OS
RC21.9.xRC for tourism + next verticals
TA131.13.xTourism vertical hub (Afro Roots)
TA11 / TA12plannedi-Spaza.online · eHemp.online
TA14 / TA15plannedMerge verticals

check for update · update now · update later — each line only offers updates within its own line (RC1 never pulls TA13, etc.).

Filenames look like BusinesSite-RC2-64bit-1.9.0_1.apk so you never mix hubs.

2. Face selfie login (mobile hub)

  1. Registration stores your selfie as a pending face.
  2. At login, take a clear front-camera selfie. First time: you may be asked for a second selfie to confirm.
  3. Once confirmed, login compares live photo to your registered face.
  4. If auto-match fails: a support Access request is opened. Admin compares photos and can Grant (this confirms your face). Then tap Verify Photo & Login again.
  5. RC1: button Photo failing? Ask admin to approve login always files an Access request with your selfie.

Names: first name and surname are stored in proper case (e.g. thabo → Thabo) even if typed wrong.

3. Photo login on the web (multi-profile)

On any public computer you can open /businessite/login (or the homepage Photo login (web) button) without scanning a QR first.

  1. Enter phone, industry, occupation, mother tongue, and a live selfie.
  2. Support reviews an Access task (compare login photo vs profile photo) and may grant, block, or flag fraud.
  3. Grant opens a timed web session and full chat. Logout returns to the homepage (/businessite?logged_out=1).

Use this when several people share one browser, or when the phone QR is not available.

4. Scan QR → full chat on the web (users)

Use the same BusinesSite phone profile in a browser without re-registering. Public pages start in Demo Mode until you scan; after link you get the full dashboard.

  1. Install and log into a BusinesSite hub (RC1, TA8, RC2, TA13, or iOS — not frozen TA5) with phone + selfie.
  2. On the computer, open https://businessite.online/businessite (large homepage QR) or /businessite/chat and leave that tab open (status: waiting for scan).
  3. On the phone, in chat say: login to web · scan qr · link my phone to web · sync to web · web login (or tap the Login to web chip).
  4. Allow camera permission. Point at the browser QR (businessite://web-chat-sync?session=…).
  5. Phone shows linked. Browser shows Linked as Your Name, then opens /businessite/chat?linked=1 — the full chat (header with your name/phone, quick chips, voice, 📎 Photo). You should not stay on the yellow “Demo Mode - Limited Access” banner.

Shared history (web ↔ mobile)

After link, both sides use the same phone timeline (/businessite/chat/history). Web polls every few seconds; mobile syncs on open and in the background. Messages you send on web (e.g. product photo success) appear on the phone and vice versa. Avoid force-stopping the app if you want background update alerts.

Unlink / logout on web

  • In full chat header: Logout — ends photo-access and/or Odoo web session and returns to the public homepage.
  • Unlink phone (confirm) — disconnects QR web-chat link only; mobile app profile stays.
  • Or open /businessite/logout or /businessite/unlink_web_chat_session?redirect=1.

Tips: Scan the QR on the same tab that is still open (do not close it mid-scan). If stuck on demo after link, hard-refresh or open /businessite/chat?linked=1. Cancel the scanner on the phone anytime.

5. Accessibility while using web

Use the bottom bar: switch language, Read page (TTS), Voice nav. See guide languages.

6. Scan QR → support desk on mobile (providers)

Support agents can open the same desk on phone or use full web chat after linking:

  1. On the web, open /businessite/support/profile (logged-in support) or link via homepage/chat QR as above for full web desk.
  2. In the BusinesSite app, scan qr / login to web and scan that code.
  3. Then use support desk, my tickets, next ticket, reply: …, mic for voice — owner-only delivery.

See also guide support.

7. Closed-app update alerts

  • Allow notifications and (Android) set battery to Unrestricted for BusinesSite.
  • Open the app once after install so background poll (WorkManager) arms.
  • Tray alerts for new hub builds appear while the app is closed (best-effort poll). True kill-state push needs FCM server key on the server.
  • Reply got it after installing to clear the nag.
Leave any multi-step flow: say stop or cancel. Say continue to stay.