Munvo SMS Gateway logo

October 2026 - SMS Gateway Release Notes

SMS Gateway New Features

At a Glance

  • Work from Gemini Enterprise: ask questions and carry out SMS Gateway tasks in everyday language.
  • Understand every reply: powered by Gemini models, flowcharts now route customer replies by what they mean, including opt-out requests.
  • Stronger security: verify that webhook and Twilio traffic is genuine.
  • Faster and more reliable: an updated Twilio integration, better performance and many fixes.

Work with the SMS Gateway from Gemini Enterprise

New feature: Gemini Enterprise Compatibility

The SMS Gateway now connects to Gemini Enterprise, Google’s AI workspace for businesses, so your teams can work with it in everyday language.

Click image to enlarge

Example: A campaign manager asks Gemini Enterprise, “How many customers replied to yesterday’s appointment reminders?” and gets the answer without opening the SMS Gateway.

  • Ask in plain language: look up messaging information or carry out SMS Gateway tasks from Gemini Enterprise.
  • Works with your existing setup: uses your current SMS Gateway configuration and access permissions.
  • Built on an open standard: powered by the Model Context Protocol (MCP), so the SMS Gateway is also ready for other AI assistants that support it.

Business Value: Your teams work with the SMS Gateway from the AI workspace they already use, with less switching between tools and faster routine tasks.

Note: This capability is optional and does not change how the SMS Gateway works today. An administrator connects it once from the Gemini Enterprise admin console, and our team can assist with setup. The updated documentation walks through each step.

See it in action: read our blog post [link to come] for a step-by-step walkthrough of Gemini Enterprise working with the SMS Gateway.

Understand What Customers Mean, Not Just What They Type

New feature: Intent-Based Routing

Powered by Google’s Gemini models, your flowcharts can now understand each customer reply and route it based on what it means, instead of requiring an exact keyword.

Example: replies to an appointment reminder.

Customer reply
Detected intent
What happens
"Yes, see you then!"
Confirm
Appointment confirmed
"Can we do Thursday instead?"
Reschedule
Customer sent to the rescheduling path
"Please stop texting me"
Opt-out
Customer unsubscribed; no further messages
Customer reply
"Yes, see you then!"
Detected intent
Confirm
What happens
Appointment confirmed
Customer reply
"Can we do Thursday instead?"
Detected intent
Reschedule
What happens
Customer sent to the rescheduling path
Customer reply
"Please stop texting me"
What happens
Opt-out
What happens
Customer unsubscribed; no further messages
  • Handles real replies: free-form answers, typos and variations that keywords miss.
  • A path for every intent: each intent leads to its own path, with a fallback for unclear replies.
  • Safer opt-outs: opt-out requests are recognized even without a keyword like STOP, and the customer is no longer contacted.

Business Value: More natural conversations, fewer replies that reach a dead end, and stronger compliance with customer communication preferences.

Note: Existing keyword-based flowcharts keep working unchanged. Intent-Based Routing is turned on per flowchart; review your opt-out paths when enabling it. See the updated flowchart documentation for configuration details.

Also in This Release

Twilio Signature Validation (Recommended)

The SMS Gateway can now verify that incoming messages and delivery updates genuinely come from Twilio, and reject anything that doesn’t. This protects your platform from forged messages. The feature is off by default and we recommend turning it on; the public URL configured in Twilio must exactly match the URL the gateway receives. See the updated documentation for setup steps.

Webhook Authentication

Webhooks sent by the SMS Gateway can now carry authentication credentials, so your receiving systems can confirm each request is genuine. This is optional, and existing webhooks keep working as before. Configuration details are in the updated documentation.

Keywords in Every ISO Language

Keywords can now be configured in any ISO 639 language, so you can respond to customers in their own language across all your markets. Existing keyword configurations are unaffected. Choose the language when configuring a keyword in the flowchart editor.

Faster, More Up-to-Date Platform

The Twilio integration has been updated to the latest supported version, message processing is faster, AWS deployments are more reliable, and improved internal monitoring helps our team detect and resolve issues sooner.

Reliability Fixes

  • Phone number format: phone numbers are now stored in one consistent format, improving matching with integrated systems.
  • Long phone numbers: fixed an issue where long phone numbers could exceed their storage field.
  • Conversation timeouts: reworked timeout handling for more predictable behavior.
  • Duplicate expiration messages: fixed a case where customers could receive two expiration messages for the same conversation.
  • Webhook settings: fixed an error that occurred when webhook settings were left empty.
  • And more: numerous smaller stability fixes across the platform.

Before You Upgrade

  • Phone numbers are now stored in a standardized format; integrations that rely on the previous format should be reviewed.
  • Conversation timeout handling has been reworked; flows that depend on exact timeout timing should be tested.

Get More from Your SMS Gateway

Ready to put these new capabilities to work? Contact Munvo to explore Gemini Enterprise compatibility and Intent-Based Routing for your messaging workflows. Our team can help you plan your upgrade, configure the new features and answer any questions about this release.

© 2026 Munvo is a trademark of Munvo Solutions Inc.

Search