← Full guide

Customer portal

A public link per repair — the customer sees live status and answers quotes without calling the shop.

What the customer sees

Publishing a repair creates a public page on OficinaOS Cloud with a redacted summary of the job. The page updates itself whenever the status changes in the app — the customer opens the link on their phone and always sees the latest version.

What the page shows:

  • Current repair status in plain language
  • Device and expected completion date
  • Timeline of events (received, in repair, ready…)
  • Pending quote with «Accept» and «Decline» buttons

What never leaves the shop

The portal publishes a redacted snapshot — only what the customer needs to see. Never on the portal: internal costs and margins, staff-only notes, other customers' data, team contact details, or history of other repairs.

The link is a per-repair secret (a random 16-character code): whoever has it sees the page — so send it only to that repair's customer. Removing the link on the job card deletes the public page.

Enabling the module (once)

The portal needs OficinaOS Cloud — the service that bridges the shop's app to the internet without exposing the shop PC.

  • Create an OficinaOS Cloud account (cloud.oficinaos.app) — or get a pairing code from our team
  • In the app: Settings → Cloud tab → paste the pairing code → «Connect»
  • The portal module is switched on in the Cloud account (during beta, by us); the app syncs by itself
  • From then on, every job card gets a «Public link» button

Day to day — publish and share

On the job card, the «Public link» button publishes the snapshot and copies the link. Send it to the customer by SMS, WhatsApp or printed on the intake slip — done.

When the status changes in the app, the next sync (up to ~2 minutes) updates the page. The «Remove public link» button deletes the page when it's no longer needed.

If a quote is pending, the customer answers on the page itself: «Accept» or «Decline» flows into the app through the normal quote flow — dated record and staff notification, exactly like an answer at the counter.

Honest limits

  • Up to ~2 minutes between a status change and the page updating (sync cycle)
  • Needs internet at the shop — offline, the page freezes at the last published state
  • The link is the only access control: if the customer forwards it, others see that repair (nothing more)
  • Without the module, LAN tracking keeps working for free — the portal only adds outside access