SOC 2 TYPE II Certified · HIPAA · PCI DSS · WCAG 2.2 AA · Trust.TruCentive.com
Only Pay for Claimed Rewards
Support | 415-386-8600
SOC 2 TYPE II Certified · HIPAA · PCI DSS · WCAG 2.2 AA · Trust.TruCentive.com
Only Pay for Claimed Rewards
Support | 415-386-8600
The study or demo may be over, but the participant experience continues through the thank-you, the payment, reward, and every follow-up.
8-minute read
A participant gives you an hour of their day. They let you pitch, answer questions, explain frustrations and kick off the relationship. You thank them and promise a payment.
What happens next becomes part of their experience with your organization. They decide whether they recognize the sender, open a link, work out how to claim their payment or reward, and look for help if something goes wrong.
A thoughtful research payment or demo reward says: we asked for your time, we appreciate your attention and contribution, and we are following through. That takes recognizable branding and a dependable process behind it.
A TruCentive customer experienced this firsthand after a Company X demo meeting. They received a $75 reward email with the subject “Enjoy your VISA gift card from Company X!” This was a demo-meeting payment; the lesson also applies to research incentives.
Company X’s name, branding and thank-you were present. But the sender was “Company X LinkedIn Giftcard Fulfillment” at noreply@tangocard.com. The brief thank-you email linked into Tango Choice redemption instructions, along with extensive terms and a link to Tango support. There was more about Tango than Company X. The experience made the reward vendor more prominent than Company X.
That creates a handoff the recipient must interpret. Your organization has thanked them, but another company’s identity and terminology increasingly shape the experience.
What to do instead: keep the purpose and sender clear. Use your organization’s email identity where supported, and clearly explain the payment partner’s supporting role. Lead with a specific thank-you and one clear next step.
The actual reward catalog showing BHN Tango branding, a $75 balance, and available reward choices.
By the time the recipient reaches this catalog, Company X has disappeared from view.
BHN and Tango branding sit above the balance and reward choices.
There is no visible Company X logo, no reminder of the study or demo, and no thank-you connecting the reward to the organization that paid for it.
This is the moment the promise becomes something the recipient can use. They see their balance, browse familiar brands, and choose something they want. That moment of anticipation and satisfaction is an opportunity to strengthen the relationship with the organization that thanked them.
But whose name is present when that happens? Here, it is BHN and Tango. Company X funded the reward, yet the payment provider occupies the screen at the moment of redemption. The recipient may remember who sent it, but the page does nothing to reinforce that connection.
What to do instead: keep your name, your thank-you, and the reason for the reward visible through selection and redemption. Identify the payment partner clearly, while making it unmistakable who is recognizing the participant. The reward should help people remember your organization and the experience they had with you.
User Experience Feedback – How do you feel about the last incentive or reward you received?
A later Company X reward email showed another kind of friction: a security code unlocked a separate reward code. Its subject referenced Visa, while a legal link in the body referenced Amazon gift cards.
Security steps can be useful. The issue is whether the message explains them clearly and consistently. The mismatch tells us the instructions were inconsistent; it does not establish which card was delivered or that a payment was missing.
Before a research session or product demo ends, tell participants the amount, expected timing, delivery method and help contact. If a partner will send the email, name that partner in advance. Then make the payment message specific to the study or demo and explain any selection or activation step before the participant encounters it.
Review the sender name, address, subject, thank-you, redemption page and support destination together, on a phone as well as a desktop. A familiar logo cannot compensate for contradictory instructions.
A payment should not depend on someone remembering a spreadsheet or an email. Your team needs to know who is still waiting and who owns the next action.
When participation is recorded, automatically create a payment record wherever possible. Include the study, participant, amount, promised date and responsible person. If review is required, put it in a visible pending-approval queue. Recording an obligation and approving payment are separate actions.
Show who is approved, who is waiting and how long each record has been pending. Assign a backup for absences. Flag records approaching the promised payment date and escalate overdue approvals.
Approval, payment issuance, message delivery and reward claim are different events. Track the distinctions your system supports. “Sent” or “Delivered” does not prove the person saw the email; make sure “claimed” means the recipient actually selected a gift card.
Make it easy for your team to update an outdated email address or SMS number and quickly resend the existing reward notification without issuing a duplicate payment. Automate reminders for unclaimed rewards, and stop them as soon as the recipient claims. Then send a post-claim follow-up from your organization: a personal thank-you, a useful resource, or an invitation to the next relevant conversation. A smooth recovery and thoughtful follow-up can turn a completed payment into continued engagement.
Monitor what percentage of issued rewards are claimed, how quickly people claim, and which gift cards or payment options they choose. Compare studies, regions, and participant groups over the same claim window to see where the experience works and where people may be getting stuck. Understanding your population means learning from actual choices, not assuming everyone values the same rewards. Use those patterns to refine your reward selection, messaging, and reminder timing. Low claim rates warrant investigation into delivery, clarity, and relevance; they do not automatically mean a lack of interest. And interpret popular choices in the context of what participants were offered.
Who owns it, and when is payment due?
What still needs to happen before it is sent?
Has the address been checked and corrected?
Is a reminder appropriate for this payment?
Does every eligible participant appear?
Recommended operating model. Match these checks to the statuses your payment system actually supports.
Participants should have a clear route to help without having to work out which company or department caused the problem. Your research team needs to check the record, explain the next step and coordinate with the payment provider.
If approval is delayed, acknowledge it and give a realistic update. If a notification needs resending, make that straightforward. The participant should not have to keep proving that they are owed a payment.
Measure the work that remains unfinished: payments issued by the promised date, aging approvals, delivery failures, missing payment records and time to resolve questions. Repeated confusion about a sender or code is a design problem worth fixing.
Before your next study, send yourself a test incentive and complete the entire journey. Then trace one participant from eligibility through approval and delivery. Your name carries the promise. Your follow-through gives participants a reason to trust it.
Explore branded research payments and demo rewards with TruCentive, from the message recipients receive to automated reminders and post-claim follow-up.
About the examples: The email examples draw on demo-meeting reward correspondence with recipient feedback dated February 5, 2025. The sponsoring organization is anonymized as Company X; the bracketed name in the quotation is an editorial substitution. The images show the actual reward email and catalog discussed in this article. Claim links, codes and recipient details are excluded. These examples concern messaging and brand continuity, not missing payments or product-wide performance.
Related reading: Research compensation · Marketing incentives and demo rewards · Automated reward reminders · Reward Link public entry page
