Support Chat in the Private App
ReBattery provides a support chat widget inside the private app for logged-in users. You can open it from any dashboard or workspace page to send a message directly to the support team.
The chat is tied to your account, so the team already knows your business context when you write in. You do not need to repeat your company name or role unless the issue involves a different account.
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 deal 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 deal 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
- Deal reference number — found in the deal 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 deal 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 deal, 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 deal 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.