# Rewards App Support

**URL:** <https://community.glideapps.com/t/rewards-app-support/82793>\
**Category:** Ask for Help\
**Created:** [June 28, 2025, 6:19am UTC](https://community.glideapps.com/t/rewards-app-support/82793 "2025-06-28T06:19:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![NEFA](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nefa/32/87350_2.png) [@NEFA](https://community.glideapps.com/u/NEFA)\
**Post date:** [June 28, 2025, 6:19am UTC](https://community.glideapps.com/t/rewards-app-support/82793/1 "2025-06-28T06:19:42Z")

</div>

I need help designing my Rewards App to enable offer claims and redemptions without QR codes. Please see below for my required flow:

1. When a user clicks “Claim Offer,” generate a unique 4-digit code and send it instantly to their email and SMS.
2. The user gives this code to the business in person.
3. The business enters the code into a text input (only visible to their business) and clicks a “Code Redeemed” button (unique to their business).
4. If the code matches an active claim for their business, mark the code as redeemed and increment a redemption tally for that business.

No QR codes should be used at any step. Please guide me on the simplest, most robust way to achieve this using Glide, including any best-practice workflows or integrations you recommend.

---

<div class="post-metadata">

**Author:** ![Mazen](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mazen/32/84042_2.png) [@Mazen](https://community.glideapps.com/u/Mazen)\
**Post date:** [June 28, 2025, 6:31am UTC](https://community.glideapps.com/t/rewards-app-support/82793/2 "2025-06-28T06:31:37Z")

</div>

Hey NEFA, and Welcome to Glide!

* * *

> [@NEFA](#):
>
> When a user clicks “Claim Offer,” generate a unique 4-digit code and send it instantly to their email and SMS.

**Step 1: Claim Offer**

- Create a “Claims” table with columns like: User Email, Business ID, Offer ID, 4-digit Code, Status (Active/Redeemed), Timestamp.
- When a user taps “Claim Offer,” generate a random 4-digit code (1000–9999), save it to the Claims table.
- Use [Make.com](http://Make.com) (or Zapier) to send that code by email and SMS. Twilio is great for SMS.

* * *

> [@NEFA](#):
>
> The user gives this code to the business in person.

**Step 2: In-Person Code Sharing**

- The user shows the code from the SMS, email, or a “My Claims” screen in the app.

* * *

> [@NEFA](#):
>
> The business enters the code into a text input (only visible to their business) and clicks a “Code Redeemed” button (unique to their business).

**Step 3: Code Redemption by Business**

- Businesses have a screen with a code input and a “Redeem” button, only visible to their role.
- The button checks the Claims table for a matching active code linked to that business.

* * *

> [@NEFA](#):
>
> If the code matches an active claim for their business, mark the code as redeemed and increment a redemption tally for that business.

**Step 4: Validation and Tracking**

- If the code is valid:
  - Mark it as “Redeemed”
  - Add a timestamp
  - Use a rollup column to count redemptions per business

* * *

**Best practices:**

- Use row owners to keep data secure
- Add logic for expired codes if needed
- Give businesses feedback if the code is invalid or already redeemed

---

<div class="post-metadata">

**Author:** ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker)\
**Post date:** [June 28, 2025, 11:00am UTC](https://community.glideapps.com/t/rewards-app-support/82793/3 "2025-06-28T11:00:59Z")

</div>

I also invite you to read this post to make sure you understand how Glide security works:

> [@Security tip: Managing role-based permissions in Glide apps](https://community.glideapps.com/t/security-tip-managing-role-based-permissions-in-glide-apps/77854):
>
> If you’re using Glide apps and need secure control over user permissions, be aware that Glide’s visibility conditions (like showing or hiding buttons for certain roles) are not a security feature. While these conditions are helpful for managing the app’s appearance, they do not protect actions at the backend level. Key Points to Protect Your Data Row Owners for Data Protection: Enabling “Row Owners” is effective for securing individual records (for viewing, editing, and deleting), but it does…

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [June 28, 2025, 3:15pm UTC](https://community.glideapps.com/t/rewards-app-support/82793/4 "2025-06-28T15:15:42Z")

</div>

> [@Mazen](#):
>
> Use [Make.com](http://Make.com) (or Zapier) to send that code by email and SMS. Twilio is great for SMS.

You can also use the native email/Twilio integrations.

> **[Twilio Integration | Glide](https://www.glideapps.com/integrations/twilio)**
>
> Send SMS messages from your Twilio account

---

<div class="post-metadata">

**Author:** ![Mazen](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/mazen/32/84042_2.png) [@Mazen](https://community.glideapps.com/u/Mazen)\
**Post date:** [June 28, 2025, 6:15pm UTC](https://community.glideapps.com/t/rewards-app-support/82793/5 "2025-06-28T18:15:03Z")

</div>

Forgot about that.
