Maison Consulting & Solutions, your ERP/CRM Partners

Tuesday, February 17, 2009

Rules for Making a Good Impression.

Among the seven suggestions: Respond to e-mails within 24 hours. And don't use business cards as cues to bombard new contacts with pitches.

cid:image001.png@01C96844.FD3789B0

 

Here are seven rules that will guarantee a strong first impression and a powerful, lasting one.

Rule #1: Respond within 24 Hours

During the course of researching my next book, I came across an interesting trend. The people who run the most successful companies are the most responsive. When I leave a voice message or send an e-mail these individuals get back to me immediately with information, whether they're at the office or traveling. One woman who oversees 5,000 employees makes it a policy to respond to e-mail within 24 hours. She says her responsiveness provides a model for her employees. If she responds quickly to employee questions or concerns, they in turn understand the importance of getting back to customers in a short amount of time.

Even if you don't have an immediate answer, acknowledge receiving an e-mail or voice message within 24 hours or less, and let the person know you're considering the request or taking action on it.

Rule #2: Greet People with Enthusiasm

When a customer or employee calls and you choose to answer, it implies that you have time to talk. Far too many people continue to multitask during phone conversations. Those of us on the other end of the line can sense it, especially when you give one-word answers to our questions and we hear typing in the background!

Give your customers and employees your full attention. Greet them like you're sincerely excited to hear from them. And if the time isn't right, be professional enough to set a later time to give them your full attention.

Rule #3: Make Eye Contact

In conversations with customers or employees, look them in the eye. I know you might love your Blackberry, but please refrain from checking your device during the conversation. Think about how it makes you feel when the person you're talking to continually takes her eyes off you to check out other people in the room. I'll tell you how I feel—like it's a waste of time to even finish the conversation.

Give customers and employees your full attention. It makes people feel as though their opinions and insights are valued. It will help you make a powerful and lasting impression.

Rule #4: Leave Smart Voice Messages

First of all, don't leave long, rambling messages with your phone number at the end. Keep the script concise. Leave your name, time you called, and phone number at the beginning. Repeat the phone number at the end, s-l-o-w-l-y. There's also nothing worse than a drawn out game of phone tag. It can't hurt to leave a specific time when you can be reached. Of course, if you leave a time, be there to answer the call!

Rule #5: Respect Contacts

A conference organizer recently told me attendees have started complaining about fellow participants who treat business cards they have picked up at booths as open invitations to cram in-boxes with solicitations. If someone gives you a card, it's an invitation to begin a conversation. It isn't permission to leave a constant bombardment of e-mail sales pitches under the guise of "newsletters." It's also not an invitation to send 10-MB files that explain what your business does.

Rule #6: Mind Your E-Mail

Speaking of e-mail, keep your correspondence concise. Time is limited. Use a subject line with no more than three to five words that grab your reader's attention. Give the pertinent information in the first line or two, and keep your correspondence to one or two short paragraphs (unless of course a detailed memorandum is expected). Also, don't forget to use proper punctuation and grammar. The spell-check function exists on your computer for a reason. Use it.

Rule #7: Remember Small Touches

When was the last time you received a handwritten note? I bet you remember it. I do. After a brief conversation with the chief executive officer of a well-known franchisor, I was surprised to receive an envelope in the mail with a short handwritten thank-you note along with several coupons for his product. The coupons were for small amounts, but the gesture left a big impression on me.

My insurance and financial planning adviser gets plenty of business from me because of numerous, small touches during the year. Several times a year I can expect to receive a handwritten note, a short voice message, or a copy of an article that I might find valuable given what he knows about my interests. None of these touches are accompanied by a hard sell, but I wouldn't consider bringing my business to anyone else.

Business is far too competitive to risk making a bad impression. But it's not that hard to make a positive one. Just think about the way you like to be treated as a client. Follow these seven rules to stand apart.

For more information about this article please visit http://www.businessweek.com/smallbiz/content/apr2007/sb20070425_158557.htm?campaign_id=rss_topStories

 

 

Warmest Regards,

Faisal F. Bin Zarah | فيصــل فهــد بــن زرعـــه

Marketing Manager | Samama Technologies

Tuesday, February 10, 2009

IIS 7.0 Features

IIS 7.0 New features

