Skip to content
AgentZforiMIS®

Membership lifecycle recipes

Prompts for member service teams handling joining, renewal, lapse, access, groups, and member-360 investigation. The language is intentionally staff-facing: identify the person, gather evidence, preview the action, then confirm.

Copy a request into your AI app and replace the words in square brackets with your own. See Using a recipe.

Understand a member before deciding what to do next

Section titled “Understand a member before deciding what to do next”

Recipe R-01-01 · Kind of request: Look up · For: Membership team, Member services

When to use it: Use this when a member calls, emails, or appears in a report and the team needs the complete context before taking action. Association staff often lose time moving between profile, billing, events, groups, and communications screens; this prompt asks for a joined-up service view first.

What AgentZ does: AgentZ searches for the right contact, reads the main iMIS evidence around that person, and separates facts from recommendations. It should show what it found, flag gaps or conflicts, and avoid changing the record unless you ask for a follow-up action.

Before you begin: Have the member name, ID, or email address ready, plus the question you are trying to answer.

Keep in mind: This is an evidence-gathering prompt. If the next step is a renewal, refund, merge, email, or access change, ask AgentZ to prepare that as a separate reviewed action.

Onboard a new individual member from enquiry to active subscription

Section titled “Onboard a new individual member from enquiry to active subscription”

Recipe R-01-02 · Kind of request: Review then change · For: Membership team, Member services

When to use it: Use this when an enquiry has become a member application or a staff member is entering a join manually. The membership team wants the person set up once, in the right category, without creating duplicates or missing welcome access.

What AgentZ does: AgentZ searches for existing contact records, checks possible duplicate matches, reviews the membership option and related access, and prepares the steps for staff approval. After approval it can help carry out supported membership setup and give a checklist for anything that still needs iMIS Staff.

Before you begin: Have the person details, membership category, start date, billing choice, and any chapter or committee context ready.

Keep in mind: New-member setup affects billing, access, and reporting. Review the proposed record, price, and start date before confirming changes.

Renew a member manually and confirm the new paid-through date

Section titled “Renew a member manually and confirm the new paid-through date”

Recipe R-01-03 · Kind of request: Review then change · For: Membership team, Finance team

When to use it: Use this for phone renewals, exception renewals, or cases where a payment or invoice does not clearly match the member status. Staff need confidence that renewing will not duplicate a charge or hide an outstanding balance.

What AgentZ does: AgentZ reads the member, subscription, invoice, and payment context, then explains the current state and the renewal effect. It should pause before creating or changing renewal records and read the result back after any approved update.

Before you begin: Have the member identifier, renewal term, payment status, and any exception note ready.

Keep in mind: If payment is still outstanding, separate the renewal decision from the payment collection step so finance can approve the handling.

Change a member grade and preview the billing impact

Section titled “Change a member grade and preview the billing impact”

Recipe R-01-04 · Kind of request: Review then change · For: Membership team, Finance team

When to use it: Use this when a member moves between student, associate, full, retired, corporate, or other grades. Grade changes often affect price, benefits, renewal timing, and reporting, so staff need the impact before making the change.

What AgentZ does: AgentZ reads the member record, current subscription context, balances, and available pricing evidence. It prepares a clear comparison and identifies whether the change can be completed directly or needs finance or membership-manager approval.

Before you begin: Have the current grade, target grade, effective date, and reason for the change ready.

Keep in mind: Local iMIS rules can make grade pricing and pro-rating different by organisation. Treat the preview as the decision aid and confirm the final charge in iMIS before committing.

Reinstate a lapsed member and restore access

Section titled “Reinstate a lapsed member and restore access”

Recipe R-01-05 · Kind of request: Review then change · For: Membership team, Member services

When to use it: Use this when a former member wants to rejoin or says they have lost access after a lapse. The team needs to distinguish a simple renewal from a reinstatement with debts, lost group access, or login issues.

