Your members,looked after without giving up your evenings
The member file, the dues, the receipts and the calendar in one register, with routines that chase and issue on your behalf, and an agent answering members on your channels. The committee keeps what belongs to it: the decisions.
Members who join, renew, lapse and come back; fees, receipts and events, all year; a secretariat that is often one person and a spreadsheet.
Already at work in this industry
One request, several outcomes
You set the dial request by request: what writes itself in the register, what the agent prepares, what goes up to the committee.
01
The register
A member joins, and the dues that come with them
The admission is entered once, on the form the association configured. The member record is created with the fields the club actually uses, the dues record is created beside it and linked to it, and every page listing members or dues shows both without anyone opening a second screen.
Every Monday the routine reads the schedule and reminds those falling due, never twice. When the payment is marked received, it fills the receipt from the record and sends it from the club’s own address. Four steps the yearly campaign takes, each written in the activity log.
Active members, dues due and overdue, events: blocks composed on live records, never an export. The secretary asks the assistant for a page and gets a proposal; nothing is saved until someone confirms.
The membership question gets answered on a Sunday night, quoting your rules
Price, how to join, what the dues cover: the agent answers straight away on your channels, from your own rules, and names the article its answer came from. A refund or a bequest, it recognises, states what the text provides without promising anything, and sends up to the committee.
Not a product list. Two or three positions, the ones this sector actually needs, and the platform each one runs on.
Membership secretary
Sign-ups, renewals, a file to keep: the register where everything is written once, and where reminders and receipts go out from, when the team is volunteer and already home.
It carries a membership from the first question to the renewal, and keeps the file straight along the way.
Answers what it costs and how to join, at any hour
Says what the dues cover, quoting your own rules
Chases the renewal, records the payment, issues the receipt
Sends a bequest or a major gift straight to a person
Dues collected, tax receipts, a bank export to reconcile: the work that comes after, piling up until the annual meeting, kept in the same register as the members.
It picks up invoices as they arrive, reads them and files them where they belong.
Picks up invoices from the inbox as they land
Reads the document, tables included
Files each one against the right record in your tool
Statutes, internal rules, committee minutes: your volunteers cannot hold all of it. It answers members on your channels, from your documents, and names the one it drew on.
It knows every document the company holds, and answers your teams from them.
The systems the agent reads and writes in this sector. Your own stay where they are.
Website
Help centre
Documentation
Membership file
Dues
Events calendar
Payments
Conversation history
Member register
Fee schedule
Event list
DOCX templates
SMTP
Activity log
Bank export
Questions
No. Those are decisions your statutes reserve to the committee, and the agent’s scope excludes them. It states what the text provides, passes the request on with the join date and the reason, and the committee decides.
You can keep it: the agent reads your file, your dues and your payments, and writes to them where you allow it. You can also replace it with Horizon, the Altores operations platform, where the file, the dues, the receipts and the calendar live in one register and the reminders run on their own: your spreadsheet is imported, column by column. The demonstration shows both.
A workspace with the association pack, which seeds the records, the pages and the routines an association uses; your spreadsheet imported on top; and a first routine switched on, the dues reminder, read and tested before it runs. The rest widens afterwards, on the same records.
No, quite the opposite: the register keeps who changed what and when, and the agent answers from your documents, so what is written once stays available as the team turns over. A new volunteer asks the agent instead of hunting for whoever knew.
Only if you decide it should. Each association has its own workspace, isolated; the assistant runs on the model configured for that workspace, which can be our sovereign AI foundation; and hosting is a choice: with us in Monaco, on your own infrastructure, or in a closed environment.
