Loyalty Points Disputes: Adjustments and Balances Members Can Check for Themselves

A points dispute is simple until multipliers and promotions stack up

A member writes in to say a purchase did not earn the points it should have. Answering takes more than a lookup: find the charge, confirm it was not refunded, apply the base rate, the member's tier multiplier and any promotion running that day, leave out what the promotion excludes, and work out the new balance. Thirty disputes a week means thirty of those, each with a reply the member will check against their own arithmetic.

Disputes arrive as HubSpot tickets, each carrying a transaction reference that matches a Stripe charge. The tier table and promotion pages live in Notion, and the support team's tracker is a sheet in Google Drive. Midweek, marketing extends a promotion, a refund lands on a charge that already earned points, or the tier table is revised for one tier, and the disputes it touches have to be worked again.

Who works in the room

Ada works the disputes and is the room's default agent. It reads Stripe and Notion through a lasting grant the loyalty program manager approved for the room, and updates HubSpot only after the support lead approves. Fin takes the tracker audit, since comparing a colleague's sheet with the approved figures is its specialty. When a dispute is settled, Ada mentions Nova with the member's points and new balance, and Nova drafts a reply that shows the working.

A week of disputes, opened to closed

The points rules, the promotion exclusions and the recording fields sit in Google Drive and in the room guidelines. A dispute the member has withdrawn is outside the review and is never written.

Promotions and tiers that change midweek

Rule changes reach different disputes in different ways. A promotion extension brings purchases in the new window into scope for the bonus, but the promotion's exclusions still apply, so a gift card bought in the extended window still earns base points only. A tier table revision is narrower: it applies to the Gold disputes the revision names, and Ada leaves every other Gold dispute at the multiplier it was worked under.

Refunds run backward through the same arithmetic. A refund on a charge that already earned points reverses those points and lowers the balance, sometimes below what the member expected. Ada records the original credit, the reversal and the new balance on the HubSpot ticket, and Nova's draft explains them in the same order so the member can follow it.

What the checks catch

• A withdrawn dispute written to by mistake
• A charge matched by amount and date instead of by transaction reference, which picks up the wrong charge
• A promotion bonus applied to a purchase the promotion page excludes
• A tier revision applied to every Gold dispute rather than the named ones
• A close-out that skips the tier with no adjustment, leaving three records instead of four

What stays with people

• Approving every points adjustment and balance before HubSpot is written
• Sending each reply to a member, which Nova prepares as a draft in Gmail
• Deciding goodwill credits outside the rules
• Signing the weekly close-out

Integrations in this workflow

Kylon is not a loyalty platform or a help desk, and it does not replace either. It sits across the ticketing, payment and documentation tools the support team already uses, and carries the coordination between them.

• Gmail
• Google Drive
• HubSpot
• Notion
• Slack
• Stripe

• HubSpot holds each dispute ticket with its transaction reference, points and balance, plus the weekly close-out records
• Stripe provides the charge and any refund for each transaction reference
• Notion keeps the tier table and the promotion pages with their dates and exclusions
• Google Drive holds the points rules and the team's dispute tracker
• Gmail carries member correspondence, and each reply is a draft a specialist sends
• Slack is where marketing announces promotion changes and finance flags refunds

Where to start

Pick one week's disputes. Connect HubSpot and give the room a lasting grant on Stripe, then write the rule that matters in the room guidelines: every dispute is matched to its charge by transaction reference, withdrawn disputes are left alone, and the support lead approves every adjustment before it is written.

“Members check the arithmetic, so the reply shows it in the order the rules apply it.”

Set it up with your agent

Open a new Room, add your agent and paste this prompt. It connects the tools, builds the App with you and asks for your rules one step at a time, and nothing goes out until a person approves it.