CRM

CRM integration

VinSolutions integration for AI-managed dealership lead response and follow-up.

TECOBI connects eligible VinSolutions sales leads to fast customer follow-up, then returns selected dealership activity to the linked CRM record. Duplicate-aware matching and configurable lead-pull and writeback controls keep the workflow connected without attempting a full system mirror.

VinSolutionsTwo-way workflowDuplicate-aware matchingSelective writeback
Explore integrations

CRM integration

VinSolutions stores need follow-up that stays tied to the right CRM record.

TECOBI connects eligible sales leads to fast customer engagement while VinSolutions remains the dealership's system of record.

01

Bring eligible sales leads into TECOBI.

Scheduled polling brings active VinSolutions sales opportunities into TECOBI with customer, source, assignment, vehicle, and trade context.

02

Match before creating another record.

TECOBI checks phone first and email second, reuses matching customer and lead records, and retains the CRM relationship for future activity.

03

Write back the activity managers need.

Human outbound messages, completed calls, appointments, hard SMS opt-outs, and selected lead updates can return to the linked CRM lead. Automated messages and individual customer replies remain in TECOBI.

Dealership salesperson using a laptop and phone to manage customer follow-up inside a showroom.
AI follow-up works best when it supports the real sales floor, not when it lives in a disconnected tool.

Connected records

Poll the lead, match the customer, and preserve the VinSolutions relationship.

TECOBI polls active sales leads, carries over customer and vehicle context, and uses phone-first matching with email fallback before creating another record.

  • Scheduled polling keeps eligible sales opportunities moving into TECOBI.
  • Duplicate-aware matching reuses the right contact and lead when possible.
  • Direction-level controls determine when lead pull and writeback are active.

Integration architecture

Keep VinSolutions and TECOBI working from the same customer story.

VinSolutions supplies eligible sales leads to TECOBI. TECOBI works the customer and returns selected dealership activity to the linked CRM lead without trying to mirror every message or field.

01

Inbound

VinSolutions lead to TECOBI

TECOBI polls eligible active sales leads, brings over customer and vehicle context, and creates or links the matching local record.

  • Customer and contact details
  • Lead source and team assignment
  • Vehicle of interest and trade-in data
02

Record matching

Reuse the right customer record

Matching checks phone first and then email, fills missing data conservatively, and preserves the CRM relationship for future activity.

  • Phone-first matching
  • Email fallback
  • Duplicate-aware contact and lead reuse
03

Writeback

Selected activity returns to VinSolutions

Human messages, completed calls, appointment events, hard SMS opt-outs, and selected lead updates return to the linked lead when writeback is enabled.

  • Human SMS and email notes
  • Completed call details
  • Appointment and consent updates

Connected data

What this integration can carry through the workflow.

  • Eligible active sales lead polling
  • Customer and lead record matching
  • Lead source and team assignment
  • Vehicle-of-interest and trade-in context
  • Human message and appointment notes
  • Completed calls and hard SMS opt-outs

Inbound lead data

What comes into TECOBI and how records are matched.

The inbound path carries enough customer, source, assignment, and vehicle context for TECOBI to begin working the opportunity while preserving the VinSolutions relationship.

Customer and lead details

  • Name, company, phone, email, and address
  • Lead source and dealership team assignment
  • Vehicle of interest and trade-in information
  • Showroom indicator and SMS opt-out status

How matching behaves

  • Matches by phone first, then email
  • Fills missing data without blindly overwriting TECOBI work
  • Reuses existing records to reduce duplicates
  • Assigns the mapped VinSolutions representative when the local lead is unassigned

Activity writeback

What TECOBI sends back to VinSolutions.

Writeback is event-based. It records the dealership actions that matter to CRM visibility without copying every internal or automated TECOBI event.

Lead and contact

Sent
VinSolutions receives

Safely matches or creates the record with contact details, address, representative, source, lead type, and hot-lead flag.

Timing

When CRM lead delivery is triggered.

Human outbound SMS

Sent
VinSolutions receives

Adds a note with the sender, time, message summary, and a link to the TECOBI conversation.

Timing

Shortly after the representative sends it.

Customer SMS replies

Not sent
VinSolutions receives

Inbound customer replies are not copied into VinSolutions as individual notes.

Timing

The conversation remains available in TECOBI.

Human outbound email

Sent
VinSolutions receives

Adds a note with the sender, time, email summary, and a link to the TECOBI conversation.

Timing

Shortly after the representative sends it.

Inbound and outbound calls

Sent
VinSolutions receives

Returns direction, result, phone numbers, timestamps, duration, recording link, and transcript when available.

Timing

After completion, with later enrichment when audio or a transcript arrives.

Appointment activity

Sent
VinSolutions receives

Adds notes for set, rescheduled, cancelled, missed, and showed events. Set and rescheduled events also apply Appointment Set status.

