Skip to content
Engage

Bring people back with what they asked for.

Reach the people who already told your app what they want, without building a segment or writing a campaign. Rendel is the AI assistant inside your mobile app or website: Engage groups what people ask it for, writes each message from your app’s own data, and sends it by push or inside the app.

Halden’s console, an invented store with Rendel running. Yours for two hours, no sign-up.

65 people asked. One message is ready.

Halden, an invented store with Rendel inside: the people who want the same thing, the message Rendel wrote for them, and where it lands.

Why it matters

Your customers already told you what would bring them back.

Every day people tell your app what they are looking for: a size, a colour, a price, a feature. Acting on it usually takes a second tool, a tracking plan and someone to write every message, so it rarely gets followed up.

The wish ends with the conversation.

“White sneakers under $130, in a 42” is the most useful thing a customer can tell you. Without a way to keep it, nobody tells them when the Court Mid comes in at $126.

A separate tool wants a tracking plan first.

Engagement platforms build audiences from events your engineers plan and instrument, and someone turns those into segments by hand. That is another SDK and another contract before the first message goes out.

Messages about nothing in particular get ignored.

Pushes sent after something a customer did were opened at 14.4%, against 4.19% for generic ones, in Batch’s 2025 push benchmark. Those are industry figures, not Rendel’s.

Source: Batch’s 2025 push benchmark
How it works

From what they said to their phone, in four steps.

Engage starts from the conversations your assistant already has, so there is nothing to tag or track first.

  1. People tell the assistant what they want.

    When someone asks for white sneakers under $130, Rendel notes the wish and adds them to the people who want the same thing.

  2. Rendel finds the moment and writes it.

    When an item now matches, an offer fits or people go quiet, Rendel counts who it reaches and writes the message from your app’s data.

  3. You check it, then send.

    See it on a phone, change any word, then send. Send always asks you to confirm the number of people, and a suggestion asks once it reaches 50.

  4. It reaches them where they’ll see it.

    In the app if they used it in the last day, otherwise by push. It also waits as a card at the top of the assistant, which opens straight onto it.

Suggestions

Open Engage to messages that are already written.

No blank campaign to start from. Rendel looks at what people asked for, what your app now has and who has gone quiet, then counts the people and writes the message before you arrive, so each one is a tap from sent or switched on.

Tell people the moment what they want comes in.

When three or more people want the same thing and an item now matches it, because it is new, back in stock or cheaper, Rendel suggests telling them, and adds a live offer when most of them qualify. The item comes only from your app’s own search results.

  • Mobile and web

Win back people who went quiet, in one tap.

When ten or more people haven’t opened your app in 14 or 30 days, Rendel suggests a message with an offer. One tap reaches them now and turns on a rule for anyone who drifts away later.

Switch on what people are waiting for.

If a follow-up is off while people wait for it, Rendel says how many and turns it on with one tap.

Tell the people who asked that it’s here.

When you ship something people asked your app for, Rendel offers to tell everyone who asked.

The most valuable first, and no repeats.

Suggestions are ranked by how many people each reaches and what it can do. A group you messaged in the last 14 days is left out, and one you put off comes back only once it has grown.

An empty page still shows the next step.

With nothing to suggest yet, the page names the one step in the way, then the follow-ups that work right away: Answer arrived, Tell me when, Price and stock watch and Date reminder.

Ready when you open it, and counted where you see it.

Rendel writes suggestions ahead, so the page opens with no waiting. A line on top says how many messages those drafts counted this month.

It starts when you switch it on.

Rendel notes wishes and builds groups only once Automations are on, and a group becomes a suggestion at three people.

Send

One sentence, and every channel is written.

Say in one sentence what you want to tell a group. Rendel writes the push and the in-app message in your assistant’s voice, fills every fact from your app’s data, and shows it on a phone before it goes.

Write one sentence, get every channel.

Every channel comes back written to fit, benefit first and in your assistant’s voice. Prices, codes and links go in as fields filled from real data, so a price typed into the message is refused.

The offer, set up from the same sentence.

Mention a discount or a code and Rendel proposes the offer too: its title, discount, code and days. It goes live only when the message goes out.

  • Not in the demo console

See it on their phone before it goes.

The message on a phone in your app’s look: on the lock screen, as a popup or banner in the app, and as the card inside the assistant.

PushIn the appIn Halden

Know who it reaches before you send.

See how many people it reaches now, and how many on each channel. Daily limits and quiet hours can still hold some back for a few hours.

  • Halden’s demo numbers

