Mobile App for Chatbot Management: iOS & Android

An operator needs real-time access to chatbots but doesn't always have a computer at hand. A mobile app for managing bots solves this: monitoring dialogs, manual intervention, scenario switching — all from a phone. Our experience shows that such a panel speeds up incident response by 3 times compared to a desktop solution. For example, for a retail chain with 20 operators, we implemented an app — dialog response time dropped from 45 to 15 seconds (a 67% improvement). With over 5 years of experience and 20+ successful projects, we deliver robust mobile app development for chatbot management. Contact us for a custom estimate and to see how the solution fits your infrastructure.

What Problems We Solve

Human Takeover — the core function. When a bot can't handle a request or a user asks for an operator, the dialog is transferred to a human. The operator receives a push, opens the chat, replies, and returns control to the bot. Latency is critical: if not handled quickly, the customer leaves. We use FCM high priority with data payload on Android and APNs on iOS — the app wakes even in Doze mode. WebSocket keeps the connection for instant message exchange. Typical push delivery latency is less than 2 seconds, verified by tests on devices in standby mode.

Bot scenario management — not all operators should edit responses. A role model separates rights: operator only chat, administrator additionally scenarios. This reduces the risk of accidental errors in production. In one project, we recorded a 90% reduction in unintended changes after implementing roles. We also support advanced features like scenario versioning and rollback.

Chatbot monitoring — see how many are waiting for an operator, how many are in progress, and which are stuck. Sorting by wait time ensures the most critical dialogs are handled first. Statistics: under a load of 500 dialogs per hour, average processing time for critical dialogs does not exceed 10 seconds. Our SLA dialog queue mechanism ensures no client is forgotten.

How the Dialog Queue with SLA Works (Step-by-Step)

1. Dialog transfer: When a bot cannot handle a request, it publishes an event to RabbitMQ.
2. Queue assignment: The event is bound to the queue of free operators. If all operators are busy, the dialog enters a waiting queue with an SLA timer.
3. Push notification: The application sends an FCM/APNs high-priority push to the assigned operator (or to all if none free).
4. Operator action: The operator opens the app, accepts the dialog, and communicates via WebSocket.
5. SLA monitoring: If not accepted within N minutes, a repeat push is sent. Overdue dialogs are escalated.
6. Return to bot: After resolution, the operator can handoff back to the bot.

How We Do It: Stack and Example

We use Swift 5.9+ (SwiftUI) for iOS, Kotlin (Jetpack Compose) for Android, and Flutter 3.x for cross-platform. Below is a key fragment of the operator WebSocket chat on iOS:

class OperatorChatViewModel: ObservableObject {
    @Published var messages: [Message] = []
    @Published var isConnected = false
    private var wsTask: URLSessionWebSocketTask?

    func connect(conversationId: String) {
        let url = URL(string: "wss://<your-endpoint>/operator/conversations/\(conversationId)/ws")!
        wsTask = URLSession.shared.webSocketTask(with: url)
        wsTask?.resume()
        isConnected = true
        receiveNext()
    }

    private func receiveNext() {
        wsTask?.receive { [weak self] result in
            guard let self else { return }
            if case .success(let msg) = result,
               case .string(let text) = msg,
               let decoded = try? JSONDecoder().decode(Message.self, from: Data(text.utf8)) {
                DispatchQueue.main.async { self.messages.append(decoded) }
            }
            self.receiveNext()
        }
    }

    func send(_ text: String) {
        let msg = OutgoingMessage(text: text, conversationId: conversationId)
        let payload = try! JSONEncoder().encode(msg)
        wsTask?.send(.string(String(data: payload, encoding: .utf8)!)) { _ in }
    }

    func returnToBot() {
        Task { await conversationService.handoff(conversationId, to: .bot) }
    }
}

Operator queue: if multiple operators are free, use round-robin or first-click. If all are busy, dialog goes to queue, SLA timer starts. Repeat push after N minutes.

Why FCM High Priority Instead of Regular Notification?

Regular notification on Android does not wake the app in Doze. A data payload with high priority always delivers. This ensures the operator receives a call even on a sleeping phone. On iOS, we use APNs with similar priority. Compare:

Source: Firebase Cloud Messaging documentation

FCM high priority is 6x faster than standard notification in Doze mode, ensuring near-instant alerting.

Platform Comparison: iOS vs Android

For cross-platform, we offer Flutter development, reducing time-to-market by 40% compared to separate native apps.

What's Included

• List of dialogs grouped by status with real-time updates
• Operator chat screen with WebSocket
• Push notifications for new dialogs (FCM high priority)
• Queue with SLA timer and repeat notifications
• Role model (operator / administrator)
• Scenario management (enable/disable, edit responses)
• Analytics: response time, number of transferred dialogs, SLA violations

Timeline and Pricing

Estimated timeline: 8 to 14 working days. Cost is calculated individually — typical investment starts at $5,000 per platform (iOS or Android). Implementing a mobile operator panel pays for itself within 3–6 months by accelerating dialog processing and reducing workload on duty specialists – clients report average savings of $12,000 annually. We guarantee an SLA for push notification response time (no more than 5 seconds) and uninterrupted WebSocket connection. Over 5 years, we have completed more than 20 bot management projects — get a consultation to discuss your tasks and evaluate the economic effect of implementing a mobile operator panel.

