Yup, very possible.
First, you need the following:
- database
- web site
- scripting language (e.g., ASP, PHP, Cold Fusion, etc.)

Write the code to access the database and setup the following sections:
- admin backend (where your guys enter and update the data)
- user/password management (where your guys enter customers and assign passwords)
- customer frontend (where the custoemrs logon and see their information)

You'll probably want some sort of messaging system where people can give you feedback about anything they don't understand and possible send an e-mail or SMS notification when their car is done. And you'll probably want to tie it into your marketing efforts and e-mail out special promotions or reminders for upcoming scheduled service (with their permission, of course!).

Of course, you have to figure out if after all this work people will actually use the system. Are most people going to be willing to dig out their username/password, go to the site, logon, and look up the information, or are they more likely to pickup the phone and call?

Think about the technical level/geek level of your customers. Are they Silicon Valley workers who spend their life online or are they tech neophytes who have trouble turning on a computer?

Many, many thanks for that! Much appreciated!

Do you know of any snippets of code where I could start to figure out how to manage this? My ideal way of doing this would be PHP/MySQL unless ASP is easier?

Many thanks again!

Steve

Sorry, I don't know PHP. The PHP Server Side Scripting forum is probably the best place to ask for that.

[edited by: LifeinAsia at 6:24 pm (utc) on Dec. 5, 2006]

I've done something similar for a car repair shop. The software they used in the office was based on an Access database.

We exported the bare minimum of data to a file, that was then ftp'd to the server where a cron would import into mysql. PHP handled the login, which was based on their license plate/last name/phone number. (which was ok, we weren't displaying any sensitive information, just the status of the car - where it was in the process, like waiting for parts etc.) Once you logged in, you saw your vehicle details, and the status.

Doing it this way meant they didn't have to do anything but use their usual software, the way they always did, which worked well, since they weren't technical. Windows scheduler did the uploads periodically, without intervention.

Hope that helps.

LisaB

I just did a quick search, and was a bit surprised that nothing obvious popped-up. So, perhaps you have an idea for something new here!

Most shops DO have some sort of in-house Windows-based system. So, why not just use a web-based system instead, and give your customers access to boot? Have you checked with the suppliers of the in-house systems to see if they have developed web-based verisons?

That said, you are a brave an unusual auto repair shop owner. I think most would be resistant to this. I have to agree with the previous poster that there's also not likely to be widespread customer acceptance. However, if nothing else, your people can use it when people call on the phone, and customer acceptance will grow over time.

I think it's always better to use existing software when you can. Perhaps this is one of those cases, though, where there is no existing software.

Keep in mind that this is just a specialized case of CRM - "customer relationship management". Do a search on that, and I guarantee you it will turn up a zillion hits. Most for expensive, Fortune-500-level solutions. But it's a ubiquitous-enough need that I'm sure there are also solutions ranging down to free PHP scripts.

If you want to do it yourself, you may well find yourself in a position to sell a solution to other shop owners.

I'm biased, but I think this is an application that sceams for a Ruby on Rails solution.

Have you checked with the suppliers of the in-house systems to see if they have developed web-based verisons?

Doubt it, none did back when we did this. We tried to put together a partnership with one of the main providers, who wouldn't even discuss it, much less consider it. (this was after we had a running version in place) This was several years back, maybe the market is more ready for it now.

While it would be nice to have a completely web-based system, linking an in-house system to a customer web interface is probably the most practical solution.

The nice thing is, if your existing in-house system uses a popular database (e.g. in the case, Access) the linking can be accomplished pretty easily, since an independant program can reach into the database and send data to the web server.

A modern approach to this would be to use a web service to receive updates. A Perl or Ruby script running on a PC with access to the database could periodically check for status changes, and send them to the web site.

Thanks for all you help!

I did indeed do a search on this and nothing really popped up!

I'd love to be able to create it myself and if anyone else has any ideas that would be great.

A lot of my customers have asked if they could have progress reports and one of the things I thought of was to have this and most customers agreed. Also it would save alot of man power by not answering calls etc. when they could just check online.

I just need some simple code to get started so I can get the Access database online with a username/password and some code that would transmit the data by php onto the web page!

Thanks again, I do really appreciate it!

Steve

Hey Steve,

Here's a couple threads to get you started:
Basics of extracting data from MySQL using PHP [webmasterworld.com]
Help developing MySQL search query [webmasterworld.com]

Also, check PHP's MySQL Functions [us3.php.net].

Once you familiarize yourself with everything, come to the PHP Forum [webmasterworld.com] and we'll see if we can get you on the right path.

See you around ;)