Business SMS AssistantYour business.Now taking texts.
Customers text a question about classes, appointments, availability or stock and get an answer from your real schedule and systems. UDX connects the assistant to what you already run, tests the whole journey and keeps it operating.
The answer comes from your business, not a script.
Neuron reads the systems you already keep current: your website, your schedule, your booking or service tools. It answers with what is true at that moment. When it cannot answer, it says so and hands the customer to a person.
A customer texts a question
A plain question to your business number, typed the way people already text.
Neuron reads live data
It reads your website, schedule and booking tools at that moment. Nothing is written in advance.
The reply is specific
Dates, times, places and open spots come from the source, so the reply matches what is true right now.
The next step is a link
When there is something to book, the reply includes the link to the page you already use.
Built in the open. Verified in production.
Destination Pickleball already kept classes, times, locations and availability in WordPress. UDX connected that business context to an SMS assistant powered by Amazon Bedrock and carried the change through review, release and browser verification like any other production software.
Destination booking page
The schedule behind the answer
The classes, times, locations, prices and remaining places the assistant reads before it replies.
WordPress operated by UDX
Two AI reviewers inspect the change
Devin and Copilot review the implementation. One calls out the production validation that still has to happen.
Rabbit CI carries it to production
Application and infrastructure changes move through validation, deployment and a visible release record.
How Rabbit CI works
The customer journey is exercised after release
Browser tests check the booking experience and report the result. The work does not end at deployment.
What would your customers text you?
Start with the question you get most often and the system that already holds the answer. Every one of these is a conversation a connected assistant can carry.
The first version usually answers one recurring, valuable question well. Then it grows.
Tell us what customers should askA new customer channel. Built like production software.
The conversation is the simple part. UDX does the connecting, the verification and the ongoing work behind it.
Connect the knowledge
WordPress, schedules, catalogs, booking tools and the business information that answers real questions.
Define the behavior
What the assistant can answer, when it should hand off and what it must never invent.
Test the whole journey
The question, the underlying data, the answer and the next step, checked together before launch.
Keep it operating
Controlled deployment, monitoring and continued iteration through Rabbit CI and UDX.
Before the first conversation.
Does this replace our website or booking system?
No. The useful version connects to the systems you already have. Your website, schedule, catalog and booking flow remain the sources of truth.
What can the assistant answer?
It can answer questions supported by the business information and rules we connect. A first version usually starts with one recurring, valuable question and expands from there.
What happens when it does not know?
We define that behavior deliberately. The assistant should acknowledge the limit and route the customer to a useful next step or a person, rather than invent an answer.
Can it complete a booking?
It can begin by answering questions and linking into your existing booking flow. Deeper actions depend on the systems and permissions you want to connect.
Who builds and maintains it?
UDX connects the data, defines the behavior, tests the customer journey, deploys the assistant and monitors it after launch.
When is an SMS assistant not worth building?
When customers rarely ask the same question twice, when the answer is not kept current in any system, or when a phone call already settles it in under a minute. In those cases we will say so. The assistant earns its keep on recurring questions that a live system can answer.
Twilio or Mailchimp. Your account, your call.
Neuron sends and receives through a carrier account in your name. It runs on Twilio or on Mailchimp SMS, and UDX connects whichever fits your volume and the tools you already pay for. Move the slider to compare each carrier's published price at your monthly volume.
$43 to $61a month
$0.021 to $0.031 per conversation
$0.0083 per segment sent and received, plus carrier fees that differ by network. A local number is $1.15 a month and 10DLC campaign registration $1.50 to $10 a month. The range spans AT&T, T-Mobile and Verizon.
Twilio US SMS pricing$45a month
$0.023 per conversation
A monthly bundle of 2,500 credits for $25, plus the Standard plan at $20 for up to 500 contacts. One credit per outbound segment, and Mailchimp lists no charge for incoming texts. Unused credits expire at the end of the month.
Mailchimp SMS pricingAt 2,000 conversations a month, Mailchimp's bundle comes in about $-2 to $16 a month under Twilio.At 2,000 conversations a month, Twilio comes in about $-16 to $2 a month under Mailchimp.At 2,000 conversations a month the two overlap. Which is cheaper depends on the networks your customers are on.
Neuron does the same work on either carrier. The number, the account and the message history stay yours, and UDX's design and operations work is scoped separately from what the carrier charges.
Published list prices for US long-code SMS, checked October 18, 2026. A reply longer than 160 characters uses more than one segment. Not included: Twilio's one-time 10DLC brand registration, Mailchimp plan tiers above 500 contacts, MMS, toll-free numbers and taxes. Mailchimp includes standard carrier vetting with bundles of 5,000 credits or more.