Account
Support.
Start with Wren for product questions. It searches the published customer documentation and can point you to the exact guide. If the documentation does not answer the question, Wren should say that clearly instead of substituting a generic answer — that gives us either a documentation gap or a product gap to fix. Use the Get help launcher to report the gap.
Wren and problem reports
Ask Wren a concrete question such as “How do I void an unused shipping label?” or “Where do I allow Wren to use Gmail?” Product answers come from the same corpus as this Help site. Where a guide exists, Wren should include its Help link. Wren can also run authorized workspace lookups and propose supported actions, but a write that requires confirmation does not happen until you approve it.
Use Report a problem in the Get help launcher when the answer is missing, a documented control is absent, or the product behaves differently from the guide. The report includes the current page and app version automatically.
We read every message at hello@bsns.cc. Email is the right path for billing, invitation and account-recovery problems, custom domains, migration questions, or anything the in-product help cannot resolve. Include the business name or tenant subdomain so we can find the right workspace quickly.
Account recovery
If you can’t log in:
- Need a sign-in link? Use /loginand choose email sign-in link. We’ll email a one-time link valid for 15 minutes.
- Still use a password? Use /forgot-password. We’ll email a reset link.
- Lost your MFA device?Email us. We can verify your identity another way and reset MFA so you can re-enroll. There isn’t a self-serve recovery path for that today.
- Invite link expired?Ask the teammate who invited you to resend it from Settings › Team. Invite links are good for 7 days.
Bug reports
You can also browse known public issues after signing in. Public issues are sanitized summaries; reports filed from app pages stay private to your tenant admins and our team.
When something looks wrong, the most useful things to send us are:
- The URL where it happened.
- What you were trying to do.
- What actually happened.
- A screenshot if it’s a UI issue.
We have audit logs and request traces on our side, so we can usually pin down the cause from a minimal report. Don’t worry about getting the details perfect.
Feature requests
We pay attention to these. We’re happy to tell you whether something is on the roadmap, what we’re prioritizing, or why we’ve chosen not to build something. The fastest way to a yes is a request that’s tied to a specific workflow you’re trying to run — we tend to build things we can see.
Status
Live incidents and the last 30 days of resolved ones are posted at /status. For business-impacting events we also contact affected customers directly. If something looks broken across the board and isn’t reflected on the status page, email us.