Outbound Call Tracker

[berryman81]

I was wondering if anyone has a template for tracking outgoing calls using access 2010. I have seen the microsoft template for inbound calls and fourms saying to modify this, but this is beyond me.

What i am after is to monitor monthly courtesy calls to my clients and to monitor this.



Nothing fancy or special and it is only for one person to use.

Can anybody offer any advise or help?

Many Thanks

EDIT

Hey again. I dont think i have made myself clear.

Here is what i have got so far:



The bottom button i want it to be an add call button which i will record the notes from that call till next month when i will do it again.

something nice and simple

[ranman256]

Where is the data coming from?
straight from another database?, a spreadsheet?

[alansidman]

This might be helpful

http://www.databaseanswers.org/data_...ters/index.htm

[berryman81]

Where is the data coming from?
straight from another database?, a spreadsheet?

At the moment it is on a spreed sheet but where i am doing monthly calls it is getting too messy

[berryman81]

This might be helpful

http://www.databaseanswers.org/data_...ters/index.htm

Sorry that means nothing to me

[rpeare]

what alansidman gave you was a very basic design structure for a normalized call center database. Because you are tracking one person in one location (one person doing the calling I assume) you can cut some of it out but it's a good idea to plan for the worst. In essence, a flat table is not the best solution if you plan on using a relational database (like Access).

[ranman256]

If the calls are in a spreadsheet then it can be imported and managed in the db.
Import the workbook to a table and continue inputing data in the db instead of the workbook.

[berryman81]

what alansidman gave you was a very basic design structure for a normalized call center database. Because you are tracking one person in one location (one person doing the calling I assume) you can cut some of it out but it's a good idea to plan for the worst. In essence, a flat table is not the best solution if you plan on using a relational database (like Access).

Hi yes it is one person from location. I have now included a more detailed idea what im after in my orig post. Please note that i have no idea about access

[Xipooo]

Hi yes it is one person from location. I have now included a more detailed idea what im after in my orig post. Please note that i have no idea about access

Frankly, you're going to want to get WELL acquainted with it if you plan on using it for your business processes. You wouldn't move your entire bookkeeping system over to Quickbooks unless you knew how to use Quickbooks. It's the same for business data like call logs and customer lists when switching from Excel to Access. You might want to investigate the application you're moving to before fully committing your data to it. Contrary to popular belief, Access is NOT just like Excel. They are Apples and Oranges.