What AgentZ does: AgentZ gathers membership, billing, group, login, and activity evidence, then explains what must be restored and what should be left alone. It can support confirmed reinstatement steps where available and provide a staff checklist for access verification.

Before you begin: Have the member identifier, intended reinstatement date, and any payment or access complaint ready.

Keep in mind: Do not restore benefits simply because the person asks. Check balances, eligibility, and policy exceptions first.

Cancel or non-renew a member with a clear leaving checklist

Section titled “Cancel or non-renew a member with a clear leaving checklist”

Recipe R-01-06 · Kind of request: Review then change · For: Membership team, Finance team

When to use it: Use this when a member resigns, is not renewing, or should be cancelled under policy. Leaving touches more than the subscription, and staff need to avoid accidental access, billing, or governance loose ends.

What AgentZ does: AgentZ reviews the member across the connected iMIS areas and turns the findings into an ordered checklist. It should separate records that can be changed after confirmation from items that require policy, finance, or native iMIS review.

Before you begin: Have the member identifier, reason, effective date, and refund or balance policy ready.

Keep in mind: Cancellations can affect audit history and future reporting. Keep a human-approved reason and do not delete the person record.

Add a member to a committee or working group

Section titled “Add a member to a committee or working group”

Recipe R-01-07 · Kind of request: Review then change · For: Membership team, Governance team

When to use it: Use this when governance, volunteering, chapters, or special-interest groups need membership maintained accurately. Staff want the person listed correctly without duplicate roles or expired appointments hanging around.

What AgentZ does: AgentZ confirms the contact, checks current group participation, reviews relevant membership status, and prepares the group membership change. It should show the before-and-after state and read it back after approval.

Before you begin: Have the group name, role, start date, end date, and approval source ready.

Keep in mind: Group membership may drive access, voting, mailings, or public listings. Confirm the role and dates carefully.

Recipe R-01-08 · Kind of request: Guided handoff · For: Member services, Support team

When to use it: Use this when a member cannot log in, cannot see member content, or says their renewal did not restore access. The support job is to identify whether the issue is status, email, permissions, or credentials before resetting anything.

What AgentZ does: AgentZ reads the member and access-related evidence it can see, flags mismatches, and suggests the next staff action. Where account creation or credential reset needs native iMIS or identity-provider handling, it produces a clear handoff instead of pretending it completed it.

Before you begin: Have the member email, reported error, and the page or benefit they expected to access ready.

Keep in mind: Do not share passwords or ask the member for sensitive credentials. AgentZ should work from iMIS evidence and staff-approved reset paths.

Investigate an unusual member account before touching anything

Section titled “Investigate an unusual member account before touching anything”

Recipe R-01-09 · Kind of request: Look up · For: Membership team, Support team

When to use it: Use this for messy member-service cases: odd statuses, contradictory invoices, missing access, unexpected benefits, or a colleague saying something just looks wrong. Staff need a diagnosis before they choose an action.

What AgentZ does: AgentZ builds a compact cross-area member view and points out conflicts or missing evidence. It should recommend the next safe step and make clear where it is uncertain.

Before you begin: Have the member identifier and a short description of what seems wrong.

Keep in mind: This is deliberately read-only. If the diagnosis points to a payment, renewal, merge, or access change, run that as a separate confirmed recipe.

Find non-members who already engage and may be ready to join

Section titled “Find non-members who already engage and may be ready to join”

Recipe R-01-10 · Kind of request: Multi-step plan · For: Membership team, Growth team

When to use it: Use this when the association wants membership growth from people already showing commitment. These prospects are more useful than a cold list because they have existing evidence of interest.

What AgentZ does: AgentZ searches across membership, finance, events, giving, and engagement evidence to build a prospect list. It should explain the inclusion rules, flag duplicates or missing contact details, and prepare segments for review before export or outreach.

Before you begin: Set the lookback period, target audience, exclusions, and whether staff want a list, a report, or an outreach plan.

Keep in mind: Check consent, communication preferences, and data-protection rules before contacting prospects.