volbor

Looking for something?

↑↓navigateEnteropenEscclose

Choose language

Get started

Quick Start: One Channel and One Test Conversation

Your first day in volbor isn't about mapping your entire company. You only need one channel where customers already reach out—or where you're ready to place a website widget—and one live message you can see in the shared inbox. Until you've verified that, adding a second channel or browsing analytics only distracts from confirming your inbound connection works.

Open your workspace using the "Get Started" button on this page. Then follow the onboarding screen: this guide doesn't replace the in-app button labels.

Get startedLearn more
  1. 01
    An empty workspace and an overcomplicated plan

    spending weeks designing workflows before sending a single test message. You can't fix what isn't running.

  2. 02
    Connecting two messaging apps at once

    an issue in one channel becomes impossible to distinguish from an issue in the other.

  3. 03
    A greeting that overpromises

    saying "we reply in 1 minute" or "we'll process your order" before anyone is assigned to cover the queue.

  4. 04
    Testing from your own workspace account

    it looks like an inbound customer message, but you're just chatting with yourself inside the dashboard.

Common First-Day Rollout Mistakes

  1. 01

    An empty workspace and an overcomplicated plan

    spending weeks designing workflows before sending a single test message. You can't fix what isn't running.

  2. 02

    Connecting two messaging apps at once

    an issue in one channel becomes impossible to distinguish from an issue in the other.

  3. 03

    A greeting that overpromises

    saying "we reply in 1 minute" or "we'll process your order" before anyone is assigned to cover the queue.

  4. 04

    Testing from your own workspace account

    it looks like an inbound customer message, but you're just chatting with yourself inside the dashboard.

Key First-Day Milestones

  1. 01

    1. Pick a channel where conversations already happen

    Choose the messenger where customers already ask questions, or deploy the website widget if your leads arrive via landing pages. Don't create a brand-new account "just for the bot" if customers already reach you elsewhere.

  2. 02

    2. Connect the channel following in-app prompts

    Open channel settings and complete the setup until the dashboard marks the channel as active. If the screen requires confirmation within the messenger app itself, complete only that step and return. Never attempt workarounds.

  3. 03

    3. Write a concise welcome greeting

    Keep it to one sentence: who is responding and what the bot does not do. For instance, mention that standard pricing inquiries can be answered immediately while custom requests are routed to an agent. Never promise SLA response times your team cannot keep.

  4. 04

    4. Send a test message from a separate personal account

    Message your channel as a customer. The message must appear in your Unified Inbox. Reply from the dashboard and confirm the reply appears back in your personal chat. Only invite a second team member after this loop succeeds.

What to Leave Out on Day One

Payments, booking calendars, multi-team role permissions, and custom reports should only be introduced once test messages reliably flow back and forth. If replies from the dashboard don't reach the customer, consult message delivery troubleshooting instead of configuring the next module. You only need a developer when data must sync to your internal systems via API, not to click "Connect channel".

Frequently Asked Questions

Do I need a developer?

No for connecting your first channel and setting up a greeting. Yes if an inbound interaction needs to sync into your internal backend via API.

Can I invite our entire shift right away?

Invite one teammate to verify the same test message loop. Onboard the entire team only after defining who should see customer conversations. See our Security page for access controls.

What should I write in our welcome greeting?

State who is on duty and which questions are resolved automatically. Remove promises about response times or stock availability unless they are fully guaranteed.

Is a chatbot mandatory on day one?

No. First establish a reliable live agent reply loop from the Unified Inbox. Introduce a Chatbot when the same questions repeat daily, not "just in case".

How many channels should I start with?

Just one. Add a second channel only when the first operates smoothly without needing manual delivery checks.

Helpful Resources & Related Solutions

  • ChatbotWhy you need it: Offload repetitive questions once live response routing is verified.
    What happens without it: Agents keep manually typing out business hours and pricing when automation is ready to help.
  • Website WidgetWhy you need it: Prevent website inquiries from getting lost in a disconnected email queue.
    What happens without it: Website visitors and messenger leads end up siloed in separate places.
  • Unified InboxWhy you need it: View test messages in the exact shared interface your team will work in.
    What happens without it: Your channel is technically "connected" but agents have no shared place to reply.
  • Launch PlanWhy you need it: Assign a channel owner and operating hours before public customers see it.
    What happens without it: The test succeeds in the evening, but no one is assigned to reply the next morning.
  • Troubleshoot DeliveryWhy you need it: Resolve issues if a test message fails to appear in your inbox or reach the user.
    What happens without it: Teams mistakenly connect a new channel instead of diagnosing the initial connection.
  • Small BusinessWhy you need it: Identify which single workflow to launch next: scheduling, payments, or basic support.
    What happens without it: The workspace stays an empty playground without live customer traction.