Announcement

How to submit a support ticket in the Vodia Help Center

Published on:

October 21, 2026

Submitting a support ticket with the right information helps our team understand your issue and reduces follow-up questions. This step-by-step guide walks you through the Vodia Help Center, from describing the problem and attaching diagnostic files to setting the business impact and providing your PBX details. You’ll also learn which call details and timestamps to include, alongside practical tips to keep troubleshooting focused and help our support team investigate your issue more efficiently.

At Vodia, we know it’s not just the quality, flexibility, integrations with world-class business software, and extensive feature suite that matter to IT departments and MSPs worldwide. Reliable support matters too. 

In June of 2025 we announced that partners with valid license keys can open a detailed ticket in our new Jira portal, the Vodia Help Center. It provides partners with technical support and assistance to sales, licensing, and billing questions, alongside links to Vodia documentation and the Vodia PBX API. We describe it as “everything Vodia” in one place. 

To improve our partners’ experience in the Vodia Help Center, we’d like to provide step-by-step instructions for submitting individual support tickets, helping our support team help you. 

How to Submit a Support Ticket with Vodia

Step 1: Open the Help Center and choose a request type

Go to the Vodia Help Center and sign in. The landing page offers three request types:

  • Technical support: for issues with your PBX, phones, or Vodia apps.
  • Sales, licensing, and billing questions: for licence or invoice queries.
  • Suggest a new feature: for product ideas.

Select technical support to raise a support ticket. Before you submit, try the search bar or the related resources section - these link to Vodia documentation and the Vodia API reference, where you may find answers to common questions. 

Step 2: Describe the issue

Summary (required): provide a short, specific title. “Inbound calls from trunk X fail with 488,” for example, is far more useful than “calls not working.”

What do you need help with? (required): describe the problem in detail, including:

  • What you expected to happen and what actually happened
  • When it started and how often it occurs
  • Any recent changes, such as an upgrade, configuration change, or new trunk or device
  • Example call details: date, time, time zone, caller, callee, and extension

Step 3: Attach diagnostic files

Drag and drop files, paste screenshots, or use “Browse.” Where applicable, please provide:

  • A PCAP capture of the affected call or registration
  • Screenshots of the error or configuration
  • Syslog output covering the time of the issue

These files help our support team investigate the issue and reduce the need for follow-up questions. If you’re unsure how to capture them, check the Vodia documentation.

Step 4: Set the business impact

Choose the option that matches the real-world effect:

Level Meaning
High Major widespread issues
Medium Partial loss of functionality
Low Minor impact
No Impact No operational impact

Please note: the form defaults to “No Impact.” If your issue affects users, change this to help our team access and prioritize your request accurately. 

Step 5: Add a documentation link (optional)

If you’ve already read a relevant page on our documentation, please paste the specific URL. This tells our support team which guidance you’ve consulted and helps us improve the documentation.

Step 6: Choose with whom to share the ticket

The “Share with” field controls which organisation can see the ticket. This is normally pre-filled with your company information, so check that the selected organization is correct before submitting.

Step 7: Fill in your system details

Complete the required fields accurately to reduce follow-up questions and further back-and-forth.

  • PBX Operation System: CentOS, Debian/Ubuntu, Windows, AlmaLinux, or Rocky Linux
  • PBX Version: the exact version number (find it in the PBX web interface)
  • PBX License Key: your license key, so we can verify your entitlement
  • Active Extensions: select the range that matches your deployment
  • Paid or Trial Subscription: select whichever applies
  • Region: Americas, Europe, Asia, or Australia
  • Vodia App Issue?: select “Yes” if the problem relates to a Vodia app (such as VodiaConnect or the Vodia web phone), or “No” otherwise

Step 8: Answer the HIPAA question

The form asks whether handling your ticket could involve a potential data breach of protected health information (PHI).

Select “Yes” if your attachments, call recordings, logs, or descriptions could contain PHI. Where possible, redact patient information from files before uploading. If you’re unsure whether your ticket could contain PHI, select “Yes” and explain your concern without including sensitive details.

Step 9: Send

Review the form and click “Send.” You’ll receive a confirmation, with replies sent via email and available in the portal, where you can add comments or further attachments.

Five tips for faster resolution

  1. One issue per ticket: This keeps troubleshooting focused.
  2. Include relevant captures up front: PCAP captures and syslog output are useful for investigating SIP and media issues.
  3. Be precise about timing: Include exact dates, timestamps and the time zone so we can identify the relevant events.
  4. Set the impact honestly: This helps our team assess and prioritize your request.
  5. Reply on the same ticket: Avoid opening a new ticket for the same problem.

At Vodia, we want to help our partners succeed. Providing clear details and relevant diagnostic files when you submit a ticket helps our support team understand the issue and investigate it more efficiently.

Ready to submit a request? Visit the Vodia Help Center or get in touch at sales@vodia.com or +1 (617) 861-3490.

Latest Articles

View All

Cloud or on-premises? Rethinking phone system reliability after a Microsoft outage

The latest Microsoft outage raises a familiar question: does every service need to run in the cloud? For business phone systems, reliability depends on the infrastructure, the people managing it and the backup options available. An on-premises PBX can keep local communications running during an internet outage, while distributing systems across locations can help limit the impact of individual failures.

November 17, 2026

A PBX That Lets You Build It Your Way

Every business handles calls differently, and its phone system should support those differences. Vodia PBX gives businesses and service providers the flexibility to shape call flows, configure individual tenants and extensions, and build a branded experience for their customers. Queues, ring groups, schedules, forwarding, and AI agents can work together around each team’s requirements, while the REST API connects the phone system with wider business workflows.

November 11, 2026

The Vodia PBX Now Supports Grok

Vodia PBX now supports xAI’s Grok, giving partners another option for building AI voice agents for their customers. Using Grok’s speech-to-speech API, a Vodia Voice Agent can greet callers, ask who they’d like to speak with and transfer them to the appropriate extension. For example, a caller can simply say they’d like to speak with sales and be connected to the sales team. The article walks through what you need to connect Vodia PBX to Grok and includes a sample call transfer script you can adapt to your own call flow.

November 5, 2026