Docs

Using Calenta

There’s no new dashboard to learn. Calenta shows up in the places you already work — your inbox, Slack, and Claude — and your Salesforce stays the source of truth. Here’s how to set it up, and what a normal week looks like.

Getting set up

You need a Salesforce org running Nonprofit Success Pack or Nonprofit Cloud, a paid Claude plan, and a Calenta account.

1. Create your Calenta account. Start a free trial and tell us a little about your organization.
2. Install the Calenta package in Salesforce. A Salesforce admin installs it once, from this production link or this sandbox link.
3. Add the connector in Claude. An admin of your Claude workspace goes to Settings → Connectors → Add custom connector, names it Calenta, and pastes https://mcp.calenta.ai/mcp.
4. Each person connects. Everyone clicks Connect on Calenta in Claude, chooses production or sandbox, and signs in with their own Salesforce login. They see only what their Salesforce permissions allow. On Nonprofit Cloud, each person needs the Fundraising Access permission set.
5. Try it. Ask Claude to show your priorities, or to give you a donor brief for someone you know.

To stop using Calenta, disconnect on the Salesforce page in your portal, for just you or your whole organization, or revoke Calenta in Salesforce. Removing the connector in Claude alone doesn’t notify us. Disconnecting revokes access and stops nightly preparation. Stored data stays until you ask us to delete it, and then we delete it within 30 days.

Your weekly brief

Every Monday — or another weekday, or every weekday, if your team prefers — each fundraiser gets a short brief by email, or in Slack if you’ve connected a channel. It covers the donors in their portfolio who need attention, with individual donors and foundations in separate lists, and for each one, the reason: a giving pattern that broke, a first-time donor in their second-gift window, a long-time supporter going quiet. Never a name without a why.

Sometimes the brief says nothing needs your attention. That’s deliberate. Calenta doesn’t invent work to look busy — all clear is a real answer, and quiet days are for the work already on your plate.

When you see a 🔍 line under a donor, it means Calenta researched them overnight and found something worth knowing before you reach out. More on that below.

Calenta in Claude

The brief tells you who needs you. For everything deeper, Calenta is a connector inside Claude — you ask questions in plain English and the answers come live from your Salesforce. A few things people ask every day:

• “Show me my priorities today”
• “Give me a donor brief for [name]”
• “How many recurring donors do we have?”
• “Who hasn't been contacted in 90 days?”
• “Give me my board packet”
• “Give me a handover dossier for [staff member]”

There’s no query language to learn. If you can ask a colleague, you can ask Claude — and if it can’t answer something from your data, it says so instead of guessing.

Logging what happened

The notes that matter most are the ones that never make it into the CRM. After a donor call, just tell Calenta what happened, the way you’d tell a colleague:

Calenta turns that into a structured note — with your exact words cited, so you can see precisely what it understood — and proposes it back to you to review. When you confirm, the note is logged in your Salesforce, on the donor’s record, where your whole team can find it.

That’s the point of the whole exercise: the context that usually lives in someone’s head, inbox, or Slack scroll ends up in your CRM instead — and it stays there even when people move on.

Donor research

Overnight, Calenta researches the donors it surfaced for you, using public sources only — news, foundation filings, organizational bios. Findings show up as 🔍 lines in your weekly brief, each labeled with how confident Calenta is in the match.

Honesty matters more here than anywhere. If nothing about a donor can be verified from public sources, Calenta says exactly that — zero findings and a few open questions beats a confident guess about the wrong person.

You can also ask anytime, before a meeting or a call:

• “Research [donor name]”

If the research is worth keeping, Calenta offers to save it as a note on the donor’s record once you’ve reviewed the findings.

Board packet & reports

When a board meeting is coming, ask for the packet:

• “Give me my board packet”

You get the headline numbers against the prior period, goal progress with the monthly run-rate you’d need to hit it, donor movement — who’s new, who’s lapsed, who came back — and your revenue mix.

Every number comes from a live query of your Salesforce at the moment you ask. No stale exports, no spreadsheet assembled the night before, and nothing you couldn’t verify yourself by looking at the same records.

The Org Context page

In your portal, the Org Context page shows you exactly what Calenta knows about your organization — and, just as important, what it doesn’t:

• What it knows — your mission, gift tiers, staff, and fiscal year, as Calenta understands them.
• The field map — which of your Salesforce fields Calenta reads, and what it uses each one for.
• Signal coverage — which signals run on your data, and which can’t yet, with the reason why.
• Worth confirming — the things Calenta isn’t sure about in your setup, listed as open questions rather than silent assumptions.

If Calenta ever surfaces a donor, you should be able to see why — field by field. This page is where that promise is kept.

What Calenta never does

More on the reasoning behind these lines: Where we put the AI and Security.

Not connected yet? Start a free trial — setup takes about five minutes. Stuck on anything? Email joe@calenta.ai or book a quick call.