AutoLens
Reference

Questions we keep getting.

Direct answers about pricing, the Chrome extension, the AI inbox, Canadian compliance, and what is and isn’t in the build queue. Every answer opens with a one-sentence verdict so you can scan, and the body is short enough to read out loud to whoever asked.

Getting started

The basics.

  1. Short version.

    AutoLens is a CRM for independent and powersports dealers. It captures vehicle listings from your dealer site with a Chrome extension, replies to inbound leads across SMS, email, Messenger, and Instagram in under three seconds, and tracks deals through a nine-stage pipeline. One inbox, one pipeline, one extension. Built in Alberta.

  2. Three groups.

    Independent used-car lots running 5 to 200 vehicles, powersports dealers with mixed inventory (motorcycles, ATVs, side-by-sides, snowmobiles), and mid-size operators with one to three rooftops who need real BDC tooling but don't want a six-month VinSolutions implementation. If you spend Saturdays posting to Marketplace, you're who we built this for.

    See who AutoLens is built for

  3. No.

    AutoLens reads your dealer site's product pages directly — no DMS connection, no IT ticket, no website install required. The Chrome extension pulls title, price, mileage, VIN, and photos from whatever your inventory pages already expose. If you can publish a vehicle to your site, you can capture it with AutoLens.

  4. Same day.

    Sign up, install the Chrome extension, capture your first vehicle. Most dealers are running on real inventory within thirty minutes. If you want the AI inbox connected, that takes one extra step per channel — provisioning a Canadian Twilio number takes about five minutes, connecting a Facebook Page goes through the standard Meta OAuth flow.

  5. For the capture, yes.

    The Chrome extension is the capture surface and that runs on a desktop browser. Once a vehicle is captured, the rest of the workflow — replying to leads, advancing pipeline cards, marking tasks done — works on the companion mobile app for iOS and Android.

    See the mobile app scope

Pricing & billing

Money questions, plainly.

  1. Four tiers.

    Lister, the extension on its own, is $24/mo. The CRM ladder is Starter $129.99/mo, Growth $239/mo, and Pro $499/mo — all Canadian dollars, and annual billing saves two months. Pricing is published, no quote calls. Founding-dealer pricing applies during early access; we'll grandfather first-cohort dealers at general availability.

    See the full pricing breakdown

  2. Yes.

    Every CRM plan includes a 7-day free trial with full feature access at your tier. A credit card is required to start the trial — you won't be charged until day 7, and you can cancel anytime before then with no charge. Lister, the extension-only plan, is $24 from day one — no trial.

  3. No.

    Month-to-month, billed via Stripe, cancel from the customer portal at any time. No onboarding fees, no annual commitments, no early-termination charges. Twilio messaging and Meta ad spend pass through at cost — there's no markup hidden in the per-message fee.

  4. Not yet.

    Pro tier covers multi-rooftop dealers today, but it's a single-account model — every rooftop you add comes off your Pro plan. Annual billing with a discount is on the roadmap; we'd rather get the monthly experience right first. Email zainMD@autolenstudios.com if you have an unusual structure.

Capture & posting

The Chrome extension.

  1. One click per vehicle.

    Open a vehicle's product page on your website, click the AutoLens extension icon, and the title, price, mileage, VIN, and photos pull into a draft listing. Repeat for each vehicle you want to post. The extension reads the page DOM directly — no DMS plumb-in, no API, no scheduled scrape.

  2. Yes.

    Motorcycles, ATVs, side-by-sides, snowmobiles, used cars, trucks. Whatever fields your product page exposes is what the extension captures. The extension doesn't care whether the unit is a 2024 F-150 or a 2019 Sea-Doo — it reads what's there and you edit anything that needs cleanup before posting.

  3. Always.

    Every captured vehicle becomes a reviewable draft inside AutoLens. You can edit the title, override pricing, rewrite the description, swap photos, or skip the vehicle entirely. Nothing goes to Marketplace until you approve it — there is no auto-post toggle, intentionally.

  4. You.

    AutoLens prepares the listing. You stay in control of when it goes live. The extension hands the approved listing off to Facebook Marketplace's own posting flow; AutoLens never has the credentials to post on your behalf without you in the loop.

  5. Re-run the capture.

    Open the product page after the price change, click the extension, and the draft updates with the latest details. If the vehicle already went live on Marketplace, AutoLens flags the live listing as out-of-date so you can re-post or edit it. Price-drop alerts to interested leads are part of the AI workflow.

Inbox, AI & pipeline

