—PRODUCT

Mobile PWA

A panel added to the phone home screen: overview, queue, conversation, pending work and push.

The mobile PWA lets the team manage the inbox and field work from a phone: an overview with four KPIs, a channel-tagged queue, replies in a single conversation, four work queues, voice-call recordings and push notifications. The session is stored on the device; offline it says “no connection” instead of showing stale data. Installation uses the browser’s “Add to Home Screen” flow.

Ready Plan: all plans

—SUMMARY

What is it for?

A panel added to the phone home screen: overview, queue, conversation and push notifications.

01HOW IT WORKS

Three steps to a working result.

Each step is one screen in the panel; nothing goes live without confirmation.

  1. 1 Add to the home screen

    Open the site in the phone browser and choose “Add to Home Screen”. On iOS, web push works only with this installation on 16.4 and later.

  2. 2 Sign in

    Sign in with email and password; Turnstile is required. There is no “Remember me” box; the session is stored persistently on the device.

  3. 3 Turn on notifications

    Turn on notifications in Settings; permission is requested after a user tap. If permission is granted but no subscription exists, the panel shows that as a separate state.

02WHAT IT DOES

Real work in one flow.

The three capabilities below are today’s scope; the sample screen is fictional and contains no real customer data.

01

The day at a glance

Pending, opened today, average first response and last seven days; the age of the oldest pending item is shown separately.

  • Response
  • Pending
02

Queue and reply in one hand

A channel-tagged list with search and a “Pending / Mine / All” filter; when you reply in a conversation it moves to you and AI goes silent.

  • Queue
  • Response
  • Conversation
03

Four work queues

Callback, comment, appointment and waitlist in one screen; “Called”, “Approve”, “Hide” and “Assign from waitlist” happen on mobile.

  • Queue
  • Approval
  • Appointment
SAMPLE SCREEN · FICTIONAL Overview · today
Pending 7 · oldest 42 min
Opened today 38
Average first response 41 s · 24 conversations
Last 7 days 312 conversations
Work waiting Callback 3 · comment 2 · appointment 1 · waitlist 1

Sample screen; numbers are fictional and contain no real customer data.

03THE DIFFERENCE IS IN THE DETAILS

Small details that change the decision.

79 items, each tied to a rule, setting or automatic behaviour in today’s product. No unsupported number, ratio or promise appears in this list.

01

Sign-in

Email/password, Turnstile and a session that stays on the device.

6 items
01

Turnstile required

Cloudflare Turnstile is required; without a token the “Sign in” button is disabled.

  • Login
  • Platform
02

12-second widget bar

If the widget does not load within 12 seconds, a “could not load” bar appears and a browser sign-in path is shown.

  • Duration
  • Platform
03

Captcha refreshes

After a failed sign-in the captcha is re-rendered; a second simultaneous request is blocked.

  • Refresh
  • Duration
04

Brand and tagline

The sign-in screen carries the “YanıtLabs” logo and the “All conversations in your pocket” tagline; the icon is /ikon.svg.

  • Tag
  • Conversation
  • Logo
05

No remember-me or forgot-password

There is no “Remember me” or “Forgot password”; persistence comes directly from localStorage.

  • Password
  • Remember me
06

Same sign-in as the panel

Sign-in uses the same POST /api/v1/auth/tenant/login address as the panel.

  • Panel
  • Login
  • API
02

Overview

Four daily KPIs, waiting work and recent conversations.

8 items
01

Four KPIs

The cards are pending, opened today, average first response and last seven days.

  • KPI
  • Response
  • Pending
02

Oldest pending

The “Pending” card also shows the age of the oldest waiting item.

  • Pending
  • Platform
03

First-response sample

Average first response is computed only from conversations with firstResponseAt; the number of conversations is written below.

  • Response
  • Conversation
  • Number
04

Excludes archive

The last seven days and total count come from the list excluding archived records.

  • Archive
  • List
  • Record
05

Waiting work

Callback, comment, appointment and waitlist counts in one list; if none exist the section is not drawn.

  • Appointment
  • List
  • Waitlist
06

Channel mix

Channel mix is shown with horizontal percentage bars.

  • Channel
  • Platform
