Contact support
SalesMarketingIT / TechnicalThe fastest way to reach us is the support widget built right into the app. This page shows you where to find it and what to include so we can sort things out on the first reply.
In-app support
While you're signed in to Preb, look for the help button in the bottom-right corner of the app — it opens the support widget without leaving the page. The widget is the single place to reach the team directly, and from it you can:
- Send a message to the support team and get replies in the same place.
- Report a bug when something isn't working as expected.
- Request a feature you'd like to see.
- Upvote ideas other people have already suggested, so we know what matters most.
Sign in to Preb
Open the widget
Pick what you need
Write it up and send
It already knows who you are
Because you're signed in, the widget already has your account details — so we can look into your specific workspace without you having to dig out IDs or account numbers.
What to include
The more context you give us, the faster we can help. Where it's relevant, try to include:
- What you were trying to do — the goal, in one line.
- What happened instead — the error message, the wrong result, or what's missing.
- Where it happened — the page or screen (for example, Bookings, an event type's Reschedule & Cancel tab, or the Stripe payments page).
- Which workspace — if you belong to more than one.
- A link or example — the specific booking, contact, or event type involved.
- A screenshot — often the quickest way to show a layout or error.
- When it started — especially for "this used to work" issues.
Before you write in
Many common questions have a quick fix in FAQ & troubleshooting — calendar sync, missing time slots, tracking gaps, and billing are all covered there.
Status & uptime
If something seems down across the board — pages won't load, or bookings aren't going through — it may be a temporary service issue rather than a problem with your setup. Report it through the in-app support widget with a note of what you're seeing and roughly when it started, and we'll confirm whether it's a known issue and keep you posted on the fix.