ARK BUSINESS INC.  /  MARKETING · SALES · OPERATIONS WINNIPEG, CANADA
ARK Sales Ltd.00:00:00

WORK / WINNIPEG DEMO

From inquiry to delivery.

The sales system behind MyRide.

THE WINNIPEG DEMO — 30 MIN

Automotive · 2026 · MyRide · Case Study

ROUTING   RESPONSE   CONSENT   HANDOFF   INTELLIGENCE

Thirty minutes, one screen recording, one database. Everything on screen is a query against a development site. Members are invented; the behaviour is the platform’s own.

The context should arrive before the customer does.

Priya

Hi — is the RAV4 still available? Mostly curious what my trade is worth.

Ron

It is. Before I quote anything on the trade — what’s the mileage and trim on yours? I can give you a real number instead of a range.

01

The inquiry

The dealership version of this story starts with a name and a phone number. Ours starts eight questions earlier.

Marketing’s job on the MyRide account was not to make the cheapest lead. It was to make a lead that could be routed. The form asks who they are and how to reach them — including the consent line, which is law, not courtesy — then cash or finance, timeline, trade-in, delivery area, what they are looking at, budget range, and the one thing that would stop them.

Eight answers is a routing record. Two answers was a hope. That decision, and the thirty percent it added to the cost per lead, is Six Thousand Dollars — the Marketing case study. This one begins the moment the record lands.

02

Intent

Four people arrive on the same afternoon. One has found the exact vehicle and wants to drive it tomorrow. One needs help choosing. One is a year away and enjoying the browsing. One wants to sell.

A conventional funnel treats all four identically and fails three of them. MyRide runs four lanes — Express, Concierge, Explore, Seller — and the lane is a property of the intent, not of the person. Complexity does not demote a lane: Priya is financing with a trade, which is the hardest transaction shape in the building, and she still gets the fast lane. Complexity changes the workflow, not the speed.

03

Routing

Who owns the next action, and what decides it? Source, vehicle, postal code, language, hours, and current load. Priya’s R3T resolves to a configured Winnipeg service zone — configuration, not a hard-coded list, because the delivery radius is a commercial decision that will change.

The failure mode this removes is the one nobody logs: a lead that belongs to everybody and therefore to nobody. Marcus booked a showroom appointment for four o’clock with no curator attached, and the system knew before a human did.

  • 16:00Marcus — showroom appointment BOOKED
  • —No curator assigned
  • —No briefing drafted
  • 08:12Escalated to the top of Today CRITICAL
04

Response

How quickly, on which channel, during what hours. The Harvard Business Review study of over a million leads found that responding inside the hour made a firm roughly seven times more likely to qualify one. That finding is why response time is a service level in the platform rather than a habit in a rep.

System response within sixty seconds. Assignment within five minutes. A named human within fifteen, during staffed hours, on the channel the person chose. After hours is handled honestly rather than by a robot pretending to be Ron.

Speed is not the whole process. But a slow response destroys the opportunity before the process gets to start.

05

Context

Every booking arrives with a briefing drafted for the person who will make the call: what the customer said, what they are trading, what the vehicle’s Truth File discloses, and what to have ready before dialling.

The briefing is drafted by an agent and approved by a human. On Priya’s drive booking the briefing state reads draft, with an action-log row beside it recording which agent proposed it and that it requires approval. The AI prepared. Ron decided.

This is the difference between calling faster and calling prepared.

06

Qualification

What matters enough to ask, and what does not. Qualification is not interrogation — most of it already happened on the form, and asking again is the fastest way to tell someone you weren’t listening.

What the call is for is the thing the form cannot capture: the reason underneath the request. Danielle’s brief is three kids under ten, hockey bags, a dog, and a cabin at Grand Beach every second weekend. No drop-down produces that sentence.

07

Appointment

What constitutes a real appointment: a named person, a time, a vehicle or a purpose, a confirmed channel, and an owner on the other end who has read the briefing. Anything short of that is a number in a report.

The distinction matters because appointment volume is the easiest metric in the building to inflate and the least connected to revenue. A desk that books forty and shows ten is worse than one that books twenty-five and shows twenty, and only one of those two facts appears in a weekly recap.

08

Confirmation

Show rate is where most of the leak in a well-run BDC actually sits. Confirmation is a workflow, not a courtesy text: an appointment that has not been confirmed on a consented channel is a risk record, and it appears in the queue with a severity computed from how close the appointment is.

