FAQ and troubleshooting

Roles

A member verified but didn't get the role. Check, in order: their wallet is linked (hub, Account panel); the rule's conditions actually match what they hold (source Held vs Staked matters); Fealty's role sits above the granted role in the Discord role list. Then have them press Verify again.

Roles disappeared after a downgrade. Working as intended: items beyond your plan's limits pause and their roles are revoked. Upgrading restores everything instantly.

Payments

I paid but nothing happened. Confirmations take a couple of minutes. If it's been longer: did you send from a wallet linked to your account? Exchange withdrawals and unlinked wallets can't match your invoice. The payment isn't lost; contact support with the transaction hash and it will be applied manually.

Can I pay from an exchange? No; withdrawals come from the exchange's address. Send to your own wallet first, link it, then pay.

Quests

The quest ended but points weren't awarded. Verification runs within about 15 minutes of expiry. If the quest shows paused, verification couldn't complete yet; the reason (usually engagement credit) is shown under the quest, and it finalizes on its own once resolved. Members also need their X connected before the quest ends.

A member expected the full points but got fewer. Each action pays on its own, so a member who only liked earns the like's points, not the quest total. The quest post lists what every action is worth and the total on offer, and My progress shows a member exactly what was counted for them and what wasn't.

Why can't I use any post for a like quest? X only exposes a post's likes to its author, so a quest (which pays everyone who liked, and therefore needs the full likers list) needs the author registered as a project X account. Retweet and comment tasks work on any post. Raffle like tasks also work on any post: a raffle only needs a yes/no per winner, which each winner's own connected X can answer.

Raffles

An entrant says the follow task failed unfairly. Follow checks run at draw time, so unfollowing after entering fails legitimately. Protected X accounts can't be checked and count as not following.

Auto quest didn't fire for a post. Retweets never fire; replies and quotes only fire if the config says so. Also check that the active-quest limit wasn't full and the account is within your plan's auto quest slots (Settings shows both).

Houses

I left a Discord server but it still shows in my dashboard. Houses are never removed automatically. Open that House's overview page and use the banner (or Leave this House at the bottom) to take it off your list. Your points and level are kept, and any Fealty activity in that server brings the House back. See Leaving a House.

How do I remove Fealty from my server? As the server owner, open Settings and use the danger zone at the bottom: type the server's name and the bot leaves; see Removing Fealty. Kicking the bot from Discord works too. Either way your data is kept for 30 days, and re-inviting the bot within them restores everything. After that the server's data is deleted; invoices and your credit stay.

How do I delete a web community? As its owner, open its Settings and use the danger zone at the bottom: type the community's name to delete it with its raffles, quests and points. This cannot be undone.

Your account

How do I delete my account? Open Account and use Delete account at the bottom. It removes your sign-ins, wallets, X and Telegram links, profile, points and alerts, and takes back Fealty's access to your Discord. Raffles and quests you created stay with their communities under "Deleted account", and so do your wins in raffles already drawn (with only the delivery wallet). If you own a web community, delete it first; if you have referral commissions waiting, they are paid out first.

Something else?

Join the Fealty Discord and ask in a ticket. Someone from the team answers, and it is usually the fastest route.

For payment issues, or if you would rather have it in writing, email support@fealty.club with your server name and the transaction hash.