Website Widget and Embedded Forms

Turn website visitors into tracked TECOBI conversations.

The TECOBI website widget gives visitors an immediate way to text, call, qualify, or apply while passing source context, lead data, and tracking events back into the operating layer.

See tracking features
One script Client-specific widget config
Multiple actions Text, call, qualify, apply
Tracked Lead, pixel, and vehicle signals
Website Widget Runtime
dealer-site.com/vehicle/123

Vehicle detail page

VehicleView pixel ready
Text Me How can I help?
Clicktecobi_widget_click
LeadwidgetSubmitted
ContextVIN · stock · lead ID

Why it matters

Website conversion should create a managed customer conversation, not just another form notification.

TECOBI connects the website action, customer message, source page, lead record, and follow-up workflow so teams can respond from context instead of chasing disconnected website submissions.

01

Most website forms create disconnected leads.

A visitor submits a form, but the follow-up often lands in a CRM queue without the page context, vehicle context, or conversation path that created the lead.

02

Customers want the fastest path to a person.

The TECOBI widget turns the website into a text-first entry point so visitors can ask a question, request help, or start a managed conversation.

03

Credit and qualification flows need less friction.

Quick qualify and full credit application flows can open from the widget or embedded forms without forcing every visitor through the same generic contact form.

04

Marketing needs better conversion signal.

TECOBI can capture lead creation, widget clicks, form submissions, vehicle page context, Facebook pixel events, and page-view signals tied back to the client.

How it works

A widget, form iframe, lead endpoint, and tracking layer working together.

01

Install the client script

The website includes the TECOBI widget script with the client ID. The loader pulls the current widget application and attaches the client ID to the runtime.

02

Load client configuration

TECOBI retrieves the client widget settings: colors, logo, button text, powered-by setting, placement, availability, soft-pull access, pixel status, and custom CSS.

03

Present the right website actions

Visitors can text the team, call the store, quick qualify when enabled, or open a full credit workflow from widget triggers or embedded form containers.

04

Pass page context into forms

The form iframe receives the current website URL so submissions can include the page the visitor came from instead of losing the source context.

05

Create or update the TECOBI lead

A website submission creates a TECOBI Widget lead when needed or updates an existing lead by phone and client, then records the inbound message.

06

Route follow-up into the operating layer

The lead can receive the configured widget auto-reply, enter text conversation workflow, trigger needs-call behavior, and become visible to queues and reporting.

Website actions

The widget can open the right customer action without sending visitors away.

The widget is designed around practical conversion paths: quick text contact, phone calls, soft-pull qualification, full credit applications, lead-specific messages, and trade workflows.

Text Me

Text-first contact form

The main widget action opens the signup/contact form and sends the visitor message into TECOBI as a customer conversation.

Call Me

Phone call option

The widget can show a call action using the lead's tracked number when present or the client's default number when the visitor is anonymous.

Quick Qualify

Soft-pull qualification

When soft pulls are enabled, visitors can submit a quick qualification flow and TECOBI can track the soft-pull submission event.

Full credit

Embedded credit application

The full credit application can be opened by trigger class or embedded directly as a longer form experience.

Simple message

Lead-specific message forms

Existing customers can be routed into a simple message workflow when a lead-specific form trigger is used.

Trade

Lead-specific trade flow

The widget runtime supports lead-specific trade form triggers so customer actions can stay tied to the existing lead.

Embedded forms

Forms can be opened from the widget or embedded directly into a page.

TECOBI exposes canonical embed containers for teams that want a form placed directly in a landing page, contact page, finance page, or campaign page.

data-tecobi-embed="signup"

Signup / contact

A standalone contact form for visitors who are ready to start a conversation.

data-tecobi-embed="quick-qualify"

Quick qualify

A soft-pull qualification form for clients with that workflow enabled.

data-tecobi-embed="full-credit-app"

Full credit application

A deeper application flow for customers ready to submit full credit information.

Tracking layer

Website actions can carry the signal marketing and sales teams need.

TECOBI tracking is built to understand the visitor action, the page that produced it, the customer record it created, and the vehicle context when the website exposes it.

Tracked

TECOBI tracking pixel

The pixel can send event name, current URL, referrer, client ID, widget status, phone, lead ID, and vehicle details.

Tracked

Vehicle-page context

When the host site exposes vehicle data, TECOBI can capture year, make, model, trim, VIN, stock number, and photo URL on VehicleView events.

Tracked

Google Analytics events

Widget clicks, option selections, and lead creation can be sent into the site's existing gtag or Universal Analytics setup.

Tracked

Facebook pixel support

Client Facebook pixel IDs can be initialized when pixel tracking is enabled, including page views as the site URL changes.

Tracked

Form submission events

Signup, simple message, quick qualify, and credit app flows can fire submission events back to TECOBI and the parent website.

Tracked

PostMessage handoff

The form iframe reports loaded, opened, submitted, lead-created, and close events back to the widget or embed parent.

Configuration

The widget can match the client brand and the conversion workflow.

Settings are managed per client, including visual styling, form behavior, pixel support, button placement, enabled state, and extra CSS for site-specific fit.

Welcome textButton textButton circle styleLogoPrimary colorText colorEmbedded background colorEmbedded text colorShow name fieldsShow email fieldShow powered by TECOBIPin left or rightSoft-pull buttonEnable or disable widgetFacebook pixel enabledExtra CSS

Lead capture and routing

Website submissions become TECOBI leads and conversation records.

When a visitor submits the widget contact form, TECOBI can create or update the lead, mark the source as the TECOBI Widget, record the inbound message, and continue the configured follow-up workflow.

01 TECOBI Widget provider attribution
02 Phone-based existing lead matching
03 Sales / Service / Parts classification
04 Web lead type
05 Assigned user support
06 Inbound message record
07 Configured widget auto-reply
08 Needs-call behavior for new leads

Developer triggers

Buttons, links, and custom page elements can open TECOBI forms directly.

The runtime listens for the same trigger convention used on this marketing site and also exposes JavaScript helpers for deeper website integrations.

tecobi-contact-us-toggletecobi-widget-toggletecobi-credit-toggletecobi-quick-qualify-toggletecobi-full-credit-togglewindow.TECOBI.openTextForm()window.TECOBI.openSoftPullForm()window.TECOBI.openFullCreditApp()window.TECOBI.openSimpleMessage(leadId)window.TECOBI.openTradeIn(leadId)window.TECOBI.closeIframe()Custom embedded form containers

See website conversion in action

Give every high-intent website visitor a faster path into TECOBI.

Book a TECOBI walkthrough and we will show how the widget, embedded forms, tracking pixels, lead routing, and profile-page form iframe work together.

Back to platform

Search TECOBI

Search the blog and site pages.

Start typing to search TECOBI content.