How conversations and deals move.

  1. Four.

    SMS via Twilio (Canadian long codes), email via Postmark or SES with inbound parsing, Facebook Messenger via the Meta Graph API, and Instagram DM through the same Meta integration. WhatsApp, Google Business Messages, web chat widget, and phone are on the workstream board.

    See the line-by-line competitor comparison

  2. Under three seconds.

    When an inbound lead arrives, AutoLens loads the conversation context, the lead's profile, the vehicle of interest, and comparable in-stock units, then generates a response with Claude. Receive-to-send is targeted under three seconds. Your dealership's tone settings drive the voice — three sliders plus a free-text “about us” field.

  3. Whenever the conversation needs one.

    AutoLens auto-escalates when a lead asks for a human, starts negotiating, brings up financing or trade-ins, signals frustration, or sends an opt-out keyword. Claude classifies every inbound before generating a reply. Once a human jumps into the thread, the AI pauses for thirty minutes — and resumes with a context-aware bridge message if nobody follows up.

  4. Yes.

    Every conversation has an AI-enabled toggle and every lead has a hard AI-disabled switch. Flip either and the AI never replies to that thread again. The conversation stays in the inbox; it just becomes human-only. Useful for VIPs, sensitive accounts, or anyone who has specifically asked to talk to a person.

Privacy, compliance & security

CASL, PIPEDA, Law 25.

Canadian dealers ask these first. We treat compliance as the operating environment, not a check-box: the gate runs on every outbound message and the data model is built around it.

  1. Yes, by default.

    Every outbound message passes through a five-step gate: suppression list, consent check (express for promotional, implied for transactional), quiet hours (9am–9pm local resolved from the lead's area code), identification footer on first contact, and audit log. STOP, UNSUBSCRIBE, ARRÊT, and DÉSABONNER are honoured instantly, before the AI worker sees the message.

  2. Yes.

    Quebec dealerships get French consent capture, French opt-out keywords, and French canned replies for STOP and HELP. First-contact SMS to Quebec leads defaults to French unless an English preference is recorded. Law 25 obligations — breach notification, privacy officer, audit trail — are baked into the data model, not bolted on.

  3. Currently US (Railway), Canada planned.

    Railway's default Postgres region is US-East today. For Quebec and PIPEDA-sensitive dealers this is disclosed upfront; we're investigating Railway's Canadian region and will publish a migration date when it's locked. Vendor DPAs are documented for Anthropic, Stripe, Twilio, Meta, Railway, Vercel, Pusher, and Cloudflare.

  4. Yes — both.

    Per-lead data export returns every message, interaction, consent record, and profile field in JSON. Per-lead cascading delete removes the lead plus all associated messages, interactions, and tasks. Both are PIPEDA right-of-access and right-of-erasure endpoints. Consent change records are retained indefinitely for audit, unless the erasure request explicitly covers them.

  5. Two founders, on incident.

    Adam and Zain are the only humans with database access, and only when investigating an issue you've reported. AutoLens is multi-tenant: every row carries a dealership ID, every query is scoped to your tenant at the application layer, and Postgres row-level security is staged as defense-in-depth. Audit logs record every state change.

Mobile, integrations & roadmap

What's shipping next, and what's not.

  1. No public date.

    The mobile app is in build — iOS and Android via Expo. Early-access members get it first and get a direct line to report issues before general release. Launch scope is intentionally narrow: inbox, active pipeline, and push notifications. Inventory editing, ad management, and full reports stay on desktop until they actually feel right on a phone.

    See the mobile launch scope

  2. Yes.

    The mobile app reads from and writes to the same Postgres database as your desktop AutoLens account. There is no separate mobile data layer, no nightly sync, no "this was edited on a different device" conflicts. Pipeline drag on mobile updates the desktop kanban in real time.

  3. Focus.

    Voice AI, dynamic Facebook carousel ads, WhatsApp, Google Business Messages, and direct API integrations with AutoTrader, Cars.com, and CarGurus are on the workstream board — not in v1. We'd rather ship a focused tool that works than a sprawling one that doesn't.

    See the honest comparison against the incumbents

  4. Email-ADF today, direct API later.

    Most lead providers send ADF XML via email; AutoLens parses ADF on inbound with a per-dealership ADF inbox address. That covers AutoTrader, Cars.com, CarGurus, TrueCar, and Edmunds for dealers whose providers email cleanly. Direct API integrations are on the workstream board for providers whose ADF email isn't reliable.

Still stuck

Didn’t find your question?

Two founders read the inbox. Email us with the actual question and you’ll get a real answer back, usually the same day.