Support Chat
ReBattery provides the same support chat widget on public pages and inside the private app. You can open it from the round message button to contact the support team.
If you are signed in, the chat stays tied to your active account, so the team already knows your business context. If you are signed out, enter your name and email before sending your first message. Return in the same browser to see replies.
Support requests are routed directly to the ReBattery support team. Replies appear in the same in-app support thread.
Expected Response Times
Support operates during UK business hours. Most queries receive a first response within one business day. Complex issues involving transaction disputes, payment reconciliation, or compliance documentation may take up to three business days while the team gathers the necessary records.
The support chat is not an instant messenger. If your issue is time-sensitive, include the transaction reference number and a clear summary so the team can prioritise it correctly.
How to Submit a Support Request
To help the team resolve your issue quickly, include the following in your first message:
- Registered email address — the one associated with your ReBattery account
- Transaction reference number — found in the transaction workspace header
- Screenshots — of any error messages, payment dialogs, or listing issues
- Steps to reproduce — if the issue is a bug or unexpected behaviour
[!TIP] Always open support from the account that owns the transaction or listing in question. This links the thread to the correct account automatically and avoids confusion when the team looks up your records.
Escalation Path
If you have a dispute with a counterparty during a transaction, contact support as soon as possible. Do not mark collection as complete if the batteries have not physically changed hands, and do not attempt to resolve payment issues outside the platform.
Support can pause transaction advancement, review communication logs, and initiate refund or payout holds while the dispute is investigated.
For common questions and self-service fixes, see Troubleshooting and FAQs.