Livecaller Guides
  • Management Console
    • Getting Started
      • Web Call
      • Co-browsing
      • Omni-Channel Inbox
    • Realtime dashboard
      • Tags Attach / Detach
    • Customer profiles
    • Inbox
      • Tag Management
      • Send Email
    • Live conversation
    • Blocked
    • Callbacks
    • Conversation history
      • Export to Excel
      • Export chat to PDF
    • Conversation Reports
    • How to transfer a chat
    • Working hours
    • Widget managemant
      • Pre-chat survey
      • Multi-language translation
      • Message typing preview
    • Chat shortcuts
    • General analytics
    • Agent Report
      • Agents performance
      • Response times
      • Availability
      • Satisfaction
      • Agent Activity
    • Notifications
      • Autoplay Policy
    • Integrations
      • Facebook Messenger
        • Meta Data Managment
      • WhatsApp
      • Instagram
      • Email
      • Viber
      • Telegram
    • Permission management
    • Chatbot
      • Events
      • Conditions
      • Actions
    • Automatic rules
    • Roadmap
  • Widget API
    • Javascript API
    • CSS
  • FAQ
    • Web call does not work?
    • How to change or translate widget texts?
    • How to remove "powered by livecaller.io"?
    • Timezone issues
    • Mobile app - iOS, Android
    • Does Livecaller support startups?
    • What is the duration for which information history is retained?
    • How to install?
    • Other Questions
Powered by GitBook
On this page
  1. Management Console
  2. Notifications

Autoplay Policy

PreviousNotificationsNextIntegrations

Last updated 3 months ago

LiveCaller uses notifications to keep you updated on incoming chats, calls, and messages. However, some browsers apply autoplay policies that restrict sound playback when the LiveCaller app is not in the foreground. This means that if the LiveCaller window is minimized or running in the background, audio notifications may not play automatically.

These restrictions are especially strict in Google Chrome, whereas Firefox provides more flexibility. Below, we explain why this happens and how to adjust your settings to ensure that LiveCaller’s notifications remain audible.

Why Doesn’t Sound Play When the App is in the Background?

By default, many browsers—especially Google Chrome—block sound playback unless the user has interacted with the page.

Chrome applies strict rules to determine whether a site can play audio automatically:

  • Sound will not play unless the user has interacted with the page (e.g., clicked or typed).

  • If the app is running in the background or minimized, autoplay with sound is blocked.

  • Chrome uses a Media Engagement Index (MEI) to decide whether a website is allowed to autoplay sound. If users frequently interact with media on a site, Chrome may allow autoplay for that site.

How to Allow Sound for LiveCaller Notifications in Chrome

  1. Open Chrome and go to: Settings > Privacy and Security > Site Settings > Additional Permissions > Sound

  2. Under Default behavior, select "Sites can play sound."

  3. If notifications are still silent, check individual site permissions:

    • Open LiveCaller in Chrome.

    • Click the 🔒 Lock icon (next to the address bar).

    • Go to Site Settings

    • Ensure "Sound" is set to "Allow."

Unlike Chrome, Firefox does not block autoplay sounds by default. This makes it a better option if you want to ensure that LiveCaller’s notifications always play sound.

  • If a site sends notifications, Firefox will allow sound without requiring user interaction.

  • You can manually allow autoplay for a website without needing a high Media Engagement Index (MEI).

How to Enable Sound in Firefox

  1. Open Firefox and go to: Settings > Privacy & Security > Permissions > Autoplay

  2. Click "Settings…" next to Autoplay.

  3. Change the default for audio and video to "Allow Audio and Video."

Best Practices for Ensuring Audible Notifications

  • Use Firefox if you want notifications to always play sound.

  • In Chrome, interact with the page before minimizing it to allow sound playback.

  • Manually adjust autoplay settings for your browser if needed.

For more details, refer to official documentations:

Chrome Autoplay Policy
Firefox Autoplay Settings