Furries PH Docs
Dashboard
Platform API docs

Workflows

Using Telegram and Discord with your account

OFF by default while release checks continue. When enabled, link your account, browse private receipts, show eligible QR codes and choose optional bot copies.

First created Last updated

interactive-botstelegramdiscordcommunicationsaccount-settings

Updated 2026-10-19 for TASK358. The new experience is OFF by default and is being prepared for release. This guide describes the supported workflow when the platform enables it. A bot appearing online, or an older notification arriving, does not establish that these features are available to your account.

The current minimum release profile keeps payment-plan features and their pay-later notification copies unavailable until the held finance feature is separately released. Ordinary supported transactions retain their existing rights. A Payment plans entry in this reference does not mean that feature is enabled.

Connect your account

  1. Sign in: Open the Furries PH account that owns your registrations and purchases. Use Rego communications settings or Partners account settings.
  2. Link the provider: Use the existing Telegram or Discord account-link control and complete that provider’s authorization. Follow the bot destination supplied by the signed-in site; a similar name or avatar does not verify a bot.
  3. Check private messaging: Return to settings and refresh. Linked and Private messaging ready describe different requirements. Supported linking connects private messaging automatically; no separate Start, Verify or Test step is required after that flow succeeds. Provider permission restrictions or an older incomplete link may still need recovery.
  4. Open a private conversation: Use a Telegram private chat or the bot’s Discord DM. Personal receipts and QR images are available only there.

Do not send passwords, verification codes, payment evidence or account recovery links to the bot. Linking uses the website and provider authorization flow. Changing a display name, sharing a server, or pasting a receipt reference does not link an account or transfer ownership.

Associate a Join waitlist entry

When the platform enables this feature, open Join waitlist entries in Partners account settings or Rego communications settings.

  1. Enter the email used for the Join entry and select Send confirmation email. The same pending response appears whether or not an eligible entry exists.
  2. Paste the emailed code into the same signed-in account within 15 minutes, then select Confirm Join entry. Never send this code to either bot.
  3. Review the associated entry. Select Withdraw, then confirm, to remove the account association. Withdrawal remains available while the switch is OFF.

This proves the entry’s ownership; it does not subscribe you to email or bot copies. Join campaign copies also require your current provider link, private messaging readiness and separate category/purpose choice. Matching an email, display name or UUID alone grants no eligibility. Anonymous Join signup remains available independently.

Changes to your Join entry or account can require you to confirm ownership again.

Requests are limited. If a result is unconfirmed, refresh and use the explicit same-request check where offered. Confirmation codes stay only in page memory and clear after submission, sign-out or an account/link change. Do not paste a code into a URL or share it in chat.

Start a private conversation

Both providers use the fph command namespace. These are the current commands; older Telegram /start, help and linking commands keep their own behavior.

TaskTelegram private chatDiscord DM
Open help/fph or /fph help/fph help
Check the connected account/fph account/fph account
Browse transaction types/fph transactions/fph transactions
Browse one type/fph transactions shop/fph transactions, then choose family
Find an owned receipt/fph find shop YOUR-REFERENCE/fph find, then choose family and enter the exact reference
View saved notification choices/fph notifications/fph notifications
Change one choice/fph notifications registration operational on/fph notifications, with category, purpose and enabled supplied together

The transaction types are standard, group, gift, dealer, shop, pos, dealer_application and bnpl. Use a receipt reference for standard registration, dealer registration or Shop search; other types use their transaction ID. If the reference cannot be used by the command, open the signed-in transaction website.

Discord slash-command availability also depends on the released command registration. Free-form Discord messages do not replace these commands. Commands in a group or server receive only directions to the private bot; they do not return your account status, amounts, transaction references or QR image.

Transaction and QR coverage

Transaction typeWhose record you can readQR in this bot experience
RegistrationsYour own registration, including a completed group/gift registration assigned to you.Admission QR only when the current canonical record permits it.
GroupsYour owned group draft and the fields your organizer/member role permits.No group-wide admission credential; each person uses their own eligible registration.
GiftsYour owned gift purchase, with buyer/recipient rights kept separate.No gift redemption secret; an assigned registration follows its own admission rules.
Dealer packagesYour authorized dealer registration projection; crew and payer details remain separate.Admission QR only when approval, confirmation and current access rules permit it.
Shop ordersYour owned buyer receipt.Ordinary order lookup only; current staff authorization still controls collection.
POS purchasesYour account-owned purchase history, including recorded corrections.No new POS QR credential.
Dealer applicationsYour own application and published decision.No admission QR from an application or approval alone.
Payment plansCurrent payer-only information when the underlying finance feature is released. This type is unavailable in the minimum release profile.No payment-plan admission or collection QR.

Read a transaction

  1. Choose a type: Select Registrations, Groups, Gifts, Dealer packages, Shop orders, POS purchases, Dealer applications or Payment plans.
  2. Choose your record: Browse up to ten cards per page. Use the available event/status filters and navigation controls to narrow the list. An empty result is not a statement about another person’s transactions.
  3. Open details: Read the current status and the sections offered for that record. These can include purchased items, amounts and fees, accepted conditions, payment schedules, payment/refund history and saved requests. Use section pages for the complete available rows and text; a short card is a preview, not an assertion that the remaining history is empty.
  4. Check current information: Use Refresh, or Open in RegoSite when offered. The website may ask you to sign in again. Website links do not contain a reusable sign-in credential.

