Leads assistant

The leads assistant answers questions about your leads in plain language and prepares changes for you. Open it on the Leads page with the Ask about your leads button.

Asking questions

Ask the way you would ask a colleague. For example:

• "Who has a trial this week?"
• "Show me the newest leads."
• "Who has been in Follow up for more than 30 days?"
• "Are any leads already members?"
• "How many leads become members after a trial?"
• "Tidy up my board."

The assistant replies in the language of your question and only quotes numbers it read from your data.

Confirming changes

The assistant never changes anything itself. When you ask for a change, it shows a suggestion listing the affected leads — nothing changes until you click Confirm. Dismiss leaves everything as it is.

What you get depends on what you ask for:

A status change made through the assistant never emails the lead. Your club's scheduled trial emails run as usual.

Several matches

When a name matches more than one lead, the assistant asks which one you mean and shows each match with email, status and creation date. Click Select to carry on with the right lead.

Leads who are already members

When someone is created as a member by hand, their lead stays on the board. The assistant finds those cases: it compares each lead's name and email address with your members (small typos are tolerated, and for kids the responsible adult's email counts too) and suggests a conversion for every match. You confirm in the usual dialog, which shows the matched member. "Tidy up my board" checks this as well.

A name alone is never enough for a match — a lead without an email address is left alone.

Permissions

• Anyone who can see leads can ask the assistant questions.
• Only people who can manage leads get suggestions for changes.
• Each person can send up to 10 messages per minute.

Privacy: what the AI model sees

We replace your leads' names and email addresses with placeholders before a request leaves our server. The model works with those placeholders; only our server puts the real names back.

1. Masking. Names become codes like [PERSON_1]; email addresses, phone numbers and IBANs are replaced too.
2. Answering. The model replies with something like "[PERSON_1] has a trial on Thursday".
3. Unmasking. Our server puts the real names back before the answer reaches you. The mapping from code to name is never sent to the model.

What the model gets about your leads

• Searches: per lead, only the placeholder name, status, dates, number of contact attempts and lead ID. Email addresses are not sent at all.
• Context about the lead: its source, the venue and class of its trial, its training group, the disciplines it asked about, which channels you can reach it on (whether an email or phone number exists, never the values) and the notes your team wrote on it. Notes are free text: we shorten them and replace detected email addresses, phone numbers, IBANs and known names.
• Statistics: numbers only.
• Suggestions: the list with real names goes only to your browser. The model only learns how many leads the suggestion contains.
• History: earlier messages go back to the model masked; earlier suggestions only as lead IDs.

Examples

• "Move everyone in New to Contacted" — the question contains no personal data. The model looks up the leads (seeing only placeholders and IDs) and prepares the suggestion. Only you see the names in the suggestion; the model gets back "12 drafted". Clicking Confirm changes the leads directly in Omoplata, without the model.
• "Book a trial for Lukas Meier" — a lead's full name is masked in your question too. The model sees "Book a trial for [PERSON_1]".
• Picking between several matches — clicking Select sends "Lukas Meier (ID 1000072)"; the name is masked here as well.