Back to Help Center

PUBLIC HELP GUIDE

Support help

Know where to ask for help and what details to include for faster troubleshooting.

What it does

  • Find relevant guides before changing account data.
  • Contact support publicly without a login requirement.
  • Include safe context so the issue can be reproduced.

How to use it

  • Search for the task or error topic.
  • Check filters, permissions and connection status.
  • Send a concise description of expected versus actual behavior.

Common checks

  • Never send passwords, tokens, API keys or card details.
  • Use a safe record reference rather than private customer data.
  • Do not delete records or repeatedly pay/send messages as a diagnostic test.
On this page

Start with the Help Center

Search Help by topic, task or keyword. Results link directly to the matching guide section—for example, add lead, reminder, permissions, ROI, invoice or CSV.

Read the relevant troubleshooting section and compare it with the actual page/filters you are using. The guides describe current supported workflows, not every feature shown in an old mockup.

Contact RevenueLancer

Use the public Contact form or email support@revenuelancer.online. You do not need to log in to submit a public enquiry.

The form asks for Full name, Work email and Message. Wait for Message sent before assuming the submission was accepted. If submission fails, follow the safe feedback or use the support email.

What to include in your request

  • Affected page or module and the task you were trying to perform.
  • What you expected, what happened instead and the exact visible error text.
  • Approximate time and timezone, plus steps already tried.
  • Your role and current business context where relevant.
  • A safe record reference or redacted screenshot if needed.

Do not send sensitive information

  • No passwords, authentication codes, API keys or secret tokens.
  • No payment card details, gateway secrets or SMTP passwords.
  • Redact private customer data and unrelated records from screenshots.
  • Do not paste provider responses or credentials just because a connection failed.

Business and account context

Knowing the affected business, role and task can help distinguish permissions from a defect. Logged-in support may provide additional context, but it is not mandatory for public Contact.

Never share another member’s login to demonstrate a visibility issue. Tell support which roles see different results and which filters they used.

Product updates

Check Product Updates for published changes when a workflow looks different. Do not treat a planned feature as already available; the current app controls remain the functional source of truth.

Safe checks before contacting support

  1. Refresh once and verify the current business, search and active filters.
  2. Check role/access or record archive state if an action or record is missing.
  3. For integrations, inspect connection status and last safe error.
  4. Retry once only when it cannot create another payment, message or destructive action.
  5. If the issue remains, describe it to support; do not delete data, remove members or disconnect provider history as a generic fix.

Troubleshooting

A teammate sees something I cannot

Compare business, role, hierarchy, assignment and filters. Include these differences in the support request without sharing either person’s credentials.

I cannot submit Contact

Check the required name, valid email and message length. If rate-limited, wait before retrying; use support@revenuelancer.online if the problem persists.

Which identifier should I send?

Use a safe record reference and approximate time, avoiding private customer details or secret tokens. Explain the task and visible error first.

Need more help?

If this guide didn’t solve the issue, send us a message and include what you were trying to do.