Skip to content
PreemptiveIntelBusiness Systems

Platform service · In development

Messaging hub

One service for SMS and email from all your systems.

Let's talk

A small service that other systems call to send text messages and emails, with a choice of sender. Templates, a delivery log and retries let every product notify people the same way.

What it covers

  • One API for SMS and email
  • Choice of sender identity
  • Templates and a delivery log (planned)
  • Retries and failure alerts (planned)
  • Shared by all our systems

Built for

Organisations whose systems each send messages in their own way.

Screens on this site are illustrations with invented sample data. Tax rules and e-invoicing support are being verified with qualified advisers and official sources. Nothing here is a statement of filed or certified compliance.

messaging / delivery log (sample)
SMSAttendance alertDelivered
EmailInvoice reminderDelivered
SMSOne-time codeDelivered
EmailEvent invitationRetrying
SMSFee noticeQueued
All projectsAttendance terminal gatewayAll projectsIdentity Management System

Key screens

messaging / templates (sample)
Attendance alertSMS
Invoice reminderEmail
One-time codeSMS

Hello {name}, your {item} is ready.

messaging / delivery report (sample)

Sent

5,420

Delivered

5,318

Failed

36

Messages per day (sample)

messaging / senders (sample)
SenderChannelUsed by
Sender ASMSAttendance
Sender BEmailBilling
Sender CEmailEvents

Illustrations with invented sample data. Screens are customised to each client.

How we would build it

  1. 01

    Listen

    We learn how your work runs today: who does what, with which files and rules.

  2. 02

    Design

    You see screens and a fixed scope with a plan and a price before we build.

  3. 03

    Build

    We deliver in short stages with live demos, so you steer as it takes shape.

  4. 04

    Support

    We deploy, train your team, and stay for fixes and the next improvements.

How do you price a project?

After the design step you receive a fixed scope, a plan and a price. Work outside that scope is quoted separately, before it starts.

Who owns the system and the data?

You own your data. Ownership and licensing of the code are agreed in writing before work starts.

What happens after launch?

We deploy, train your team and stay available for fixes and improvements, under a support arrangement agreed up front.

Contact

Have a workflow that needs a system?

Describe how it runs today. We will reply with questions and a proposed next step.

Start the conversation