Token gated time scheduling using NFT & Calendly.
Token protected scheduling system allows user to either monetise their time with cryptocurrency or give chance to book time only for people having specific token* in their wallet.
*The token can be anything starting with ERC20, ERC721, ERC1155 as well as something completely custom that fits specific need of the customer. Using standard interface can however make it easier for an issuer to hit public thanks to out of the box integration with markets like OpenSea etc.
A standalone system may be a valuable product itself for those who already have a brand and expertise and want to share the knowledge at a certain price, Especially for those attracted to web3 world. It may be desired in all those fields where the expertise is around the blockchain domain. It would be a pity to advice via online meetings on I.e “how to invest in a brand new NFT project and get rich” without allowing people to pay in a cryptocurrency of some form.
Additionally, it can be an appealing extension for any token released for exclusive group by a celebrity (We write more about tokens usage for celebrities here) in the past. Let’s imagine a case that a celebrity has already issued a token and holders are super happy about it. To further increase the buzz and excitement they can allow people to book exclusive meeting with them so it becomes even more luxurious. With such additional usage of the token come even higher prices of token on the market and a lot of other benefits relevant for the context.
The workflow can differ dependently on business logic. For some cases it can be possible to book time only after payment and for others it is impossible to even see a calendar when one has no token.
At 3dev.io, we recently implemented an idea of web3 integration with battle-tested Calendly, so that the whole logic of time management is somewhat handled externally. This has been achieved by not showing the calendar until someone has proved he/she has the token. Then we allowed the user to see calendar and to book the meeting. After that we also tested the case where user can be asked to pay immediately for an appointment. This is of course something that depends on the use case. We do not need it if there is no will to earn on selling one’s time and if booking functionality is restricted only to members of the same community or a DAO.
Let’s see it on example:
1. User picks a consultant and fires the process of proving he/she is in fact possessing necessary token. It is done by connecting the Metamask (or other wallet). This lets the system query on chain data of related smart contract (provided at system initial setup). From now on we are sure that the user has a token and will be able to pay for the visit.
2. We allow user to pick specific time
3. We inform the user that a meeting is all set and know is the time to pay for it with the token. In case the user has more than one of such token the system picks firs of those. User of course can skip the payment step at this point, but then his appointment will be cancelled by job that runs every 15 minutes and checks whether there is an appointment that has not been paid. This is possible by deep integration with Calendly system and by handling having a link between the Calendly event and the dying user wallet address.
The use-case described in the article shows a bridge between web3 world and real life. It can be valuable addition to existing web3 solutions or a standalone system itself creating new opportunities in all known and also those complexity new business branches.
- Crypto Trading Signals for Huobi | HitBTC Review
- How to trade Futures on FTX Exchange | OKEx vs Binance
- OKEx vs KuCoin | Celsius Alternatives | How to Buy VeChain
- ProfitFarmers Review | How to use Cornix Trading Bot
- How to buy Bitcoin Anonymously | Bitcoin Cash Wallets
- WazirX NFT Review | Bitsgap vs Pionex | Tangem Review