The bot shows only the part of the record your current account may see. A group organizer, group member, gift buyer, gift recipient, dealer participant and payment-plan payer have different rights. A payment-only view may deliberately withhold the admission reference, items or QR. Blank or unavailable data is not permission to infer an amount, payment success or admission eligibility.

These new commands read records and notification settings. Payment submission, refunds, transfer, cancellation, approval, check-in and collection remain in the existing authenticated workflows. Existing finance buttons retain their separate rules.

Buttons expire after five minutes and are single-use; using one can retire other buttons in the same page. Start a fresh command or refresh if an old button no longer works. Forwarded buttons do not give the recipient access. Unlinking, changing the linked identity, changing the source record or pausing the feature can invalidate a page before its displayed expiry.

Show an eligible QR

  1. Open the current receipt privately: Choose the relevant registration, dealer package or Shop order.
  2. Choose Show QR: The bot rechecks your account and the current record. An eligible image includes its purpose, readable reference and current status.
  3. Use the stated purpose: Registration/dealer admission and Shop lookup have different rules. A Shop lookup image can exist for an unpaid, cancelled or refunded ordinary order; it does not authorize collection. Staff still validate payment, fulfilment and any current financing restriction.
  4. Use the website if unavailable: A withheld QR stays withheld. If encoding fails before an upload, an authorized receipt/link can be returned instead. An uncertain upload is not automatically sent again.

Show QR is a deliberate action. Routine notification and blast copies do not include admission or collection images. Unsupported transaction types, gift redemption secrets, payment QR and account-pairing QR do not become admission credentials through this feature.

Treat a delivered image as private: a copied admission credential may be usable by someone else. Telegram delivery uses a protected PNG document and Discord uses a PNG attachment, but provider storage, screenshots and downloads can persist. Unlinking or pausing prevents future access and sends; it cannot recall an existing chat image. Staff must always check the current canonical record.

Choose optional notification copies

Open Bot notification choices in Partners, or Telegram & Discord bots in Rego communications settings. Telegram and Discord have separate saved choices. Select Operational, Announcements or Marketing, then explicitly turn the desired category ON or OFF. Changing the purpose selector alone does not subscribe you.

CategoryWhat its label covers
RegistrationRegistration updates and confirmations
TransactionsOrders and transaction updates
FinancePayment and financial updates
ApplicationsApplication and submission decisions
RemindersUpcoming dates and reminders
SocialActivity related to your community account
PlatformPlatform service updates
AnnouncementsEvent and platform news
Account securityReviewed optional account/security notices
SupportReviewed updates to your support requests
Staff operationsUpdates for your authorized assigned work

Unselected choices are OFF. A saved ON choice is different from account eligibility: delivery also needs the released source, current linked identity, private-messaging readiness, current permission and applicable consent. A listed category is not a promise that every kind of message is released. After a link changes, Confirm for current link explicitly renews that one choice; the system does not silently transfer old consent to a new destination.

Required email, email preferences, existing reminders and established bot messages keep their own rules. A bot opt-in does not subscribe you to email or marketing. A bot opt-out does not stop required email. Asking to read your own receipt does not require marketing consent.

Copies are short summaries with a normal authenticated website link where appropriate. They do not reproduce an entire private email. Password reset and magic links, OTPs, MFA secrets, signed invitations and gift redemption secrets are not copied. Existing notification channels are not duplicated merely because a new bot-copy category has been selected.

Email-blast copies

An authorized organizer can separately choose a Telegram or Discord copy for an email blast. Receiving one still requires your current linked account, private delivery, applicable category/purpose choice and consent. An organizer cannot override your opt-out by selecting the copy checkbox.

You may receive email only, either bot only as a copy of the same selected campaign audience, or both copies alongside email. The bot text can be shorter and separately reviewed. An anonymous or email-only contact is not matched to a bot using an email address. A failed bot copy does not resend an accepted email.

If something does not work

What you seeWhat to do
New bot features are pausedUse the existing website. Linking and withdrawal of a saved ON choice remain available where state can be confirmed.
Feature availability cannot be confirmedRefresh later; the system does not assume the feature is ON.
Linked, private messaging connectingRefresh settings after the supported connection flow. If it remains pending, review provider permissions and the account-link controls.
Private messaging blockedReview whether the bot is blocked or DMs are restricted, then use the existing relink/recovery controls.
Private delivery unconfirmedAn earlier provider result was uncertain. Refresh/review the current state; do not repeatedly trigger test messages.
Saved for a previous linkVerify the intended account and explicitly confirm each desired choice for the current link.
No reply, expired button or unavailable recordStart one fresh private command or use the signed-in website. Do not submit a financial action again because a bot reply is missing.
Another account’s reference does not openUse the account that owns the record or the existing authorized delegation workflow. A reference is not proof of ownership.
Save result is uncertain or another tab changed settingsRefresh and inspect the saved choice before making another change.

For support, provide the provider, approximate time and timezone, attempted command, and sanitized displayed error. Share a receipt reference only through the authenticated support route when requested. Never include bot tokens, session links, QR images, verification codes or payment evidence in a public report.

All docs