07

Last five conversations

“Recent conversations” always shows the last five records; “(all →)” moves to the Conversations tab.

  • Conversation
  • Tab
  • Record
08

Empty state

On first open with no conversations it says “No conversations yet”.

  • State
  • Conversation
03

Inbox

A channel-tagged list, search and three filters.

7 items
01

Default is All

The default filter is All; the “Pending” tab stands out with a count badge.

  • Filter
  • Tab
  • Pending
02

Pending and Mine

“Pending” means unassigned and not RESOLVED; “Mine” means assigneeId equals the session user.

  • Pending
  • Team
  • Ownership
03

Turkish-aware search

Search covers customer name, phone, email and title with Turkish case sensitivity.

  • Search
  • Language
  • Email
04

Sorted by last message

The list is sorted newest to oldest by last message.

  • Message
  • List
  • Pending
05

Row labels

“Callback”, “Waiting for reply”, “AI answering / With agent”, “Resolved” and the waiting time appear on the row.

  • Call
  • Response
06

Header and refresh

The header says “N waiting for reply” or “Nothing pending”; there is a refresh button.

  • Refresh
  • Response
  • Pending
07

Empty and no-result differ

An empty list and “no results found” are separate messages.

  • List
  • Message
04

Conversation

Message history, reply, resolve/reopen and the ownership bar.

9 items
01

Polling every eight seconds

While visible it polls every eight seconds; when the app is in the background the timer stops and refreshes immediately on return.

  • Duration
  • Refresh
02

One request

Visibility and window focus are merged within 750 ms; a single request is sent.

  • Window
  • Platform
03

No optimistic rendering

The server is written first, then the list refreshes; no bubble appears before sending.

  • List
  • Server
  • Refresh
04

NOT DELIVERED bar

If delivery.chatwoot is “failed”, a red “Message saved but NOT DELIVERED to the customer” bar appears.

  • Shipping
  • Conversation
  • Customer
05

AI goes silent

The ownership bar says: if AI is answering, “the moment you send a reply the conversation moves to you and AI goes silent”; if with an agent, it says AI is not writing.

  • Ownership
  • Conversation
  • Response
06

Callback bar

If a phone/web customer is waiting on the line, an urgent “Callback waiting” bar appears.

  • Call
  • Customer
  • Phone
07

One PATCH for status

A single PATCH sets RESOLVED / OPEN; no unnecessary system message is written.

  • Status
  • Message
08

Bubble roles

Bubbles are split into INTERNAL / OUTBOUND / inbound; the role label is Agent/AI/System/Customer.

  • Role
  • Customer
09

Reply box grows

The reply box grows automatically up to 130 px.

  • Response
  • Platform
05

Pending work

Four sub-tabs for callback, comment, appointment and waitlist.

8 items
01

Four sub-tabs

Callback, Comments, Appointments and Waitlist tabs; counts appear in the header.

  • Appointment
  • Waitlist
  • Call
02

Called in callback

“Called” assigns the conversation to the user (CUSTOMER_REQUEST), “Completed” resolves it and “Open” goes to the conversation.

  • Call
  • Team
  • Ownership
03

Comment draft pre-filled

For a comment the AI draft is pre-filled in the textarea; “Approve and send” calls reply, “Hide” calls hide.

  • Comment
  • Draft
  • Approval
04

Approve/cancel appointment

An appointment request has “Approve” / “Cancel”; there is also a Today view and a staff filter.

  • Approval
  • Appointment
  • Cancel
05

Waitlist call/called/cancel

The waitlist offers tel: “Call”, “Called”, “Cancel” and “Assign from waitlist”.

  • Waitlist
  • Cancel
  • Call
06

Assign-from-waitlist panel

“Assign from waitlist” picks a time + calendar, “Find available times” brings candidates and “Assign to this time” completes it.

  • Ownership
  • Waitlist
  • Panel
07

Waitlist order

Waitlist order is by queue number, then creation time; items waiting for action appear on top.

  • Order
  • Waitlist
  • Queue
08

Staff “Mine” filter

