If an instant crypto swap case has been open for seven business days without a useful reply, send one precise follow-up in the existing official conversation. Treat seven business days as a checkpoint, not a guaranteed resolution date: confirm the dates, rebuild the evidence, ask for the current status, and avoid duplicate messages, extra payments, and impersonators.
Summary: Seven business days are not automatically seven calendar days, so count from the relevant order, claim, or official-reply date. Gather one compact case packet and request a status update through the original official channel. Follow verified instructions, but never send another deposit or trust an unsolicited private message.
This guide covers an already-open swap case, not a new pending-order diagnosis. If you have not contacted support, first collect the order details and use the official route. For a first transaction check, see the stuck crypto swap order checklist.
RevBit describes its service as a non-custodial instant crypto exchange. Your follow-up should identify the existing exchange application and provide relevant evidence, not request wallet credentials or attempt to force a blockchain transaction.
Confirm when seven business days started
Before writing that seven days have passed, identify the event relevant to your case. It may be the exchange order, your claim, or the first official support reply. Use the event named by the applicable instructions or terms, and record the date, time, and time zone when available.
Business days are working days, not a fixed seven-day timer. Weekends generally do not count, and an applicable public holiday may change the result. RevBit’s Terms state that claims on exchange applications should be submitted within seven business days to support@revbit.net, but this claim window is not a promise that every case will receive a reply or finish within seven business days.
| Item | What to record |
|---|---|
| Starting event | Order, claim, or first official-reply date |
| Business-day count | Working days, excluding weekends and applicable holidays |
| Follow-up checkpoint | Date for one status request |
| Proof | Order email, claim, ticket history, and replies |
Do: Explain the calculation briefly: “I submitted the claim on [date] and am following up after seven business days.”
Don’t: Call seven business days a guaranteed response, refund, or resolution deadline.
Reassemble one complete case packet
A follow-up works best when an agent can match it to the open case quickly. Put the essential facts in one short note because extra screenshots and speculation do not automatically strengthen a claim. Inconsistent amounts, copied wallet details, and unrelated transaction hashes can slow review.
- Copy the exact Order ID from the exchange page, confirmation email, or original support conversation.
- Copy the transaction hash, or TxID, for the payment you sent. A TxID is the blockchain record used to locate a transaction.
- State the asset pair in plain language: the asset sent and the asset expected.
- Record the sending and receiving networks. Networks are separate blockchain routes, and the same token can exist on more than one route.
- Record order creation, payment broadcast, confirmation, claim submission, and latest-reply timestamps.
- Add the existing ticket ID or the subject line of the original email thread.
- Attach only relevant screenshots or public blockchain links, and hide unrelated personal information.
- Write the exact question: current status, review status, or whether more evidence is required.
Check every character before sending. An uppercase letter, number, or network label can distinguish one order from another. Never include a seed phrase, private key, wallet password, login password, or one-time code.
For a practical boundary around sensitive information, read what not to put in a swap support ticket.
Do: Make one clean packet with the Order ID, TxID, pair, networks, timestamps, and ticket reference.
Don’t: Send wallet secrets, passwords, one-time codes, or unrelated wallet screenshots.
Follow up in the existing official channel
Use the same email thread, site chat, or support conversation whenever possible. A reply preserves the history and shows that you are asking about an open case rather than creating a new one. If the case began on the website, use the official RevBit support page and reference the existing ticket.
RevBit lists technical support at support@revbit.net. Keep the message easy to scan by including the ticket ID and Order ID, stating the business-day count, identifying the original request, and listing the key transaction facts. Ask for the current status and whether a particular document or transaction detail is missing.
Example follow-up: Hello, I am following up on case [ticket ID] for Order ID [order ID]. I submitted the claim on [date], and seven business days have elapsed based on my records. The payment TxID is [hash], the pair is [asset sent] to [asset expected], and the networks are [sending] and [receiving]. Please confirm the status and tell me whether more evidence is required. Thank you.
Remove emotional accusations, repeated explanations, and demands that cannot be verified. Save the sent message, timestamp, and any automated case number so future replies remain connected to the same record.
Do: Reply once in the established official channel and make the request easy to match.
Don’t: Open duplicate tickets merely because the first one is quiet.
Ask for status without escalating the payment
The purpose of the follow-up is to obtain a status, not to change the transaction. Ask whether the case is awaiting review, whether a specific item is missing, and what instruction you should follow next. If support gives an unclear instruction, ask for clarification in the same official thread.
Never send a second deposit, repeat the swap, or transfer additional crypto to “unlock” the first case. A new payment creates a new transaction and does not prove anything about the original order, while pressure is not proof of a legitimate request.
RevBit’s Terms say memo or destination-tag recovery may involve a fee and review of up to 14 days. That wording concerns this type of recovery and is not the standard timeline for every swap case, so do not apply it automatically to another issue.
A reply may say the case is still being reviewed, request a clearer transaction record, or ask you to confirm a detail. Respond with the missing evidence once, keeping the ticket reference visible, and quote any unanswered point if the response does not address your question.
Do: Ask for the current status and whether specific additional evidence is required.
Don’t: Send another deposit, pay an unsolicited unlock charge, or claim that a new transfer will accelerate review.
Reject unofficial Telegram and WhatsApp requests
Waiting for crypto support can create an opening for impersonators. Someone may claim to be a recovery agent, administrator, validator, or senior support representative and ask you to move the conversation to Telegram or WhatsApp. Typical requests include an unlock payment, verification transfer, wallet connection, seed phrase, private key, password, or one-time code.
Do not use a profile name, logo, or screenshot as proof that an account is official. Check the support route from the service website or documentation you already trust, then continue in the existing case. A public social-media account does not make an unsolicited direct message proof of case ownership.
If an unofficial account contacts you, stop replying, do not click its links, and record the username, message, and requested payment. Return to the original official support channel and report the impersonation attempt. If you connected a wallet or disclosed a secret, treat that as a separate security incident and consult the fake crypto exchange support scam checklist.
Do: Verify the domain, support page, and existing ticket before trusting a request.
Don’t: Send crypto for “unlock,” “verification,” or “recovery,” or share wallet secrets in a private message.
Frequently asked questions
Is seven business days the same as seven calendar days?
No. Calendar days include weekends, while business-day counting excludes non-working days and may be affected by applicable holidays.
Should I open a second ticket if there is no reply?
Usually, no. Reply to the original official thread with the existing ticket ID and Order ID, and use another route only if official support instructs you to.
Can I send more crypto to speed up a case?
No. Do not send another deposit, repeat the swap, or transfer crypto to unlock a review because the additional transaction is separate and can create another loss.
Where can I follow up besides email?
Use the same official site chat or support conversation if that is where the case began, or use RevBit’s official support route. Avoid unsolicited private messages.
What information should I include in the follow-up?
Include the Order ID, existing ticket ID, relevant TxID, asset pair, networks, important timestamps, and a short description of what remains unanswered. Never include seed phrases, private keys, passwords, or one-time codes.