MoonClerkv1.0.3

A finance ops analyst pulls all MoonClerk payments for a given form and date range to reconcile subscription revenue against the accounting ledger. They use list_payments and get_form to cross-check amounts, statuses, and customer records before closing the month.

A subscription business tracks customers whose status is past_due or canceled using list_customers with status and next-payment-date filters. The team exports this data nightly to a dashboard and triggers retention emails for at-risk accounts.

A nonprofit uses MoonClerk forms to collect recurring donations and memberships. Staff use list_customers and get_customer to build giving histories and segment donors by form and checkout date for campaign targeting.

An event organizer creates a separate MoonClerk form per event and uses list_forms plus list_payments to report registrations, revenue, and payment status per event. The data feeds a spreadsheet for capacity planning and refund processing.

A support agent receives a billing question and uses get_customer and list_payments to find the customer's payment history, form, and current status. This lets them resolve refunds, failed charges, or form change requests quickly.

Businesses use MoonClerk forms to charge customers on a recurring schedule for products or services. The skill enables automated reporting on active subscriptions, upcoming payments, and failed charges to keep revenue predictable.

Nonprofits accept one-time and recurring donations through MoonClerk payment forms. This skill helps staff pull donor records and payment histories for stewardship, receipts, and campaign analysis.

Organizers sell tickets, seats, or course enrollments via MoonClerk forms. The skill supports reporting on registrations, payment statuses, and customer details for logistics and refunds.