Skip to main content
Use this page to submit support requests correctly and avoid back-and-forth.

​
Open the support page

  • Open Support.
  • Choose the support flow that matches your issue.

​
Request forms available in Remapdb

FormWhere to clickRequired fieldsPlan requirement
General support requestClick the button with the support email addressCategory, Subject, Description, CaptchaNone
Widget code installation helpIn Widget code installation, click Request helpWebsite URL, CaptchaNone
WordPress plugin installation helpIn WordPress plugin installation, click Request helpWebsite URL, CaptchaFeature access required
Widget complete custom styling helpIn Widget complete custom styling, click Request helpWebsite URL, CaptchaFeature access required
Custom auto-reply email domain helpIn Custom auto-reply email domain, click Request helpBusiness email address, From name, CaptchaFeature access required
For the full styling-specific guide, open Widget styling request process.
If a request form is disabled, check your plan and feature access.

​
What happens after you submit

1

Your request is validated

Remapdb validates required fields and verifies captcha before creating the request.
2

Request details are stored

The request is saved with technical context such as request metadata.
3

Attachments are linked

If you attached files in the general support form, they are linked to the request.
4

You see confirmation immediately

You see a success message that confirms your request was received.
5

Support replies by email

The team replies to your request email. Usual response time is 1 to 3 business days.

​
File attachments

  • File attachments are available in the general support request form.
  • Maximum file size is 20MB per file.
  • You can attach images by directly pasting them into the description field while you are typing, or by using the upload button in the attachments section.
  • If upload fails, submit the request without files, then include clear text details and re-send files in follow-up.

​
Information to include in your first message

  • Live page URL where the issue happens.
  • Widget ID.
  • Exact issue description: expected result and actual result.
  • Exact error text and code, if shown.
  • Screenshot or short video.
  • Time of the latest failed test and your timezone.

​
How to find details for support requests

Use this checklist when a form asks for URL, widget ID, or technical evidence.

​
Live page URL

  • Open the exact page where the issue happens.
  • Copy the full address from your browser address bar.
  • Use the published/live URL, not an editor-preview URL.

​
Widget ID

  • Open the Installation item in the main navigation.
  • In the Code tab, open 2. Install widget code.
  • Find the data-widget="..." value in the embed script. That value is your widget ID.
  • If needed, use Code installation for the full example.

​
Exact error text and code

  • Reproduce the issue once.
  • Copy the full message exactly as shown on screen.
  • If an error code is shown (for example 0032 or 9017), include the code with the message.

​
Time of latest failed test

  • Right after reproducing the issue, note the exact date and time.
  • Include your timezone (for example UTC+2).

​
Screenshots or short video

  • Capture the full page state where the issue is visible.
  • Include the browser address bar in at least one screenshot.
  • If possible, include the exact error message in the capture.

​
Vehicle combination used in test (for quoting/widget issues)

  • Note the exact selection used:
    • vehicle type
    • brand
    • model
    • generation
    • engine

​
Endpoint path and method (for API issues)

  • Include the request path (for example /api/widget/seo).
  • Include the request method (GET or POST).
  • If available, copy this from your integration logs or browser/network logs.