Appmint Customers & Benefits

▶ Play video

Watch on YouTube ↗

Video chapters

1. 0:00 Welcome
2. 0:05 Overview: from contacts to perks
3. 0:25 Part 1 · Contacts — Contacts: explained
4. 0:42 Add, import and find contacts
5. 2:07 Part 2 · Customer groups — Groups: explained
6. 2:21 A VIP group and a rule-based group
7. 3:42 Part 3 · Group benefits — Group benefits: explained
8. 3:53 VIP 10% off, and Leo's price on the shop
9. 4:49 Part 4 · Applications and approval — Applications: explained
10. 5:04 Studio Club: Leo applies, we approve
11. 7:02 Part 5 · Shared accounts — Shared accounts: explained
12. 7:17 Leo orders for Northwind Cafe
13. 9:02 Wrap-up

Written guide

Evidence: this course uses earlier local captures, including unsaved forms inspected on 2 October and visually reviewed on 4 October 2026. Saving membership, delivering invitations, enforcing Buyer/Manager access and consuming benefits require separate outcome checks; this pass did not complete those live operations.

What you will learn

This course covers Appmint CRM Customers and Benefits: contacts, customer groups, shared accounts, benefit packages and enrolment. We will show how the records connect, then create and check each part. A group organises customers; a shared account gives people a defined relationship to an account; a benefit package has its own eligibility and approval.

01. Find and maintain contacts

Contacts is the customer directory; groups and benefits organize or entitle those customers. Search the existing identity before creating another.

Steps

Open Customers & Benefits → Contacts. Search by email, open the matching record and inspect Basic Information. For a new controlled customer use Add Contact, fill the actual identity fields and save, then reopen and inspect the saved record.

Check the result

The older recorded editor sent welcome/profile notifications and did not persist Groups through profile update. Recheck current behavior; use the dedicated group operation below.

02. Create and manage group membership

Static groups contain selected members. Dynamic groups derive membership from rules and require a tested matching and nonmatching example.

Steps

1. Open CRM → Customers & Benefits → Contacts.
2. Select New Group in the Groups & Contacts sidebar. The separate Customer Groups tab lists groups; the inspected creation entry is in Contacts.
3. Enter Group Name, a useful Description and Static Group, then select Save.
4. Return to Contacts and narrow the search to the intended people. Select their card checkboxes and check the selected count.
5. Open Bulk Actions → Bulk Update → Add to Group, choose the saved group and apply once.
6. Reload, select the group and confirm the intended customers by email. Clear the selection before another bulk operation. Use Remove from Group only for the specific membership you intend to remove.

Actual unsaved 2 October form. The older drawer title says Edit Group although it was opened through New Group; current source distinguishes New Group for a new record. Saving the group name alone does not add members.

Check the result

Dynamic Group is not complete simply because you select its type. The Contacts group editor currently offers Static/Dynamic but does not expose rule fields beneath that selector. Existing saved rules are evaluated elsewhere, but a complete novice-followable rule-creation path remains unverified. Use Static Group for explicit membership until the editable rule path and matching/nonmatching results are demonstrated.

03. Create a shared purchasing account

Shared Accounts associates people with an account customer; it does not share a password. Buyer and Manager have different order visibility.

Steps

1. Select Shared Accounts → Start a shared account.
2. Under Which customer is the account?, select the existing account customer. This is the account being bought on.
3. Under Add someone to this account, select the person who will buy, or enter the intended new member email. This second identity is distinct from the account itself.
4. Choose Buyer or Manager after reading its scope. Buyer sees their own orders; Manager has the wider account scope described by the form.
5. Review the optional email note and select Add to account only when you intend to create the relationship and notify the recipient.
6. Reopen the account and check membership. Then test with the member's own login; the operator's view cannot prove their permissions.

Actual unsaved form. The account customer is selected but no member has been added. This is not an invitation-delivery or access result.

Check the result

Existing-customer association and new-email invitation are different paths. Both may notify; verify delivery and access for the intended recipient.

04. Prepare a benefit package

Benefits define the actual entitlement and its eligibility. Saving an inactive package does not prove a discount or shipping perk is applied.

Steps

1. Open Group Benefits → Create Benefits.
2. Enter the package Name, display Title and description. Inspect Status—the captured new form starts Active, so deliberately choose an inactive preparation state when the package is not ready.
3. Select the Application Form only when enrollment needs that saved form. Decide whether Requires Approval applies and provide the actual information/legal agreement.
4. Scroll through Customer Groups, Perks and Validity Period. Configure the eligible audience and real entitlement; a badge or title alone grants no benefit.
5. Select Create, reopen the package through its edit action and compare status, eligibility, perk and dates.
6. Before advertising it, verify the benefit in its actual consumer—for example checkout for a discount—not merely in this editor.

