Car sales: keep each inspection and buyer follow-up together

1. Choose the space and the outcome

A buyer asks about service history while another books a test drive. Separate the vehicle facts from the actions so neither the documents nor the next call gets lost.

Open the app and use the space selector to choose your personal space or an authorized shared space. You can name a shared space “Car sales”. The manual workflow works in a free personal space; AI and shared work require an eligible plan and allowance. Before inviting a member, check whether they should see the information in this case.

2. Keep the context in Notebook

Open Notebook, choose New note and enter “Car C07 — inspection record”. Replace the example below with your own information. Choose the appropriate folder, or create one from the folder row. After saving, reopen the note to confirm the content was stored.

Use separate fields in the note for seller statements and verified inspection results. Do not mark the vehicle inspected just because the appointment was booked. Complete that task only when the report has arrived.

Code: C07
Model year: 2022
Odometer: 48,000 km (seller statement)
Inspection: not yet completed
Service history: requested
Next step: confirm the inspection before discussing an offer.

3. Turn the next steps into tasks

In Tasks, choose New task and name the first action “Request the service history”. Add a short description and the case name. Set a due date for a real commitment. Enable a reminder separately if you need a notification: a due time alone is not a reminder. In a shared space, choose an actual member as assignee before saving.

The other two actions in this example are “Confirm the test-drive time” and “Follow up after the inspection”. These are separate outcomes; completing one does not complete the others.

4. Ask Doneh for help when useful

Return to Home in the same space and keep the approval shield enabled. Send the relevant note text with the prompt below rather than relying on a note title alone. Review proposed titles, dates, assignees and any deletions, then approve only the changes you intend.

This step is optional and requires AI access. If using voice input, check the transcription. Do not assume Gmail, Drive or Calendar is connected; this workflow also works without those integrations.

5. Review the result and close the loop

Find “Request the service history” using task search. Use List or Kanban when reviewing several cases. Start a task when work begins and mark it done only after the outcome is reached. Add new facts or decisions back to “Car C07 — inspection record” so the next reader understands what changed.

Final check: one findable note, three non-duplicate tasks, confirmed owners and dates for commitments, and a clear next step. If saving fails, check the list before creating a second copy. Replace all fictional example data before using the workflow for real work.

Sources & further reading

1. Open the app
2. Plans and access