Members who renew, because you noticed they lapsed.

Grounded in live records

Every answer is drawn from your own ledger with your permissions applied, and names the documents it used. Nothing is answered from a snapshot or a summary.

A role, not a prompt

Each agent is scoped like a job — accounts payable, procurement, dispatch, period close — with the same limits you would put on the person doing it.

Explicit tool permissions

An agent holds a named list of the actions it may take. Matching an invoice does not imply paying one.

Value and action limits

A hard ceiling per agent, per period, and per document type, which it cannot cross however it is asked.

The queue

What every agent is working on, what is waiting on a person, and what has been held — in one place, with the reason on each item.

Triggers

An arriving document, a breached threshold, a date, or a state change on a record. Agents start on events, not on somebody remembering.

Human approval gates

Anything over a limit routes to a named person, with the reasoning attached, so approving takes seconds rather than an investigation.

Escalation paths

Who it hands to when it reaches a limit, how long it waits first, and what that person sees when it arrives.

Segregation of duties

An agent cannot approve what it raised. The rule that applies to your people applies to your agents.

Full reasoning log

Every step is written to the audit trail on the document it touched, so a decision can be read back months later.

Ask in plain language

The console answers operational questions from live records and offers the next action, rather than handing back a paragraph.

Spend control

Ceilings per agent and per period, so autonomy runs to a budget you set rather than an open account.

Recurring billing

Membership fees billed on an interval and count — monthly, annually, or otherwise — generated rather than diarised.

Plans

Priced at a fixed rate, from a price list, or as a monthly rate that prorates, so a mid-year join is not a manual calculation.

Prepaid or postpaid

Invoice at the start of the period, after it, or a set number of days before, which is how a renewal notice actually works.

Follow calendar months

Align renewal to calendar boundaries rather than anniversary dates, where your year runs that way.

Days until due

The payment deadline applied to every invoice the subscription generates, rather than set by whoever raised it.

Submit automatically

Generated invoices finalised on their own, or held as drafts for review first. A switch rather than a habit.

Bill through arrears

Keep billing where a previous invoice is unpaid, or stop — a policy on the record rather than a monthly judgement.

Cancel at period end

Stop future billing at the end of the current term without cancelling invoices already raised.

Reminders ahead of expiry

A sequence that runs before the date, so a lapse is prevented rather than reported.

Events

Conferences, meetings, and courses as records with dates, capacity, and the chapter or committee running them.

Registration

A booking as an order, so a place taken is stock reserved rather than a name on a list somebody maintains.

Member and non-member pricing

Separate price lists by membership category, so the discount is applied rather than remembered.

Fees to the ledger

Event income posting as it is raised, so an event’s contribution is known during it rather than after.

Capacity and attendance

Registrations against places, and attendance against registrations — the two numbers that decide the next one.

Booking on the portal

Members booking and paying themselves, with the payment landing against the invoice it clears.

Codes and concessions

A discount that only applies to someone holding the code, with usage limits validated at booking.

Scoped access

A portal user sees their own record and nothing else, enforced by the same permission model as everything internal.

Self-service details

Members updating their own address, preferences, and contact details rather than emailing the office to do it.

Renewal and payment

Renewing and paying online, with the payment landing as a payment entry against the invoice it clears.

Event booking

Places booked and paid for through the portal, with capacity respected in real time.

Documents and receipts

Certificates, receipts, and statements generated from the record and downloadable rather than posted out.

Requests

Queries raised as issues against the member, tracked with a clock rather than lost in a shared inbox.

Issues

Raised by email, portal, or phone, and linked to the member and the membership they concern.

Service level agreements

Priorities with a time to respond and a time to resolve, so a member query has a commitment behind it.

Support hours

The clock runs only in the hours you actually cover, and stops on the days the holiday list says you are shut.

SLA pause

The timer holds while you are waiting on the member, with the hold time added back when they reply.

Resolution record

What was done, by whom, and when, attached to the issue rather than living in one person’s mailbox.

Portal tickets

Members raising and following their own queries, on the same records the office is working from.