The staff “Mine” filter is found by matching the staff record’s business user ID.

  • Filter
  • Team
  • Record
06

Voice calls

Fifty calls, transcript, recording and latency measurements.

7 items
01

Fifty records

The list uses voice-calls?limit=50; the transcript is not in the list response and is fetched separately when the detail opens.

  • Record
  • Voice
  • List
02

Direction and recording on the row

The row shows direction, status, duration and a “recording” tag when a recording exists.

  • Record
  • Duration
  • Tag
03

Recording playback

If a recording URL exists the detail uses audio controls with preload=none; otherwise it says “No recording for this call”.

  • Record
  • Link
  • Call
04

Summary and transcript

A summary is shown if present; the transcript is in a pre-wrap box, otherwise it says “No transcript”.

  • Transcript
  • Summary
05

Latency measurement

Latency is drawn only when measured: ASR, LLM, TTS, end-to-end p50 / max (ms).

  • Delay
  • Platform
06

Status mapping

Completed, Failed, In progress/Starting, Missed and Busy are shown.

  • Status
  • Platform
07

Empty state

With no calls it says “Inbound calls will appear here once your number is connected…”.

  • State
  • Call
  • Number
07

Push notifications

Six states, the iOS 16.4 requirement and VAPID subscription.

7 items
01

Six states

Unsupported, not set up, not asked, denied, on and off; each has its own explanation and action.

  • State
  • Platform
02

iOS 16.4 and home screen

On iOS, web push works on 16.4+ and only with “Add to Home Screen”; even if PushManager appears in a Safari tab, the subscription fails.

  • iOS
  • Tab
  • Web
03

Permission after a tap

Permission is requested after a user tap.

  • Permission
  • Team
04

VAPID and subscription

The public VAPID key comes from GET /api/v1/push/vapid; the subscription is written with POST /api/v1/push/subscribe.

  • API
  • Push
05

Two-sided unsubscribe

Disabling cancels the browser subscription and sends DELETE /api/v1/push/subscribe to the server; no further sends to an unreachable address.

  • Cancel
  • Server
  • Delete
06

Permission without subscription

For “I allowed it but get no notifications”, “permission granted but no subscription” is a separate off state.

  • Permission
  • Notification
  • State
07

Settings and update

Settings has “Turn notifications on / off”, an error bar and an “Update the app” button.

  • Settings
  • Error
  • Notification
08

Session

Device-stored session, 401 behaviour and sign-out.

8 items
01

localStorage key

The session is stored as JSON under the yanit_mobil_oturum key.

  • Session
  • Platform
02

Read on launch

On launch the session is read with readSession(); without a token the Sign-in screen is drawn.

  • Session
  • Platform
03

Bearer header

Every request adds Authorization: Bearer <token>.

  • Bearer
  • Platform
04

API does not clear on 401

On 401 the session is not cleared on the server; the caller decides.

  • API
  • Session
  • Call
05

The app clears it

On an “invalid session” error the app clears the session and returns to sign-in.

  • Session
  • Error
06

Sign-out clears

“Sign out” clears the session and all in-memory lists.

  • Session
  • List
07

No remember-me

There is no separate “Remember me” box; behaviour is the same on every sign-in.

  • Remember me
  • Platform
08

Refresh unverified

The session lifetime or refresh-token code is absent from this copy; unverified.

  • Refresh
  • Session
09

Offline

No-connection bar, no cache and version checks.

6 items
01

onLine and events

The initial state is read from navigator.onLine; offline and online events are listened to.

  • Offline
  • List
  • State
02

No-connection bar

A sticky “No connection — live data cannot update” bar appears at the top.

  • Offline
  • Platform
03

No API cache

The service worker deliberately does not cache API responses; offline the list appears empty.

  • API
  • Cache
  • List
04

Version check false offline

The update check returns false offline; no false “new version available” warning appears.

  • Offline
  • Warning
05

Manual update

“Update the app” updates service workers, clears caches and reloads the page at the end.

  • Refresh
  • Service worker
  • Cache
06

Check every five minutes

The version is checked every five minutes and when the app comes to the foreground; no background polling.

  • Duration
  • Platform
10

Deep links