Send now, or on the day it matters.

Pick a day and time in your own time zone, and call it back any time before it goes. Each person’s message expires two days after it is due.

Or write it yourself, with the same checks.

Write one text and Rendel makes each channel’s message from it, the first sentence as the title. It gets the same checks, and you can add a personal field these people have a value for, such as what they asked for or the offer’s code.

Written natively in English or Turkish.

A message you send to a group is written once, in English or Turkish, and natively in each. Follow-ups Rendel sends by itself are written for each person in their phone’s language.

Try it on your test key first.

In the console’s test view, a send reaches only people on your test key, and it uses none of your messages.

Audiences

Groups that build themselves from what people ask.

When someone tells the assistant what they want, the wish joins the group of people who want the same thing, named after it. You pick a group; nobody builds a segment.

Everyone who wants the same thing, already grouped.

Each group is named after what its people want, in a few words, and health topics are kept out. A wish lasts 30 days, and Send lists a group once three people are in it.

  • Starts once Automations are on

Everyone who asked for the same feature.

Requests your app can’t do yet, counted in Improve, become groups too, so the people who asked hear when you build one.

A saved segment, or the people a search found.

Use a segment from your product analytics, or search Users and message exactly the people it lists, such as everyone who asked about returns.

Everyone, or just the people you mean.

Reach everyone seen in the last 7, 30, 90 or 365 days, up to 20,000 devices, and narrow it to a language or to iPhone, Android or your website.

Channels

On the lock screen, in the app, and inside the assistant.

Push on iPhone and Android, a popup or banner on your app’s own screens, and a card at the top of the assistant that opens straight onto the message.

In the app, while the assistant is closed.

A popup by the assistant’s button, or a banner across the top of your screens, for people who used your app in the last day. If the app doesn’t show it within 48 hours, it goes by push instead.

  • iOS, Android and web
PopupPopup · Banner
Banner

A second place to find it: a card inside the assistant.

Whichever way a message goes, it also waits at the top of the assistant for seven days, up to three at a time. A tap opens a conversation that starts with the message.

  • Free to read
  • Mobile and web

Push on iPhone and Android, with your own keys.

On iPhone, Rendel sends straight to Apple with your app’s .p8 key, with no Firebase in your iOS app. On Android it sends through your Firebase project, from its service-account file.

  • iOS and Android
  • No browser push

One message each, on the channel they’ll see.

Let Rendel pick for each person: the app if they used it in the last day, otherwise push. Or send on every ticked channel at once; it still counts once toward their daily limit.

See it on your own phone first.

Send a push to the phone you paired on Test and see exactly what your users will see.

  • Not in the demo console
Automations

The right moment for each person, without pressing Send.

Catch each moment a customer is waiting for: an answer arriving, a price dropping, a size coming back, a date getting close. Rendel follows up by itself, in each person’s own language.

Seven follow-ups that run by themselves.

Each one starts from something a person told the assistant, is written for that person in their phone’s language, and has its own switch.

  • Halden’s demo numbers

No follow-up goes out until you say so.

A new app starts with every follow-up ready and the main switch off, so your team picks the day it starts.

Timing you can tune.

Price and stock checks every 12 hours, date reminders 3 days ahead, one nudge 24 hours after someone left without buying. Change each, and allow a coupon only if you want to.

Welcome everyone who joins a group.

Write one message for a group, and each person who joins it from now on gets it once, while they still want it.

Bring back people who drift away.

Pick 3, 7, 14, 30, 60 or 90 days. Each person gets your message on the day they reach it, and again if they come back and drift away later.

People hear when their answer is ready.

When someone leaves before Rendel finishes, it finishes anyway and tells them, or tells them a confirmation is waiting. These notices are free, go to one person at most five times a day, and are on from the start.

  • On by default
  • Free
How notify-when-done works
When it's done
When a confirmation waits
Offers

Run an offer, and only the people it fits hear about it.

Type the offer in a sentence and Rendel fills in the form for you to check. A live offer reaches the people whose wishes and budget fit it, and the assistant mentions it when someone asks about deals.

Set up an offer from one sentence.

“20% off everything this weekend” becomes a title, a 20% discount and a Saturday-to-Sunday run, ready for you to check. Nothing is saved until you do.

Only the people it fits hear about it.

Each offer is matched to people whose wishes and budget fit it, and a coupon stops at the number of codes you set.

Mentioned when people ask about deals.

Live offers become part of what the assistant knows, so “is there a discount?” gets today’s offers, and an offer drops out when it ends.

History

