Knowledge BaseLeads and Customer ContactContact tools and data

Can we customize forms or connect our finance and trade-in tools?

Yes. We recommend Remora's native forms and shopper tools. They are built into your website, included in your plan, and designed to turn more visitors into conversations. If your dealership is committed to a third-party finance or trade provider, we can connect it as well.

Why we recommend our native tools

Your plan includes the full suite of conversion tools: payment-calculation inquiries, trade-in inquiries, vehicle-availability forms, custom step-by-step forms, a secure credit application, a new-vehicle builder, and digital retailing.

Native tools give you more from every inquiry:

  • They create a better user experience. Each tool carries your unique design and branding, from shopping to contact.
  • Inquiries are measured. Form submissions count as conversions in your traffic reporting, broken down by traffic source.
  • Leads go where you need them. Each form sends to the sales team, service team, campaign team, CRM, or any combination you choose.
  • One team supports it. Remora builds, updates, and troubleshoots the whole experience. A change or a fix is a single request.
  • They pass Pagespeed Insights. Native forms don't require external JavaScript, which creates better organic and agentic search visibility.

You also control what the shopper sees after submitting. We can show a confirmation message or send the shopper to a page of your choosing, such as one explaining your benefits.

Third-party finance and trade tools

When a third-party provider's application is embedded on your website, that provider controls what happens inside it: its wording, branding, account settings, and submission processing. Remora updates the website page around the tool and helps connect it, and the provider handles changes and submission problems within its application. If you are weighing a third-party tool, ask us if we have a native version first.

Request the change

Send the page, the form or tool name, the exact change, the expected destination, and a relevant screenshot. If a field or behavior requires new platform functionality, the team can review it as a development request.