Timing

As each appointment event occurs.

Sold appointment status

Limited
VinSolutions receives

The appointment integration does not mark a lead sold. A separate sold-deal workflow can update the related buyer relationship when configured.

Timing

Handled through the sold-deal workflow, not appointment writeback.

Hard SMS opt-out

Sent
VinSolutions receives

Updates the matched VinSolutions contact's SMS preference and consent state.

Timing

When TECOBI records a hard opt-out.

Automated or restricted messages

Not sent
VinSolutions receives

Automated messages, blasts, call-linked messages, and internal-only or admin-only activity are excluded.

Timing

No individual CRM note is created.

Configuration

Controls that determine how the integration operates.

A dealership needs a VinSolutions dealer ID, and the overall system control plus the appropriate dealership-level direction must be enabled before data can move.

01

Dealer ID

Routes each request to the correct VinSolutions dealership and is required for both inbound lead pull and writeback.

02

Lead pull

Allows eligible VinSolutions leads to enter TECOBI. Turning it off stops inbound polling for that dealership.

03

Writeback

Allows calls, human messages, appointments, opt-outs, and selected lead updates to return to VinSolutions.

04

Auto push

Immediately creates or links eligible TECOBI-originated leads. It affects lead-delivery timing, not writeback permission.

05

Push on appointment

Can trigger CRM lead delivery when an appointment is made. Appointment-note writeback still follows the writeback control.

06

ADF/XML pass-through

Avoids API-pushing an ADF lead already delivered to the CRM, reducing the chance of duplicate records.

07

User mapping

Connects TECOBI users to VinSolutions users for correct activity credit, with a dealership or default user as fallback.

08

Eventing

A configuration control exists, but the current production workflow uses scheduled polling rather than VinSolutions event subscriptions.

VinSolutions path

Return selected dealership activity without copying every TECOBI event.

Human outbound messages, completed calls, appointment events, hard SMS opt-outs, and selected lead updates can return to the linked VinSolutions lead. Automated messages and individual customer replies are excluded.

01

Bring eligible sales leads into TECOBI.

Scheduled polling brings active VinSolutions sales opportunities into TECOBI with customer, source, assignment, vehicle, and trade context.

02

Match before creating another record.

TECOBI checks phone first and email second, reuses matching customer and lead records, and retains the CRM relationship for future activity.

03

Apply TECOBI coverage

Customer, source, team, vehicle-of-interest, and trade-in context. Phone-first matching with email fallback and duplicate-aware record reuse.

04

Route, inspect, and improve the outcome

Human outbound message notes, completed calls, appointment events, and hard SMS opt-outs. Direction-level controls, user mapping, and safeguards against duplicate opportunities.

TECOBI fit

Where TECOBI supports this workflow.

01

Customer, source, team, vehicle-of-interest, and trade-in context.

02

Phone-first matching with email fallback and duplicate-aware record reuse.

03

Human outbound message notes, completed calls, appointment events, and hard SMS opt-outs.

04

Direction-level controls, user mapping, and safeguards against duplicate opportunities.

Proof path

Prove the integration through traceable activity and clean records.

The useful proof is a linked customer and lead path, visible human activity, appointment updates, completed call context, and fewer duplicate opportunities.

Next pages

FAQ

Common questions about this workflow.

Is the VinSolutions integration available?

Production integration. Available for configured dealership accounts with the required VinSolutions dealer access and direction-level controls enabled.

What data can the VinSolutions integration carry?

Eligible active sales lead polling. Customer and lead record matching. Lead source and team assignment. Vehicle-of-interest and trade-in context. Human message and appointment notes. Completed calls and hard SMS opt-outs.

Does every TECOBI message write back through the VinSolutions integration?

Writeback is event-based. It records the dealership actions that matter to CRM visibility without copying every internal or automated TECOBI event. The integration does not send customer sms replies or automated or restricted messages as individual CRM notes. Activity is written only after TECOBI has a linked VinSolutions lead. If the link is missing, TECOBI retries briefly and then skips the activity instead of creating a new opportunity solely to hold a note.

Does TECOBI replace the dealership's existing CRM or DMS?

VinSolutions remains the dealership's CRM system of record. TECOBI returns important dealership activity, not a complete transcript or continuous field-for-field copy. Exact behavior depends on the dealership's enabled VinSolutions configuration.

Google reviews

Customer teams describe the response and follow-up experience.

Synced Google reviews add public customer voice around TECOBI support, follow-up coverage, handoffs, and day-to-day impact.

Highest-rated automotive vendor on Google

Loading reviews…

Pulling the latest Google review signal from TECOBI’s Google Business Profile.

Search TECOBI

Search the blog, customer stories, and platform pages.

Search TECOBI content by product, industry, resource, integration, article, or customer story topic.

Start typing to search TECOBI content.