> For the complete documentation index, see [llms.txt](https://docs.perkville.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.perkville.com/integrations/integration-reference/abc-ignite/class-appointments.md).

# Class/Appointments

To award points for classes and appointments our default integration considers a member in attendance if their `attendedStatus` is "Attended" and the event's `status` is "Completed."

If a member is not marked as attended they won't get their points. You can learn more about ABC Ignite attended status [on their website](https://help.abcfinancial.com/ignite/memops/schedule/Tracking_Attendance/Set_the_Attendance_Status.htm).

This logic can be customized. Often businesses that don't take class attendance will award points if the class is marked as "Completed." Reach out to your Perkville representative to discuss how this can be configured to align with your gym's operations.

## Troubleshooting missing class or appointment points

If a member attended a class or appointment but did not receive the expected points:

1. Confirm the activity is a class or appointment earning activity rather than a facility check-in.
2. In ABC Ignite, verify the member's `attendedStatus` is **Attended** and the event's `status` is **Completed**, unless your Perkville integration has been customized to use different criteria.
3. Confirm the ABC member record, event, and location are the ones connected to the customer's Perkville profile.
4. Confirm an active Perkville earning rule applies to that activity and location.
5. Allow for the normal integration sync window, then review the customer's Perkville activity history.

If the ABC record meets the configured criteria but the activity still does not appear in Perkville, contact Perkville Support and include the member name/email, external member ID, location, class or appointment date/time, and the attendance/status values you verified.

## Attendance status reference

The table below describes **default** Perkville processing. Businesses with custom mappings should verify their actual conditions with their Perkville representative.

| ABC Ignite record                                    | Default result / what to check                                                                                                            |
| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| `attendedStatus = Attended` and `status = Completed` | Meets the default class/appointment attendance conditions. An eligible earning rule and matching member/location are still required.      |
| `attendedStatus` is absent or not `Attended`         | Does not meet the default attended condition; verify whether staff marked attendance.                                                     |
| Event status is pending or not `Completed`           | Does not meet the default event status condition. Do not assume points are awarded before completion.                                     |
| No-show                                              | Check the actual values of both status fields; do not award points merely because a booking exists.                                       |
| Customer received unexpected points                  | Check for customized status criteria, other check-in rules, and duplicate or separate eligible activities before requesting a correction. |

### Information to provide when points look wrong

Compare the ABC event and the customer's Perkville transaction history. Include the **ABC member ID, club/location ID, event or appointment identifier (if available), activity date/time and timezone, both status fields, and the relevant Perkville earning rule** in your support request. Do not transmit passwords or access credentials.

{% hint style="info" %}
Whether a later status change automatically triggers reprocessing depends on the configured integration workflow. Confirm that behavior with your Perkville representative before relying on a replay or making manual adjustments.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.perkville.com/integrations/integration-reference/abc-ignite/class-appointments.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