Mobile App Analytics: Firebase, Amplitude, AppsFlyer and Attribution

Our team regularly encounters projects where analytics is already "set up" but yields no real insights. A typical example is a startup with 50k DAU: tracking dozens of events without a single answer to the question "why don't users reach payment?". In two weeks we built a basic funnel and found that 70% of users drop off at the phone number verification screen. After fixing the bug, retention increased by 12%. The takeaway: analytics should start with specific questions, not tracking everything indiscriminately.

Why Event Taxonomy is the Foundation of Mobile App Analytics?

Firebase Analytics, Amplitude, Mixpanel — technically similar. The difference lies in what you put into them. A common mistake: events like screen_view, button_tap_1, button_tap_2 without context. A month later, no one remembers what button_tap_2 means.

Proper taxonomy: object + action + context. product_viewed, checkout_started, payment_completed with parameters product_id, category, price, source. This allows building funnels, cohort analysis, and retention without additional tracking.

We document the naming convention in a tracking plan — a document (Google Sheet or Amplitude Data Catalog) describing every event, its parameters, and triggering conditions. The tracking plan is synced with the analytics team before development begins, not after. This approach ensures that data remains interpretable months later and doesn't become a dump. Experience from 50+ projects confirms: without a tracking plan, analytics maintenance costs increase 2-3 times due to rework.

What Should You Choose for Mobile App Analytics: Firebase, Amplitude, or Mixpanel?

The table below highlights key differences between the three popular platforms. Choice depends on budget, traffic, and tasks.

Firebase Analytics — free, deep integration with Google Ads, BigQuery export for raw data. Limitations: data latency up to 24 hours, limited funnels. For startups with Google Ads traffic, it's the first choice.

Amplitude — product analytics focused on cohorts and user journeys. Journeys (formerly Pathfinder) shows actual paths between events — not assumed funnels but real routes. Session Replay records sessions for UX analysis. The free tier up to 10M events/month is enough for most products at launch.

Mixpanel — close to Amplitude, stronger in real-time segmentation. Insights, Funnels, Retention cover 90% of product analysts' tasks.

How to Solve Multi-Channel Attribution with AppsFlyer?

Knowing where a user came from is a separate task. Firebase Attribution works only within the Google ecosystem. For multi-channel attribution (Facebook Ads, TikTok, Apple Search Ads, programmatic), an MMP (Mobile Measurement Partner) is needed.

AppsFlyer is the market leader. OneLink — universal deep link working on iOS and Android, correctly attributing installs from any channel. Protect360 — built-in fraud protection (fake installs, click injection on Android). Adjust and Branch are competitors with similar features. Branch excels in deep linking; Adjust is popular in gaming.

According to Apple, with iOS 14.5, apps must obtain user permission via ATT before collecting IDFA for tracking. AppsFlyer uses probabilistic matching (IP + user agent + timing) for these users — accuracy is lower but better than nothing. SKAdNetwork and Privacy Preserving Attribution provide aggregated data from Apple with a 24-72 hour delay.

How to Set Up Crash Analytics to Not Miss Bugs?

Firebase Crashlytics is the standard for crash reporting. It automatically groups crashes by stack trace, shows affected users %, and sends velocity alerts when crash rate increases by more than 10% per hour.

Important: symbolication. On iOS, .dSYM files must be automatically uploaded with each build — via Fastlane upload_symbols_to_crashlytics or Xcode Cloud built-in. Without symbols, crashes in Crashlytics appear as memory addresses. This happens more often than expected when switching to a new CI — in one project with 500k users, we found that 40% of crashes remained unsymbolicated due to a missing CI/CD step. After automation, bug response time dropped from 3 hours to 15 minutes.

For React Native and Flutter, @sentry/react-native and sentry_flutter provide additional context: breadcrumbs, network requests before the crash, Redux/Provider state.

Below is a comparison of popular crash analytics tools to choose according to your needs.

Environment Setup

Three environments with separate Firebase projects: dev, staging, production. Mixing analytics from test sessions and production is a common mistake that skews all metrics. On iOS via GoogleService-Info.plist per scheme, on Android via google-services.json in each flavor folder.

Timelines: basic analytics with Firebase + Crashlytics — 3-5 days. Full tracking plan + Amplitude/Mixpanel with funnels and cohorts — 2-3 weeks. Attribution via AppsFlyer with deep linking and fraud protection — 1-2 weeks. Cost is calculated individually based on integration complexity.

What Is Included in Our Work

As part of analytics implementation, we provide:

• Development and approval of a tracking plan with product and marketing teams.
• SDK integration (Firebase, Amplitude, Mixpanel, AppsFlyer) considering your stack (Swift/Kotlin/Flutter/React Native).
• Setup of funnels, cohorts, dashboards, and alerts.
• Automation of symbolication and .dSYM upload via Fastlane.
• Documentation of events and parameters.
• Team training on the analytics platform.
• Two weeks of post-release support and tracking adjustments.

Our experience: 7 years of analytics implementation and over 80 successful projects in mobile development. We guarantee data correctness and transparency at every stage.

Contact us for a consultation on setting up analytics for your app. Request an audit of your current analytics — and we will show you which metrics you are losing.