Your marketing or notification system already generates a file - a nightly export, a triggered list, a CSV your CRM produces on its own. Instead of building an API integration or uploading it by hand, you point that system at a secure SFTP location. SMPPCenter picks the file up, validates it, and pushes it into your account as an SMS or RCS campaign, with a delivery report handed back the same way once it's run.
Your system dumps a CSV or XLS file - recipient numbers and message content, or a DLT-approved template reference - to a dedicated SFTP location, on the schedule that fits how your system already works: near real-time or a fixed pickup cadence.
We pick the file up and validate it - recipient number format, DLT template match, sufficient account credits, and overall file structure. Anything that fails is rejected and reported back rather than sent or silently dropped.
Validated records are pushed into your account as a campaign and sent. A delivery report is written back to your SFTP location - typically the next day - so your own system can pull it in the same way it dropped the file.
Tell us how your system produces it - we'll set up the SFTP location, validation rules, and report format around it.
Talk to a SpecialistBanking, NBFC, and government systems that already export batch files on a schedule and can't easily be re-architected around a live API.
Campaign lists exported from a CRM or marketing platform, dropped straight into a send - no developer needed for every campaign.
Teams that want the reliability of an automated pipeline without building and maintaining an SMPP or REST API integration.
SFTP file drop is one way in - if your system can call an API or hold an SMPP connection open, those paths work too. See SMPP Software Features for the full platform, or compare protocols in SMPP vs HTTP API.
FAQ