Vodia’s new SMS Management feature centralizes all customer SMS provider connections under SIP Trunks for each tenant. It allows you to easily add supported providers and manage SMS numbers with custom settings like name, number, provider and message routing. Policies can be created for opt-in/opt-out messaging, welcome messages, message retention and conversation management with keywords. Additionally, menu selections offer customizable options for customers, such as providing information or directing them to URLs. This enhances SMS management by streamlining provider setup and message handling for better customer interaction.
Under Numbers, you can specify the SMS number for the user to check the values below:
Name: Name with customer or group name
Number: Add the SMS DID
Policy: If no policy has been created, choose "none"
Provider: Choose your provider
URL prefix: This prefix can be unique for each number: set the prefix you want in the provider portal and use that prefix when you assign the SMS number
Source: Souce can come to the assigned extension
Destination: Destination messages can be sent to any other extension or to the same extension
Policies
You can create policies for your SMS messages: check below for what each policy can be used
Names Policy: Name the Policy
Opt-in or opt-out: Choose what kind of policy this will be "opt-in or out"
Welcome message: Write a welcome message for the customer
Resend welcome message after: choose the number of days for the duration of the message
Keyword for stopping conversation: Choose a keyword - for example "Stop"
Keyword for resuming conversation: Create a message if the user would like to continue
Duration for keeping messages: Choose the number of days Vodia will keep the messages
Allow only text messages: Turn on or off to only allow texting
Menu selection
In this section, you can create a set of destinations for the customer under the first box with a name for the menu, which can be anything, and then the message box. Themessage box can contain information about a product - you can include a URL for the customer to explore and provide a list of actions from which they can choose.
Vodia’s 2025 marked a year of pragmatic AI adoption, unprecedented platform robustness, and laying the foundation for the next phase of the PBX. With version 69 reaching exceptional stability, focus has shifted to version 70, which introduces a redesigned admin interface and major architectural improvements in scalability, resilience, and flexibility. Alongside steady expansion of integrations and partner tooling, the roadmap for 2026 emphasizes refined user experiences, modernized apps, and continued investment in reliability over hype.
Delaying PBX upgrades may feel safe in the short term, but real-world dependencies like security standards, app compatibility, and vendor APIs eventually force reactive upgrades at the worst possible time. Staying reasonably current with Vodia PBX versions, rather than clinging to outdated releases or jumping on every new preview, helps maintain security, compatibility, and performance while avoiding emergency upgrades, especially as newer features and OS requirements become unavoidable.
The New York City Department of Education has issued a Request for Expression of Interest signaling its intent to modernize district-wide communications by moving away from legacy landline PBX systems. Serving 1.1 million students across 1,800 schools, the proposed transition to a cloud-based VoIP platform focuses on resiliency, scalability, multilingual capabilities, hybrid deployment options, and integration with Microsoft Teams for more than 150,000 staff members.
.svg)
