This page is generated from the application itself. The list of screens below is the same list the software builds its own menu from, and the sentence under each one is the sentence the screen shows the person using it. Nobody retypes any of it, so it cannot quietly fall behind what we actually ship.
It is also deliberately unflattering in places. A good number of things here are built, tested and delivered switched off, because they text or call customers and that is a decision a dealer makes, not a default we help ourselves to. Those are marked, and the last section lists them on their own.
Every screen carries one of these five labels. They mean exactly what they say — a feature that needs a paid account somewhere else, or a written permission, is never labelled as though it just works.
Three clocks run outside this software and outside us. We start all three on day one so they run while the rest of the setup happens, and the platform tells you plainly when a provider is not connected instead of reporting a message it never sent.
| What has to happen | How long it usually takes | Why it exists |
|---|---|---|
| A2P 10DLC registration (Twilio) | 1–3 weeks | Carriers block business texting to US numbers until the brand and campaign are approved. |
| RCS sender registration | 2–6 weeks | Rich messages (branded, with buttons) need a registered sender; plain texts work without it. |
| Email domain authentication (SendGrid DNS) | 1–2 days | Without the DNS records, dealership email lands in spam or is refused. |
| WhatsApp Business sender approval (Meta) | 2–4 weeks | Meta verifies the business and approves the display name before any WhatsApp message can be sent. Optional: texting works without it. |
US carriers will not deliver business text messages to a mobile number until the business behind them is registered and the campaign describing what those messages say has been approved. This is called A2P 10DLC. It applies to every vendor in this market equally, and anyone who tells you they can start texting tomorrow is either already registered under somebody else's brand or is about to have their messages filtered.
What we need from you to file it: the exact legal business name as it appears on the letter from the tax authority, the matching tax identification number, the dealership address, and a live website showing the same business name. A mismatch between the name on the tax letter and the name you type is the single most common reason a registration is rejected, and each rejection costs another one to two weeks.
What we file on your behalf: a description of what the messages are for, the wording your web forms use to ask for permission, and five real sample messages taken from what the platform actually sends. We do not invent samples. Links in messages point at your own domain, never at a public link shortener, because a shortener is an automatic rejection.
Opting out is handled for you. A customer who replies with a stop word is flagged immediately, and every sequence, campaign and automated follow-up for that number halts. That is enforced in the software, not in a policy document.
The platform has a checklist screen that owns this, and it is a checklist of proof rather than of promises: a row goes green when the platform has actually seen the thing work, not when somebody ticks a box. Connecting a provider is not proof; a real message that a provider really accepted is.
The order that works: start the texting registration on day one because it is the longest clock, import your customer book while it runs, connect your vehicle list, connect your service data, then film the short consent-recorded sample that a rep's video likeness is built from.
Until a provider is connected, the platform says so on the screen and in the logs. It does not report a send that did not happen. There is also a rehearsal mode that intercepts every message even when real keys are loaded, so a store can watch a full day of automation run before a single customer hears from it.
One gate stands in front of every automated message. A customer marked as do-not-contact is never messaged by anything, including a rep pressing send. A customer who has replied with a stop word is never texted again. Quiet hours are enforced in the customer's own time zone, and an automated message that would land at the wrong hour waits rather than going out.
Every automated message is also guarded by its own cause, once — one per repair order, one per appointment, one per alert. Running the automation twice never sends a message twice. Any reply from the customer, or a booked appointment, stops the follow-up sequence cold.
A reply to a customer who wrote to you first is treated differently from a message we start: answering someone is not the same as cold outreach, and the software knows the difference.
For stores operating where implied permission expires, there is a stricter mode that ages permission out from the last transaction instead of treating silence as consent.
This platform is new. There is no wall of logos here and no case-study percentages, because every number in this market is unaudited and ours would be too. If you want a reference, ask and you will get an honest answer about where we are.
It supplements the system you already run rather than replacing it. Activity flows back into your existing setup, so nobody has to abandon what the store is trained on.
Each dealership runs on its own installation with its own database, so your customer list is not pooled with anyone else's.
Nothing on this page is read from any store's data. It is built from the software's own source, so it describes the product, never a customer.
This is the platform's own menu, in its own order, with its own descriptions. If a screen is renamed or a new one is added, this list changes with it in the same release — the build fails otherwise.
The dialling panel on this screen is one of the features that ships switched off — see the last section.
Every text, email, call recording and voicemail for one customer in a single thread, so nobody has to guess what the last person said to them.
Ships with "Approve everything automatically" ON, so nothing changes until a play is set to ask — except that anything with a dollar amount in it now always waits for a manager.
Everything that waits on a person, in one place: lifecycle plays, a new customer's lead video, a walkaround narration (rendered in the drafter's own voice) and the offers on a repair-order page. Open a card to read exactly what goes out, then approve, edit or decline it. Every check (consent, quiet hours, "did they write in?") runs again at the moment it sends, a night approval goes in the morning on its own, anything with a dollar amount waits for a manager, and one button pauses every automatic send.
Two-way sync with an outside calendar needs you to connect that account once.
Appointments, test drives and service visits on one grid, with the confirmations and reminders that go out before each one.
The log of people standing in your store right now — who walked in, who they are with, who picked them up and what happened.
Stays empty until your vehicle list is connected.
Most of it runs on repair orders, so it needs your service data flowing in first.
It counts your own customer book, so it stays empty until your deals, repair orders or customer list arrive — and it says so in plain words when they have not.
Automated email is delivered switched off and can only be turned on by an administrator. It also needs an email provider account and a day or two of domain paperwork before anything can leave the building.
Finds the customers already in your book who are worth contacting today, and says in plain words why each one came up.
Plain if-this-then-that rules your managers write themselves, without waiting on us to build them.
What the send policy did: each call, appointment, status change or message that came in from your phone system or your CRM, and whether the automation stood down, snoozed or carried on. The rules themselves are changed on the Setup screen, under Marketing settings.
Before a link can be texted the store needs a public web address, its name in Setup and a texting account. A friend's own number is the only one ever texted, proved by a code they receive.
Each buyer's one personal link, the friends it brought in, and which of them bought — counted from your own delivered deals, never from a stage somebody typed. Any thank-you reward is set by a manager, and the only text a friend ever gets is one they asked for.
Needs your store's own social accounts connected. Two of the networks we can post to also require a platform review before they will accept posts.
Chooses which video engine each kind of video is made with, so a store can mix a premium engine for first contact with a cheaper one for routine follow-up.
Eighteen starter scripts and a plain version for each wired moment are included as drafts for a manager to approve. Nothing is sent to a customer in this version, and each rep approves every line their own face would say.
Written consent from the person being cloned is required before any likeness or voice is trained, and that is enforced in the software.
Reading a caller the status of the car in your shop works with no voice account at all. Booking live on the call, and calling people back, do not.
Local creators, the links you give them, and the exact clicks, bookings and repair orders those links produced. Fees are negotiated inside a band you set, and nothing is offered until you set a budget.
How each rep and each team is actually doing — response times, appointments kept, cars delivered — from your own records rather than anyone's estimates.
Empty until a manager enters each rep's goal for the month. A rep without one reads "no goal set" rather than a made-up number, and the alert about reps falling behind only speaks about reps who have a goal.
Two features on this screen ship switched off because they contact customers — see the last section.
The launch checklist. Every row is proof rather than a tick: it goes green when the platform has seen the thing work, and it links to the screen that owns the control.
Brings your customer book across from whichever system you run today. The export goes through a dry run first, so you see exactly what would land and what would be skipped before anything is written, and an import can be rolled back.
Where your dealer system's nightly export arrives. Deals, repair orders and customer records come in here overnight and become the rest of the platform's raw material.
The keys and accounts for every outside provider, stored encrypted, with a one-tap check that says honestly whether each one answers.
Sends the day's activity back into the system your store already lives in, matched to the right customer, so nobody has to work in two places. Repeated deliveries and re-run overnight exports are matched up so an activity lands once.
The health of your own installation — whether the background work is running, how big the database is, and when the last backup was taken.
The callback board on this screen belongs to the answering menu, which is set up on the Setup screen and published by you rather than switched on by us.
For groups: which store a user belongs to and what they may see when more than one rooftop shares an installation.
These are built, tested and delivered in the off position. Every line below is checked against the code that decides the default when this page is generated — if somebody flips one of these on by default and forgets to change this page, the build stops.
Carries the same conversation on the same thread over WhatsApp instead of a text, and answers people who message the dealership there first. It ships off because Meta has to verify the business, approve the name customers see and read each message template before anything can be sent, and because permission to message someone on WhatsApp is a separate permission from texting them. Until all of that is done every play simply keeps texting.
Rings you once, you press a key once, and it then dials your call list one number at a time so nobody ever answers to silence. It ships off because it makes outbound calls, and because leaving a recorded message needs a staffed opt-out line first.
Goes back to a buyer who turned down a warranty or protection product and offers it again at the moment it would have paid for itself. It ships off because your store has to price those products first, and because it texts a customer who already said no once.
Asks a buyer to rate the experience a set number of hours after delivery, routes a good score to your public review page and a poor one to a manager privately. It ships off because it texts customers, and because a store should choose the wording and the timing before it starts.
An outbound voice call to a customer who turned down recommended work at their last visit. It ships off and needs express written permission on file before it may be switched on at all, because it is an automated voice call.
A short text shortly after a car is checked into the shop, asking whether the owner would like a number on it. It ships off because the carrier-approved wording for it has to be filed before it may send, and because a shop visit is not an invitation to be sold to.
Lets the overnight appraisal go straight to the customer without a manager looking at it first. Because nobody has seen the car on that path, the customer is told it is an estimate: a range that becomes firm after a ten-minute look. It ships off on purpose: money leaves the building on that path, so a person signs off on every number until your store decides otherwise.
Prints and posts a physical piece to a customer through a mail provider. It ships off, needs a provider account and a budget you set, and needs postal addresses on your customer records — most imported books do not have them.
Tracks a local creator's link from the click through to the booking and the sale, and negotiates a fee inside a band you set. It ships off because a partner programme is a decision, not a default, and because you set the budget before anything is offered.
Gives each buyer one personal link. A friend who opens it types their own name and mobile, proves the number with a code, and reaches the buyer's salesperson marked as referred; when the friend buys, the rep and the managers are told. Once switched on, buyers are asked on their own — a thank-you text a few days after delivery, one at day 30 and one on each purchase anniversary — each waiting for quiet hours, a pause and any text in the last day, and never sent late. When a friend buys, a manager decides the reward on the Approvals screen (never a salesperson); approving records it as owed and texts the customer a thank-you, and the store marks it paid once it has paid it — the Referrals screen keeps each customer's total for the year. It ships off because the texts go to your customers, because the carrier-approved wording for them has to be filed first, and because any thank-you reward is money only a manager may promise.
Routes a new enquiry inside your existing routing rules to the rep who matches on area, language or the kind of vehicle. It ships off because who gets which customer is a management decision, not something software should assume.
The upgraded message format that shows your logo and tappable buttons instead of plain text. It ships off and flips on only after the carriers approve your store as a sender, which is a queue of its own. Plain texts work without it.
Short videos starring the customer's own rep and their real car, whose link will ride inside a text the store already sends. It ships off, jokes are never used at serious moments, and in this version nothing is filmed, made or attached to a text yet: the scripts, the approvals and the store's picks are ready for when it is.