Did you buy a ticket? See what happens next!

You’ve made an excellent choice for your well-being! To ensure a smooth experience, we’ve outlined a few simple steps to keep in mind after purchasing a ticket on the Stebby platform.

What to Do After Buying a Ticket? 

1. Review the Service Provider’s Information 📖

Each Service Provider has its own booking system. Before you head out, check the Service Provider’s Stebby profile. It often contains specific instructions: whether you need to book a time slot, what information to send via email, or if you can simply show up right away.

2. Get in touch and provide your ticket code 🎫 

When you buy a ticket, the money isn’t transferred to the Service Provider’s account immediately, and they won’t see your details. That’s why it’s important to make yourself known! Unless otherwise requested on the profile, send the service provider a short message including:

  • Your first and last name
  • The name of the service
  • The ticket code

💡 Where can you find the ticket code and contact information? The ticket code is displayed in a window that opens immediately after your purchase. You can also find it in the “Tickets” section of your Stebby account and in the confirmation email sent to you. You’ll find the Service Provider’s contact information on their Stebby profile, on the left-hand side.

3. Enjoy the service! 💆‍♀️🏋️‍♂️ 

The service provider will mark the ticket as used (and earn their fee) only after you’ve booked a time slot or actually received the service. Unless the service provider has provided additional instructions, you can simply show up with your purchased ticket and enjoy the service by presenting a valid ID.

⏳ Please note! Be sure to check how long your ticket is valid. Don’t leave your plans to the last minute, because both you and the service provider must redeem the ticket before it expires!

EXAMPLE of a ticket👇

🎟️ Did you buy an event ticket instead? Read HERE to find out what to do with your event ticket.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.