Help
Support
How to reach a human, and what to include so the first reply is useful.
There is a person on the other end of all of these. Pick whichever suits the question, and include enough detail that the first reply can be useful.
Where to reach us
info@rtlbridge.ir. Best for account and billing questions, and anything that needs a paper trail.
Discord
Quick questions, workarounds, and talking to other people using RTLBridge.
The link Settings points at; fine for anything, including partnership questions.
Troubleshooting
Check here first; most reported problems have a one-line answer.
What to include
For anything about a specific run, these five lines turn a long exchange into a single reply:
What I asked for: <the specification, or a link to the chat>
What I expected: <the behaviour you wanted>
What happened: <the error, or what the module did instead>
Configuration: <mode, output language, tools that were on>
When: <roughly when the run was, and its chat title>Tip
A share link carries all of this at once: the spec, the generated files and the simulation output, without you copying anything.
Billing questions
Include the date and the ledger entry you are asking about. If it is about a charge, your activity table has the exact line, and quoting it saves a round trip.
Deleting your account
Email us from the address on the account and say what you want removed. We will tell you what is deleted and what is retained as a financial record before anything happens.
Feature requests and bugs
Both are welcome, and specific ones are far more likely to land. "Show the port list above the code" is something we can act on; "better output" is not. If you hit a bug, saying how to reproduce it matters more than describing how bad it was.
- Say what you were doing, what you expected, and what happened.
- Include a share link if a run is involved.
- Tell us your browser if the problem is visual.