Xsquare Technology builds custom software on Plivo: two-way SMS and MMS, voice calls and IVR menus, number porting, US 10DLC registration, CRM integrations and dashboards for calls and messages. The build runs on your own Plivo account, so you keep the code, the phone numbers and the billing relationship with Plivo.
If you already use Plivo, or you are moving to it from another provider, this page explains what we build, how porting and 10DLC work on Plivo, and how a project with us runs. If you are still choosing a platform, start with our Twilio vs Plivo vs Telnyx comparison.
What we build on Plivo
Most Plivo projects are a mix of messaging, voice and a web app that ties them to the rest of the business. Typical builds include:
- Two-way SMS and MMS. Appointment reminders, order and delivery alerts, inbound replies routed to the right person, keyword handling and opt-out handling. Plivo’s Messaging API covers SMS, MMS and WhatsApp.
- Voice calls and IVR menus. Call routing, “press 1 for sales” menus, call forwarding, voicemail, call recording and conference lines.
- PHLO flows. PHLO is Plivo’s visual workflow builder. We set up PHLO where a visual flow is enough, and write code where the logic needs your database or business rules.
- SIP trunking. Connecting an existing PBX or softphone system to the phone network through Plivo’s SIP trunking product, Zentrunk.
- CRM integrations. Logging calls and texts against contacts in HubSpot, Salesforce, Zoho or a custom CRM we build for you.
- Dashboards. Browser-based screens where your team sees conversations, call history, campaign results and who needs a follow-up.
- Mobile and web front ends. When the messaging or calling feature needs its own app, our web development and mobile app development teams build it.
How voice calls work on Plivo
When someone calls a Plivo number, Plivo requests the answer URL you set for that number. Your application replies with Plivo XML, a short list of instructions that Plivo runs in order. Elements such as Speak (text to speech), Play, GetDigits and GetInput (keypad or speech input), Dial, Record and Conference cover most call flows. Outbound calls work the same way: your app starts the call through the API, and Plivo fetches XML from your answer URL once the call is answered.
That design keeps the call logic in your own code. An IVR menu can look up the caller in your CRM, check opening hours, or send the call to whoever owns that account. We write and test those handlers, add logging so you can see what each call did, and plan what the caller hears if your server is slow or down.
PHLO is the alternative for simpler flows. A PHLO can start on an incoming call, an incoming SMS or an API request, and you build it by connecting components such as IVR menus, play audio, send message and HTTP requests on a canvas in the Plivo console. It suits flows that a non-developer will want to change later.
Porting your numbers to Plivo
Most businesses want to keep their existing numbers. According to Plivo’s support documentation, self-service port-in for US and Canadian numbers is done in the Plivo console under Phone Numbers, Port-In, and Australian ports are requested through a support ticket. You will need:
- The owner’s name or business name and the service address on file with the current carrier.
- A Letter of Authorization signed by the authorized user or owner.
- A recent phone bill (Plivo asks for one from the last 30 days).
- The account number and port PIN from the current provider, if it has one.
Plivo says a port can take up to four weeks, depending on the number type and the current provider. Keep the old account open until the port completes, or the numbers can stop working. Plivo’s documentation also notes that toll-free numbers are ported for voice by default, and SMS on toll-free numbers needs a request to Plivo support. We prepare the paperwork, configure the numbers on Plivo before the port date, and test calls and texts once they move.
10DLC registration for US texting
If you send business texts to US mobile numbers from ordinary 10-digit numbers, you need 10DLC registration. Plivo states that messages from US long codes that are not linked to a registered campaign will not be delivered. Registration on Plivo has four steps:
- Create a profile with your business details.
- Register a brand for the business that sends the messages.
- Register one or more campaigns describing what you send, such as account notifications, customer care or marketing.
- Link your Plivo numbers to a campaign. Each number can be linked to one campaign.
This can be done in the Plivo console or through Plivo’s 10DLC API. Campaigns are reviewed by The Campaign Registry and the carriers, so the details matter: a clear opt-in, a privacy policy, and sample messages that match what you really send. Our guide to 10DLC campaign rejections is written for Twilio, but the review rules it describes apply on Plivo too; only the console steps and fees differ.
Moving from Twilio to Plivo
A move from Twilio is mostly a rewrite of the call-flow and messaging code, plus porting and registration. TwiML and Plivo XML do similar jobs with different element names (for example Say and Gather on Twilio, Speak and GetDigits on Plivo), and webhook parameters differ (Twilio identifies a call by CallSid, Plivo by CallUUID). We map each flow, rebuild it on Plivo, test it on a spare number, and only then port the live numbers. Your US texting also needs a 10DLC brand and campaign on the new provider, so plan that before the cut-over date.
Examples of our communications work
Our published communications projects so far are built on Twilio rather than Plivo. DialEdge AI is a MERN-stack calling dashboard for sales and support teams, and Textjin is an SMS campaign tool with a responsive dashboard. Dashboards and integrations like these use the same building blocks on Plivo: webhooks, call-flow instructions, messaging APIs and a database behind them. For Twilio work, see our Twilio development services; for Telnyx, see Telnyx development.
How a Plivo project with Xsquare runs
- We review what you have today: numbers, providers, call flows, message volumes and the systems you need connected.
- We agree a written scope with clear stages, so you can see progress before the next stage starts.
- We build on your Plivo account, test with spare numbers, and keep your live numbers untouched until launch.
- After launch you get the code, the documentation and the logins. We sign an NDA with clients as standard.
Our team is based in India, and we work with clients in the USA, Canada and other countries. To discuss a Plivo project, contact us with a short description of what you need.
Frequently asked questions
Can you work on our existing Plivo account?
Yes. We build on your account so you keep the numbers, the message history and the billing relationship with Plivo. You can give our team its own user access and remove it when the project ends.
Should we use PHLO or custom code?
Use PHLO when the flow is simple and someone on your team will want to change it without a developer. Use code when the flow needs your database, CRM lookups, complex routing or careful testing. Many projects use both.
Do we need 10DLC registration to text US customers from Plivo?
Yes, for business texting from standard US 10-digit numbers. Plivo requires a registered brand and campaign, with your numbers linked to that campaign, before those messages are delivered.
Can you show Plivo examples?
Our published case studies, such as DialEdge AI and Textjin, run on Twilio. Plivo builds use the same patterns, and we can walk you through how your project would work on Plivo before you commit.

