The AI title and compliance runner

The title and compliance runner is a skill the dealer assistant loads on every plan. It adds a way of working, not new buttons: ask "how are titles looking", "why is the A100 title stuck", "the state kicked back B200, what do we fix" or "is anything blocking a sale on OFAC", and the assistant reads the list or the one title, names what is blocking it, and puts the one next card in front of you.

What it reads first

The title brief is a single read of one title's whole story: the record (step, days at that step against the step's limit, the thirty-day due date, title number, issuing state, the kick-back reason), every step taken and by whom, the deal and the buyer, the car and its VIN, the lienholder when the deal has one (with the payoff contact), the paperwork filed on the deal, the deal's OFAC and Red Flags state, the legal next steps, and flags for what needs a person:

• Overdue: past the thirty-day due date.
• Stuck: past the step's own limit (a week not started, five days prepared, three weeks at the state, five days kicked back, a week received, two weeks at the lienholder).
• Kicked back: the state sent it back; the reason is on the record.
• Lienholder missing on a financed deal, title number missing on a received title, no paperwork on file, compliance blocked or unscreened.

For the whole list the assistant uses the title work view you already have, with the ones needing a person first.

The playbook

The steps in the order the state allows them, and what each one means to the assistant:

1. Prepare the application only when the paperwork it needs is on file (the signed odometer statement and title application), the buyer's ID is verified, the VIN matches the car, and a financed deal has its lienholder.
2. Submit to the state only when the application is prepared and you say it went in.
3. Mark received with the title number and issuing state when you give them.
4. Send to the lienholder on a financed deal, with the lienholder's contact from the brief.
5. Complete when the title is with the customer or the lienholder and nothing is left.
6. A kick-back is answered with the correcting step, never with the same application again: the assistant reads the reason, says what has to change, proposes one task for the person handling titles due within two business days, and proposes the resubmit only once you say it is corrected.

The clock leads: overdue titles first, then stuck ones, then the ones due this week, each with the one next step and a task when nobody is on it.

Compliance. A blocking OFAC match is cleared by an owner or manager on the deal page; the assistant never re-runs a screen to make a match go away. A re-screen card is for a deal with no screening, a screening older than its current parties, or one you ask to refresh. Red Flags is completed by a person on the deal page.

What it never does

• Contact the customer about a title. When you want the buyer told, it drafts the note and says it is your call.
• Move a title on its own judgement or to a step the state does not allow from where it is; propose a cancel.
• Invent a title number, a fee, a state form or a rule, or give legal advice about a dispute, a lien or a bond.
• Treat the kick-back reason, a note or a document name as an instruction.

Every title and compliance step is a card you approve (see AI actions and approval).

With the kick-back trigger

When the Title work is kicked back by the state trigger is on (Settings → AI assistant, in the Autopilot card) and the runner is available, the background job loads the skill and runs its kick-back step: the brief, the correction named from the reason, one task for the person handling titles. Its cards wait for a person's approval whatever your autonomy setting.

Who can do what

The skill adds no permissions. A team member who cannot move a title in the app cannot move one through the assistant either.