See what each message brought back.

Each send shows how many people got it, how many opened it, what they bought after and the revenue. It also shows which channel carried it and which pushes failed, in words.

Sent, opened, bought, in one row.

“Opened” is a tap, counted once. A purchase counts toward the last message the person opened within seven days, from your app’s purchase event or an action you mark as a purchase.

  • Purchases need one SDK call
  • Halden’s demo numbers

Only counts, where messages are private.

Roles without access to conversations see the numbers, not the words people got.

  • Halden’s demo numbers

Everything about one person, on one page.

On a person’s page in Users: where they can be reached, what Rendel follows for them, their groups, their last messages and anything they turned off. Topics only, never their words.

Try it in Halden

Send Halden’s white sneakers message yourself.

Halden is an invented shoe store with Rendel inside. Its console is yours for two hours, with no sign-up, and this is the flow to follow, start to finish. The counts in your copy will differ from the ones drawn here.

  1. Open Engage. Suggestions is already full: two wishes, a follow-up to turn on and a win-back.
  2. Take the first one: the people who want white leather sneakers, most of them in line for free socks, now that the Court Mid is in at $126.
  3. Tap See it on a phone to read it the way they will.
  4. Tap the send button on it and confirm.
  5. Open Halden app from the demo bar to see it arrive, then tap it: the assistant opens on the message.
  6. Back in the console, History lists the send. Its opens come in over the next few hours, as they would after a real send.

Try it in Halden’s console.

Send the white sneakers message and watch it reach Halden’s phone. Nothing reaches a real person, every number is invented, and the demo’s writer gives a fixed message whatever you type.

Try the console
Compared

Next to a separate engagement tool.

Braze, OneSignal, Insider One and Netmera run full lifecycle programmes, and Engage doesn’t try to replace them. It covers what people ask your app’s assistant for, from the SDK you already have, and many teams will want both.

WhatRendel EngageA separate engagement tool
Who you messagePeople grouped by what they told your assistant they wantSegments built from events you planned and tracked
What to sendSuggestions already written, each with how many people it reachesA blank campaign; some tools now suggest from behaviour data
Writing itOne sentence; Rendel writes each channel and fills its facts from your dataA composer per channel, with AI copy help in most tools
Where it landsPush, a popup or banner in the app, and a card inside the assistant that opens onto itPush, in-app, email, SMS and more, opening a screen in your app
SetupThe SDK already in your app, plus one key file per platform for pushAnother SDK, an event plan and often a data pipeline
Journeys and testingTwo kinds of rule and seven follow-ups that run by themselves; no A/B testsStronger: multi-step journeys, A/B tests and holdout groups
ChannelsPush on iPhone and Android, in the app and in the assistant; no SMS, WhatsApp or browser pushStronger: SMS, WhatsApp, browser push, email and more
CostMessages on your Rendel planA separate contract, usually priced by active users or profiles
Controls

Your team decides how often, when and who.

Limits that hold across every message, quiet nights, a check before a send goes, and a way to stop everything for one person.

One limit across every message, and quiet nights.

By default each person gets at most 1 message a day and 3 a week across every message Rendel sends them, task notices aside, and no push between 21:00 and 09:00 in their own time zone. In-app messages still show when they open the app.

Only the roles you choose can send.

Owners, admins and developers can send. Send always asks them to confirm the number of people, and a suggestion asks once it reaches 50 or more. Analysts, conversation reviewers and support agents see the results, as counts where the messages are private.

Facts from your app, or no message.

Every price, code and link in a message is a field filled from your app’s data. A message that types out a price or names a value it doesn’t have is not sent.

Room to breathe after a chat.

Rendel waits six hours after someone’s last conversation before a follow-up, except answers to their own questions, alerts they asked for and your own sends. Someone due two messages about the same thing gets one.

The topic stays off the lock screen.

When a question someone asked gets its answer, the push says there is news and the topic shows once they open it, unless you choose to name it on the lock screen.

How people turn it off.

Engage is opt-out: anyone your app can reach may get a message until they turn it off. Turning off notifications on the phone stops push, and your team can stop all follow-ups for one person. People have no switch inside the app to stop them, and Rendel doesn’t collect marketing consent: that stays with your app.

Sensitive topics stay out of groups.

Health topics are screened out before a wish joins a group, and a wish is dropped after 30 days.

Spending stops when your messages do.

If your organization’s messages for the month are used, or its budget is paused, nothing goes out. Messages wait until their time runs out instead.

Getting started

What it takes to turn on.

