Simply decide how you tend to make bookings - would you want to set up a profile for a company client, or for different people within your agency. It really depends on how it works best for you, and if you want to receive reports, how you want to split down the information.
For example:
(i) profiles by agency staff member
In this case, you can see how many bookings each member of staff has made, and total value of bookings for the month.
An example, for the Fantastic Travel Group, where there are 4 members of staff at one location could be:
FTG-Karren
FTG-Siobhan
FTG-Mike
FTG-Andrea
So each member will have their own sign-in, and store their own preferences.
And you can register to receive reports, listing all the above profiles, so you can see the bookings made by each individual.
(ii) profiles by client
In this case, you can store each passenger's details, or the company's details so you can recall them and their preferences - either option is possible.
For example, company Great Ideas has 3 regular travellers, Jenny Grewcock, Richard Barnes and David Hampton - so you can either:
(a) set up profile by passenger - eg. Great-Jenny / Great-Richard / Great-David
In which case you can store the route Jenny travels frequently on, and the fact that she has a vegetarian meal etc, and recall this each time you make bookings on this profile. Or
(b) set up profile for the company - ie. GreatIdeas
In this way you won't see individual travel details, or individual preferences, but you will just have one sign-in, and one total report for this company, which may be all you require.
(iii) profile by location
If you have more than one location, you may like to have one profile for each agency office. This is possible, as a number of people can use the same profile at the same time.
For example, First for Travel in Nottingham and Leicester decide to have 2 profiles, First-Nott and First-Leic. This means that they just need one profile and sign-in for each office which is easy for each staff member to remember.
Then for reporting, they can see performance for each branch.
format of profiles
For both the user-ID and password fields a minimum of 4 and a maximum of 10 characters is required. For reasons of security it is also recommended that a combination of alphanumeric characters are used for these fields.