Asking questions¶
Once your AI client is connected (Connect your AI client), ask it about your CiviCRM data in plain language, as you would ask a colleague who knows the database.
What you can ask¶
Questions that read records work best. For example:
- "How many donations did we receive last month?"
- "What has happened on the case for the Example Food Bank since September?"
- "Who is registered for our next event, and who hasn't paid?"
- "List the activities assigned to me that are still open."
The AI looks up the field names it needs first, then reads the records. To see what it can use, ask it "Which CiviCRM tools do you have?"
What the AI can and cannot do¶
- It sees only what you can see. It signs in as you and uses your CiviCRM permissions. If you cannot open a contact or a case in CiviCRM, the AI cannot read it either.
- It reads, it does not change anything. It cannot add, edit or delete records.
- Your administrator may have narrowed it. Your permission profile can leave out some tools or kinds of record. If the AI says it cannot reach something you need, ask your administrator.
Getting good answers¶
- Long lists are cut short. Each lookup returns at most the site's row cap (usually 50), and the AI is told when there were more. Narrow the question (a date range, a group, a status), or ask for the next page.
- Counts are exact, sums are not. "How many" is answered from the full count, however many records match. A sum or average is worked out by the AI from the rows it received, so it is only right when every row came back; for a large total, use a CiviCRM report instead.
- Check before you act. The AI can misread a field or miss rows. For anything that matters, such as a report to your board or a message to a donor, check the figures in CiviCRM.
Your data and the AI provider¶
- What the AI reads goes to its company: Anthropic for Claude, OpenAI for ChatGPT. Follow your organisation's rules on what may be shared with them (What the AI provider sees).
- Every lookup is logged in CiviCRM: who asked, what was asked for, and how many records came back. Your administrator, or an auditor, can read that log.