Part 1 — The full documentation
01Full documentation map
Manager Seats is one topic in a much bigger library. This page now covers the rest of it too. Use the map below to jump to a topic — each card is a plain-English Anthos guide, written from the full documentation, with the Manager Seats deep dive following in Part 2.
02Card Templates — all 8 types
Every loyalty program starts with a template. Anthos has eight, and picking the right one matters more than the design: each type accrues, redeems, and behaves differently in the scanner and in kiosk mode.
Stamps
The classic buy-X-get-one-free card. Set how many stamps fill the card and what the completed card earns. Works by visits or by spend — and that choice matters: expense-based Stamp cards are not credited automatically in kiosk mode.
Cashback
Customers earn a percentage of each purchase back as a balance they can spend later. Handled manually at the till — Cashback cards are not credited automatically in kiosk mode.
Reward
Points customers collect and exchange for rewards from a list you define. Visit- and points-based Reward cards work with kiosk automation; expense-based ones do not.
Membership
A card that proves belonging — clubs, gyms, communities. Membership cards accrue on visits or points, and automatic accrual in kiosk mode does apply to them.
Discount
A standing percentage off for the cardholder. One rule catches people out: the discount applies to the bill, but items you exclude don't count — excluded products are left out of the discounted total rather than discounted.
Coupon
A one-time welcome offer — the new-customer hook. One use, then it's done, which is exactly what makes it a first-visit tool rather than a loyalty program on its own. Kiosk automation applies to Coupon cards.
Multipass
A prepaid bundle of visits — buy 10 sessions, use them one at a time. Non-obvious rule: redemption visits are just redemptions; nothing accrues when a pass visit is used. Kiosk automation applies.
Gift Card
A prepaid balance someone buys for someone else. Requirements that surprise people: a Gift card needs an online store with Stripe connected to sell it, the physical version works from a printed QR code, and a gift card sitting in a wallet cannot receive push notifications the way other cards can.
Repeat visits → Stamps or Reward. Belonging → Membership. A standing saving → Discount or Cashback. A first-visit hook → Coupon. Prepaid sessions → Multipass. Something to sell as a present → Gift Card.
03Customers & segments
Cards only matter once people hold them. This section covers getting customers into Anthos, finding them again, and grouping them so messages land with the right people.
Getting customers in: four import routes
- Manually — add a customer one at a time from the Customers section.
- CSV / Excel file — bulk-import an existing list from a spreadsheet.
- Another loyalty platform — migrate customers in from the system you're leaving.
- An existing customer database — bring a database across rather than starting from zero.
Enrolling new customers
Each card template has an enrollment form with its own unique link and QR code. Put the QR where customers stand — till, table, receipt — and the link anywhere digital. A customer fills in the form, gets the card in their wallet, and appears in your Customers list. No app download for the customer.
Visits, counted by status
Customer activity is tracked as visits, and visits are counted by the customer's status — new, inactive, and active. That split is what tells you whether the program is growing regulars or collecting ghosts: a rising inactive count is a win-back job, not an acquisition job.
Segments
Segments are dynamic groups built from filters — activity, points, visits. Build them once and they stay current. They are also the sending list for manual push campaigns (see Push notifications), and managers need the View / Edit Segments permissions to work with them.
Archive is not delete
Archiving a customer is the soft option — it tidies the list while keeping the record. Deleting is the hard one. When in doubt, archive. The same thinking applies to manager seats in Part 2: check what you need from the record before anything is removed.
04Push notifications
Push is how a wallet card talks. Anthos's own promo page shows the range: an instant update when points land, a manual marketing message, an offer when a customer is nearby, feedback requested an hour after a purchase, and a reminder when someone hasn't returned. The documentation puts hard numbers on each kind:
| Kind of push | How it works | The limit |
|---|---|---|
| Scheduled / event pushes per template | Set against a card template — tied to dates or events in the card's life. | Up to 3 per template |
| Location pushes | Sent from a location — for example on a visit, or after 30 days inactive. | Up to 2 per location |
| Geo-push | Reaches customers within about 330 feet of a location, using the message set on that location. | Up to 10 location-based pushes per sub-account on the highest plan; more for a fee |
| Manual campaigns | Written and sent by you to a segment — the promo page's custom push designer is this, with a picture and your text. | Unlimited on paid plans |
| PWA messages | For customers on the web-app version of the card rather than a wallet pass. | Separate channel |
A push is triggered by something changing. If a customer's balance doesn't change, no push goes out. A scan that adds nothing sends nothing — which is why the instant “you earned points” message only ever follows a real accrual.
Geo-push, in detail
The geo-push radius is about 330 feet around a location: a customer carrying the card who comes within that distance can receive the message set on that location. The allowance is counted per sub-account — up to 10 location-based pushes on the highest plan, with more available for a fee. Keep two numbers apart: the Coupon card has its own, separate proximity rule of 100 metres — that is a coupon mechanic, not the geo-push radius, and the two should never be merged into one figure.
The push automation hub
Beyond one-off sends, the automation hub runs the pushes a program needs every week, set once and left to fire:
- Next visit reminder — a nudge timed around when a customer would normally come back, sent while the habit is still warm rather than after it has gone cold.
- Birthday congratulation — an automatic birthday message for the customer's day, the friendliest push a program sends all year.
- Triggered auto-push — a push fired by an event on the card or the account, so the message follows something the customer actually did.
Richie AI for Business — help writing the push
Richie AI for Business is the assistant inside the push tools: it helps a business draft and shape the messages it sends its own customers. Keep it separate in your mind from Prospecting Richie, the AI Sales Copilot in the agency prospecting tools — same first name, different job, different audience. Richie AI works on messages to people who already hold your card; Prospecting Richie finds businesses that don't have an account yet.
05RFM analysis
RFM is the analysis that ranks your customers by behaviour instead of by gut feel. It scores every customer on three things:
- Recency — how long since their last visit. Recent is better.
- Frequency — how often they come. Often is better.
- Monetary — how much they spend. More is better.
Put together, the scores sort your base into the people your field guide already names: high-RFM customers are The Regulars — protect them. Customers whose recency is slipping are becoming Ghosts — they are the win-back segment, and the 30-days-inactive location push in the section above exists for exactly them. RFM turns “we should message lapsed customers” into a named, countable list you can send to through segments.
06Dashboard & statistics
The dashboard is the program's front window — the first screen, summarising how the loyalty program is doing. Underneath it, statistics break into the same four areas the manager permissions use (see Part 2, permissions):
- Revenue statistics — income generated through cards, redemptions, and campaigns.
- Feedback statistics — satisfaction ratings and reviews customers submit through their cards.
- Referral statistics — how many customers arrived through referrals, and how referrals perform.
- Customer profile statistics — engagement per customer: visits, points earned and redeemed, interaction history.
For franchise chains, the same dashboard rolls up across branches — visits, activity, retention, feedback, referrals, and customer profiles for the whole chain — while branch-level access stays with the main franchise owner (see Part 2, Franchise chains).
Manager statistics, read properly
The manager side of statistics lives on the manager profile (Part 2, section 20): the profile tiles, the editable Information section, and the Last Transactions grid are the figures the figures catalogue captions as Managers, Manager Profile, Information, Save, and Last Transactions. A weekly statistics report rounds the same numbers up on a weekly rhythm, so owners who don't open the dashboard daily still see the program's week in one place.
07Locations, kiosk mode & the Scanner App
Three topics that meet at the counter. Locations are the places; the Scanner App is the tool staff use in them; kiosk mode is the scanner's automatic gear. Each has a full treatment inside the Manager Seats deep dive — this is the map of how they fit together.
Locations
A location is created with a name, an address (pick from the suggestions as you type, then set the exact point with the map pin), the cards it applies to, and a geo-push message for customers within about 330 feet. Locations feed everything else: the geo-push above, and the Location dropdown on a manager seat — create the location first, then the seat. Full detail in Part 2.
The Scanner App
The scanner is free, runs from the browser, and installs to the home screen — no app store, no extra hardware. Staff sign in with their own manager seat; customers can be found by name, phone, email, or card serial number when a card isn't at hand. Sign-in, install, sessions, and the white-label link are covered step by step in Part 2.
Kiosk mode
Kiosk mode credits stamps or points automatically on scan — built for busy counters — with a scan delay so the same card can't be credited twice by accident. It applies to most templates, but not expense-based Stamp and Reward cards, Cashback, Discount, or Gift cards. Managers can work in kiosk mode; only the main admin can change its settings. Full detail in Part 2.
08Plans, workflows, API & automations
Platform plans
Anthos runs three plans — Launch $249/month (2 managers, 1 promotion, 1 location), Scale $349/month (10 managers, 3 promotions, 3 locations), and Dominance $449/month (50 managers, 10 promotions, 10 locations) — annual-tariff “from” prices, every plan with unlimited digital cards and push, and a 14-day free trial. The manager-seat side of the plans is in Part 2, Seat limits by plan.
Workflows & API
Workflows automate the program: a trigger fires — something happening on a card or to a customer — and an action follows, inside Anthos or in another tool. The full trigger and action lists, the Draft-versus-Working rule, and the card-type limits are in the Workflow Builder section; the API, MCP, webhooks, and automation platforms are in the API section; and the till, store, and messaging connections are in Integrations.
Automations with other apps
The Anthos promo page promises connections to 5,000+ apps through its automations. In practice that is where loyalty events leave Anthos: a new customer joins a mailing list, a redemption lands in a spreadsheet, a lapsed regular creates a follow-up task. Exact connectors and Anthos plan requirements for workflows and API access are listed under Still to confirm rather than guessed here.
09Workflow Builder: triggers & actions
The Workflow Builder turns Anthos into a program that runs itself: pick something that happens — a trigger — and the chain of actions you attach to it runs on its own, across any of the eight card types, with as many steps as you need.
Triggers: what can start a workflow
- About the customer — a customer is created, a customer is deleted, or today is the customer's birthday.
- About the card — a card is installed, expires, is deleted, is issued, or is scanned in the Scanner App.
- About value on the card — a coupon is redeemed, a stamp count is reached, a points count is reached, a rewards count is reached, a used-rewards count is reached, stamps are about to expire, or bonuses are about to expire.
- About signals — a review is left, a customer moves into an RFM segment, or an inbound webhook arrives from another system.
Actions: what a workflow can do
- Wait and Condition — pause the chain, or branch it on a filter, before anything is sent.
- Send Email, Send SMS, and Send push and web-push — message the customer on the channel that fits.
- Accrue and Redeem — add value to the card, or take a reward off it, automatically.
- Send HTTP request — hand the event to another system in real time.
- Send conversion to Meta Ads — report the event back to your ad campaigns.
- Change card expiration — extend or shorten the card's life as part of the chain.
Conditions and filters vary by trigger and by card type — a points threshold on one card, an installed/not-installed check on another — so build the filter for the card the workflow is actually about.
Draft first, then Working
Every automation starts in Draft mode: saved, visible, and completely inactive. Switch it to Working mode when it should run in real time — and you can switch it back to Draft at any time. The counter next to an automation's name shows how many times its trigger has fired, so a workflow that has never run is easy to spot.
Card-type limits inside workflows
- Points count reached works only with Cashback, Reward, and Gift cards.
- Rewards count reached and Used rewards count reached work only with Stamp cards.
- The card bonus balance filter applies specifically to Reward cards.
Two practical requirements: SMS actions need a connected Twilio account, and email actions need Mailgun, SMTP, or SendGrid. And one honest limit: automation logs viewed through the API show totals only — how many times a workflow triggered and how many failed — not which individual customers a failed step missed. That identification is not supported yet.
10Integrations: POS, commerce & messaging
Integrations connect Anthos to the tools a business already runs — the till, the online store, the booking system, the chat channels. Each one below is a separate connection with its own rules; the differences matter, especially where two connections look alike.
Toast POS — restaurants
Toast is connected per restaurant location. One requirement catches people out: the restaurant's Toast account needs third-party integration access through Toast's Restaurant Management Suite (about $50/month, giving access to 200+ Toast partners) — that is a Toast requirement, not an Anthos one. The flow: in Toast, open Integrations, browse and purchase integrations, find the loyalty connection, add it, choose the location or location group, and accept the terms. Then turn rewards on at the POS itself (Toast Marketing → Loyalty → Rewards Program → Enable Loyalty → Save → Publish Changes). Staff need POS terminal access with their 3–8 digit POS access code.
Toast identifies each location with a long location GUID — not the same as the Restaurant ID. The GUID goes into the field labelled “Restaurant ID” in the Anthos connection (Settings → Integrations → Add Integration → Toast → Connect), from the business owner's sub-account, signed in on the main app domain. Sign in through a different domain and the Toast integration simply does not appear. Strip any ?guid= prefix or trailing parameters before pasting, and repeat the connection for each location. The same loyalty card can serve several locations. Card-specific Toast setups exist for Reward, Stamp, Cashback, Discount, and Membership cards.
Shopify — two connections that are not the same
| Shopify POS connection | Shopify store app | |
|---|---|---|
| How it connects | A custom app using the Admin API | A ready-made app, installed in one click from Integrations |
| Card types | Stamp, Cashback, Discount, or Reward | Cashback only — and the type cannot be changed afterwards |
| How value accrues | Manually, through the Scanner App | Automatically from Shopify orders — no scanner needed |
| What customers see | No storefront widget, and no provider branding on show | A storefront widget, carrying the provider's branding |
| Your own domain | Can be connected through a white-label domain | Cannot — connect from the main app domain only |
Whichever route you take, connect it inside the client's sub-account — the one that must receive the orders, cashback, and customer data. Connect in the agency account first and the app binds to the wrong place; the fix is to remove the app from the Shopify store completely, disconnect it in the agency account, sign in to the client's sub-account on the main app domain, and reconnect there only. For the store app: email is a mandatory field on the card issuance form, a new store registration issues the customer a cashback card, point additions and spending sync automatically, choosing points in the widget's “Ways to redeem” produces a discount code applied at payment, a paid order's details flow back to the card, a cancelled order deducts the points again — and until the connection is activated, the card can be issued to a maximum of 10 customers.
Altegio — salons and bookings
Altegio connections earn stamps, cashback, or multipass visits automatically from the visits and payments recorded there. Set it up inside a sub-account, not the agency account, with full admin access in Altegio and an active loyalty card. The connection step is an invitation: add the integration's address in Altegio with every checkbox enabled across Settings, Loyalty, and Clients, then invite. Cashback behaviour is controlled from the Altegio side.
On a Stamp setup, selecting the card delivery channel can trigger a mass WhatsApp send of card links — and a possible spam block. Leave it off. The usual stamp rule is “purchase or service completed”; alternatives are a receipt over a set amount, a stamp for every set amount spent, or specific products and services by ID. A typical setup is 2 visits in a day earning 1 stamp, credited only after payment. A Multipass must be configured in Altegio first. Finish by synchronising clients from Altegio.
ActiveCampaign — email marketing
Connect from ActiveCampaign's Apps area by adding the account with the Anthos API key, then, on the Anthos side, add a resource under Connected applications, choose a trigger, and map the fields. The standard contact fields are not enough — expect to create additional fields (around 35 are mappable: balances, card type and status, install and share links, stamps and rewards counts, expiry, location coordinates, and more). One step is easy to miss and fatal if missed: add a subscription for the contact by email, or the messages will not reach them. A typical chain runs: customer created → added to the mailing list → card issued → install link emailed → share link after install → reward news at nine stamps or more.
Manychat — chat channels
Manychat covers Instagram, Facebook, WhatsApp, and Telegram. Register on the channel you use, connect from Integrations with the API key, and — for Telegram — create a bot through @BotFather if you don't have one. Create the custom fields first so customer data has somewhere to land, then build the flow: a trigger (a referral link or a keyword) → the bot asks for first name, last name, phone, and email → the customer is created and the card issued → a Telegram message follows with the install link, and the share link about ten seconds later. Click Set live when the flow is ready.
Square — payments and loyalty
Square needs two things in place before connecting: a Square account, and loyalty already set up inside Square. Connect from Integrations and sign in to Square. Connecting creates a Reward card whose template mirrors every reward level configured in Square, kept in sync from the Square side — so the card issuing form must make phone a required field, and install-link delivery needs Twilio connected in the mailing settings. From then on, customer profiles sync both ways between Square and Anthos, and bonus quantities and reward availability stay matched in both directions. Staff redeem in the Square POS app (Library → rewards → customer → award → purchase amount → Review Sale). Most failures trace back to a short list: a free Square plan or an ended Plus trial, no loyalty program created, a country Square loyalty doesn't cover, a phone number that isn't in international format (or is fictitious, or already tied to a loyalty account), the wrong Square account, no location set in Square's Loyalty settings, or the connection switched off in Square's app-integration settings. Test with real, valid phone numbers — test numbers don't create customers in Square.
HighLevel, UChat & WordPress WooCommerce
Three more connections follow the same house pattern: connect from the Integrations section with an API key or an account sign-in, then map which events trigger what. HighLevel ties loyalty events into CRM pipelines and messaging. UChat does the same for chat-first customer journeys. WordPress WooCommerce connects a WordPress store so shop activity and loyalty stay in step — it sits as its own top-level connection rather than under the POS group. The detailed per-field mapping for these three is confirmed at pattern level in the source documentation; the exact Anthos-side field lists are under Still to confirm.
11API, MCP, webhooks & automation platforms
For everything the built-in integrations don't cover, Anthos exposes an API — and, on top of it, a set of ready-made bridges to the big automation platforms, so loyalty events can reach the other apps a business uses without custom code.
MCP — run the program from an AI assistant
The MCP connection lets AI assistants such as Claude, Cursor, and VS Code work with a loyalty program in plain language. Sign-in is by OAuth 2.1 with the account (recommended) or by a personal API key; on a white-label or custom domain, the account's own API host replaces the standard one. Once connected, the assistant can work across customers and segments (create, find, update, delete), templates (including reward and membership tiers and feedback links), cards (issue, look up, update, set expiration and tier), balances (add or subtract stamps, points, scores, visits, amounts, purchases, and rewards; redeem coupons), locations, UTM links, workflows (build, activate, pause, run, inspect logs), external services, white-label settings, and — on agency plans — sub-accounts, searched and acted on for the agency. It needs an account on a plan that includes API access and an MCP-compatible client; the extra local setup is only needed for the API-key route on one desktop client.
Webhooks — Anthos tells your other systems, instantly
A webhook notifies another system the moment something happens — no manual checking, and no developer needed to switch one on, as long as the receiving address belongs to a system that can accept it (an automation platform, a CRM or internal tool, or a testing tool while you build). Events include card scanned, card issued, customer created, payment completed, payment refunded, and card balance updated, plus agency-side events such as a sub-account company being created or removed and a manager being created. Setup: Left-hand menu → Settings → Webhooks tab → Add webhook, enter the receiving URL, tick the events, set the status to enabled, and save.
The automation platforms
Each platform connects the same way at heart — find the connection in Integrations, sign in, and connect with the Anthos API key — then differs in how you build:
| Platform | Reach | How a build goes |
|---|---|---|
| Zapier | 5,000+ apps | Create a Zap, pick the Anthos event as the trigger (test it — “New Customer” is the usual first), then add the action, such as issuing a card, mapping the template to the customer. |
| Pabbly | 1,000+ apps | Create a workflow; a classic first build takes a new or updated spreadsheet row and creates a customer — only name and phone are mandatory. |
| Integrately | 1,100+ apps, millions of ready-made automations | Pick the trigger on the left and the action on the right, paste the webhook URL into the Anthos account, make a test customer, and activate. |
| KonnectzIT | Visual canvas builder | Create a Konnectz, drag the app into the middle, capture a live webhook response from a real test action, and build from the actual data it returns. |
| Albato | Trigger-and-action builder | Create an automation, add the trigger and the connection, add the action (issue a card is the standard example), map the fields, save, and start. |
| Make.com | Scenario builder | Create a scenario, add the app, and start from an event such as “customer created” — the standard chain issues the card and adds the first reward. |
Which of these are live on which Anthos plans is listed under Still to confirm — the promo page's “5,000+ apps” line is the Zapier figure, not a promise that every platform is on every plan.
12Prospecting Richie — your AI Sales Copilot
Prospecting Richie is an AI sales copilot for agencies: it finds businesses, opens sub-accounts for them, and writes and sends a personalised email chain to each one. It shares a first name with the push assistant in section 04 — they are different tools, and this section keeps them apart.
Richie AI for Business (in Push notifications) helps write and time messages to a business's own customers. Prospecting Richie (here) finds new businesses for an agency and emails them. Different audience, different screen, different rules — don't carry settings from one to the other.
Where it lives, and the prompts come first
Find it at Left-hand menu → Agency (crown icon) → Prospecting (plus icon). Before Richie can be activated, its prompts must be customised — there are six of them (a first cold email and five follow-ups). The GPT help can be switched off to write a prompt from scratch instead. Bracketed variables inside a prompt are fixed placeholders: they can't be edited or newly invented, but placeholders can be added or removed with the placeholder icon. Use Generate preview to read exactly what will go out before anything sends.
A prompt aimed at Spanish-speaking owners must be written entirely in Spanish, and a Portuguese one entirely in Portuguese. Mixing English into a translated prompt breaks the output — translate the whole prompt, instructions included, or write it in the target language from the start.
Launching a run
- Start Auto Prospecting
Choose the business category you want Richie to look for.
- Set the search area
On the map, enter the area and use “search in this area”. Work step by step — 20–30 companies at a time is the pace the guidance recommends.
- Pick a snapshot
Select the snapshot the new sub-accounts should start from.
- Review the companies
Read the list and deselect anything that shouldn't be contacted — large networks are the usual example.
- Confirm, then “Let's start”
Review the assignment confirmation and click “Let's start.” From that click, the run is locked: changes can no longer be made.
On launch, Richie creates the sub-accounts and an AI-generated email chain for each client, and progress is tracked in the mailing list Richie generates (agency side: crown icon → mailings icon → mailings tab).
Sender rules you don't control — and shouldn't promise around
- The sender is chosen by priority, not by you: Resend first, then Mailgun, then the other connected providers (SMTP, SendGrid, or HighLevel where the account has it connected). The sender cannot be picked manually.
- Statistics depth depends on the provider: Mailgun and Resend report the most (sent, delivered, opened); SMTP and SendGrid report less.
- Stopping: cancelling a mailing stops its pending messages. To stop one recipient, use the inbox tab, the recipient list on the sub-account profile — or do nothing and let a reply do it: a reply from the same address Richie wrote to stops that recipient automatically.
Hard limits, stated plainly
- Richie verifies email addresses before sending, and skips a business that is marked closed, has no decision-maker email found, has no valid email on its website, or already has a sub-account created by the agency.
- Richie cannot be launched on sub-accounts that already exist or were created manually — only Richie-created sub-accounts can receive Richie campaigns. Otherwise, Richie-created and manual sub-accounts work exactly the same.
- A run cannot be restarted for the same company or contact — not even after deleting the sub-account and stopping the campaign.
- Richie contacts cannot be downloaded, and that is not planned. There is also currently no label showing whether a sub-account was created by Richie or by hand.
- Nothing stops a different agency from independently creating the same business as its own sub-account.
13Support: chat, AppSumo, roadmap & community
When something is stuck, there are four doors: live chat inside the app, the AppSumo redemption route for code buyers, the public roadmap for what is being built, and the community for talking to other owners. Who each door is for matters as much as where it is.
Live chat (Intercom)
After signing in, click the chat icon in the bottom-right corner, then Messages at the bottom of the popup, and — for a first conversation — “Send us a message”. The message field takes typed text plus GIFs, emojis, and file attachments from the three icons beside it.
The built-in chat is the support channel for direct Anthos customers — accounts on a trial or a paid subscription. It is not available to the end clients of agencies working through sub-accounts: those clients go to their agency's own support team instead. Agencies can connect a separate chat widget for their own clients, so an agency's customers are never left without a door — it's just the agency's door, not this one.
AppSumo codes
AppSumo buyers redeem from the AppSumo registration page: first name, last name, email, a password (entered twice), then the code in the AppSumo Code field and Validate Code. Applied codes collect in the “Your application codes” field, the plan they add up to shows in the plan field — then accept the terms and click Get Started. Redeemed codes also appear afterwards in the AppSumo tab of the account's Settings.
Roadmap & updates
After signing in, the bell icon in the bottom-right corner opens a popup with three tabs — Updates, Roadmap, and Help Center — landing on Updates by default. The Roadmap tab groups what's coming into In Progress, Up Next, and Future, and the updates feed is where shipped changes are announced; both can be followed from the same popup.
Community
The owner community lives in a Facebook group. The route in is from the bottom of the main site: scroll to the footer, click Community, then Join Group on the group page. It's the place for owner-to-owner questions — what worked, what didn't — alongside, not instead of, the support routes above.
14Figures & the screenshot catalogue
Good help documentation shows the screen, not just the words. This catalogue lists the figures the Anthos guides should carry — starting with the confirmed captions on the manager statistics pages — and the kinds of screenshots each topic needs, so the Anthos versions are captured consistently.
Confirmed figure captions: Managers & Statistics
The manager statistics guide figures carry short, exact captions — each one just the name of the screen or field it shows. In the order a reader meets them:
- Managers — the grid itself (used wherever the grid is shown).
- Manager Profile — the profile screen reached from a username.
- Information — the editable details section on the profile.
- Save — the button that commits profile edits (captioned wherever it appears).
- Last Transactions — the transactions grid under the profile.
- Add Manager — the popup, followed by one figure per field: Full Name, Email, Contact Number, Password, Repeat Password, Location, Notes, and the Send access to email toggle.
- Edit — the pencil action at the end of a grid row.
The same one-label style runs through the other confirmed sets: the chat figures are captioned Chat Icon, Messages, Send us a message, and Message; the AppSumo form carries one figure per field (First Name, Last Name, Email, Password, Repeat Password, AppSumo Code, the applied-codes field, the plan field, Terms of Agreement, Get Started, and AppSumo); the roadmap figures are Bell Icon and Roadmap; the community figures are Community and Join Group; and the webhook figures are simply Webhooks and Events. The Anthos rule to copy is the style, not the words: caption every figure with the UI element it shows.
The screenshot types the library uses
Grids & data tables
The working screens: the Managers grid, profile tiles, Last Transactions, customer grids, statistics grids, automation lists, and webhook/event lists. Capture the whole table, headers included.
Popups & forms
Add/Edit Manager, Add webhook, the AppSumo registration form, integration connection dialogs, and the workflow trigger/filter and condition/action builders — one figure per field wherever a field can be got wrong.
Phone & wallet shots
Cards as customers see them: Apple Wallet and Google Wallet passes, scanner phone screens, install-link screens, and the Shopify storefront widget.
Maps
Anywhere distance is the point: the geo-push radius around a location, the prospecting search area, and location maps.
Print materials
The physical kit: QR codes, table tents, and stickers — photographed in place, not just exported as files.
Settings, toggles & widgets
Plan and compare-plans views, kiosk settings, location forms, payment and subscription screens, and the support chat popup in its open and closed states.
Third-party screens
Toast, Shopify, Altegio, ActiveCampaign, Manychat, Square, HighLevel, UChat, and the automation platforms. In the source library these are usually uncaptioned, with the step text doing the explaining — for Anthos, caption them anyway.
Embedded video
The source library mixes Loom walkthroughs, shorter Boom clips, YouTube videos, one interactive demo format, Google Drive files, and a social-group embed. Anthos versions should be Anthos recordings in the real interface — see the video sections.
Part 2 — Manager Seats, the deep dive
15What a manager seat is
Every person who works with your loyalty program should work under their own name. A manager seat is a separate profile — name, email, and password — created by the account owner. Whoever holds the seat signs in with those details and can only see and do what the owner has allowed.
Seats are used in two situations:
- In a store: salespeople and till staff get a seat so they can open the Scanner App, scan customer cards, and add points or stamps — while their transactions stay recorded under their own name.
- In an agency: a team member gets a seat in the agency workspace so they can help run client sub-accounts, with access limited to the sub-accounts work they actually do.
Video walkthrough: “Managers” — record and embed the Anthos version here.
It should show the Managers grid, the Add Manager popup, and the Edit Manager permissions.
Never share the owner's login with staff. If someone needs access, give them a seat. When they leave, delete the seat — their access ends. What happens to their past transactions in reports after deletion is not yet confirmed for Anthos — see Still to confirm before relying on it.
16The Managers grid
Everything starts in one place: Left-hand menu → Managers. The Managers screen lists every seat on the account in a grid with these columns:
Illustration of the Managers grid layout, drawn for this help page — not a screenshot. Rows and names are examples only. Replace with a real Anthos screenshot before publishing.
- User Name — click a name to open that manager's full profile (see section 20).
- Created — when the seat was created.
- Notes — the internal note recorded on the seat, such as a shift or store.
- Location — the location the manager is tied to, if one was set.
- Status — the seat's current state.
- Pencil icon at the end of a row — opens the Edit Manager popup (see section 21).
17Add a manager
Path: Left-hand menu → Managers → Add Manager. You can start from the Add Manager button at the bottom of the Managers grid, or from the Create Manager tile. Both open the same Add Manager popup.
Agency accounts: in the agency dashboard, open the User section — the bottom icon in the left-hand menu — then open Managers in that menu. Adding a team member there follows the same popup and the same fields below.
- Open the Add Manager popup
From the Managers grid, click Add Manager (bottom of the grid) or the Create Manager tile.
- Full name
Type the manager's full name. This is the name shown in the Managers grid and recorded against their transactions.
- Email
Enter the manager's email address. It is used for the access invitation and as their sign-in for the Scanner App.
- Contact number
Add a phone number for the manager, if you want it on the profile.
- Password, then confirm it
Create a password for the seat in the Password field, then type the same password again in Repeat Password. The two entries must match. (Anthos password rules are listed under Still to confirm.)
- Location — optional, and powerful
The Location dropdown lists the locations already created on your account. Pick one to tie the manager to that location — or leave it unset: with no location chosen, the manager can service all cards created in the account, at every location.
- Notes
Use Notes for anything your team needs to know about this seat — shift pattern, store, or role. The note appears in the Managers grid.
- Send access to email
Leave the Send access to email toggle on to email the manager their access invitation. Turn it off only if you plan to hand the sign-in details over another way — with the toggle off, no invitation is sent.
- Create the seat
Click the create button in the popup. The manager profile is created and appears in the Managers grid, ready to sign in.
| Field | What it is for |
|---|---|
| Full Name Required | Display name in the grid, the profile, and transaction records. |
| Email Required | Access invitation recipient and Scanner App sign-in. |
| Contact Number Optional | Phone number kept on the profile. |
| Password Required | The password you set for this seat at creation. |
| Repeat Password Required | Must match the Password field exactly. |
| Location Optional | Restricts the seat to one location. Leave unset to allow all cards in the account. |
| Notes Optional | Internal instructions or context; shown in the Managers grid. |
| Send access to email On by default | Sends the access invitation by email. Off = no invitation is sent. |
Screenshot to capture in Anthos: the Add Manager popup with all fields visible — Full Name, Email, Contact Number, Password, Repeat Password, Location, Notes, and the Send access to email toggle.
Where the Location dropdown comes from
The Location list in the Add Manager popup is not typed in by hand — it is filled from the locations already created on your account, under Left-hand menu → Locations. A location there is created with a name, an address (suggestions appear as you type; pick the right one, then set the exact point with the map pin), the cards it applies to, and a geo-push message that reaches customers within about 330 feet of that spot. So the order matters: create the location first, then create or edit the manager seat and pick it from the dropdown. If the business only has one site, or the manager genuinely covers everywhere, skip the field — with no location set, the manager can service all cards created in the account.
18Signing in to the Scanner App
A seat is only useful once its holder can sign in. Managers sign in to the Anthos Fidelity Scanner App with the email and password on their seat — the same details the owner set when the seat was created. The main account login also works in the scanner, but staff should always use their own seat.
- Open the Scanner App
Go to app.anthosfidelity.com/scanner-app on the device — it opens in a new tab. The scanner opens on a sign-in screen: “Welcome to the digital card scanner app.”
- Sign in via email
Under Sign in via email, enter the email address registered on the manager seat.
- Enter the password
Type the password set for that seat, then tap Sign In. The manager is in and can scan cards.
- One seat, one device at a time
Don't sign in with the same seat on several devices at once — sharing one login across devices interrupts the session. Each person scanning should have their own seat.
The Anthos promo page describes the same flow from the owner's side: once a business account is created, the owner gets a link to the free Scanner App, shares it with every salesperson, and monitors shared statistics. Manager seats are how each of those salespeople gets in — under their own name. No extra hardware is needed.
Put the scanner on the home screen
The Scanner App runs from the browser — there is nothing to download from an app store. Open the scanner link on the phone or tablet, then use the browser's Add to Home Screen option (on iOS or Android) to install it. From then on, the Scanner App icon sits on the home screen like any other app, and staff open it with one tap. Signing in also adds the app to the home screen. If the install option doesn't appear, clear the browser cache and open the link again.
If your business uses its own domain (white label)
Always use the scanner link under your own domain, not the standard app.anthosfidelity.com link — that is what keeps your branding intact. You can reach your domain's scanner link three ways: from your dashboard, click your profile picture (top right) and open the Scanner App tab; from the white-label settings (crown icon → settings → Scanner App branding → Open); or from the Managers section. Copy that link to any device, or open it and install from there.
Sessions end every 24 hours
For security, a scanner session ends automatically every 24 hours, and this cannot be changed. Build it into the routine: each person signs in fresh at the start of their workday, rather than mid-shift when a customer is waiting. And keep one login per person — signing in on several devices with the same credentials interrupts the session, which is exactly what separate manager seats prevent.
The white-label link behaviour and the 24-hour session above come from the source documentation this page is modelled on. Confirm both against the live Anthos product — the exact scanner link under a white-label domain, and whether Anthos scanner sessions end at 24 hours — before treating them as Anthos fact. They are also listed under Still to confirm.
19The scanner at work: search, scanning & kiosk mode
Once a manager is signed in, the scanner home page is where the day happens. Open the app menu with the three-line icon at the top right; Settings is where scan behaviour is set — a beep on scan, showing the scan result, copying the QR code to the clipboard, and a debug mode — using simple toggles.
Finding a customer without a scan
If a customer doesn't have their card ready, the manager doesn't have to stop. Customers can be searched in the scanner by name, phone number, email, or card serial number — then the transaction continues as normal.
Kiosk mode: automatic stamps and points
Kiosk mode is a scanner mode for busy counters: when it's on, stamps or points (depending on the card type) are added automatically when a card is scanned, with no manual input. A delay can be set so the same card can't be credited twice by accident. The kiosk settings page lists the account's card templates, and automatic accrual applies to most of them — visit- and stamp-based Stamp cards, visit- and points-based Reward cards, Multipass, Membership, and Coupon cards. It does not apply to expense-based Stamp and Reward cards, Cashback, Discount, or Gift cards; those are still handled manually. Test kiosk mode on a test card before using it live.
Both the administrator and a manager can switch kiosk mode on and work in it — but only the administrator (the main account) can change the kiosk mode settings. A manager can use kiosk mode; they cannot reconfigure it. If the setup is wrong, it goes back to the owner, not the till.
Scanning, card by card — every guide read
Each card type has its own scan-and-transact guide, and all of them have now been read in full: Stamp, Multipass, Cashback, Gift, Coupon, Membership, Discount, and Reward — plus the shared guide to redeeming a promotion at the till. The flows differ where the cards differ: what a scan accrues, what it can redeem, and what staff confirm on screen before completing the transaction. Train staff on the guide for the card type your business actually issues, not on a generic flow. One honest exception: the Stamp guide's “Redeem rewards” section has not been re-verified line by line — it is listed under Still to confirm.
Screenshots to capture in Anthos: customer search in the scanner (name / phone / email / card serial), the scanner Settings toggles, and the Kiosk mode settings page with the card template list.
20The manager profile
Click a manager's username in the Managers grid to open their profile. The profile is where you review a seat's activity — and it is also where deletion lives.
Summary tiles
Illustration of the profile summary tiles, drawn for this help page — not a screenshot, and no real manager data is shown.
What's below the tiles
- Information — the manager's account details, shown in editable view. Save changes with the Save button. The Delete button sits at the bottom of this section (see section 24).
- Permissions — the access controls for this seat; the full list is explained in section 22.
- Last Transactions — this manager's recent activity, listed by User Name, Date, Phone, Device, Template, Event, Amount, and Balance. All of a manager's transactions can be downloaded from here.
Screenshots to capture in Anthos: the profile summary tiles, the Information section, and the Last Transactions grid with its download action.
21Edit a manager
Use Edit when a manager's details change, when they move location, or — most often — when you want to change what their seat can do.
- Find the row
On the Managers grid, find the manager you want to change.
- Click the pencil icon
The pencil icon sits at the end of the manager's row. Clicking it opens the Edit Manager popup.
- Change the fields
Every field on the profile is shown in editable view — update details such as name, contact number, location, or notes as needed.
- Set the accesses
In the same popup, set this manager's permissions — what they can view and what they can change. Each permission is explained in section 22.
- Save
Click Save. The changes are saved and the Edit Manager popup closes.
Review seats whenever someone changes role. A salesperson who becomes a store manager needs more access; someone who moves to a single location should have their Location set, so their seat matches the job they actually do now.
22Permissions, in plain English
Permissions decide what a seat can see and do. Most come in pairs: View lets the manager look, Edit lets them change things. A few are single switches. Grant the least access that lets the person do their job — you can always add more later from the Edit Manager popup.
AStatistics
Numbers about how the program is performing. All four are view-only.
- View Revenue statisticsViewAnalytics on income generated through cards, redemptions, and campaigns.
- View Feedbacks statisticsViewCustomer feedback submitted through cards, such as satisfaction ratings and reviews.
- View Referrals statisticsViewHow many customers arrived through referral programs, and how referrals are performing.
- View Customer profile statisticsViewEngagement per customer: visits, points earned and redeemed, and interaction history.
BTemplates, customers & segments
The design of your cards and the people who hold them.
- View TemplatesViewSee the available card and communication templates.
- Edit TemplatesEditModify templates or create new ones for cards and communications.
- View CustomersViewSee the customer list, customer profiles, and activity logs.
- Edit CustomersEditChange customer data such as name, phone number, tags, birthday, or card status.
- View SegmentsViewSee customer groups built from filters like activity, points, and visits.
- Edit SegmentsEditCreate or modify dynamic segments used for targeted campaigns.
CDay-to-day operations
The till work: scanning, issuing, and messaging customers.
- View OperationsViewLogs of customer actions — visits, accruals, and redemptions.
- Make AccrualsActionManually issue points, stamps, or rewards to customers. This is the core permission for scanner and till work.
- View MailingsViewSee past and scheduled email and SMS campaigns.
- Edit MailingsEditCreate and send email and SMS campaigns.
- View PushesViewSee scheduled and sent push notifications.
- Edit PushesEditSend or modify push notifications.
DLocations, sub-accounts & billing
The sensitive end of the account. Grant these sparingly.
- View LocationsViewSee the list of geo locations and their details.
- Edit LocationsEditAdd, edit, or remove location data such as addresses and contacts.
- View Sub-accountsViewSee all linked sub-accounts in an agency workspace.
- Edit Sub-accountsEditManage sub-accounts: create them, rename them, and change their settings.
- View PaymentsViewPayment history, invoices, and billing dates. There is no matching Edit permission — billing changes stay with higher-level roles.
- Edit PlansEditUpgrade, downgrade, or cancel plans.
- Edit SnapshotsEditCreate or restore snapshots — backups of account settings, templates, and data.
23Suggested starting sets
Not sure where to start? These three combinations cover the most common jobs. They are Anthos suggestions, not fixed roles — adjust them per person in the Edit Manager popup.
Till / Scanner only
For salespeople who scan cards at the counter.
- Make Accruals
- View Operations
- View Customers
Store manager
For the person running one location day to day.
- Everything in Till / Scanner only
- View Locations
- View Pushes · View Mailings
- View Revenue statistics
- View Feedbacks statistics
Agency team member
For agency staff working across client accounts.
- View Sub-accounts
- Edit Sub-accounts
- Plus whatever the client work needs
24Delete a manager
Delete a seat when someone leaves or no longer needs access. Note that Delete is not on the grid row — it lives inside the manager's profile, in the Information section.
- Open the profile
On the Managers grid, click the username of the manager you want to remove (not the pencil icon — that opens Edit).
- Go to Information
On the profile details screen, open the Information section.
- Click Delete
At the bottom of the Information section, click Delete.
- Confirm with Remove
The Delete Manager popup asks you to confirm. Click Remove to delete the seat for good.
Check the seat's Last Transactions on the profile first if you need a record of their activity — all of a manager's transactions can be downloaded from the profile. What happens to a deleted manager's past transactions in reports, and whether deactivation is offered as a softer alternative to deletion, are listed under Still to confirm.
25Agency team members
In an agency workspace, a manager seat is a team member seat. Add team members from the User section of the agency dashboard (bottom icon in the left-hand menu), then Managers.
For a team member to be able to create sub-accounts — manually or through prospecting — grant exactly these two permissions: View Sub-accounts and Edit Sub-accounts. Add further permissions only for the client work that person actually does.
Clients' own staff follow the same pattern inside each sub-account: the sub-account signs in to the Scanner App with its own login, or creates manager seats for its salespeople, who then sign in with their seat details.
Working with sub-accounts
The Sub-Accounts screen (from the Agency section) summarises the client base in four tiles — Total, Paid, Unpaid, and Trial sub-accounts — and lists each sub-account by User Name, Registration Date, Plan, and Status. The list can be filtered by status and searched by sub-account name, email, phone number, or company ID, and the full list can be exported. New sub-accounts are added from the Actions menu (name, company, contact number, email, password, plan frequency, and plan expiration date). Once inside a sub-account, you can switch directly to another sub-account without going back to the agency view first.
Franchise chains: the two hard limits
Franchise accounts work differently, and both differences are about what a manager seat can never do:
- Locations stay with the owner. A franchise has one main account, and only its owner has full access to all branches — viewing them, editing cards, and managing settings across the chain. Staff can be added as managers at franchise level, but even a manager given every available permission still does not gain access to the locations. Permissions do not add up to branch access.
- Managers cannot create reports. In franchise chains, report creation is reserved for higher-level roles. Managers can view and manage only what their role allows.
Both franchise limits come from the source documentation this page is modelled on. Confirm that Anthos applies the same rules — locations reserved to the main franchise owner, and no report creation for managers — before relying on them. See Still to confirm.
26Seat limits by plan
How many manager seats you can create depends on your Anthos Fidelity plan. Prices below are the plans' “from” prices on the annual tariff, as shown on the Anthos pricing page.
Launch
from $249/month
- 1 promotion
- 1 location
- Unlimited digital cards
- Unlimited push notifications
Scale
from $349/month
- 3 promotions
- 3 locations
- Unlimited digital cards
- Unlimited push notifications
Dominance
from $449/month
- 10 promotions
- 10 locations
- Unlimited digital cards
- Unlimited push notifications
Every plan starts with a 14-day free trial. What happens when you reach your seat limit is listed under Still to confirm — check there before planning team sizes around a limit.
27Watch: video walkthroughs
The source documentation leans heavily on video, so the Anthos help centre should too. Every video below is an Anthos recording to make — the cards describe what each walkthrough must cover, based on the matching written guides on this page. No third-party videos are embedded here.
Managers — the full walkthrough
The flagship video for this topic, linked from the manager seats, profile, and statistics guides: open the Managers grid, add a manager, set permissions in Edit, open a profile, and delete a seat. Mirrors sections 16, 17, 21, 20, and 24 of this page.
Quick Win: manager seats for salespeople in local stores
A short, practical cut aimed at store owners: open the manager section, add a manager with their details, connect them to a location, hand over their credentials, then view the manager's details and track their statistics. Only the opening of the source version is transcribed — it covers downloading a manager's transaction history — so the Anthos script is to be written from the coverage list here, not reconstructed from the original.
Scanner App overview — how it works
From the scanner link to the home page: open the scanner on a phone, sign in, see the app added to the home screen, open the menu with the three-line icon, and set scan behaviour in Settings (beep, show result, copy QR code, debug mode). Mirrors sections 18 and 19.
Scanner App on iOS — login, and installing on Android
Two short platform cuts. iOS: sign in via email with a manager's credentials. Android: open the scanner link in the browser and install it with Add to Home Screen, including the white-label reminder to use the link under your own domain. Mirrors section 18.
Scan and make transactions — finding a customer
Scanning a card and completing a transaction, plus the fallback every manager should know: search for the customer by name, phone number, email, or card serial number when the card isn't at hand. Mirrors section 25.
Kiosk Mode — automatic stamps and points
Turning kiosk mode on in the scanner settings, how stamps and points are credited automatically on scan, the scan delay that protects against duplicate credits, which card templates automation applies to — and the admin-only line: managers work in kiosk mode, only the main account changes its settings. Mirrors section 13.
Agency + Franchise — live demo
A longer demo recording in two parts: the franchise dashboard (visits, activity, retention, feedback, referrals, and customer profiles across branches) and a live walkthrough of agency and franchise use cases — sub-accounts, branch access, and why locations stay with the main franchise owner. Mirrors section 19.
Record every video inside the real Anthos interface, with example data only — never a live customer's details. When a video is published, replace its card above with the Anthos embed and keep the coverage list as the video's description.
28Video library: full analysis
The documentation leans on video throughout, so here is the whole video library analysed as a library — what each video is, what can actually be established about its content, and where the honest gaps are. Anthos versions of every one are what the cards in section 27 are for; no third-party video is embedded anywhere on this page.
| Video | What it covers | Analysis status |
|---|---|---|
| Managers walkthrough | The flagship managers video, reused across the manager seats, profile, and statistics pages: the grid, adding a manager, permissions, the profile, and deleting a seat. | Transcript visible only for roughly the first three minutes of 4:15. Seat counts mentioned inside it are old, video-only figures — they are not current plan facts and are flagged in section 29. |
| Quick Win #6 — manager seats for salespeople in local stores | From its own description: open the manager section, add a manager, connect them to a location, hand over their credentials, then track their details and statistics. | Mostly description only. Only the opening of the transcript is visible (about 40 seconds of 2:02), and it covers downloading a manager's transaction history; the rest is description-only, so no full script is reconstructed here. |
| Scanner App overview | How the scanner works end to end: the link, sign-in, the home page, and making transactions. | Matches the written scanner guides, which this page follows in sections 18–19. |
| Scanner App login | Signing in to the scanner with an email and password. | Short and single-purpose; the written login steps carry the same content. |
| Scanner install — iOS | Getting the scanner onto an iPhone, including home-screen install. | Platform-specific cut of the install guide. |
| Scanner install — Android | The same install on Android, via the browser's Add to Home Screen. | Platform-specific cut of the install guide. |
| Scan & make transactions + customer-search update | Completing a transaction from a scan, plus the search update: find a customer by name, phone, email, or card serial number. | The search update is the substantive part — it changes daily counter work, and it is written up in section 19. |
| Kiosk Mode | Automating stamp and point distribution: turning it on, automatic accrual on scan, scan delays, and duplicate protection. | Matches the kiosk guide; the admin-only settings line is the detail to carry into the Anthos version. |
| Agency + Franchise live demo | A longer demo with chapters, including a franchise dashboard segment (visits, activity, retention, feedback, referrals, customer profiles across branches) and a live agency/franchise walkthrough. | Chapter-level structure is established; the franchise hard limits it demonstrates are written up in section 25. |
| Push notification videos | The clips on the geo-push, automation hub, next-visit reminder, birthday congratulation, triggered auto-push, and marketing push guides. | Catalogued with their guides in section 04. Found alongside the written pages; not individually transcribed. |
| Workflow Builder video | The video companion to the automation guide in section 09. | Found, not transcribed. The written trigger and action lists carry the content. |
| Integration & API tutorials | Video companions for ActiveCampaign, webhooks, Zapier, and Pabbly, plus the support videos for live chat and AppSumo. | Found, not transcribed. The written flows in sections 10, 11, and 13 carry the content. |
| Kiosk Mode video (external link) | The kiosk walkthrough linked from the kiosk guide. | Link confirmed unavailable when checked directly. The written kiosk guide in section 19 is the source of record here. |
| Video tutorials folder | The wider tutorials collection linked from the docs tutorials page, beyond the managers/scanner set above. | Catalogued as a collection. Individual tutorials outside the topics on this page are listed here for completeness, not summarised sight-unseen. |
These videos live on Loom and similar hosts, and most expose a title and a short description — transcripts, where they exist at all, are partial: the Managers walkthrough is readable for roughly its first three minutes, Quick Win #6 for its first 40 seconds, the scanner login video for its first 35 seconds, and the Android install video has no transcript at all. So this analysis is built from what is verifiable: each video's title, its published description and chapters, whatever transcript is genuinely visible, and the written guide it accompanies. Where only a description exists, this page says so and does not invent a script. The Anthos scripts should be written from the coverage lists here and filmed in the real Anthos interface.
29Still to confirm
The following points could not be verified against the live Anthos product when this page was written. They are flagged here rather than stated as fact — confirm each one, then fold the answer into the sections above.
- At the seat limit — when a plan's seats are used up (Launch 2 · Scale 10 · Dominance 50), is creating another manager blocked with an upgrade prompt, or are extra seats available at a price?
- Deactivation vs deletion — the Managers grid has a Status column, which suggests seats can be inactive as well as deleted. Does an inactive seat still count toward the plan limit, and can it still sign in to the Scanner App?
- After deletion — do a deleted manager's past transactions remain in statistics and reports, attributed to their name?
- White-label scanner link — the source documentation says managers should always use the scanner link under the business's own domain when white label is set up, reached from the dashboard profile menu, the white-label settings, or the Managers section. Confirm the exact Anthos behaviour and link format.
- Scanner sessions — the source documentation ends scanner sessions automatically every 24 hours, with no setting to change it, and warns that sharing one login across devices interrupts the session. Confirm that Anthos sessions behave the same way.
- Kiosk mode control — the source documentation lets a manager switch kiosk mode on and work in it, but reserves kiosk settings changes to the main administrator. Confirm Anthos draws the same line.
- Password rules — minimum length or character requirements for manager passwords are not stated anywhere in the source material.
- Email already in use — what happens if you add a manager with an email that already has an Anthos account or seat?
- Workflows & API access — which Anthos plans include workflows and API access (including the MCP connection for AI assistants, webhooks, and the Zapier / Pabbly / Integrately / KonnectzIT / Albato / Make bridges), and which exact connectors sit behind the promo page's “5,000+ apps” automations claim, are not confirmed here.
- Push limits in Anthos — the per-template (3), per-location (2), and paid-plan manual-push figures come from the source documentation; confirm Anthos applies the same numbers.
- Gift card requirements — the online-store-plus-Stripe requirement, printed-QR format, and no-wallet-push limit for gift cards come from the source documentation; confirm for Anthos.
- Old video-only seat limits — not current facts — a managers walkthrough video that is over three years old mentions seat counts of up to 10 and up to 50 managers tied to the source product's own plans, with manager statistics starting on a higher tier. Those figures appear in no current plan text and are not Anthos limits; the Anthos seat numbers on this page (Launch 2 · Scale 10 · Dominance 50) come from Anthos's own pricing, in section 26.
- The 2024 franchise price — not a current fact — a 2024 live-demo video mentions a franchise price of $4,000 per year with no location limit. That is video-only, from 2024, and appears in no current plan page. Do not quote it as Anthos pricing.
- Scanner sign-in method — the written guides say sign-in is by email, but a scanner login video shows sign-in by phone number with an SMS code. Confirm which method (or both) Anthos actually offers before the scanner training is finalised.
- Videos found but not transcribed — Quick Wins #1–#5 and #7, all card-creation videos plus the coupon demo, the scanner-on-iOS video, the Workflow Builder video, the ActiveCampaign tutorial, the API/webhook and automation-platform clips, and the support clips for chat and AppSumo were located but never transcribed; the whole Video Tutorials folder was found but not opened. The linked kiosk video was confirmed unavailable at its address. No scripts have been invented for any of them — they are catalogued in sections 27–28 as “found, not transcribed”.
- Pages read only in part — the support FAQ's collapsed questions, the Shopify POS fields below the first screen, one truncated prospecting sentence, the restore-card sender note, the full Google Pay on Android page, the wallet-appearance section for Android, parts of import/export and of the per-card customer profiles (including the Reward “Transaction Cancel” area and Multipass “Subtracting Visits” past its first step), the coupon scanner FAQ's manual-refresh steps, the Add a Location FAQ, the WhatsApp bot's webhook fields (shown only in figures), the Meta Ads Pixel advanced tail, the Stamp scanner “Redeem rewards” section, and the tail of the MCP setup detail. One integration page in the source index (Vendasta) was not in the audited list and was not read. Anything resting only on these is provisional.
- Geo-push allowance — the figure of up to 10 location-based pushes per sub-account on the highest plan, with extra pushes for a fee, comes from the source documentation; confirm Anthos applies the same allowance and the same 330-foot radius.
- Workflow Builder details — the full trigger and action lists, Draft vs Working behaviour, and the card-type limits in section 09 come from the source documentation; confirm the Anthos Workflow Builder matches before training staff on specific chains.
- Integrations availability — Toast, Shopify (both routes), Altegio, ActiveCampaign, Manychat, Square, HighLevel, UChat, and WooCommerce are documented connections; confirm which are enabled on Anthos plans, and the exact Anthos field mapping for HighLevel, UChat, and WooCommerce, which the source documents at pattern level only.
- Franchise rules — the source documentation states two hard limits for franchise chains: even a manager with all permissions does not gain access to locations (only the main franchise owner has full access to all branches), and managers cannot create reports. Confirm whether both apply in Anthos before relying on them.
Contact Anthos Fidelity at +1 (813) 697-8095 or hello@anthosfidelity.com.
30Where to put this help centre
One help centre only works if people can find it in the moment they are stuck — at the till, in the app, or out in the field. Give it one permanent home and then link to that same address from everywhere else. Do not copy the page into separate places: copies go out of date, a single linked address never does.
The one address to use everywhere
Host this page on your own domain, at a short address people can say out loud and type from memory. Either of these works — pick one and use it consistently:
Publish it there as a public page — no sign-in required to read it. A customer or agent who is locked out, mid-setup, or on a new phone is exactly the person who cannot sign in first to get help.
For customers (business owners & their staff)
- Inside the Anthos dashboard: a permanent “Help” link in the left-hand menu and in the profile menu — the two places owners already look when something is unclear.
- On the promo site: “Help” in the top navigation and the footer of app.anthosfidelity.com/promo, next to Pricing — so people find answers before and after they sign up.
- In the Scanner App: a Help link on the sign-in screen and in the app menu, so till staff can open it on the same phone they scan with.
- In onboarding messages: put the address in the welcome email and the first push messages, so every new account starts with the link saved.
- At the counter: a printed QR code by the till that opens the help centre — staff scan it with the same phone they use for the Scanner App.
For field agents
- Saved on the phone: have every agent open the address once and use “Add to Home Screen”, the same way the Scanner App is installed — help then sits one tap away, next to the scanner.
- In the field kit: print the QR code and the short address on the agent's card, one-pager, and the boarding-pass / field-guide materials they already carry.
- In the agency workspace: link it from the agency dashboard alongside sub-accounts, so an agent helping a client can open the exact section — for example Manager Seats — during setup.
- In agent group chats: pin a message with the single address in the team's WhatsApp / Messenger group, so nobody circulates old screenshots or PDFs.
- Deep links for training: share links to a section, not just the home page — the address plus #add, #scanner or #permissions lands the agent on the exact guide.
Every printed QR code, email, and menu link points to the same one address. When the help centre is updated, it is updated in that one place, and everyone — customer, till staff, and field agent — immediately sees the current version in their language and theme.
Un centro de ayuda solo funciona si la gente lo encuentra en el momento en que lo necesita: en la caja, en la aplicación o en el campo. Dale un único hogar permanente y enlaza esa misma dirección desde todos los demás lugares. No copies la página en varios sitios: las copias quedan desactualizadas, una sola dirección enlazada nunca.
La única dirección para usar en todas partes
Publica esta página en tu propio dominio, con una dirección corta que se pueda decir en voz alta y recordar. Cualquiera de estas dos sirve: elige una y úsala siempre:
Publícala como página pública, sin necesidad de iniciar sesión para leerla. Un cliente o agente bloqueado, a mitad de una instalación o con un teléfono nuevo es justo la persona que no puede iniciar sesión primero para pedir ayuda.
Para clientes (dueños de negocios y su personal)
- Dentro del panel de Anthos: un enlace permanente de «Ayuda» en el menú lateral y en el menú del perfil, los dos lugares donde los dueños ya buscan cuando algo no está claro.
- En el sitio promocional: «Ayuda» en la navegación superior y en el pie de app.anthosfidelity.com/promo, junto a Precios, para que la gente encuentre respuestas antes y después de registrarse.
- En la Scanner App: un enlace de Ayuda en la pantalla de inicio de sesión y en el menú de la aplicación, para que el personal de caja lo abra en el mismo teléfono con el que escanea.
- En los mensajes de bienvenida: incluye la dirección en el correo de bienvenida y en los primeros mensajes push, para que cada cuenta nueva empiece con el enlace guardado.
- En el mostrador: un código QR impreso junto a la caja que abre el centro de ayuda; el personal lo escanea con el mismo teléfono que usa para la Scanner App.
Para agentes de campo
- Guardado en el teléfono: que cada agente abra la dirección una vez y use «Añadir a pantalla de inicio», igual que se instala la Scanner App: la ayuda queda a un toque, junto al escáner.
- En el kit de campo: imprime el código QR y la dirección corta en la tarjeta del agente, en la hoja de una página y en los materiales que ya lleva.
- En el espacio de la agencia: enlázalo desde el panel de la agencia junto a las subcuentas, para que el agente abra la sección exacta — por ejemplo, Asientos de gerente — durante la instalación con un cliente.
- En los chats del equipo: fija un mensaje con la única dirección en el grupo de WhatsApp / Messenger del equipo, para que nadie circule capturas ni PDF antiguos.
- Enlaces directos para formación: comparte enlaces a una sección, no solo a la portada: la dirección más #add, #scanner o #permissions lleva al agente a la guía exacta.
Cada código QR impreso, correo y enlace de menú apunta a la misma única dirección. Cuando el centro de ayuda se actualiza, se actualiza en ese único lugar, y todos — cliente, personal de caja y agente de campo — ven al instante la versión actual en su idioma y tema.
Uma central de ajuda só funciona se as pessoas a encontrarem no momento em que travam — no caixa, no aplicativo ou em campo. Dê a ela um único endereço permanente e ligue esse mesmo endereço a partir de todos os outros lugares. Não copie a página para vários locais: cópias ficam desatualizadas, um único endereço ligado nunca fica.
O único endereço para usar em todo lugar
Hospede esta página no seu próprio domínio, num endereço curto que dê para falar em voz alta e decorar. Qualquer um destes dois serve — escolha um e use sempre o mesmo:
Publique-a como página pública, sem precisar entrar para ler. Um cliente ou agente bloqueado, no meio de uma instalação ou com um telefone novo é exatamente quem não consegue entrar primeiro para pedir ajuda.
Para clientes (donos de negócios e suas equipes)
- Dentro do painel da Anthos: um link permanente de «Ajuda» no menu lateral e no menu do perfil — os dois lugares onde os donos já procuram quando algo não está claro.
- No site promocional: «Ajuda» na navegação superior e no rodapé de app.anthosfidelity.com/promo, ao lado de Preços — para a pessoa encontrar respostas antes e depois de se cadastrar.
- No Scanner App: um link de Ajuda na tela de entrada e no menu do aplicativo, para a equipe do caixa abrir no mesmo telefone usado para escanear.
- Nas mensagens de boas-vindas: coloque o endereço no e-mail de boas-vindas e nas primeiras mensagens push, para cada conta nova já começar com o link salvo.
- No balcão: um QR code impresso ao lado do caixa que abre a central de ajuda — a equipe escaneia com o mesmo telefone do Scanner App.
Para agentes de campo
- Salvo no telefone: cada agente abre o endereço uma vez e usa «Adicionar à tela inicial», do mesmo jeito que o Scanner App é instalado — a ajuda fica a um toque, ao lado do scanner.
- No kit de campo: imprima o QR code e o endereço curto no cartão do agente, na folha de uma página e nos materiais que ele já carrega.
- Na área da agência: ligue a central a partir do painel da agência, junto às subcontas, para o agente abrir a seção exata — por exemplo, Assentos de gerente — durante a instalação com um cliente.
- Nos grupos da equipe: fixe uma mensagem com o único endereço no grupo de WhatsApp / Messenger da equipe, para ninguém circular capturas ou PDFs antigos.
- Links diretos para treinamento: compartilhe links para uma seção, não só para a página inicial — o endereço mais #add, #scanner ou #permissions leva o agente direto ao guia exato.
Cada QR code impresso, e-mail e link de menu aponta para o mesmo único endereço. Quando a central de ajuda é atualizada, ela é atualizada nesse único lugar, e todos — cliente, equipe do caixa e agente de campo — veem na hora a versão atual, no seu idioma e tema.