volbor

Looking for something?

↑↓navigateEnteropenEscclose

Choose language

Get started

Message Delivery: Silence Doesn't Mean «The Customer Is Thinking»

If a customer sends a message and Inbox stays empty, or you reply and nothing arrives in their messenger, the conversation is stalled. Before you test delivery in both directions, do not rewrite welcome copy or connect additional channels: you will be debugging the wrong problem.

This page is a step-by-step checklist. It does not display account-specific server logs and does not replace live status indicators on your connection dashboard.

Get startedLearn more
  1. 01
    «Connected» Status Without a Test

    your shift trusts the green badge, but the customer is messaging a bot that your dashboard isn't listening to.

  2. 02
    Replies Sent to the Wrong Chat

    the thread is logged in Inbox, but the customer sees nothing because another auto-responder is intercepting messages.

  3. 03
    Testing from the Same Account as the Bot

    internal test prompts get confused with actual customer conversations.

  4. 04
    Waiting for Real Customers as Proof

    your first real customer drop-off becomes an unrepeatable live outage.

Common Pitfalls of a «Silent» Channel

  1. 01

    «Connected» Status Without a Test

    your shift trusts the green badge, but the customer is messaging a bot that your dashboard isn't listening to.

  2. 02

    Replies Sent to the Wrong Chat

    the thread is logged in Inbox, but the customer sees nothing because another auto-responder is intercepting messages.

  3. 03

    Testing from the Same Account as the Bot

    internal test prompts get confused with actual customer conversations.

  4. 04

    Waiting for Real Customers as Proof

    your first real customer drop-off becomes an unrepeatable live outage.

Core Troubleshooting Steps

  1. 01

    1. Distinguish between the two failure modes

    Inbound messages are missing in Inbox. Or inbound messages show up, but replies from your workspace never reach the customer. These are separate failure points. Do not attempt to fix both simultaneously by simply tweaking your greeting copy.

  2. 02

    2. Retest from an independent third-party account

    Send a short text. Note the exact timestamp. Refresh your workspace feed. If the message doesn't appear, open your channel settings screen and confirm you are messaging the exact bot handle configured in your account. For Telegram setup details, refer to the connection guide.

  3. 03

    3. Eliminate duplicate auto-responders

    If a legacy bot or third-party service is still hooked up to the same messenger, the customer may see its responses while your inbox shows an empty feed or foreign messages. Maintain exactly one active auto-responder during testing. See migration.

  4. 04

    4. Hold traffic until two-way delivery is verified

    One clean roundtrip test from an external account is worth ten copy revisions. Once successful, have a colleague repeat the roundtrip test. Only then turn on ad campaigns or public direct links.

What NOT to Do

Do not create a brand-new bot before diagnosing the status of your current one: running two bots simultaneously doubles confusion. Do not delete a channel with active conversations just to «start over fresh» before documenting what failed to deliver. Disconnecting stops incoming traffic; conversation history does not transfer anywhere automatically.

If events must be acknowledged by your backend, silence might originate on the webhook receiving endpoint rather than the messenger. Check API & Webhooks independently from live chat: your customer and your internal database are separate destinations.

Frequently Asked Questions

Messages were visible yesterday, but the feed is empty today

Check whether you switched channels or workspaces. Look for the conversation in the exact workspace used yesterday. A newly created empty workspace does not automatically pull past history.

A customer says they sent a message, but we don't see it

Ask for the exact timestamp and recipient handle they messaged. Compare it with the bot your workspace is monitoring. Third-party bots or an employee's personal messenger account will never appear in your team inbox.

Replies appear in our Inbox, but the customer never receives them

The inbound pipeline is working. Check for a conflicting secondary auto-responder, messenger rate limits, or replies directed to an incorrect thread. Avoid disconnecting and reconnecting the channel blindly.

Should we contact volbor support right away?

Run two clean roundtrip tests and verify that no secondary auto-responder is active first. If your channel dashboard displays an error code not covered here, pause and do not repeatedly toggle disconnect.

Should we test attachments too?

Yes, if you promise attachment handling in your welcome flow. If attached files aren't clearly visible for reps to respond to during testing, remove that prompt from your welcome copy.

Related Links and Solutions

  • Unified InboxWhy it matters: The single workspace where your shift must see incoming messages.
    Without it: Messages are stranded across personal staff smartphones.
  • Connect TelegramWhy it matters: Verify setup order when troubleshooting this specific channel.
    Without it: Teams try to fix delivery without inspecting the channel connection screen.
  • Platform MigrationWhy it matters: Disconnect legacy auto-responders to prevent double-replies.
    Without it: Customers receive phantom replies missing from your Inbox.
  • Quick StartWhy it matters: Rerun the roundtrip test if the channel was linked without verification.
    Without it: Text tweaks mask a completely broken webhook pipeline.
  • Webhooks and APIWhy it matters: Separate backend sync timeouts from messenger delivery issues.
    Without it: Backend sync bugs are mistakenly diagnosed as messenger disconnects.
  • Launch ChecklistWhy it matters: Keep channels private until two-way message delivery is confirmed.
    Without it: Your first live customer interaction becomes a support incident.