Beta access
For the current beta and preview flow, write to support@akiwaki.com with a short note on how you schedule across time zones and which browser surfaces matter most to you.
The best feedback for TimeBridge is grounded, practical, and tied to real writing moments: what you typed, where you typed it, what you expected, and what happened instead.
For the current beta and preview flow, write to support@akiwaki.com with a short note on how you schedule across time zones and which browser surfaces matter most to you.
The most useful bug report includes the exact phrase typed, the surface used, a screenshot, and the expected result. That lets us separate blockers from edge noise quickly.
Privacy questions are welcome. For anything related to permissions or connected calendars, use privacy@akiwaki.com with Privacy in the subject line.
If you want to talk partnerships, product feedback, or early user programs, use contact@akiwaki.com .
TimeBridge is strongest when feedback is tied to a real scheduling sentence and a real browser surface. This format keeps the loop focused.
Example: can we meet monday 2 pm london dubai or anytime after 2pm london is fine.
Gmail compose, LinkedIn messaging, Outlook Web, or another Chrome text surface all matter because the writing surface itself can affect behavior.
Tell us what you expected to see, what the popup did instead, and whether the issue blocks you or is just irritating.
These are the questions we expect most often while the beta and preview surfaces are still taking shape.
No. TimeBridge helps earlier in the workflow. It helps the user decide on the right time and shape the message before a booking link or calendar invite is even the right next step.
No. The user reviews the suggestion, edits if needed, and decides what to send. Automatic sending is not part of the current beta posture.
Assist helps suggest and prepare timezone-aware scheduling text. Insight builds on that by adding real availability awareness so the product can decide better times before the calendar is opened.
The intended privacy direction is minimum-permission access focused on free/busy availability rather than event titles, descriptions, guests, or attachments.