Skip to content

Prompt Library

Prompts you can copy, paste and edit. The assistant understands plain language, so change the wording to suit how your team talks. You rarely need to name your organisation or website: if your account has one of each, the assistant finds them on its own.

If you have not connected an assistant yet, start with Connect an AI Assistant. A few lines about your setup, saved once as project instructions, make every answer sharper.

The connector ships with five tasks. In Claude, open the attachments menu in the message box, choose the Fluentos connector, and pick one. Other apps list them wherever they show a connector’s prompts.

TaskUse it when
Audit a campaign setupYou are about to publish, or inherited a campaign and want every problem
Check localisationYou want to know which languages are translated, reachable and converting
Review campaign performanceIt is Monday and you want to know what moved and what to do about it
Diagnose an underperforming campaignImpressions, engagement or goals dropped and you want the likely reasons
Suggest how to improve a campaignYou want changes backed by what already works on your own website

The prompts below are for the questions those tasks do not answer on their own.

Review "[campaign name]" before I publish it. What is its schedule, which
display rules all have to be met, how often can it come back after a close,
and where does the submitted data go?
For our spin-the-wheel campaign "[campaign name]", list every segment, its
chance of being selected, its wording, and where winners and losers land.
In what format does the birthday field in "[campaign name]" send the date to
[integration], and which dates does it let a visitor enter?
Read the custom code on the buttons of "[campaign name]" and tell me where the
submitted data is posted.
Is "[campaign name]" translated for every language it can show in, and which
languages read the default wording?
Show me the wording of "[campaign name]" in [language] and [language] side by
side, so I can check the translations read naturally.
Compare the mobile wording of "[campaign name]" against desktop and list every
difference, with the step and the language so I can find it in the builder.

Give a time range. Without one, the numbers are lifetime totals.

Summarise last month for [website] in five bullet points I can send to my head
of ecommerce. Plain language, and say where a number is too small to conclude
anything from.
Compare this month against last month across all campaigns on [website]. I only
want what moved meaningfully.
For "[campaign name]" over the last 30 days, break performance down by device,
language, and new against returning visitors.
Impressions on "[campaign name]" dropped in the last [number] weeks. Is it
traffic or the campaign?
Could two of my live campaigns on [website] qualify for the same visitor on
the same page, and which one wins when they do?
Show me the priority of every live campaign on [website], strongest first, and
tell me which ones can suspend which.
Can another campaign suspend or replace my embedded banner "[campaign name]",
and can a visitor close it?
Which pages, devices, languages or visitor types are not reached by any live
campaign on [website]?
Review every live campaign on [website] and give me the five things I should
change, in order, each with the rule or number behind it.
We are about to change our URL structure from [old] to [new]. Which campaigns
have display rules that reference the old addresses?
Write a short handover note for "[campaign name]": what it does, who it
targets, and anything unusual a colleague should not change by accident.
Which numbers led you to that? Show the figures you used, the time period, and
anything you left out.
Now give me the three things you would actually do about it, in priority order.
Be blunt. If something in this setup is a genuine problem, say so plainly rather
than listing everything that is fine.