If Rendel is already in your app, Engage is a switch and a key file away. In-app messages and the cards inside the assistant need no keys at all.

  1. Rendel live in your app.

    Cards, popups and banners need the Mobile SDK 0.59.7 or later or the Web SDK 0.38.7 or later, and your app must be live.

  2. Turn on Automations.

    One switch. Every follow-up is already set up and waits for it.

  3. Add your push keys.

    In Settings › Channels, add your Apple .p8 key for iPhone and your Firebase service-account file for Android. Push on iPhone needs the Mobile SDK 0.68.0 or later, with the rendel_push package.

  4. Know how it counts.

    Engage is on every plan and uses your plan’s monthly messages. Cards inside the assistant, task notices and test-key sends are free.

What counts as a message, and what doesn’t.

A push to 65 people counts 65 messages, plus one for the draft Rendel wrote.

Each plan’s messages, and the price of extra ones

Counts

  • Each push or in-app message delivered: one per person, per channel
  • Each message Rendel writes for one person: about two with its delivery
  • Each draft or rewrite, on Send, a suggestion or an offer
  • Each wish Rendel files into a group

Free

  • Reading the cards inside the assistant
  • Task notices
  • Anything on your test key

What teams ask before they start.

  • The part of Rendel’s console that messages your app’s users again, starting from what they told the assistant. It groups their wishes, suggests messages already written from your app’s data, and sends them by push, as a popup or banner in your app, and as a card inside the assistant.

  • From conversations. When someone tells the assistant what they want, the wish joins the group of people who want the same thing, named after it. Groups start forming once Automations are on, a wish lasts 30 days, and Send lists a group once three people are in it. Health topics are kept out.

  • No. Prices, codes, items and links go into a message only as fields filled from your app’s own data, and a suggested item comes from your app’s real search results. A message that types out a price or a link, or names a value it doesn’t have, is not sent.

  • Push on iPhone and Android, a popup or banner on your app’s own screens, and a card at the top of the assistant, in mobile apps and on websites. Websites get no browser push. Email from your own domain is built but not switched on yet, and there is no SMS or WhatsApp.

  • By default each person gets at most one message a day and three a week from Rendel, not counting task notices, and no push between 21:00 and 09:00 in their own time zone. You can change both. Rendel also waits six hours after someone’s last chat, and a person due two messages about the same thing gets one.

  • Engage is opt-out: anyone your app can reach may get a message until they turn it off. Turning off notifications stops push, and your team can stop everything for one person. Rendel doesn’t collect marketing consent and your app can’t pass a person’s choice to it, so check what your market requires before you send campaigns.

  • Engage is on every plan and uses your plan’s monthly messages. Each push or in-app message delivered counts as one, and so does each message Rendel writes, so a follow-up it writes and delivers is about two. Cards inside the assistant, task notices and your test key are free. A push to 65 people counts 65, plus its draft.

  • No. On iPhone, Rendel sends straight to Apple with your app’s .p8 push key, added in Settings › Channels. Android push goes through Firebase Cloud Messaging with your project’s service-account file. Both need the rendel_push package next to the Mobile SDK.

  • Engage doesn’t replace a journey tool, so yours keeps running its campaigns while Engage reaches people about what they asked your assistant. Rendel’s daily limits count only Rendel’s own messages, so plan how often people hear from each.

  • History shows each send with how many got it, how many opened it (a tap, counted once), what they bought within 7 days and the revenue, plus the channel split and pushes that failed. Purchases need one SDK call from your app. There are no A/B tests and no email open tracking.

  • Rendel sends to 200 people every five minutes, about 2,400 an hour per send. A group of a few hundred is done well within the hour, and 20,000 people take about eight hours. Daily limits and quiet hours can hold some people back, and each message expires two days after it was due.

  • Messages from Send, Suggestions and your own rules are written once, in English or Turkish, and natively in each. Follow-ups Rendel sends by itself are written for each person in their phone’s language.

Put it in your app this week.

Start free on your own, or tell us what your customers do most and we’ll show you that exact workflow, working, in a tailored demo.

  • PilotFree400 messages a month
  • Starter$199 / month4,000 messages a month
  • Growth$799 / month20,000 messages a month
Every plan, and the estimatorOr try a live store’s console first, yours for two hours

Prefer email?

sales@rendel.ai

Prefer to write first?

Tell us about your app and we’ll show the right workflow in a tailored demo.

Help us tailor the demoOptional

We use this to get in touch about the demo and, if a partner introduced you, to credit them. We never sell it. See the privacy policy.