Wondering what the new features in IIS 7.0 going to be? Here you go! you can get a glimpse of IIS 7.0 in this article.


     IIS7 will ship with both Windows Vista and Windows Longhorn Server. It's obvious that Microsoft has put a lot of time and effort into this release and you can expect IIS7 to be the platform of choice as soon as people can get their servers upgraded. It includes a several new functionalities with very rich integration with ASP.NET.

http://dutt.backup.googlepages.com/IIS7.0.png

Feature 1: HttpModules and HttpHandlers can participate in all the requests i.e we can have a ASP.NET HttpModule for a JSP or PHP page even. Building HTTPmodules for authentication, authorization, logging, url-rewriting, auditing now will be very easy with .NET.

Feature 2: ASP.NET configuration can be integrated with IIS. IIS now uses the same web.config configuration model, which means you can have both configure ASP.NET and IIS in a single web.config file. You can now set things like default pages, IIS security, logging, etc within a web.config file and xcopy/ftp it to a server.

Feature 3: This has an integrated Admin UI tool that can manage both IIS and ASP.NET settings. Rich GUI supports settings for Membership, Roles and Profile providers. This tool also supports remote delegated admin over http -- which means you can point the rich-client admin tool at a shared host server and manage your users/roles/profile settings remotely over http.

Feature 4: It provides better request auditing and error debugging. A new functionality called "Failed Request Event Buffering" (affectionately known as "FREB") is introduced. This allows administrators to configure applications to automatically save request information anytime an error occurs during a request, or if a request takes longer than a specified amount of time to complete. This allows us to analyze what exactly happened during a request failure and what errors or exceptions have occurred. This can capture tracing messages generated within ASP.NET or within any component or class library that uses System.Diagnostics -- which makes it much easier for developers and admins to instrument and analyze what is going on with systems at runtimes.

Feature 5: It provides better configuration APIs and command-line tools. In addition to new config and admin APIs, we now have a great command-line admin story that you can use to set/modify/retrieve all configuration information as well as manage the server (start/stop individual apps, lookup their health state, register new apps, refresh SSL certs, etc). The class hierarchy in brief can be figured as:

IIS7.0_New_Features1


A code snippet uses the new .NET APIs to query IIS7 to list the active worker processes on the computer. It also lists the Requests and other details about the request like Url, Clinet IP address ..etc.

ServerManager iisManager = new ServerManager();

foreach(WorkerProcess w3wp in iisManager.WorkerProcesses) 

{

    Console.WriteLine("W3WP ({0})", w3wp.ProcessId);

    foreach (Request request in w3wp.GetRequests(0)) 

    {

        Console.WriteLine("{0} - {1},{2},{3}",

        request.Url,

        request.ClientIPAddr,

        request.TimeElapsed,

        request.TimeInState);

    }

}



Feature 7: Let us examine the new management UI. Here's what the new IIS Manager looks like:

IIS7.0_New_Features2




The first thing to notice is the new "Features View" which is shown above. While you can still use the "Content View" to show the files that make up your Web Site in the main pane of the tool, most of the time you'll be using the "Features View" to change site and application settings.

IIS7.0_New_Features3


Feature 8: "Actions" pane is a task-based pane shows you the most common tasks that are related to the currently selected object. For example, here's a close up of the "Actions" pane as it looks when the "Default Web Site" is the currently selected object.

IIS7.0_New_Features4

 

The contents of the "Actions" pane will naturally change as the selected object changes, but this pane is where you'll generally find links that lead you through most of your common admin tasks.




Feature 9: Modular Architecture


Unless you've been living under a rock somewhere for the past few years, you've heard about all the problems that IIS has had when it comes to security. In earlier versions of IIS, it was either installed or it wasn't. If IIS was installed then all the features were installed. In an attempt to minimize potential vulnerability, in IIS 6, the majority of features were disabled by default, but they still got installed. This time around Microsoft has taken the next logical step. IIS7 is almost completely modular. Take a look at the installation screen:

IIS7.0_New_Features5

Now granted, I've installed everything to play around with it all, but on a production server, you now have the flexibility to install only the features you need. That way if you don't use CGI, then you don't need to worry about some new bug that someone finds in the CGI handler. You also won't need to install a patch and reboot, because the affected code was never even installed on your server so there's nothing to patch!