Please add Cash on Delivery + Offline Manual Bank Payment since this software is dedicated for local businesses and this is more important for people that don't use online payments and not always have balance credit in their online wallet or online
Amelia has a no show flag, can trafft also have a No Show or No Access flag (or custom flag depending on business neeed) for clients. It can be limited so the flag can only be marked once the meeting time starts and the employee is at the location o
For businesses booking across countries and time zones, it should be easy to see, set, and use each client’s local time. Adding a client time zone throughout the platform would make scheduling far less confusing, help handle daylight saving changes correctly, and make sure clients always receive the right appointment information. What this would make possible: Show a client’s time zone in their details at a glance so teams can quickly confirm where the client is based. Store the time zone alongside other client info such as email and phone number when onboarding a new client. Edit or set the client’s time zone from the backend — especially useful when staff create or update bookings on a client’s behalf. Use the client’s own time zone for reminders and notifications so appointment messages reflect their local time, not the staff member’s time zone. Handle daylight saving time more reliably for clients in different regions, reducing the yearly confusion that comes with seasonal clock changes. Include the client time zone in the interface, API responses, and webhooks so it’s visible both inside the product and in connected systems. Add the meeting start date and time based on the customer’s time zone to API fields so external email tools, CRMs, automations, and reporting systems can send accurate confirmations and stay in sync. Why this matters: Reduces mistakes and missed appointments caused by time zone mix-ups. Removes the guesswork for teams working with clients from places like San Francisco, Amsterdam, and Sydney. Helps businesses keep communications consistent across their own tools, including custom email flows. Makes global scheduling smoother and more reliable for both staff and clients. This would be a must-have improvement for any business serving clients across multiple regions.
Custom Ordering of Employee Selection
When customers are booking, the order of location options can make or break how quickly they choose the right one. Let us control how locations appear on the booking page so the best option is easy to find—without extra scrolling or confusion. With this feature, you could: Manually reorder locations so your preferred option shows first (for example, putting Google Meet/virtual at the top and in-person options below) Create a clearer booking flow by organizing locations in a way that matches your business (by city, region, service type, or popularity) Optionally show the nearest location first based on the customer’s current location or a provided address, helping customers pick the most convenient place faster Why this matters Faster decisions for customers (especially when you have many locations) Fewer wrong-location bookings and less back-and-forth A booking experience that reflects how you actually want customers to book
Currently, the Meta Pixel integration allows us to track the following events: PageView BookingProcessStep BookingConfirmed I would like to propose adding an additional event specifically for when a gift voucher is purchased. This would be very valuable for those of us running Meta ads, as it would allow us to: Track conversions from campaigns that are aimed at selling gift vouchers. Optimize ads more efficiently using Meta’s event-based conversion tracking. Better understand the customer journey and revenue sources beyond just bookings. I believe this feature would be useful for many businesses on Trafft, since gift vouchers often represent an important revenue stream and require their own ad campaigns. Thank you for considering this feature request, and I’d be happy to provide any further details or use cases if needed.