Skip to main content
A prompt is a pop-up message that customers see in your app. This page shows you how to create one in a campaign and publish it.
A prompt always belongs to a campaign. Open the campaign first, or create one.

​
Add a prompt to your campaign

You can add a prompt in the campaign’s List view or on its orchestration canvas. Either way, the Create Prompt form opens. Add it on the canvas when a flow should decide who sees the prompt and when. A Preferred store prompt needs this, because it reads each customer’s suggested store from the block before it. Recipients explains how a flow decides who gets a communication, and when.
  1. Go to Campaigns and open the campaign the prompt belongs to, or create a new one.
  2. Select Add activities, or Add activity if the campaign already has some.
  3. On the Select an activity page, point at the Prompt tile and select From scratch. To start from a saved prompt instead, select From template. Reuse with templates explains how.
The Create Prompt form before a type is picked. Details has an empty Name, Background color #00000000, an empty Text color and an empty Analytics identifier. Type has an empty What type of campaign do you want to create? field, and there's no Message content panel yet. Segmentation has All selected, with Audience below it. Schedule shows Start date 2026/11/02 00:00 and End date 2026/11/29 23:00, filled in from the campaign. Save and Publish are greyed out. The Create Prompt form before a type is picked

​
Fill in the details

Once you’ve saved the prompt, its ID shows at the top of Details, with a copy icon.

​
Choose the prompt type

Under Type, open What type of campaign do you want to create? and pick a type. The type decides what the prompt does for the customer and which fields the form adds. Changing the type clears the image, the suggested store field and any button navigation you’ve set. The headline, body and button texts stay. Select field with suggested store id lists the details the prompt gets from the block connected before it. Pick the one that holds each customer’s suggested store. The list stays empty until the prompt’s block is connected after a block that passes on customer details. That block has to pass on each customer’s suggested store. Connect it on the canvas and select Save, then open the prompt again. Block reference shows which blocks those are.

​
Write the message

The Message content panel appears once you’ve picked a type. Fill in at least one of Image, Headline text and Body text. When the prompt’s block is connected after a block that passes on customer details, you can add those details to Body text. Type { and pick one from the list. It shows in the text in braces, such as {CustomerId}, and each customer sees their own value. See Personalise a triggered communication. Preview shows the prompt as you build it. Then name the buttons. A Regular prompt needs at least one of the two. As soon as you name a button, pick where it takes the customer:
  • In-app navigation opens a place in your app. Pick it under Choose from list. See Deeplinks.
  • Navigate to external URL opens a web page. Enter a full address that starts with http:// or https://.
If you clear a button’s text, its navigation is cleared too. The Create Prompt form scrolled down to the Message content panel of a Regular prompt, with the side menu on the left and Cancel, Save and a greyed-out Publish at the bottom. The Image upload field is empty. Headline text reads Coffee week is on, and Body text reads 2 for 1 on hot drinks in a text editor with a formatting toolbar. Approve button text reads See the offers, with In-app navigation selected under it and a Choose from list field for the deeplink. Navigate to external URL is below it. Decline button text reads Not now, with In-app navigation and Navigate to external URL both unselected. The Preview below the fields shows the headline and body text at the top, and a See the offers button above a Not now button at the bottom. Message content for a Regular prompt, with the preview below it

​
Choose who sees it

In Segmentation, pick who the prompt is for:
  • All shows it to every customer.
  • Audience shows it to the customers in the audiences you pick. See Segments and Audiences.
When the prompt’s block is connected on the canvas, the flow decides who gets the prompt. Segmentation then shows Customer, already picked, and you can’t change it. To pick All or Audience instead, disconnect the block before you publish the prompt. While it’s connected, the form also adds Validity period of prompt, for how many days each customer sees it. What changes in the form explains both.

​
Set the schedule

Customers can see the prompt between its Start date and End date. If the campaign has dates, both start as them, and both have to stay inside them. The end date has to be later than the start date. A Preferred store prompt doesn’t need an end date. Lifecycle explains what happens on each date.

​
Save or publish

  • Save keeps the prompt as a draft. You only need Name and Type for that. Customers don’t see drafts.
  • Publish asks you to confirm first. If the start date is still ahead, the prompt becomes active on that date. Otherwise it goes live as soon as you confirm.
You’ll know it worked when the prompt shows in the campaign’s List view as Scheduled or Active. Lifecycle explains what you can still change after that.

​
Troubleshooting

Something required is still empty or not valid. Look for red text under the fields. The ones people miss most often are Analytics identifier and the navigation choice under a Regular prompt’s button.
If none of these answers your question, contact Lobyco support. Send them the campaign’s name and the prompt’s ID, from the top of Details.
  • Add an activity — adding the prompt in the List view or on the canvas
  • Recipients — how a flow decides who gets a communication, and when
  • Lifecycle — the statuses a prompt moves through after you publish it
  • Deeplinks — picking a place in your app for a button to open
  • Block reference — the blocks that can come before a prompt on the canvas
  • Reuse with templates — saving a prompt as a template, and what a copy keeps
Last modified on October 21, 2026