Opening the right conversation, comment, appointment or waitlist item from push.

6 items
01

?conversation=

?conversation=<id> opens the conversation screen; the parameter is cleared with history.replaceState.

  • Conversation
  • Platform
02

Comment, appointment, waitlist

?comment=, ?appointment= and ?waitlist= open the Pending work tab and the right sub-tab.

  • Appointment
  • Waitlist
  • Comment
03

Back does not exit the app

Because pushState is used, Android back / iOS swipe back does not exit the app; popstate returns to the list.

  • List
  • Push
  • iOS
04

Closing a conversation

When closing a conversation it calls history.back() if history exists, otherwise goes straight to the list.

  • Conversation
  • Closing
  • List
05

Push comment

A comment on the push side states that the service worker opens /?conversation=….

  • Push
  • Comment
  • Conversation
06

sw.js unverified

sw.js is absent from this local copy; the real notification-click routing is unverified.

  • Notification
  • Platform
11

PWA installation

Service worker, standalone detection and safe area.

7 items
01

Service worker in production only

The service worker is registered only in production: navigator.serviceWorker.register(“/sw.js”).

  • Service worker
  • Platform
02

Error is not swallowed

If registration fails an error is written to the console; “Add to Home Screen” and push do not work.

  • Error
  • Push
03

iOS standalone

iOS standalone detection uses display-mode: standalone or navigator.standalone.

  • iOS
  • Platform
04

Safe area

env(safe-area-inset-bottom) and env(safe-area-inset-top) are used for notched phones.

  • Safe-area
  • Phone
05

Sign-in icon

The sign-in screen uses the /ikon.svg icon.

  • SVG
  • Platform
06

No registration in development

The service worker is not registered in development; caching avoids the “code did not change” illusion.

  • Service worker
  • Platform
07

Manifest unverified

manifest.webmanifest, sw.js, index.html and icon files are absent from this copy; start_url, display, icon sizes and cache strategy are unverified.

  • Link
  • Index
  • File

04CONTROL AND SECURITY

Human approval, masking, records.

These are this surface’s current security behaviours; no general “GDPR compliant” certificate is claimed.

Turnstile cannot be skipped

Turnstile is required at sign-in and is fail-closed on the server; without a token the sign-in button is disabled.

No stale data offline

The service worker does not cache API responses; offline it says “no connection” and shows no stale customer data.

Session on the device

The session is kept in localStorage and cleared on sign-out and on an “invalid session” error. On 401 the caller decides whether to clear it.

05WHICH PLAN

Plan and add-ons.

The mobile PWA is available on every plan; being a business user is enough. If an add-on such as appointments is off, it returns 403 and does not lock this screen.

Starter ₺2,750 / mo excl. VAT This surface is on every plan
Growth ₺7,900 / mo excl. VAT This surface is on every plan
Business ₺17,500 / mo excl. VAT This surface is on every plan

All amounts are monthly and exclude VAT. See the plans page for the current list and calculator. Plans and calculator →

06FAQ

Four questions, four clear answers.

Is it in an app store?
No. The mobile PWA is installed from the browser with “Add to Home Screen”; it is not an App Store/Google Play package. On iOS, push works only with this installation on 16.4+.
Can I read conversations offline?
No. The service worker does not cache API responses; offline a “no connection” bar appears and the list looks empty. No stale data is shown.
I get no notifications, what should I do?
First check the “permission granted but no subscription” state. On iOS, home-screen installation and 16.4+ are required. Toggle notifications in Settings; a dead subscription is cancelled both in the browser and on the server.
What can I do on mobile?
Four work queues: callback (“Called”), comment (approve/hide), appointment (approve/cancel) and waitlist (call/assign). You can also reply, resolve/reopen and play a voice recording.

+RELATED POSTS

Posts on this topic

Posts from the same topic cluster that complete this page. Mobile PWA posts.

Guide

Call center or AI assistant?

A practical comparison for SMEs: when a call center makes sense, when an AI voice assistant does, and how volume, scope, handover, cost and data should decide.

Let’s set this up on your account.

Try free for 14 days without a credit card; we will do the first setup together.

Call Start 14-day trial