# Fidelect: full public website context > This file consolidates the public, English-language content of fidelect.com for language models. It is a discovery aid, not a replacement for the canonical web pages, current pricing endpoint, privacy policy or terms of service. ## Product scope Fidelect serves two connected audiences. The consumer mobile app keeps loyalty cards, points and rewards together. The business platform helps customer-facing teams operate loyalty programmes, segment customers, run journeys and campaigns, manage configured communication channels, and connect relevant commerce and operational work to the customer relationship. The public industry pages describe implemented business use cases for retail, beauty and wellness, restaurants, fitness, non-clinical healthcare front offices, automotive workshops and businesses that need a flexible setup. # Website pages ## Earn rewards everywhere you already shop. Source: https://fidelect.com Every loyalty card, point balance and perk in one app. The morning coffee, the haircut and the weekly shop all start paying you back. ## Three steps, then it runs itself. Source: https://fidelect.com/customer-experience Add your cards once. From then on Fidelect tracks the points, watches the expiry dates and tells you when a reward is worth taking. ## Your rewards, always in your pocket. Source: https://fidelect.com/mobile-app Every card, balance and reward in one app. Check what you have before you walk in, and redeem it before you walk out. ## Loyalty that actually shows up for you. Source: https://fidelect.com/about/customers You go back to the same places. Fidelect makes sure that counts for something. ## The loyalty system your counter has been missing. Source: https://fidelect.com/about/businesses Most businesses do not struggle for lack of customers. They struggle because customers do not come back. ## Blog Source: https://fidelect.com/blog Notes on loyalty, customer relationships and the work behind the product. ## One system behind every returning customer. Source: https://fidelect.com/business Loyalty, marketing, operations and analytics on one foundation, so the work of keeping a customer stops being spread across five tools. ## Talk to us. Source: https://fidelect.com/contact Support questions, partnership ideas or a demo request. One form, and a person reads it. ## Simple, transparent pricing Source: https://fidelect.com/pricing Start confidently, scale as you grow. No hidden fees, no surprises. ## Retail: Inventory and repeat purchases Source: https://fidelect.com/industries/retail Connect your catalogue, stock, orders, returns and loyalty so every selling moment strengthens the customer relationship. ## Beauty & wellness: Appointments and rebooking Source: https://fidelect.com/industries/beauty-wellness Connect the daybook, front desk, service, checkout and client history so every appointment feels considered and the next visit is easier to secure. ## Restaurants: Reservations and regulars Source: https://fidelect.com/industries/restaurants Bring menus, ordering, kitchen progress, pickup, delivery and dine-in service into one operating flow built around the guest. ## Fitness: Memberships and retention Source: https://fidelect.com/industries/fitness Bring schedules, access, attendance, memberships, balances and motivation into one member journey built for participation and retention. ## Healthcare: Front-office care and reminders Source: https://fidelect.com/industries/healthcare Coordinate appointments, service status, family and caregiver relationships, referrals and follow-up without turning front-office work into a clinical record. ## Automotive: Workshop and service follow-up Source: https://fidelect.com/industries/automotive Connect intake, estimates, approval, parts, technician time, pickup and future maintenance so every job stays clear from arrival to release. ## Other businesses: A flexible setup for any business Source: https://fidelect.com/industries/other-businesses Start with loyalty, referrals, campaigns and messaging. Add only the lightweight structure that matches how your team actually works. # Blog articles # The customer portal became the center of the loyalty program Source: https://fidelect.com/blog/customer-portal-at-the-center Published: 2026-06-07 Author: chaqchase What we learned while bringing points, rewards, membership, shopping, and support into one customer-facing place. We started building the customer portal as a place to check points. That sounded small enough. A balance, a list of recent activity, and a rewards catalog. The usual pieces. It didn't stay small for long. Once customers could see their points, they needed to understand where those points came from. When they expired. Which rewards were available, which ones were locked by tier, what happened after a reward was claimed. Then membership came into the picture. Orders followed. Gift cards, coupons, referrals, bookings, wishlists, messages, and support requests came after that. The portal slowly became the place where the customer relationship actually made sense. ## A balance alone doesn't explain much A points total is useful for a few seconds. It answers one question. Customers usually have several more: - How did I earn these points? - Can I use them now? - Is anything about to expire? - Why is this reward locked? - How close am I to the next tier? - Did my last purchase count? Those questions need context. A transaction history helps. Clear expiry dates help. Tier progress and reward rules help. The work here is mostly about removing uncertainty. If someone has to ask staff what their balance means, the portal missed part of its job. ## Membership needs a home Membership programs tend to spread themselves across several places. The card lives in a wallet app. Renewal details arrive by email. Benefits are listed on a web page. A staff member has to confirm whether a discount applies. That gets hard to follow, especially when the business offers more than one membership plan. We put the membership card, plan status, dates, benefits, and verification details together. Customers can open one page and see what they have. Staff can scan a QR code and confirm it. It's a pretty plain flow. That's part of why it works. ## Commerce changes the shape of the portal Adding a shop creates a different kind of customer visit. Someone may arrive to check points, notice a product, save it to a wishlist, apply a coupon, then use a gift card at checkout. The loyalty program is now part of a purchase flow. The details matter. A reward needs to behave predictably beside a coupon. Gift card balances have to update. Orders need a status customers can understand. Saved items should still be there later. Each piece touches the same customer record. That shared context keeps the experience from feeling stitched together. ## Bookings belong in the same account For service businesses, a purchase may begin with an appointment. Customers need to see available times, submit the right details, and know whether a booking is confirmed or still waiting for approval. They may earn points when the service is completed. They may also receive a reminder or a follow-up offer. Keeping that activity in the portal gives the customer one history. The business gets a clearer view too. ## Messages need context A message is more useful when the customer can act on it. An expiry reminder should lead to the relevant reward. An order update should open the order. A booking message should include the current status. A support conversation should have enough context that the customer doesn't have to repeat the whole story. This pushed us to treat notifications and messages as part of the product flow. They aren't a separate feed sitting beside it. ## The hard part is deciding what belongs A portal can get crowded fast. Every team has another item they'd like to place on the home screen. Every feature seems important when you look at it on its own. We keep coming back to one question: what does the customer need to understand or do right now? Balances, active offers, membership status, recent orders, and upcoming bookings usually deserve more attention. Older history and settings can sit deeper. The exact order will change as we learn. The principle stays the same. The portal should help customers move without making them study the system first. ## Where we landed The customer portal now covers a wider part of the relationship than we expected at the start. It gives customers one account for rewards, membership, shopping, bookings, and communication. It also gives the business one customer-facing surface to maintain. There's still plenty to refine. We're working through the small moments: empty states, unclear statuses, expired offers, failed payments, and all the places where a customer might wonder what happened. That work rarely looks impressive in a feature list. It has a large effect on whether the whole experience feels dependable. # What changes when everything shares one customer record Source: https://fidelect.com/blog/one-customer-record Published: 2026-06-07 Author: chaqchase A practical look at connecting loyalty, orders, campaigns, messages, bookings, and support around the same customer. Customer software tends to split over time. Orders go into one system. Loyalty points live somewhere else. Campaigns use a separate audience list. Support has its own inbox. Bookings may come from another tool entirely. Each system works well enough on its own. The trouble starts when a real customer moves between them. We've spent a lot of time on this part of Fidelect: making loyalty, commerce, communication, and daily operations use the same customer record. It sounds like a data decision. It changes the product in very practical ways. ## Staff stop piecing together the story Consider a customer who placed an order, used a reward, contacted support, and booked another visit. When those actions live in separate tools, a staff member has to search for the customer several times. Email addresses may differ. Phone numbers may be formatted differently. One account might be duplicated. Even when the records match, the timeline is scattered. With a shared record, the order, redemption, conversation, and booking appear around the same person. The team can see what happened without asking the customer to explain it again. This is basic context. It saves a surprising amount of confusion. ## Loyalty rules can use real activity A loyalty program needs reliable events. Points may come from purchases, referrals, visits, bookings, achievements, or a manual adjustment from staff. Each event has its own timing and failure cases. An order can be cancelled. A payment can fail. A referral can be invalid. A booking can be missed. When loyalty shares the operational record, the system can respond to those changes. Points get issued when the right event completes. A reversal follows a refund. A tier updates from the same history used for reporting. The customer sees a balance that has a traceable reason behind it. ## Campaigns become easier to target Audience targeting gets vague when campaign data is copied from place to place. A segment called "recent customers" might be based on last week's export. A win-back campaign might include someone who purchased yesterday through another channel. A membership message might reach people whose plan already expired. Shared data reduces that drift. Segments can use current order activity, tier, points, membership state, booking history, message engagement, or other details already attached to the customer. It also becomes easier to answer a useful question: why did this person receive this message? ## Support can see what the customer sees Support conversations often begin with missing context. "My points are wrong." "My coupon didn't work." "Where is my order?" Simple messages with several possible causes. When support can see the same order, reward, coupon, and points history, the first reply can be useful. The agent has less searching to do. The customer spends less time sending screenshots. We still keep permissions in mind. A shared customer record shouldn't mean every team member sees everything. Roles and audit logs matter more as activity gets connected. ## Reporting becomes less slippery Reports often disagree because they count different versions of the same event. The commerce tool counts an order. The loyalty tool counts points issued. The campaign tool claims a conversion. Finance later records a refund. If those systems never reconcile, the numbers slowly drift apart. A shared record gives reports a common path back to the underlying activity. Campaign results can reference orders. Reward costs can reference redemptions. Customer value can include the history the business has decided to track. The numbers still need careful definitions. One data model doesn't remove every reporting argument. It gives the team a clearer place to resolve them. ## Identity is the awkward part Customers don't always arrive with a neat account. They may buy at the counter with a phone number, shop online with an email address, then join a membership later. Families may share a number. Staff can mistype details. Imported records may already contain duplicates. Merging those identities needs restraint. An incorrect merge is worse than a duplicate. It can expose private information or assign activity to the wrong person. We treat matching as a process with confidence levels, verification, and human review where needed. Some records should stay separate until there's enough evidence. ## One record creates responsibility Connecting customer activity makes the product easier to use. It also raises the cost of careless choices. Permissions need to be specific. Deletion and export requests have to reach connected data. Audit logs need enough detail to explain changes. Retention rules should apply consistently. This work sits underneath the visible features. Most customers will never think about the record itself. They'll notice that their points update, their order can be found, and support already knows what they're asking about. That's the outcome we're working toward. # The work behind a reward that feels simple Source: https://fidelect.com/blog/the-work-behind-a-simple-reward Published: 2026-06-07 Author: chaqchase A reward takes one tap to claim. Making that tap reliable touches rules, stock, checkout, staff tools, messages, and reporting. From the customer side, a reward is a short flow. Open the app. Pick something. Tap redeem. Use it. We want it to feel that simple. Behind the tap, the system has several decisions to make. The customer needs enough points. The reward has to be active. Stock may be limited. Their tier might matter. A redemption code may need to be created. Staff may need a way to verify it. The transaction has to show up in reports. Most of the work sits below the surface. ## Eligibility has to be clear A reward can have several rules: - A points cost - A start and end date - A minimum tier - A limit per customer - A total stock limit - A location restriction - A product or category condition These rules need to agree across the customer portal, checkout, staff tools, and API. If the portal says a reward is available and checkout rejects it, the customer sees a broken promise. If staff can redeem something the customer can't see, support gets harder. We keep the eligibility check in one place and return a reason when it fails. That reason can then be written for the person seeing it. "Gold members only" is useful. "Invalid request" is not. ## Points need a proper ledger A balance looks like one number. We treat it as the result of many entries. Points are earned, spent, expired, reversed, adjusted, and sometimes restored. Each change needs an amount, a reason, a timestamp, and a link to the event that caused it. That history matters when something goes wrong. If an order is refunded, the system needs to know which points came from that order. If a redemption is cancelled, it needs to know whether points should return. If staff make an adjustment, the business needs an audit trail. Updating a balance directly would be easier at first. It would leave very little to explain later. ## Stock changes the redemption flow Digital rewards can often be issued immediately. Physical rewards have inventory. The system needs to decide when stock is reserved. It also needs to release that reservation if the redemption expires or is cancelled. Two customers can try to claim the last item at nearly the same time. That's a small concurrency problem with a very visible result. We handle the reservation as part of the redemption transaction. The customer should either receive a confirmed reward or keep their points. A half-finished state is hard for everyone. ## Codes need a lifecycle Some rewards are used through a code. The code may be shown to staff, copied into checkout, or scanned from a membership card. It should be unique, hard to guess, and limited to the intended use. A code also needs a status. Issued, used, expired, cancelled. Staff need to see enough information to verify it without gaining access to unrelated customer data. Once used, it should stay used. Repeated taps, slow networks, and retries can't create a second redemption. This is where idempotency becomes practical. The same request can arrive twice and still produce one result. ## Checkout has to settle the order Rewards can affect checkout in different ways. A fixed discount reduces the total. A percentage reward needs limits. A free item needs a matching product. Free shipping depends on the delivery method. A gift card behaves more like stored value. Then coupons enter the same order. The business needs clear rules for stacking. The customer needs to see which benefit applied and why. Totals should stay stable between the cart, payment step, receipt, and any later refund. We store the applied benefit on the order itself. Recalculating an old order from current rules can produce a different answer. ## Staff tools are part of the customer experience Many redemptions finish at a counter. Staff need a quick screen to find the customer, scan a code, confirm the reward, and move on. Slow or unclear staff tools turn a smooth app flow into an awkward conversation. Permissions matter here. A cashier may need to redeem a reward without seeing full customer history. A manager may need to reverse a mistake. The audit log should show who did each action. The customer rarely sees these controls. They feel the result when the line keeps moving. ## Messages should match the state Customers may receive a confirmation, expiry reminder, cancellation notice, or balance update. Those messages have to follow the real redemption state. Sending a reminder for a reward that was already used creates doubt. Announcing points before the transaction finishes can do the same. We trigger messages from completed state changes and keep a record of what was sent. ## Reporting closes the loop Businesses need to know how rewards are being used. That includes redemptions, points spent, reward cost, unused claims, location, tier, and the orders connected to each reward. The definitions need to stay consistent with the operational system. This is useful for ordinary decisions. A reward may be popular and expensive. Another may be claimed often and rarely used. A tier-only benefit may have almost no eligible customers. The goal is to make those patterns visible without turning the reward flow into a reporting exercise for the customer. ## Simple takes coordination The best version of this feature is quiet. The customer sees an available reward, claims it, and uses it. Staff verify it quickly. The points history makes sense. Reports update later. Getting there means working through the unglamorous cases: retries, refunds, expiry, low stock, duplicate requests, permissions, and unclear rules. That's where a lot of the product gets built. # Introducing Fidelect Source: https://fidelect.com/blog/introducing-fidelect Published: 2025-08-17 Author: chaqchase A new foundation for customer-driven businesses Today, we're introducing Fidelect. A foundation for how businesses and customers actually connect. ## Loyalty was never the problem For years, businesses have been sold the same pitch. Add points. Add rewards. Add discounts. Here's the thing: loyalty programs don't fix broken systems. They sit on top of them. Most businesses have no coherent way to understand their customers. Data lives in five different places. Tools don't talk to each other. Every decision happens in a vacuum. Loyalty programs were designed to patch over that reality. ## We started with a different question We asked: what if everything lived in one place? Understanding customers. Engaging them. Growing with them. What if you didn't need six tools to do the job of one? That question became Fidelect. ## What Fidelect actually is Fidelect is a platform that works for both sides. For businesses: a unified system to understand customers, run engagement, and make better decisions. No more juggling six different tools. For customers: a clear way to see their rewards, track their progress, and feel recognized by the places they choose to return to. It brings together things that usually live in separate tools: - Customer profiles and history - Purchases, visits, interactions - Rewards and recognition - Communication and campaigns - Insights that lead to decisions Loyalty lives inside this system. It's one layer. A way for businesses to show appreciation, and for customers to see that appreciation reflected back. ## Systems, not shortcuts Shortcuts don't scale. They create debt. Fidelect is modular. Start with the basics. Expand when you're ready. No rebuilding. No migration headaches. No changing how your data flows. Start by understanding who your customers actually are. Add engagement when it makes sense. Run campaigns when you need them. See what works. Everything connects because everything shares the same foundation. ## Why loyalty still matters Loyalty is mutual value. Customers return to places that remember them. Businesses grow when they give people a reason to come back. In Fidelect, loyalty works both ways: - Customers earn real rewards for their choices - Businesses learn what actually matters to their customers - Both sides benefit from continuity The goal is building something worth returning to. ## Built for real places, real people Fidelect is for businesses that operate in the real world. And for the customers who walk through their doors. Places with repeat visitors. Places where people actually want to come back. Places where long-term relationships beat one-time transactions. Retail. Services. Clinics. Fitness. Hospitality. Different industries. Same need: a better way to grow together. ## Infrastructure, not trends We're building infrastructure. Something you can rely on as your business grows, changes, evolves. Something that gets better without getting more complicated. Customer relationships are commitments. ## What's next This is the beginning. Fidelect will keep growing. New capabilities, same foundation. Grounded in one simple idea: the best business relationships benefit everyone involved. Businesses get the tools to do right by their customers. Customers get experiences worth coming back for. This post introduces the foundation. What comes next shows how it works.