Raisely AI Assistant – Raisely

Raisely AI Assistant is an in-product, AI-powered assistant inside Raisely admin that helps nonprofit teams interpret fundraising performance and decide what to do next. In practice, it works like a “data analyst teammate” you can talk to in plain language: you ask questions about your organisation or campaigns, and it responds with summaries, trends, and recommended next steps.

Raisely AI Assistant is currently in beta, which means it’s ready to use and still actively improving. You may occasionally see an answer that needs review, a result that could be clearer, or a minor issue in the experience. That’s part of the beta process, and feedback from real fundraising workflows will help us make the assistant more accurate, useful, and reliable over time.

The most important expectation to set is that Raisely AI Assistant is designed as a read-only experience. That means it can help you understand what’s happening in your data and suggest actions you might take, but it will not directly change your settings, publish edits, send emails, or modify campaign configuration on your behalf. This is intentional: trust is the product, and the assistant is built to prioritize accuracy, clarity, and permission-safe responses.

What Raisely AI Assistant can do

Raisely AI Assistant is best at taking common “dashboard questions” and turning them into clear answers you can act on immediately. Typical requests include:

“How many new donors signed up this month?”
“How much did we raise on [Campaign] during [Date range]?”
“Show me the latest 5 donations received today.”
“What is the current progress to goal for [Campaign]?”

See our AI Prompt Library for more examples!

What it cannot do is “click around” in your account like a human or perform actions automatically. If you want something changed, it will typically recommend what to change and where to do it (and may provide wording you can use), but the actual change remains in your control.

For questions specifically about the Raisely product, please continue to use the support chat bot, which is separate from the Raisely AI Assistant.

Permissions and visibility: why the assistant sometimes says “I can’t access that”

Raisely AI Assistant is permission-aware by design. It can only answer using the data it has permission to access, and it should not reveal information you don’t have access to in Raisely already. In beta, access may also be limited to admins or users with the appropriate org-level permissions.

If you ask a question that requires data you don’t have access to (for example, a campaign you can’t view, or a data set restricted to higher-permission roles), the assistant may respond that it can’t access that information. When that happens, the goal is not to be vague. A good “permission-safe” response will:

Explain that it does not have access to the requested data, and
Suggest a more limited version of the question that it can answer, or
Indicate what type of role/permission is required to access the missing information.

How to turn it on (enablement and consent)

To use Raisely AI Assistant, it must be enabled for your organisation.

In Raisely admin, open Settings.
Navigate to AI tools.
Find Raisely AI Assistant and toggle it On.
Review the AI Policy presented during enablement.
Select Agree & enable to confirm.

If you do not see an AI tools area in Settings, one of two things is usually true: either you are not an admin (or do not have the required permissions), or your organisation has not been enabled for the beta feature set yet. In either case, the next step is to ask an org admin to confirm access and enablement.

How to open the assistant in Raisely admin

Once enabled, you can open the assistant from within Raisely admin. Typically, you’ll see an AI Assistant entry point in the interface (often a button in the bottom-right corner). Clicking it opens a chat panel where you can type your questions. If you close the panel and reopen it, the experience should return you to where you left off.

How to use it well: how to ask questions that get accurate, helpful answers

Because Raisely AI Assistant is optimized for accuracy and relevance, the best results usually come from giving it enough context to answer precisely. You do not need to write a perfect “prompt,” but you should aim to include:

A timeframe. Instead of “How are we doing?”, use “How are we doing this week?” or “Compare May 1–May 31 to April 1–April 30.” If you don’t specify a timeframe, the assistant may choose a default window, which can lead to answers that don’t match what you expected.

A scope. Many questions change meaning depending on whether you’re asking about your whole organisation, a specific campaign, or a subset of campaigns. If you have a scope selector in the assistant (for example, organisation vs. a specific campaign), set it before you ask. If you’re not sure what scope is active, explicitly include it in your question (e.g., “For our Spring Appeal campaign…”).

A clear metric definition when needed. Some terms are used differently across teams and tools. If you ask about “conversion,” you may mean donation conversion, fundraiser activation, or something else. If you get an answer that feels off, a good follow-up is: “What definition are you using for conversion rate here?” This helps align on the same metric meaning.

One primary question at a time for complex analysis. It’s okay to ask multi-part questions, but if you need a detailed analysis, it can be more reliable to break it into steps. For example: first ask for a summary, then ask “why,” then ask for recommended next actions.

🔗 View the AI Prompt Library

Troubleshooting and support

Finding the AI Assistant

If you cannot find the toggle in Settings → AI tools, start by checking permissions. In most cases, you need admin-level access (or a similar org-level role) to see AI settings. If you are an admin and still don’t see it, your organisation may not be enabled for the beta yet. An org admin can confirm whether AI tools are available for your account and, if necessary, contact Support for enablement.

Not seeing the AI Assistant

If AI is enabled but you don’t see the assistant entry point:

Refresh the page (hard refresh if needed).
Confirm AI is still toggled on in Settings → AI tools.
If your browser has aggressive privacy settings, ad blockers, or script blockers, try an incognito/private window to rule out extensions interfering with the UI.
If your org recently enabled AI, give it a short moment and refresh again—some UI changes can take a short time to fully reflect.

Data returning errors

This is usually a permissions issue or a scope mismatch. First, confirm you have access to the campaign or data in Raisely normally. Then try a narrower question (for example, one specific campaign you can view, or a simpler metric over a shorter timeframe). If the assistant consistently cannot access data you believe you have access to, capture the exact question you asked and share it with Support so the team can reproduce the issue.

If a result looks surprising, it doesn’t necessarily mean it’s incorrect. It often means the timeframe, scope, or metric definition differs from what you intended. The fastest way to reconcile is:

Re-ask with an explicit timeframe (e.g., “From May 1 to May 31…”).
Specify the campaign or organisation scope (e.g., “Only the Spring Appeal campaign…”).
Ask the assistant to describe the definition it used (e.g., “How are you defining conversion rate here?”).
Verify against the corresponding Raisely dashboard/report using the same scope and date range.

If it still appears wrong, please capture: the question, the selected scope (if applicable), the timeframe you intended, and a screenshot of the response. Because the assistant is in beta, these examples are especially helpful for improving accuracy and making future responses more reliable.

Loading errors

Occasional slowness can happen during high usage or temporary system load. If you hit latency or an error:

Try again after a short pause.
Ask a smaller question first (narrow scope to one campaign and a shorter date range).
Avoid stacking multiple comparisons and requests in a single message when diagnosing performance.

If errors persist, include the error message (if shown) and approximate time it occurred when contacting Support.