09

Handoff

The sales process has seams. The customer should never feel them.

A handoff is complete when the next person knows what was promised, what was asked, and what the customer already told someone else. When Kevin phoned the shop and moved himself from Explore to Express, Ron pressed a button that does not work without a reason — the override wrote down who, when, from which lane to which, what was skipped, and why.

Without the handoff

Can I get your name? And what were you looking at today?

With it

Kevin — you found the F-150 on the lot and wanted Saturday morning. It’s held. Let’s talk about the trade before you drive out.

10

Follow-up

Follow-up is not persistence. Follow-up is a new reason to continue the conversation.

Every contact in the system carries a structured reason — an appointment, a price change, a document the customer asked for, a match against a brief. There is no free-text nudge. The Selection Set that Danielle opened and did not answer produces a why-now with a question attached, not a check-in.

11

Permission

When the business should explicitly leave someone alone.

There is exactly one function through which a message leaves this company, and it checks four things: consent exists for that channel and has not been revoked, it is inside the person’s hours, the cadence cap has not been hit, and there is a structured reason. There is no force flag.

  • 21:41Drive reminder to Priya — reason: appointment DISPATCHED
  • 21:44Sales nudge to Jasmine by SMS — no consent record for this channel BLOCKED
  • —“Just checking in” — refused before a row could be written

The third attempt has no row in the log at all. The reason was rejected as invalid before the message could become a record. A profile is not permission to pursue.

12

Transaction

What downstream result actually matters. Not the appointment, not the show — the funded, delivered transaction, and the gross profit attached to it.

A transaction file cannot reach signing without a promise checklist met by a named human, with evidence against each applicable gate. The checklist is the mechanism that stops a brand promise from dying quietly in the finance office.

13

Retention

The dealership loses the customer the day the car leaves. Sixty days after delivery, Sam’s ownership record carries an answered thirty-day check-in — the heated seats were the best money we spent — with six months, one year and a Winter Check scheduled, each one offered to the consent gate, which may refuse.

The relationship does not end at delivery. That is where the next transaction starts.

A MyRide vehicle handed over to its new owner at delivery.
MyRide delivery · Manitoba
Oren handing over keys to a customer at a MyRide delivery.
Oren · delivery
Ron completing a MyRide vehicle delivery with a customer.
Ron · delivery

The only photographs on this site. Delivery is the end of the sales system, and these are evidence that it completed — not decoration.

THE FUNNEL

—LeadsUNMEASURED
↓
—ContactedUNMEASURED
↓
—ConversationsUNMEASURED
↓
—AppointmentsUNMEASURED
↓
—ShowsUNMEASURED
↓
—TransactionsUNMEASURED

Every row reads UNMEASURED and that is the honest state. The platform is built, seeded and running on a development database; no customer transaction has been processed through it. These rows get numbers when the first hundred Winnipeg garages are live — not before, and never as a placeholder.

CALL SCORES

Three from the demo.

03:41

Context10 / 10 Listening9 / 10 Qualification8 / 10 Value9 / 10 Brand9 / 10 Advance9 / 10 Record6 / 10
Total60 / 70

Strong call. The trade details never made it onto the record, so finance will ask again.

04:12

Context9 / 10 Listening7 / 10 Qualification8 / 10 Value6 / 10 Brand9 / 10 Advance4 / 10 Record8 / 10
Total51 / 70

Good conversation. No appointment ask.

06:03

Context8 / 10 Listening9 / 10 Qualification5 / 10 Value8 / 10 Brand10 / 10 Advance7 / 10 Record9 / 10
Total56 / 70

Held the line on the range without over-promising. Never established the payoff amount.

Scores are against the seven ARK dimensions. Audio is not published — no consented recordings exist. The scores are from the demo’s scripted calls.

WHAT SURVIVED

Four things from this build are now in every ARK BDC regardless of client. One: a structured reason on every outbound contact, with “just checking in” refused by name. Two: the briefing before the dial, drafted by machine and approved by a human. Three: severity computed from the facts of a record rather than configured in a dashboard, so the queue cannot be gamed by whoever writes the filter. Four: lanes reported separately and never combined, because a person who is not buying yet is not a failed Express lead. Everything else in this case study is MyRide’s. Those four are ours.

RELATED PLAYBOOKS

RELATED

MyRide has a case study on all three division sites. Each links to the other two by name.