The SMSEagle Outlook plugin adds a message window to Outlook on Windows. A user writes the text there and the device delivers it through its SIM card – as SMS, a wake-up call, or an advanced text-to-speech call – without anybody opening the web interface.
The Outlook plugin solves this simply: staff send SMS from Outlook, with no access to SMSEagle settings.
Create an API v2 key and switch on only the send permissions your users are meant to use – the plugin never reads contacts or other users’ data.
Enter the device URL and API key in Send Settings once. They stay on that machine, per Windows user, ready for every message from then on.
Everything sent from Outlook is recorded under the API key owner’s account, whoever clicked Send.
Create the key
Go to Settings > Global settings > API, open API v2, and create a key named for this integration – for example Outlook plugin – owned by the user Outlook traffic should be recorded under.
Scope it down
In the permissions box, enable just the methods your users are meant to use: section Messages: Send SMS; section Calls: Make a TTS call, Make a TTS Advanced call, and nothing else. Sending to contacts and lists happens inside Outlook, so the plugin never calls the contact or group methods.
One new button, no new app
Once the plugin is installed and Outlook is reopened, New SMS/Call shows up in the SMS group on the Home ribbon – no separate application to open or remember.
Configure delivery once
Fill in the SMSEagle URL and the API key from Step 1, then set the defaults – message type, Unicode, call duration, and the advanced TTS voice – every new message window starts from these.
Type, pick, or expand a list
Type numbers separated by commas, or pull them from the Outlook address book or a distribution list. Choose SMS, TTS, or TTS Advanced, and click Send – the device queues it immediately.
SMSEagle hardware SMS gateway
SMSEagle combines hardware and software into a single, self-contained gateway. It is designed for critical environments, so security is built in from the ground up, confirmed by CE, FCC, ISED, UKCA, PTCRB, RCM, IMDA, TDRA, CB Scheme, GCF, carrier certifications (Verizon, AT&T) and ISO 27001.
Just one API v2 key with the send permissions your users need – nothing else has to be installed on the device.
Outlook 2013, 2016, 2019, or Microsoft 365 desktop, on Windows 8 or newer. The installer adds .NET Framework 4 if it’s missing.
Yes. The plugin expands both personal Outlook lists and Exchange distribution lists, and sends to every member with a Mobile or Business phone number.
The API key’s owner. Messages and calls sent from Outlook show up in that user’s conversations and reports, whoever actually sent them.
Revoke the API key on the device. The plugin stops working immediately, with no changes to other Outlook settings.
No. The plugin resolves Outlook contacts and lists to plain phone numbers itself and hands the device a list of numbers directly.