Actual unsaved form. These upper controls do not show all perk and validity fields; continue down the editor before saving.

Check the result

Test each selected perk at its actual consumer before promising it to customers.

05. Enroll, review and activate

Enrollment is the customer’s relationship with a package. Pending, approved and active are different states; review the application and actual entitlement separately.

Steps

1. Open Enrollments → Enroll Customer.
2. Search by the customer's name or email and select the correct result. Choose the intended Benefit Package; typing its name in Notes does not link it.
3. Review the optional notes, then select Submit Enrollment. If the package is missing, finish package setup and return rather than selecting an unrelated offer.
4. Find the resulting application and use its review/approval actions according to your process. Reopen the same customer's record after each decision.
5. Where activation is required, use the offered Activate action and inspect validity. Finally check the customer's actual benefit outcome.

Actual unsaved form. The disabled button is expected with missing selections and is not an application failure.

Check the result

The older form offered inactive packages; eligibility enforcement and status transitions remain required runtime checks. Do not demonstrate a successful benefit using a saved enrollment alone.

06. Connect workflows and notifications

Workflows manages benefit application stages. Notifications supplies message templates; it is separate from the sender and from evidence that the customer received the message.

Steps

Open Workflows → New Workflow where a definition is needed. Inspect the actual benefit-application stages. Submit a controlled enrollment and locate its task. In Notifications create the appropriate template, configure its actual event context and controlled recipient, then verify the resulting delivery.

Check the result

Creating the workflow may immediately create the default definition. Exact notification variant/context must be verified rather than guessed.

07. Read back entitlement and access

A complete setup ends with persisted membership and the customer’s actual benefit or shared-account behavior. A summary count is supporting information.

Steps

Reload Contacts, the group and the enrollment. Verify the same customer identity in each. Test Buyer and Manager visibility independently and inspect the customer’s relevant purchase or service entitlement. Correct the specific relationship if the result differs.

Check the result

Do not claim all group perks or shared-account permissions proven from one customer test. Public invitations, dynamic rules and each perk need their own outcome checks.

Your next check

Return to the chapter for the action you need. When you change the configuration, check the matching record, customer view or destination again. A saved setting and a successful external outcome are different observations.

Detailed examples and earlier saved results

The examples below preserve earlier recorded settings and results. Use your own group names and business terms; inactive packages and empty boards are preparation evidence, not completed customer entitlement.

Locate a customer before creating another

Open Contacts and use Search contacts... to look for the person's email or name. In our organization Alex Cedar already exists as [email protected]. Select the contact to open Edit Contact.

The first section, Basic Information, includes Email, Username, First Name, Last Name, Middle Name, Title, Prefix, Suffix, Phone, Account Type, Birthday and Sex. Email is marked required. Account Type offers Subscriber, Contact and Customer. Fill only information you actually have and need; an unknown phone number should remain empty.

To add a new person, choose Add Contact. This build still labels the opened drawer Edit Contact even when the record is new. Enter a real customer email only when you intend to register that customer: the current save operation dispatches a welcome notification. Our course capture inspects this form without submitting a fictional email.

The remaining sections organize company information, lead and sales information, groups and benefits, additional emails, phone numbers, addresses, social media, preferences, profile images, security/login, affiliations, subscriptions, projects, security questions, community profile and activity history. Expand the section relevant to the information you are maintaining instead of trying to complete every section at once. Security and login changes are separate operational decisions; do not reset access just to add a consultation note.

Current limitation: profile Save also dispatches a profile-update notification. In addition, the Groups field shown inside this editor is stripped by the current update API, including for staff. Do not use that field as proof that group membership was saved. The dedicated group workflow is being verified below; the application issue is logged separately.

Create a consultation customer group

Choose Customer Groups. The toolbar includes a plus icon to create a record; its current form title is updateData. Select the plus, then enter:

The other type is Dynamic. Its rule editor exists, but the rule-evaluation and membership demonstration is still being verified; this first group uses Static deliberately.

Select Save. The observed success message is Data inserted. In this build the list did not immediately refresh, so click the refresh icon beside the search field. Confirm that the group appears. You can also return to Contacts and see its name in Groups & Contacts.

Now add Alex through the dedicated group operation:

1. Return to Contacts. Search [email protected] and confirm the filtered result is Alex Cedar.
2. Select Select all above the filtered list. Check 1 selected before continuing; a broader search can select more people than intended.
3. Select Bulk Actions, then Bulk Update. Deduplicate is the initially selected bulk tab; it does not add group membership.
4. Open Action and choose Add to Group. The current selected control displays the internal value add_to_group; the action button reads Add to Group.
5. Open Select Group and choose crm-general-course-consultation-clients.
6. Select Add to Group once. Data updated appears and the left group count changes from0to1.
7. Reload, then select the group in Groups & Contacts. Confirm 1 contacts in crm-general-course-consultation-clients and the Alex Cedar row.

This updates the group's membership list without editing Alex's customer profile. To undo an incorrect assignment, use the same filtered selection and Bulk Update with Remove from Group, then verify the group again. That removal action is present in the UI and source; the recorded example keeps Alex in the intended group.

Understand shared purchasing accounts

Select Shared Accounts, then Start a shared account. The first question is Which customer is the account? The account is an ordinary customer record representing, for example, an agency, department or wholesale buyer. Its customer groups determine the benefits members receive when buying on it. This does not ask people to share a password.

Use Find the customer this account belongs to to choose an existing customer. The member form appears after selection. It offers Buyer and Manager. The Buyer explanation says Sees only their own orders. The final action is Add to account.

The implementation distinguishes an existing customer from a new email. An existing customer is linked directly; a new email receives an invitation and becomes associated after signup. Both paths send a notification. Our recording stops before that final action, so it proves the setup controls, not a delivered invitation or a completed membership. A shared account is not listed as established merely because its customer was selected—the first association creates the shared-account relationship.

Prepare a benefit package before enrolling anyone

Open Group Benefits → Create Benefits. A package includes Name, Title, Status, Description, an optional Application Form, Requires Approval, Information, Legal Agreement, Customer Groups, Perks, visual badge settings, Notifications and Validity Period.

For our local draft, Name is crm-general-course-consultation-prep, Title is Consultation client discount, and Status is Inactive. Expand Perks, enter 5 in Discount, and keep Discount Type Percentage. We use Consultation client as Badge Text. No customers or groups are assigned to this package.

Perks also exposes Early Access, Priority Support, Free Shipping, Free Shipping Minimum, Shipping Discount and Exclusive Products. These are different business commitments. Enable only the terms you intend to offer, and test the relevant storefront behavior before advertising them. Creating a package is not evidence that a checkout discount has been applied.

Select Create, then check the saved card. To verify the persisted configuration, open the card's three-dot menu → Edit, then expand Perks. The recorded readback shows Discount 5 and Discount Type Percentage. Use Cancel to close this inspection without changing the package.

The current course package is inactive and has no enrollment. In Enrollments, the status filters include Pending, Under Review, Approved, Rejected, Active, Expired and Cancelled. Enroll Customer opens Customer, Benefit Package and Notes, with Submit Enrollment as the final action. We inspected but did not submit that form. The current selector includes the inactive test package; eligibility enforcement needs verification before this is taught as a successful enrollment.

Prepare the application review board

Open Workflows. With no workflow configured, the dashboard shows zero workflows/stages and No Workflows Selected. Select New Workflow once. This creates the default benefit-application definition immediately; it does not open a naming drawer.

The result shows 1 workflow configured, 6 Stages, and these columns: Application Submitted, Under Review, Documents Required, Final Review, Approved, Rejected. Reload and return to Workflows to confirm it remains. Our board has zero tasks because creating the review process is separate from enrolling a customer.

Use the Kanban view to see stage columns and Table for a tabular view. The stage names distinguish a request for more information from a final decision. Do not use Escalate overdue simply to explore: it is an operational action on overdue work, not a view toggle. Connecting an actual submitted enrollment to this board still needs verification; the empty board does not prove that connection.

Locate benefit message templates

Open Notifications → Create Template. The Create Notification Template form exposes Name, From, Subject, To, Datatype, Variant, Subtype, Delivery Type, Is Default, HTML, Text, Attachments and Thumbnail. Show Template Variables is available beside the editor. Delivery Type initially shows email.

A template defines message content and matching conditions; it is not the SMTP delivery server. Our example organization has no benefit templates yet. We inspected this form and chose Cancel, leaving it unchanged. Do not type a guessed variant or recipient expression: use the event's documented context, preview the resulting message and verify delivery before enabling a customer-facing template. Template creation and actual notification delivery remain separate release checks.

Verification notes