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
—PRODUCT
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.
—SUMMARY
A panel added to the phone home screen: overview, queue, conversation and push notifications.
01HOW IT WORKS
Each step is one screen in the panel; nothing goes live without confirmation.
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.
Sign in with email and password; Turnstile is required. There is no “Remember me” box; the session is stored persistently on the device.
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
The three capabilities below are today’s scope; the sample screen is fictional and contains no real customer data.
Pending, opened today, average first response and last seven days; the age of the oldest pending item is shown separately.
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.
Callback, comment, appointment and waitlist in one screen; “Called”, “Approve”, “Hide” and “Assign from waitlist” happen on mobile.
Sample screen; numbers are fictional and contain no real customer data.
03THE DIFFERENCE IS IN THE DETAILS
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.
Email/password, Turnstile and a session that stays on the device.
Cloudflare Turnstile is required; without a token the “Sign in” button is disabled.
If the widget does not load within 12 seconds, a “could not load” bar appears and a browser sign-in path is shown.
After a failed sign-in the captcha is re-rendered; a second simultaneous request is blocked.
The sign-in screen carries the “YanıtLabs” logo and the “All conversations in your pocket” tagline; the icon is /ikon.svg.
There is no “Remember me” or “Forgot password”; persistence comes directly from localStorage.
Sign-in uses the same POST /api/v1/auth/tenant/login address as the panel.
Four daily KPIs, waiting work and recent conversations.
The cards are pending, opened today, average first response and last seven days.
The “Pending” card also shows the age of the oldest waiting item.
Average first response is computed only from conversations with firstResponseAt; the number of conversations is written below.
The last seven days and total count come from the list excluding archived records.
Callback, comment, appointment and waitlist counts in one list; if none exist the section is not drawn.
Channel mix is shown with horizontal percentage bars.
“Recent conversations” always shows the last five records; “(all →)” moves to the Conversations tab.
On first open with no conversations it says “No conversations yet”.
A channel-tagged list, search and three filters.
The default filter is All; the “Pending” tab stands out with a count badge.
“Pending” means unassigned and not RESOLVED; “Mine” means assigneeId equals the session user.
Search covers customer name, phone, email and title with Turkish case sensitivity.
The list is sorted newest to oldest by last message.
“Callback”, “Waiting for reply”, “AI answering / With agent”, “Resolved” and the waiting time appear on the row.
The header says “N waiting for reply” or “Nothing pending”; there is a refresh button.
An empty list and “no results found” are separate messages.
Message history, reply, resolve/reopen and the ownership bar.
While visible it polls every eight seconds; when the app is in the background the timer stops and refreshes immediately on return.
Visibility and window focus are merged within 750 ms; a single request is sent.
The server is written first, then the list refreshes; no bubble appears before sending.
If delivery.chatwoot is “failed”, a red “Message saved but NOT DELIVERED to the customer” bar appears.
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.
If a phone/web customer is waiting on the line, an urgent “Callback waiting” bar appears.
A single PATCH sets RESOLVED / OPEN; no unnecessary system message is written.
Bubbles are split into INTERNAL / OUTBOUND / inbound; the role label is Agent/AI/System/Customer.
The reply box grows automatically up to 130 px.
Four sub-tabs for callback, comment, appointment and waitlist.
Callback, Comments, Appointments and Waitlist tabs; counts appear in the header.
“Called” assigns the conversation to the user (CUSTOMER_REQUEST), “Completed” resolves it and “Open” goes to the conversation.
For a comment the AI draft is pre-filled in the textarea; “Approve and send” calls reply, “Hide” calls hide.
An appointment request has “Approve” / “Cancel”; there is also a Today view and a staff filter.
The waitlist offers tel: “Call”, “Called”, “Cancel” and “Assign from waitlist”.
“Assign from waitlist” picks a time + calendar, “Find available times” brings candidates and “Assign to this time” completes it.
Waitlist order is by queue number, then creation time; items waiting for action appear on top.
The staff “Mine” filter is found by matching the staff record’s business user ID.
Fifty calls, transcript, recording and latency measurements.
The list uses voice-calls?limit=50; the transcript is not in the list response and is fetched separately when the detail opens.
The row shows direction, status, duration and a “recording” tag when a recording exists.
If a recording URL exists the detail uses audio controls with preload=none; otherwise it says “No recording for this call”.
A summary is shown if present; the transcript is in a pre-wrap box, otherwise it says “No transcript”.
Latency is drawn only when measured: ASR, LLM, TTS, end-to-end p50 / max (ms).
Completed, Failed, In progress/Starting, Missed and Busy are shown.
With no calls it says “Inbound calls will appear here once your number is connected…”.
Six states, the iOS 16.4 requirement and VAPID subscription.
Unsupported, not set up, not asked, denied, on and off; each has its own explanation and action.
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.
Permission is requested after a user tap.
The public VAPID key comes from GET /api/v1/push/vapid; the subscription is written with POST /api/v1/push/subscribe.
Disabling cancels the browser subscription and sends DELETE /api/v1/push/subscribe to the server; no further sends to an unreachable address.
For “I allowed it but get no notifications”, “permission granted but no subscription” is a separate off state.
Settings has “Turn notifications on / off”, an error bar and an “Update the app” button.
Device-stored session, 401 behaviour and sign-out.
The session is stored as JSON under the yanit_mobil_oturum key.
On launch the session is read with readSession(); without a token the Sign-in screen is drawn.
Every request adds Authorization: Bearer <token>.
On 401 the session is not cleared on the server; the caller decides.
On an “invalid session” error the app clears the session and returns to sign-in.
“Sign out” clears the session and all in-memory lists.
There is no separate “Remember me” box; behaviour is the same on every sign-in.
The session lifetime or refresh-token code is absent from this copy; unverified.
No-connection bar, no cache and version checks.
The initial state is read from navigator.onLine; offline and online events are listened to.
A sticky “No connection — live data cannot update” bar appears at the top.
The service worker deliberately does not cache API responses; offline the list appears empty.
The update check returns false offline; no false “new version available” warning appears.
“Update the app” updates service workers, clears caches and reloads the page at the end.
The version is checked every five minutes and when the app comes to the foreground; no background polling.
Opening the right conversation, comment, appointment or waitlist item from push.
?conversation=<id> opens the conversation screen; the parameter is cleared with history.replaceState.
?comment=, ?appointment= and ?waitlist= open the Pending work tab and the right sub-tab.
Because pushState is used, Android back / iOS swipe back does not exit the app; popstate returns to the list.
When closing a conversation it calls history.back() if history exists, otherwise goes straight to the list.
A comment on the push side states that the service worker opens /?conversation=….
sw.js is absent from this local copy; the real notification-click routing is unverified.
Service worker, standalone detection and safe area.
The service worker is registered only in production: navigator.serviceWorker.register(“/sw.js”).
If registration fails an error is written to the console; “Add to Home Screen” and push do not work.
iOS standalone detection uses display-mode: standalone or navigator.standalone.
env(safe-area-inset-bottom) and env(safe-area-inset-top) are used for notched phones.
The sign-in screen uses the /ikon.svg icon.
The service worker is not registered in development; caching avoids the “code did not change” illusion.
manifest.webmanifest, sw.js, index.html and icon files are absent from this copy; start_url, display, icon sizes and cache strategy are unverified.
04CONTROL AND SECURITY
These are this surface’s current security behaviours; no general “GDPR compliant” certificate is claimed.
Turnstile is required at sign-in and is fail-closed on the server; without a token the sign-in button is disabled.
The service worker does not cache API responses; offline it says “no connection” and shows no stale customer data.
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
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.
All amounts are monthly and exclude VAT. See the plans page for the current list and calculator. Plans and calculator →
06FAQ
+RELATED POSTS
Posts from the same topic cluster that complete this page. Mobile PWA posts.
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.
AI support plans count messages in some places and conversations in others. Five questions to ask and how the two models compare.
Five common multi-channel customer communication mistakes — tone, handover, stale knowledge, ownership and measurement — and how to fix them.
Try free for 14 days without a credit card; we will do the first setup together.