Support
Write to support@roomchime.com. We answer within two business days. Tell us what you were doing, what you expected and what happened. Never send a password or a phone-control link.
Signing in
- Use the same sign-in method each time. Each account has its own workspace, so a different email opens a different, empty workspace.
- "Too many attempts" means the network made many sign-in requests in a short time. Wait a minute, then try again.
- If the studio says your workspace changed, it reloads with the account you are signed in with now.
AI assistant connectors
The connector guide has the setup for each assistant, and its troubleshooting table covers sign-in loops, missing events, plan limits and revision conflicts. When you write to us, name the assistant and the prompt you used.
Billing
- Change your card, download invoices or cancel in the billing portal, opened from the studio.
- After you cancel, Plus stays active to the end of the period you paid for.
- If a payment fails, update your card in the portal. Plus continues for a short grace period while the payment is retried.
- For a billing question, include the email on your invoice, never card details.
Deleting a run
In the studio, open run history, choose the run and delete it. You can download its CSV first. Deletion cannot be undone. The event stays, so you can run it again. A live run must end before it can be deleted.
Privacy requests
To get a copy of your data, correct it or delete your whole account, write to privacy@roomchime.com from the email you sign in with. Guests can ask the host to delete a run, or write to us with the room code and the time of the room. The privacy policy explains what we keep.
Security reports
If you find a vulnerability in RoomChime, write to support@roomchime.com with "Security" in the subject. Include the steps to reproduce it and what an attacker could reach. We confirm receipt, keep you updated and credit you if you wish.
- Test only against your own account and workspace.
- Do not access other people's data, degrade the service or send automated traffic at volume.
- Give us a reasonable time to fix the issue before you share it.
Our security contact is also published at /.well-known/security.txt.