VooDoo SMS

The VooDoo SMS integration sends text messages from OpsMerge through VooDoo SMS, a UK SMS gateway. Alert notifications reach your on-call techs even when they are away from email, new tickets can ping the service desk, and you can send ad-hoc SMS to contacts straight from OpsMerge.

Availability: UK organisations only. VooDoo SMS delivers via UK direct-to-carrier routes and bills in GBP; it has no US carrier registration. The integration only appears in Settings when your organisation's country is set to the United Kingdom.

Bring your own account

OpsMerge never resells SMS credits. You hold your own VooDoo SMS account, top up credits in the VooDoo portal, and paste your REST API key into OpsMerge. Your live credit balance shows on the integration page, and every message sent uses credits from your own balance (typically one credit per 160-character message; longer or unicode messages use more).

What you get

• Alert SMS — when an alert fires at or above a severity you choose, the numbers you list get a text. Optionally restrict to specific alert types (device offline, check failures, domain monitoring, backups, and so on); leave the type list empty to receive all of them. One global template, editable on the page.
• Ticket incoming — a new ticket arriving from a client (portal, inbound email or an alert-raised ticket) texts your service desk numbers. Tickets your own staff create do not trigger it.
• Ticket replied to — a client replying to a ticket texts the assignee's mobile (from their user profile). Internal notes and staff replies do not trigger it.
• Ad-hoc SMS — compose a message to selected contacts (those with a phone number) and/or typed-in numbers.
• Audit log — every SMS the platform sends is recorded with its delivery status (Delivered, Undelivered, Expired, Rejected), updated from VooDoo delivery reports for 48 hours after sending.

Setup

1. Sign up at voodoosms.com if you don't already have an account (trial accounts come with free credits).
2. In the VooDoo portal, generate a REST API key — see How to get your API key.
3. In OpsMerge, go to Settings → Integrations → VooDoo SMS.
4. Paste the API key and choose a Sender ID — 4 to 11 letters or digits, shown as the sender name on recipients' phones (e.g. your MSP's name). The key is verified against your VooDoo balance before it is saved, and stored encrypted.
5. Enable the events you want, add recipient numbers, and adjust the templates.

UK mobile numbers can be entered as 07700 900123 or 447700900123 — OpsMerge normalises them before sending.

Templates

Each event has an editable message template using {{.Variable}} placeholders. Click a variable chip under the template box to insert it.

Event	Variables
Alert	{{.Severity}}, {{.AlertType}}, {{.AgentHostname}}, {{.Message}}, {{.CheckName}}, {{.Timestamp}}
Ticket incoming / replied	{{.TicketNumber}}, {{.Subject}}, {{.ClientName}}, {{.Requester}}, {{.Priority}}, {{.Status}}

Messages are capped at 918 characters (402 when the text contains unicode characters such as emoji or smart quotes).

Cost control

SMS costs real money, so two guards are built in:

• Hourly cap (default 100) — the maximum SMS the platform sends for your organisation per rolling hour, across all events. Sends over the cap are dropped and recorded in the audit log as Throttled, so an alert storm cannot drain your credit balance.
• Send-error banner — if VooDoo rejects a send (most commonly out of credits), the error shows at the top of the integration page until a send succeeds again.

Permissions

Permission	Grants
sms.manage	Connect/disconnect, edit templates, recipients and limits
sms.send	Ad-hoc and test sends, view the audit log

Admin roles get both by default; Technician roles get sms.send.

Troubleshooting

• "VooDoo SMS rejected the API key" — regenerate the key in the VooDoo portal (Send SMS → API SMS) and reconnect. Keys are account-wide, not per-sub-account.
• Balance shows "unavailable" — VooDoo's API was unreachable when the page loaded; the connection itself is unaffected. Refresh the page.
• Messages stuck at "Sent" — delivery reports are polled every 5 minutes; a message undelivered after 48 hours expires at the carrier and is marked accordingly.
• A contact was skipped in an ad-hoc send — the contact has no phone number, or the number could not be normalised to a sendable form.