Email, phone and customer ID will be matched to a single customer
Consent will be stored per channel and checked before every send
Lifetime value, churn risk and next likely purchase will be shown for every customer

Ola Hansen

Fjordvern Forsikring · customer since 2014

PoliciesTravel · Home · Car

Annual premiumNOK 14,200

Preferred channelRCS (modelled)

Cancellation riskLow

Consent per channel

RCSWhatsAppSMSEmail

Latest events

Renewed car insurance3 weeks ago

Made a claim in the app2 months ago

Opened a travel insurance offeryesterday

Data: core systems · online account · customer service.

Who do you want to reach?

AI Segmentation › New audience

Customers on a fixed-price contract that expires within 60 days, who have not replied to the previous offer.

Build rules

The rules the platform built

Contractfixed pricecontract register

Expireswithin 60 dayscontract register

Reply to previous offernoevents

Consentmarketing: yeschecked before every send

ProposalRCS gets the best response in this groupRemove

ProposalSend on Tuesday at 18:00 – most people open thenRemove

8 410 in the group · 7 960 can be reached · 450 held back because consent is missing

RCS 6,880 · WhatsApp 610 · SMS 470

Updated every nightEdit rulesApprove and save

02 · Intelligence

The platform proposes who, what and when. You approve.

Describe the audience in plain language. The platform will build the rules, show why, and propose channel, timing and content. Sometimes the proposal is to send nothing.

Audiences will be built from one sentence, with every rule visible and editable
Signals the platform finds on its own – what the customer uses most, and when the customer replies – will be marked as suggestions
Next best action will be proposed per customer, with the expected effect
Drafts will be written in your tone of voice

Good to know Customers who got the previous offer on RCS replied twice as often as those who got it by SMS.

03 · Delivery

RCS, WhatsApp and SMS from one platform.

Three channels, each with its own strengths. The platform picks the one that gets through.

FjordvernVerified business

RCS · 18:00

Travel insurance

Going away? Travel insurance covers the whole family – even at the cabin.

See the coverCall us

Delivered 18:00 · Read 18:06

RCS

Logo, name and verified badge
Images and carousels
Buttons for links, calls and directions
Delivered and read

Best for: offers, notices that must be taken seriously, anything where the brand matters

Strømvik Energi og ServiceWhatsApp · business account

WhatsApp · 10:12

Heat pump service

Your heat pump is due for a service. Pick a time that suits you.

10.12Pick a time

Delivered 10:12 · Read 10:20

Business profile with name and logo
Image, document and buttons
Approved templates for utility messages
Delivered and read

Best for: customers who already use WhatsApp

LindraText message

Text message · 14:05

Open evening shift on Saturday, 15:00–23:00, at Lindra Søndre. Can you take it? Call the staffing desk.

Delivered 14:05

SMS

Text and links
Reaches every phone
Delivery status
Sender name without logo

Best for: what has to reach everyone, whatever the phone

Everyone gets the message.

If the recipient doesn’t have RCS or WhatsApp, the same message arrives as SMS. Automatically.

One send.You write the message once.

With RCS

Brekkvik kommuneVerified business

RCS · 08:00

Water off · Fjellveien

The water in Fjellveien will be turned off tomorrow from 09:00 to 13:00 for work on the mains. You may want to store some water this evening.

See mapCall the duty line

Delivered 08:00 · Read 08:04

Without RCS

BrekkvikText message

Text message · 08:00

The water in Fjellveien will be turned off tomorrow from 09:00 to 13:00 for work on the mains. You may want to store some water this evening.

Map: brekkvik.iqub.no/water

Delivered 08:00

Every message can be looked upWhich route it took, when it arrived and whether it’s been read.

One line on the invoiceYou pay for the channel that was actually used.

You decide the orderIn time, you’ll choose it yourselves, per template – RCS first, then WhatsApp, then SMS, for example.

04 · Result

Every krone tagged, every result measured.

Cost per message, and an invoice that matches 1:1. Then every send will be measured in what matters to you: profit for a retailer, renewals for an insurer, shifts covered in health care.

POAS (profit on ad spend) will be measured per campaign, audience and channel
Uplift against the control group will be shown in percentage points and kroner

Why profit rather than revenue? Read the article →

Result per send

Toppfart Sport · last 30 days

POAS 2.0overallTarget: POAS 1.0

Send	Sent	Cost	Profit	POAS
Welcome series	4,120	NOK 2,060	NOK 8,030	3.9
Abandoned basket	3,300	NOK 1,650	NOK 5,610	3.4
Running-shoe repurchase	2,610	NOK 1,310	NOK 3,640	2.8
Black Week reminder	12,400	NOK 6,200	NOK 4,960	0.8 Below target

Data: orders · cost of goods · sending cost. POAS = profit divided by cost; below 1 is a loss.

From sentence to call

MCP · from your AI assistant

You write

“Notify the 312 customers in Lade about tomorrow’s power cut.”

The assistant calls

send_message({
  audience: "lade",
  template: "planlagt-stromstans",
  channels: ["rcs", "sms"]
})

iQub replies

Ready for approval · 312 recipients

Simplified example. A real call also carries authentication.

Integration

Connect with the API, or from your own AI assistant.

Everything you can do in the portal, you can do via the API – or from Claude, ChatGPT or Copilot via MCP.

Send messages and fetch status and cost per message
Fetch templates per channel
Manage users, roles and senders

Privacy and security

What you can count on.

Data processing agreement in Norwegian

From day one.

Data in the EU/EEA

Both storage and processing.

Every message logged

Per recipient, with the operator’s response.

Consent on the profile

Will be checked before every send.

Next step

Try iQub in your own AI assistant.

In a walkthrough we connect iQub to the assistant you already use. You write one sentence, approve it – and the message lands on your own phone before the meeting is over.

Book a walkthrough

The team behind iQub comes from LINK Mobility, APSIS and Oracle · Meet the team →

Or write to us

hei@iqub.no

We normally reply within one working day, from the people building the platform.