Test one enquiry from start to finish
Use fictional customer details and a typical service request. Add the vehicle, a photo and a note, then find the same record from the conversation and calendar. Ask a second person to pick up the enquiry without explaining it to them.
Check whether the team can tell a new enquiry from an agreed appointment. Review how replies are prepared, who approves them and what happens if a message fails. Do the same tasks on a phone, where staff may actually use the system.
Separate CRM needs from production tools
For a wrap or PPF shop, customer records and bookings are one part of the job. Design proofing, film inventory, cutting patterns, deposits, accounting and installer scheduling are separate requirements to verify. Do not assume the word “all-in-one” includes your version of each task.
Make three lists: what must work on day one, what can remain in an existing tool, and what would be helpful later. Ask for a demonstration of every must-have. A proposed integration is different from an integration working in your shop.
Check the website and channel setup
If your website already works well, ask whether the CRM can be used without replacing it. Confirm how enquiries will reach the team, which phone numbers and messaging channels are supported, and who is responsible for setup.
Ask what a public demo is showing. Sample records, prepared replies and test phone calls are useful demonstrations, but they do not establish that your production channels are connected. Confirm verification, consent and usage limits before going live.
Understand the complete price
Ask for the currency, billing frequency, setup fees, included users, usage charges, support scope and optional add-ons in writing. If a one-time purchase is offered, confirm what it includes and which hosting, phone, messaging, maintenance or support costs continue.
Clarify cancellation, export and ownership terms before choosing. Do not compare a base monthly fee with another tool’s total operating cost. For Mdnr, commercial scope and pricing are agreed separately before purchase; using the sample demo does not create a subscription.
Make data and handoffs part of the trial
Check who can access customer information, how staff sign in, how corrections are made, and how the team can retrieve records when someone is away. Ask for the available export and deletion process rather than assuming a button exists.
Test with fictional data until the production setup and permissions are agreed. A successful trial is one your team can explain: where the customer lives, where the car history lives, and who handles the next step.
Where Mdnr fits
Mdnr focuses on customer messages, vehicle details, photos, bookings and follow-ups for auto customization shops. Nori is the assistant inside Mdnr; your team reviews replies and confirms prices and bookings. A branded website is an optional add-on.
Use the sample portal to check that workflow, then discuss any specialist requirement before purchase. Mdnr should be judged on the tools and setup your shop actually needs.
Your quick checklist
- Can staff find the customer and every vehicle?
- Do photos, notes and conversations stay connected?
- Are draft replies and confirmed bookings clearly different?
- Does the phone workflow work for your team?
- Can you keep the website you already like?
- Which integrations are working, configured or still proposed?
- What is the full cost, including ongoing usage?
- How do access, export, support and cancellation work?